Change Orders Don't Kill Projects. Not Writing Them Down Does.

In construction, change orders are not the exception. Every project has them. The question is never whether they will happen. The question is whether anyone writes them down properly when they do.

Most contractors know this, and most still don't do it. There's always something more urgent on a live project, and the paperwork feels like it can wait until things calm down. It usually can't. Putting off the paperwork is one of the most expensive habits in this business.

---

Every Project Has Change Orders. Not Every Contractor Documents Them.

Change orders come with the work. Designs get revised, site conditions turn out differently than expected, and owners change their minds partway through. All of it is normal, and all of it generates change orders that need to be documented properly.

Small projects are not exempt. On projects between $1M and $5M, the average project generates 3.73 change orders, with some reaching 13. On $5M to $10M projects, that number climbs to 5.88. By the $10M to $50M range, the average reaches 7.93, with some projects seeing as many as 29.^[1]

The financial exposure compounds quickly. A $5M project at a 14.8% gross margin^[2] carries roughly $740,000 in expected profit. If change orders represent 10% of project value, and unbilled change orders routinely reach 10 to 20% on typical projects^[3], that is $500,000 moving through the documentation process.

How much of that was formally recorded? How much was actually recovered?

On smaller projects, nobody usually answers those questions until the job is over and it's too late to fix anything.

What 27 Change Orders Looked Like on One $16.9M Project

In 2011, Elite Construction was awarded a $16.9M federal contract for a project in Kingston, Ontario. Over the course of the work, 27 change orders were issued. Elite received $1.3M in additional payments through proper channels. The owner acknowledged the work had been done.

When the project wrapped up, Elite submitted another claim, this time for $4.2M covering delay and extra work. The Ontario Court of Appeal threw it out completely. The work itself wasn't in dispute. The problem was that Elite never issued the formal written notices the contract required, within the deadline the contract set. We'll come back to how that happened in Section 4. The number worth remembering for now is 27 change orders on a single mid-size project.^[4]

---

Change Orders Are Not All the Same

Change orders don't all call for the same response. There are four main causes, and each one needs a different kind of formal correspondence. That's why a single template can't handle the problem.

Design Deficiencies

This is the biggest category by volume, covering errors and omissions, non-compliant design, incomplete drawings, and faulty specifications. When something like this turns up on site, the contractor has to issue a formal Notice of Design Deficiency. Who ends up paying depends on the contract type, but the notice has to go out either way.

Variation

Here the owner asks for a change to the scope. This is the easiest category to deal with, because once the variation is approved in writing, getting paid is straightforward. The trouble starts when contractors do the work before they have that written approval.

Acceleration and Prolongation

This is usually the largest category by value and the hardest to document. Prolongation is when the project runs longer than the original schedule. Acceleration is when the contractor gets told, or pushed, to speed up and make back lost time. The two tend to happen together, and each needs its own paper trail: a Delay Notice and an Extension of Time claim.

Differing Site Conditions

These are conditions nobody saw coming: the soil isn't what was expected, there are buried utilities, contamination, or groundwater. The contractor can usually claim more time and money for this, but only by showing the conditions weren't reasonably foreseeable at tender. Making that case starts with a formal Differing Site Conditions Notice, filed as soon as the condition shows up.

The matrix above is meant to be used, not just read. Find your contract type and the cause of the change order, and the cell tells you what to write and who pays. On a live project you need that answer right away, not weeks later when you finally get around to looking it up.

---

Small Contractors Are Especially Exposed

Big projects have contracting teams whose whole job is keeping the paper trail in order: tracking notices, watching deadlines, and checking correspondence before it goes out. On a project under $100M, that team usually isn't there.

What happens instead is that people get the signature and move on to the next thing. Nobody is keeping a running record as the project goes, so when something goes wrong later, there's often nothing to fall back on.

It isn't negligence. The capability was just never part of how these projects are run.

Small projects basically do not think about this at all and then at the end they discover there's nothing there.

Pillarix expert interview

