Construction Change Orders: How to Keep the Paper Trail Straight

A construction change order is the written record of a change to a job that is already under agreement: what is being added or removed, what it does to the price, what it does to the schedule, and whether the customer has approved it. The short answer for a residential remodeler: write the change down before the work starts, get a clear approval, leave the issued document alone afterward, and bill each approved change once, by its number.

The form itself is the easy part. The trouble comes later, when the estimate, the change orders, and the final invoice stop agreeing with each other, or when the homeowner's copy says something different from the office's.

This guide is operational advice for keeping those records straight. It is not legal advice, and it does not describe what your contract or your state requires.

What Does a Construction Change Order Record?

A change order answers six questions about one change.

• Which job and which agreement. The customer, the address, and the number of the estimate or agreement being modified.
• Which change. Its own number and date, in sequence for that job: CO-01, CO-02, and so on.
• Scope added or removed. Plain words, specific enough that someone who was not in the room could do the work from it. Removed work counts. A credit is a change.
• Price adjustment. The amount added or credited, with the agreed total before and after.
• Schedule effect. Working days added or removed. If there is no effect, write "no change" so the line is a statement and not a blank.
• Approval status. Who approved it, when, and how. Or that it is still waiting on an answer.

Commercial projects often use standard forms for this. The American Institute of Architects' instructions for its G701 Change Order form describe it as "used for implementing changes in the work agreed to by the owner, contractor, and architect." The form has the preparer enter the original contract sum, "the net change by previously authorized Change Order," the amount of the current change, and the new contract sum, plus any change in contract time.

A small remodeling company may never touch that form. The arithmetic is still worth borrowing: each change order states where the total stood before it and where it stands after.

Proposed, Approved, Performed, Billed: Four Different Things

A change moves through four states, and each one is a separate fact with its own date.

• Proposed. The change has been described, priced, and sent. Nothing has been agreed.
• Approved. The customer has agreed to that scope, price, and schedule in a form you can show later.
• Performed. The work was done.
• Billed. The amount appears on an invoice.

Records go wrong when one state stands in for another. A crew performs a change that was only proposed. A change is approved on site and the office never hears about it, so it is never billed. A proposed change gets billed because it sat in the same folder as the approved ones.

When Should You Write and Approve a Change?

The working rule is before the work on that change begins. At that moment both sides still have a decision to make. After the wall is closed, the conversation is about a bill.

The usual triggers are a customer request, a hidden condition such as rot behind the tile, a specified material that is swapped for another, and work that comes out of the scope.

For a hidden condition, pause that part of the work, photograph what you found, write the change, and ask for approval before continuing. Attaching photos to the job and capturing a signature on site are covered in what a field service mobile app should do.

Sometimes a signature is not possible in the moment. The homeowner is at work, and the crew is waiting. A reply by text or email to the specific written change is still a record. Attach it to the change order and note how the approval was given, whether on paper, by electronic signature, or by written reply. Whether a given form of approval satisfies your agreement is a question for the agreement itself. If it says how changes must be approved, follow that process.

Write the no-cost changes too. A zero-dollar change order for a swapped paint color is short, and it settles later what was agreed.

Why Should an Issued Document Stay Unchanged?

Once a document has been sent, a copy exists that you do not control. The homeowner has it in an email, a printout, or a photo on their phone.

If the office then opens its own file and corrects a price or rewrites a line, there are two documents with the same number that say different things, and no record of which came first. Nobody has to be dishonest for this to happen. The file was editable, so someone edited it.

The alternative is a small set of rules:

• A draft can change freely. Until it is sent, it is a working file.
• An issued document is locked. Keep exactly what the customer received, as it was sent.
• A correction is a revision. CO-02 Rev 1 replaces CO-02 and says what changed. The original stays on file, marked superseded. If the scope, price, or schedule moved, the revision needs its own approval.
• A cancelled change is voided, not deleted. The number stays in the sequence with a status, so a gap does not raise questions later.

The same rules apply to estimates and invoices. An invoice that went out wrong is corrected with a revised invoice or a credit, and the original stays in the file.

On paper or with a template, this comes down to habit: save a PDF at the moment you send, name it with the document number and revision, and do not overwrite it.

How Do Estimates, Change Orders, and Invoices Connect?

Think of the three as a chain. The accepted estimate or agreement sets the base amount. Each approved change order adjusts it and states the total before and after. Each invoice bills against the current agreed total and refers to the documents by number.

Charges get double-counted in a few ordinary ways:

• Billed alone, then billed again. A change is invoiced by itself when the work is done, then also included in the final invoice's revised total without subtracting the earlier invoice.
• Edited in and added on. Someone updates the original estimate file to include the change, and a change order is also issued for it. The base now contains what the change order adds.
• A revision counted beside the original. Rev 1 is added to the total next to the version it replaced.

Three habits prevent them. The base amount does not move once it is accepted. Each change order number is billed on one invoice, and the log records which one. The final invoice shows its work: the original amount, each approved change, the revised total, what has been invoiced already, and the balance.

