Construction Change Orders: How to Document and Track Them

A change order should be a simple document: here's the change, here's the cost, here's the schedule impact, both sides sign. In practice, change orders cause more disputes than almost anything else on a project, usually because the work started before the paperwork caught up. A client asks for an upgrade during a walkthrough, the crew is already on site and it's easier to just do it, and the actual change order gets written up, if at all, after the fact, once nobody remembers the exact scope or price that was discussed.

A change order that can't be disputed later includes a few specific things, not just a price. The American Institute of Architects' own guidance on change orders lists the same core elements: a clear scope description referencing the affected drawings or specs, cost and schedule adjustments, dated supporting documentation, and signatures from the owner, contractor, and architect before it becomes part of the binding contract record. Leaving any of these out is usually where the ambiguity creeps in.

• A specific description of the change, not just "extra work," but exactly what's being added, removed, or substituted
• Reference to what it's changing from the original contract or scope
• The cost, broken down enough that it can be checked, not just a lump sum
• Any schedule impact, including whether the change delays the completion date
• Who requested the change and the date it was requested
• A signature line for both parties, with space for the date actually signed

The ideal order is request, price, written approval, then work. In the real world this breaks down constantly, a crew is already on site, a wall is already open, waiting a week for signatures costs more than the change itself. When work genuinely has to proceed before a formal change order is signed, send a written confirmation the same day summarizing the scope, price, and who approved it verbally, even if the signed document follows later. That written confirmation is what protects you if the formal paperwork gets delayed or disputed afterward.

A verbal change order, work added or altered based only on a conversation, is the single most common source of unpaid change order disputes. Many contracts actually prohibit them outright, stating that only a written, signed change order modifies the contract price or schedule, which means a contractor who performs extra work on a verbal instruction alone may have no contractual right to be paid for it, regardless of whether the client actually asked for the work. Treat any verbal request as something to confirm in writing immediately, not as a change order in itself.

A change order that just says "$2,400" invites a dispute later about what that number actually covers. Breaking the price into labor, material, and markup, even briefly, gives both sides something to check it against if a disagreement comes up, and it makes it much easier to isolate exactly what's being disputed if only part of the price is in question. This matters most on larger changes, where a vague total is far more likely to be challenged than a specific breakdown.

On a lot of projects, the client, the architect, the general contractor's PM, and sometimes even a subcontractor can all end up initiating changes in practice, even if the contract only names one of them as authorized to do so. This isn't necessarily a problem, but it helps to be clear about who can actually approve a change, as opposed to who can request or suggest one. A superintendent noticing a field condition that requires a change should raise it, but the formal approval, and the commitment to pay for it, usually needs to come from whoever holds that authority under the contract, not from whoever happened to be on site when the issue came up.

A change order that sits in someone's email inbox for two weeks, half-approved, is an easy way to lose track of what's actually been agreed to. Giving each change order a specific owner and a status, requested, priced, sent for approval, signed, rejected, keeps it from quietly stalling. This is a legitimate use of general task tracking: assigning "get Change Order #14 priced and sent to the client" as a task with an owner and a due date, separate from the change order document itself, makes it visible on someone's list instead of buried in a thread. ConstruDo's task management is built for exactly this kind of follow-up, assigning the person responsible for moving a change order to the next step and tracking it until it's actually resolved, rather than it depending on someone remembering to check back.

A running log of every change order on a project, even a simple spreadsheet, makes it possible to answer "where do we actually stand on changes" without digging through email threads. Download a blank log template as a CSV file. Illustrative example entries below are fictional and for illustration only.

The project, people, and company below are fictional and for illustration only. They do not describe a real ConstruDo customer or project.

On a small office buildout, the client asked to add two additional electrical outlets per room partway through framing. The electrician's foreman agreed verbally to proceed, and the work was done within two days. The general contractor's project manager, however, hadn't yet priced or written up the change, and the request sat undocumented while other parts of the project moved forward.

Three weeks later, during a review of outstanding paperwork, the PM caught the gap, created a written change order describing the added outlets and the labor and material cost, and sent it to the client for signature, noting that the work had already been completed at the client's verbal request.

The client signed it without objection, since the request and the completed work matched. Had a dispute come up at final payment instead, with no written record at all connecting the outlets to a client request, the contractor would have had a much weaker position to argue from, memory and the fact that the outlets exist, rather than a document showing the client specifically asked for them.