The numbers show the gap. On small projects, margins fall from 25.8% to 22.8%^[5] because of change orders that weren't handled well. And if a dispute does come up, going after it is expensive. Just getting an arbitration started runs $40,000 to $50,000^[6] before any lawyer has billed an hour.

Most small contractors can't take on that cost, so they let the claim go and eat the loss.

---

The Paper Trail Is Your Legal Weapon

In a dispute, a verbal agreement is worth almost nothing. What protects you is having the event written down at all. An email can do that just as well as a formal letter, the channel itself is not the issue. What matters is that the record exists, that it captures the right information, and that it goes out in time. For a delay, that means noting when the delay started, what caused it, whether you told the other side, and what was done to mitigate it, all recorded as it happens. Most notice provisions also set a deadline, often only a few days, to get that record out. Miss the deadline or leave out what matters, and an otherwise valid claim can still fail.

The Notice Window Is Not a Suggestion

The Elite Construction case put it plainly: a notice provision is a condition precedent^[4]. Miss the window and you don't just weaken your claim, you lose it, with nothing to fall back on afterward.

A second Ontario case reinforces the point. In Urban Mechanical v. University of Western Ontario (2018 ONSC 1888)^[7], a subcontractor failed to issue a written dispute notice within 7 business days of the GC's decision. The court ruled this constituted automatic acceptance of the GC's position. All related claims were waived.

The pattern across North American case law is consistent:

The specific triggers move around over the years. Supply chain problems jumped during the pandemic and then dropped off, and owner-directed changes have only climbed recently. The contract-management failures, though, never leave the top of the list. It isn't that the industry doesn't care about them. They're just hard to fix without a dedicated team, which is the gap this whole article is about.^[8]

Post-Project Remediation Does Not Work

A lot of contractors bring in an outside consultant once a dispute is looming. The problem is that it's usually too late. If the documentation wasn't kept up during the project, there's very little for the consultant to build on. Some things can be reconstructed after the fact, but most of the deadlines have passed and most of the evidence isn't there. And the consultant's fees, which could have been folded into the claim and recovered, just become another cost instead.

---

Act During the Project. Not After.

There are three reasons this cannot wait until project completion.

Notice windows are hard deadlines. Contracts set a notice window, often 10 business days. Elite Construction shows what happens when you miss it: $4.2M gone, with the work itself never in question, simply because the formal notices weren't issued when each change order came up. Once that window closes, there's no way back.

Good documentation keeps you out of a dispute in the first place. When change orders are documented properly as the project runs, most of them just get reimbursed, with no dispute at all. The alternative is spending 15 months in arbitration to get back money that was yours from the start.

You can't recreate the evidence later. Once the project is over, documents are harder to track down, people remember things differently, and a lot of the deadlines have already passed. The chance to put together a claim you can actually recover on closes while the project is still going.

---

What AI Does Here

You don't necessarily need a dedicated contracting team. What you need is a tool that takes each change order, the moment it happens, and turns it into properly formatted, properly worded documentation, written for the right contract type with the right notice timing. The point is to get it written down when it happens, instead of after.

The agent does the same work a contract specialist would, just faster. When a change order comes up, it works out the cause, matches it to the right contract framework, and drafts the correspondence that situation calls for, in the correct format and with the notice timing the contract requires. A design deficiency under a stipulated-price contract needs a different letter than the same deficiency under design-build, and the agent handles that distinction.

It doesn't send anything by itself. The draft goes to your team, who review it, make changes, and decide what actually goes out. The agent does the heavy lifting of getting a correct, complete draft onto the page, and the people who deal with the client make the final call. A small team that could never keep up with all this documentation by hand can now stay ahead of it.

In testing on real change order correspondence, this changed the economics of the work itself:

~90%

faster than manual drafting. A letter that takes 10 to 20 hours by hand drops to about an hour.

~95%

fewer letters going out with missing information, measured against a manual baseline.

~8x

return on investment on a typical engagement.

Speed and cost both matter, but completeness is what wins or loses a claim. A letter that goes out on time but leaves out a required detail fails just like a late one would. The agent's job is to get every notice right the first time, while your team stays in control of what actually gets sent.