A Fictional Example: One Kitchen, Three Changes

This example is invented for illustration. The job, the customer, and the numbers are fictional.

A remodeler takes on a kitchen under agreement A-1042 for $42,600, planned at 30 working days.

• CO-01, approved. The customer asks for a wider window over the sink. Adds reframing and the larger window: +$1,850 and +2 working days. Signed before framing starts.
• CO-02, approved. The customer decides to hire their own tile setter. Removes the backsplash tile and labor from the scope: −$1,200, no change to the schedule. Approved by email reply, attached to the document.
• CO-03, proposed. Two pendant lights over the island: +$640 and +1 working day. Sent, with no answer yet.

The agreed total is $42,600 + $1,850 − $1,200 = $43,250, at 32 working days. CO-03 is in neither number. If the customer approves it, the total becomes $43,890 and the schedule 33 days. Until then, no one runs wiring for the pendants and nothing about them appears on an invoice.

At the end of the job, two earlier invoices total $29,820, both billed against the original agreement. The final invoice reads:

• Original agreement A-1042: $42,600
• CO-01, wider window: +$1,850
• CO-02, backsplash removed: −$1,200
• Revised total: $43,250
• Less previously invoiced: −$29,820
• Balance due: $13,430

Now the double-count. Suppose the office had sent a separate $1,850 invoice for CO-01 the week the window went in. That is a reasonable way to bill. But the amount previously invoiced is then $31,670, and the balance due is $11,580. If the final invoice still subtracts only $29,820, the customer is asked to pay for the window twice.

What to Track in a Change Order Log

A change order log is one list with one row per change order, across all open jobs. A spreadsheet is enough to start. Useful columns:

• Job and agreement number
• Change order number and revision
• Date written and date sent
• Short description, marked as an addition or a removal
• Price change and schedule change
• Status: draft, sent, approved, declined, voided, or superseded
• Who approved it, when, and how
• Date the work was performed
• Invoice number it was billed on
• Running agreed total for the job

Review it once a week with three questions. Is anything performed that was never approved? Is anything approved and performed that has not been billed? Is anything sent and still unanswered? A change order waiting on a reply is a small quote, and the timing and wording in our guide to estimate follow-up apply to it.

Is a Template Enough, or Do You Need a System?

A document template and a spreadsheet log are enough when one person writes all the documents, a handful of jobs are open at once, and changes are occasional. The discipline matters more than the tool. If PDFs are saved at sending and the log is kept current, the paper trail holds.

A connected system starts to help when:

• Totals are retyped from one document into the next, and the retyping is where errors enter.
• More than one person issues documents.
• Changes are agreed in the field and reach the office days later.
• Answering "what is the agreed total on this job right now?" means opening several files.
• A sent document has already turned up different from the office copy.

In a connected system, the rules above stop depending on memory. Numbers are assigned in sequence. An issued document locks. A revision links to the version it replaces. The invoice draws its lines from approved change orders, and the log is a view of the same records, with no second file to keep in step. The accounting system still holds the financial record; the job documents feed it.

If you are weighing that step, custom software for service businesses covers the signs a spreadsheet has been outgrown, and building a software system around your service business explains why the handoffs between stages are where a build should begin.

How LoGa Approaches Job Documents

LoGa AI Systems is an Oklahoma City company that builds custom software and business systems for service businesses. Our approach to job documents follows this guide: number each document, lock it when it is issued, record later changes as revisions, and have the invoice read from what was approved.

The way we scope and sequence that work is laid out on how it works. To have your own estimate-to-invoice flow mapped, start with a free bottleneck audit.

Frequently asked questions

What should a construction change order include? The job and the agreement it modifies, its own number and date, a plain description of the scope being added or removed, the price adjustment with the agreed total before and after, the effect on the schedule, and the approval status: who approved it, when, and how. If there is no change to price or schedule, write that down too, so the line is a statement and not a blank.

Should a change order be approved before the work starts? As a working practice, yes. Before the work begins, both sides still have a decision to make. Afterward, the conversation is about a bill. When a signature is not possible in the moment, a written reply to the specific change, kept with the document, is a far better record than a memory of a conversation. What your contract or your state requires is a separate question, so read your agreement and ask an attorney if you are unsure.

How is a change order different from an invoice? A change order records an agreement to change the job: its scope, price, and schedule. An invoice requests payment. An approved change order raises or lowers the agreed total, and an invoice then bills against that total. Keeping them separate lets you see which changes were approved, which were performed, and which have been billed.

Can a change order lower the price of a job? Yes. Removing work from the scope is a change, and it is recorded the same way as an addition, with a credit in place of a charge. Writing it as a numbered change order keeps the reduction from being handled as an informal discount on the final invoice, where it is easy to forget or to apply twice.

Can I edit a change order after I send it? It is better not to. Once a change order has been sent, the customer holds a copy, and editing your file leaves two different documents with the same number. Issue a revision instead: a new version with its own revision number that says what changed, while the original stays on file marked as superseded.