Change Orders in Construction: How to Manage Them Without a Fight, With a Request Builder You Can Copy

Picture a Thursday afternoon on a building site. The owner walks through the half-finished lobby, looks at a window and says, with great enthusiasm and no malice at all, "What if this were a little bigger?"

It is the cheapest-sounding sentence in the history of construction. Nobody gasps. The superintendent nods. The owner leaves happy. Six weeks later, an invoice arrives for $11,400, the steel supplier explains that the lintel was already fabricated, the opening date has slipped by nine days and the owner is genuinely baffled: "But I only asked a question."

(This story is illustrative, but if you have worked on a building, you have met a version of it.)

That is what a change order is for. It takes the question, the answer, the price and the date and puts them on one page, signed by the people who have the authority to sign, before anyone lifts a tool. This guide explains what change orders are, why they appear on almost every project, where the fights come from, how to price and approve a change without a duel at dawn and how to keep a log that turns surprises into a short list. In the middle there is a small builder you can use to write a change request that a contractor and an owner will both understand.

What a change order is, in plain English

A construction contract describes a deal at one moment: this work, for this price, by this date. A change order is the written amendment to that deal. It says that the work, the price, the time or all three are now different, by how much and who agreed.

Three terms come up again and again, and they are easy to mix up.

• A change request is where it starts. Somebody, owner, designer or contractor, says "this needs to be different" or "I found something." It is a proposal, not an agreement.
• A change order is where it ends: a signed document that changes the contract. Once signed, the new price and the new date are the contract.
• A directive (some contracts call it a construction change directive or an interim directed change) is the emergency lane. It lets the owner tell the contractor to proceed with the work before the price and the time are settled, with the final numbers agreed later. It exists because walls do not wait for lawyers. It is also where many disputes are born, because "agree later" has a way of becoming "argue later."

The wording and the forms differ from one contract to another. The widely used AIA A201 general conditions and the ConsensusDocs family are two examples, and each has its own definitions, forms and notice periods. This guide is general information, not legal advice: read the change clause of your own contract, and if real money is at stake, have a construction lawyer read it with you.

Why changes are normal

New owners sometimes treat the first change order as an insult, as if the project had failed a test. It has not. Changes happen on nearly every building for reasons that rarely involve bad faith.

1. The owner changes their mind. A tenant arrives, a use changes, a budget loosens or tightens, or a person walks the site and finally sees a room that was only lines on paper before.
2. The drawings are incomplete or in conflict. Two sheets disagree, a detail is missing, a pipe runs through a beam. Even good designers work against a deadline.
3. The ground or the building surprises everyone. Soil that is softer than the report said, old pipes behind a wall in a renovation, an unmarked utility. These are usually called unforeseen or concealed conditions, and your contract says who carries the risk.
4. A code or an inspector requires something. Rules get interpreted, and the interpretation sometimes arrives after the design.
5. A product is unavailable or a better one appears. A long-lead item is delayed, so the team swaps it, or a contractor proposes a cheaper alternative that saves money for everyone.
6. Somebody discovers a better way. Value engineering, in good faith, produces changes that lower cost. Those change orders are a sign of a healthy team.

A project with zero changes is not a perfect project. It is more likely a project where nobody is asking questions. What you want is not no changes, it is no surprises about changes: each one seen early, priced fairly and decided by someone with the authority to decide.

Where the fights really come from

When change orders turn into disputes, the cause is almost never the change itself. The same five patterns appear again and again.

1. Verbal approvals

"The architect told us to go ahead." "The owner said it was fine on Tuesday." Both can be true and still leave the contractor with no signed paper and the owner with no budget. A verbal approval is a story, and stories are remembered differently by everyone in the room.

2. Late notice

Many contracts give a short window to report a change or a claim. The 2017 edition of the AIA A201, for instance, sets a notice period measured in days, not months, as I understand it. A contractor who waits until the end of the job to mention that a change cost them three weeks may find that the contract has already closed the door. An owner who waits until the end to say the change was never authorized may find they have lost the argument for a different reason: they watched it happen and said nothing.

3. Vague pricing

"Extra electrical, $9,000." What extra electrical? How many hours, what materials, what markup, which of these were already in the base price? A price without a breakdown is an invitation to argue about the breakdown.

4. The invisible cost: time

Money is easy to see on a change order. Time often is not. A change can delay other trades, push a delivery or move an inspection. If the form has no line for days, the days still exist; they just appear later, as a surprise, usually wearing the face of a delay claim. This is where your schedule and its critical path matter: a change that lands on a task with float may cost nothing in time, while the same change on a critical task moves the finish by exactly its length.

5. Nobody owns the decision

