Change orders and scope creep: how to handle a change on a construction job
A change order is a short written record of what changed, what it costs, how many days it adds and who approved it, made before the extra work is done. It is how you stop scope creep turning into a dispute.
The short version
Most jobs change. A client adds a room, a condition on site is not what the drawings showed, an inspector asks for something extra. The change itself is rarely the problem. The problem is doing the extra work on a handshake, then arguing about what was agreed. A change order is the short written record that fixes this: what changed, what it costs, how many days it adds and who approved it, written down before the work is done.
Scope creep, clarification or change?
Before writing anything, work out which of three things you are looking at. They need different handling.
| It is... | How to tell | What to do |
|---|---|---|
| Already in the scope | The written scope, drawings or specifications already cover it | Do it. Point to the page that says so. |
| A clarification | The documents are unclear or disagree, and the answer does not add work | Ask the question in writing and keep the answer. See how to track RFIs. |
| A real change | It adds, removes or alters work compared with the agreed scope | Write a change order before the work starts. |
Scope creep is what happens when real changes are treated as clarifications, or as already included, and nobody writes them down. A clear scope of work with exclusions is the best protection, because it gives you something to compare each request against.
What a change order should contain
- The reason. Client request, unforeseen condition, design change, code requirement or an error in the documents.
- What changed. Which part of the scope, drawing or specification it touches, in words someone who was not on site can follow.
- The cost. The extra (or reduced) amount, kept separate from the original contract value.
- The time. The days it adds to the schedule, or none.
- The effect on milestones. A new milestone for the extra work, or a change to an existing one.
- Who asked and who approved, and when. The approval is what makes it binding in practice, so it needs a name and a date.
A six-step way to handle a change
- 1
Stop and name it
As soon as someone asks for something that is not in the scope, say so plainly: "That is outside what we priced. I will write it up." Do this the first time, not the third.
- 2
Write it before you do it
Describe the change and the reason. Most contracts set rules for how and when changes must be approved, so read yours. Starting extra work first is the most common way to end up unpaid or in a dispute.
- 3
Price the money and the time
Give the extra cost and the extra days as separate numbers. A change that costs nothing but delays the finish still needs recording.
- 4
Get a decision from the right person
The person with authority to approve should say yes or no in writing. A reply from someone without that authority does not settle it.
- 5
Update the scope, schedule and milestones together
Once approved, the contract value, the finish date and the milestone list should all move at the same time. If they are updated separately, they drift apart.
- 6
Keep the record
Declined changes matter too. Months later, "we asked and you said no" is as useful as "we asked and you said yes".
Common traps
- Doing the work "to keep the job moving" and sorting out the paperwork later.
- Agreeing on site, by text or in a hallway, with nothing the office can find.
- Pricing the change but forgetting the days it adds.
- Folding a change into the original price so you can no longer see what the job originally cost.
- Approving a change without updating the milestones, so the final invoice does not match the work.
- Treating an RFI answer or an addendum as free when it quietly adds work.
How ScopeMark helps
- The subcontractor raises it from the job. The subcontractor holding an awarded job can raise a change order on the web or the phone: the reason, what changed, the extra cost and the extra days.
- The company decides. Owners and project managers see the waiting change orders and accept or reject each one. Approved and declined ones stay listed as earlier change orders.
- Approval moves everything together. Approving adds the new milestone, the extra cost to the contract value and the extra days to the due date in a single step, so the three cannot disagree. They are not edited separately.
- The original stays visible. The job's budget view keeps the original contract value apart from the approved changes, so you can always see what it was first.
- Answers stay with the job. The answers to RFIs and the addenda that explain why something changed can be kept on the project as a record of what was asked and answered.
- Invoices follow the work. The milestone from an approved change order is confirmed and invoiced like any other milestone.
ScopeMark does not decide whether a change is fair, does not price it and gives no legal advice. People write, approve and reject; the platform keeps the record. See how to sub out a project, from scope to invoice for where change orders fit in the whole flow.
Questions people ask
What is a change order in construction?
A change order is a written record of a change to the agreed scope of work: what is added, removed or altered, the effect on cost and schedule, and who approved it.
What is the difference between scope creep and a change order?
Scope creep is extra work that slips in without being agreed or recorded. A change order is how you record a real change properly, so it is priced and approved instead of absorbed.
Should I do the work before the change order is approved?
Check your contract. Many contracts require approval before extra work starts, and doing it first is a common reason extra work goes unpaid or disputed. This is general guidance, not legal advice.
Who can raise a change order in ScopeMark?
The subcontractor holding the awarded job raises it, with a reason, what changed, the extra cost and the extra days. Owners and project managers of the company decide whether to accept or reject it.
What happens when a change order is approved in ScopeMark?
Approving adds the new milestone, the extra cost to the contract value and the extra days to the due date together, in one step. The original contract value stays visible separately.
Does ScopeMark hold or move our money?
No. ScopeMark does not process payments between companies and subcontractors. The buyer pays directly, outside ScopeMark, and records the payment. ScopeMark's only revenue is its subscription.