An architect hints, the contractor assumes, the owner's brother-in-law has an opinion and the real decision-maker finds out at the pay meeting. If the project has no clear answer to "who can approve a change, and up to what amount," then every change is a small constitutional crisis.

The life of a change, step by step

Here is a process light enough for a small building and strong enough for a large one. The names change from one contract to another, but the sequence does not.

1. Spot it and say it. Whoever sees the problem or the idea reports it in writing the same day. A photo and two sentences are enough. This starts the clock honestly for everyone.
2. Describe it. What exactly is different from the contract documents? Which sheet or spec section? Is it an owner request, a design issue, a hidden condition or a contractor proposal? The category matters, because it usually decides who pays.
3. Price it. The contractor provides a breakdown: labor hours and rates, materials, equipment, subcontractor quotes, the markup the contract allows. The owner or the owner's representative checks it against the base price and against what the market says.
4. Time it. The contractor states the impact on the schedule in working days, even if the answer is zero. If the answer is not zero, they show which activities are affected.
5. Decide it. The person named in the contract signs, rejects or asks a question. The decision has a deadline, because waiting is a decision too, and an expensive one.
6. Record it. The change enters the log and the cost report. The schedule is updated. The owner's contingency goes down by the amount.
7. Close it. When the work is done, the change is confirmed as complete and the final cost is compared with the approved price.

If a step keeps getting skipped, the paperwork will be heavy at the end of the job. Heavy paperwork at the end of a job is how friendships end.

Pricing a change fairly

Pricing is where goodwill goes to be tested. A few habits keep it calm.

• Ask for the breakdown, always. Not to catch anyone out, but so that both sides see the same arithmetic. If the contract has a fixed markup for overhead and profit on changes, the breakdown should show it as a separate line.
• Compare with the base price. A good approach is to look at how the original bid priced similar work. Unit prices in the contract make this easy, which is a reason to ask for them early.
• Separate direct cost from impact. The cost of installing the extra pipe is one thing. The cost of the crew waiting for it, the delay to the next trade or the extra supervision is another. Both can be legitimate, and both should be named.
• Watch the cumulative effect. Ten small changes in one area can disrupt the work in ways none of them would alone. If you notice the pattern, say so early and agree how to handle it, instead of discovering it in the final account.
• Do not split a big change into small ones to stay under an approval limit. If you own a building, you will eventually learn how often this happens. A good owner's representative watches for it.

A tip from the other side of the table: the contractor who prices a change quickly and openly is usually the one you want on the next job. The contractor who sends a lump sum and a sigh is telling you something about how the rest of the relationship will go.

Protect the schedule, not only the budget

An owner who watches only the money can win every pricing argument and still lose the project. Suppose a change costs $6,000 and adds six working days to a project that has a fixed opening date and a lease starting on the first of the month. The real cost is the rent on an empty space, the staff on payroll waiting to open and the customers who were told a date. That is why each change order should answer three questions together: how much, how long and how does it fit the plan.

For a large project, a short schedule analysis attached to the change shows exactly which activities move. For a small one, a sentence is enough: "No impact: the framing crew works around it" or "Moves the drywall start by four days, because the inspection must happen first." The point is that someone looked.

If a change does hurt the schedule, you have options: pay for extra shifts, resequence the work, relax a later task or accept the later date. All of them are fine, as long as they are chosen on purpose and written down. The worst option is the default one, where the schedule simply slips and everyone finds out at the end. Our guide to construction schedule delays lists the usual suspects.

Keep a change log

A change log is a spreadsheet with one row per change. It is the least glamorous tool in construction and one of the most useful. A good one has:

• A number, a date, a short description and who requested it.
• The category: owner request, design issue, unforeseen condition, code, contractor proposal.
• The price and the days, as requested and as approved.
• The status: requested, priced, waiting for a decision, approved, rejected, in progress or complete.
• The decision date and the name of the person who decided.
• A running total of approved money and approved days.

Look at the log once a week, at the same meeting. Sort it by status. Every line that is waiting for a decision has a name and a date. Every line that is waiting too long is a conversation to have today, not at the end. The free change request log in the toolkit is set up this way, with automatic totals, and it works as well for a kitchen remodel as for a clinic.

If you are managing the money as well, connect the log to your earned value report and your contingency: when a change is approved, the contingency goes down by that amount and the forecast goes up. Seeing that on one page tells you how much room the project still has.

What owners can do to need fewer change orders

You cannot get to zero, but you can get a long way down.

• Make the big decisions before the drawings are final. Layout, finishes, equipment and use. Changes made on paper cost minutes; changes made in concrete cost money.
• Ask for coordination before construction. A review where the trades check their drawings against each other finds conflicts while they are still lines.
• Keep a contingency and use it on purpose. Many owners reserve a percentage of the budget for unknowns. The right figure depends on the project and the stage of design, so ask your advisor, but having none is a decision to be surprised.
• Name one decision-maker and a backup. With authority and a deadline: "Answers within three working days."
• Have an advocate. An owner's representative or an experienced project manager reads change requests the way an accountant reads an invoice. The role is explained in detail in the owner's representative article and in Part 2 of our construction series.

For the wider picture of how a building project holds together, the five flows in Part 1 of the series are a good companion, and the contract risks guide covers the clauses that decide who pays when something goes wrong. Scope discipline in general is the subject of how to stop scope creep.

What contractors can do

This guide is written mostly from the owner's side of the table, but a fair process needs both sides to play their part.

• Report early and in writing. A short email with photos beats a long letter next month.
• Price transparently. The breakdown is your friend. It protects you from the accusation that you padded the number.
• State the time impact every time. "None" is a legitimate answer. Silence is not.
• Do not start extra work without an order. If the situation really is urgent, use the directive and keep a log of what was done.
• Keep your own log. The owner's log and yours should say the same thing at the end of every month. If they do not, find out why now.

Build a change request

Here is the builder. The sample is a small clinic build-out. Replace each field with your own change and the page on the right becomes a request that gives the owner everything needed to decide. The tool also warns you when something that usually causes trouble is missing: no number, no days or no deadline for the decision. Nothing you type leaves your browser.

Interactive tool

The change request builder

Loading the tool…

The weekly change meeting (fifteen minutes)

If you only adopt one habit from this guide, make it this meeting. It can be part of your regular project meeting.

1. Open the log and read the total approved money and days, out loud.
2. Go through every item waiting for a decision. Each one gets a name, a date and a yes, a no or a "what do you need?"
3. Ask the contractor: is anything being built that is not in the log?
4. Ask the owner: is anyone asking for something that is not in the log?
5. Update the schedule and contingency. Write down what changed.

The fourth and fifth questions are the ones that prevent the Thursday-afternoon window. Say them every week and the hallway conversation becomes a written request, which is exactly what we wanted.

Common mistakes

• Treating a verbal "yes" as a decision. Ask for the form. Politely, every time.
• Pricing without a breakdown. Ask for one.
• Leaving time out of the change. Ask for days, even when it is zero.
• Letting changes pile up unsigned until the final account. Unsigned changes do not age well.
• Using the directive as a habit. It is an emergency lane, not a shortcut.
• Hiding a change behind a different one. A small approved change should not become a large unapproved one.
• Forgetting the contingency. Every approved change should reduce it visibly.

What to do this week

Open your contract and find the change clause. Underline who can approve a change, in what form, and how many days anyone has to give notice. Then start a one-page log with the changes you already know about, whether they are approved or not. If you have changes without paper, put them on the agenda of the next meeting and settle them while everyone still remembers. If you would like someone to read your change requests on your behalf, that is part of my work as an owner's representative, and you can tell me about your project on the contact page.

Which change on a past project cost you the most: the money, the time or the relationship? Tell me in the comments.

More tools. The contract calendar, the risk register and the decision log are free in the toolkit. The publishing calendar shows what comes next in the construction series.

Also read. How the whole building is run, from first idea to keys: project management in construction. And the difference between the person who builds and the person who protects your interest: construction management vs. project management.

Frequently asked questions

What is a change order in construction?

A change order is a written agreement, signed by the people with authority under the contract, that changes the work, the price, the time or all three. It records what changed, how much it costs and how many days it adds or removes, so that the contract and the project stay in step.

Who pays for a change order?

It depends on the cause and on the contract. Owner-requested changes are normally paid by the owner. Changes caused by errors in the design documents or by conditions the contract assigns to the owner usually are too, while changes caused by the contractor's own mistakes usually are not. Read your contract's change and claims clauses, and ask a construction lawyer when the amount is large.

Can a contractor start work before the change order is signed?

Many contracts allow it only through a written directive from the owner, with the final price and time settled afterwards. Starting without any written instruction is risky for both sides: the contractor may not be paid, and the owner may have no record of what was ordered. If it is an emergency, write down what was ordered, when and by whom the same day.

How do I keep change orders from blowing up my budget?

Make the big decisions before the drawings are final, keep a contingency, name one decision-maker, require a price and a time impact on every change, and review the log every week. A project with a weekly log is rarely surprised by its total.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

NameEmail (required, never shown)

Which change on a past project cost you the most: the money, the time or the relationship? Post comment

Your name and email create a small profile that shows you are a real person. The email is never shown. The first time, I send you a confirmation link, and every comment is reviewed before it appears. Please keep it respectful and leave links out.