Scope creep is decided on site, in a sentence like “yeah, we can move that outlet.” The cost of that outlet is fixed the moment somebody says yes. That cost includes the electrician's hour, the patch, the paint and the day it pushes the drywall inspection. What is not fixed is whether anyone gets paid for it. That depends on whether the yes was written down before the work started, with a name and a price status attached. Scope creep is a capture problem, not a client problem.
The standard advice on scope creep construction firms get is about the client: set expectations at kickoff, write a tighter contract, say no more often. All of that is useful. None of it touches the point where the money is lost. That point is a verbal agreement on a Tuesday afternoon that nobody records until the invoice goes out six weeks later, or never.
The client asked. Someone on the builder's side agreed.
Clients ask for things. That is normal and mostly reasonable. They are seeing the framed room for the first time, and the window sits lower than it looked on the drawing. Asking does not create a cost. Agreement does. Every unbilled extra on a job traces back to a moment when somebody working for the builder said yes. Sometimes they said nothing and then did the work.
That reframing matters because it moves the problem somewhere the builder controls. Nobody can stop a homeowner from asking about a niche in the shower wall. A builder can control who is allowed to answer and what that person writes down. It can also control how fast the record reaches whoever prices it.
Where the yes actually happens
It almost never happens in the office. These are the usual places:
- Walkthroughs. The client and the superintendent stand in the room, and the client points at a wall.
- The sub on site says “easy, I'll just run it over there.” The sub then bills the builder, and the builder has nobody to bill.
- Phone and text to the PM. The request sits on a personal phone, in a thread with a dozen other messages.
- Designer or architect direction. A marked-up sketch is handed to the foreman and treated as an instruction.
- Silence. The crew notices the drawing does not work and fixes it the obvious way. Nobody records that it was a change.
Each of these has the same shape. Someone in the field makes the decision. One person holds the record, if there is one. Nobody sets the price.
Why the price is set before the paperwork exists
Once the work is in, the builder's position changes. Before the work, the client wants it and will agree to a number to get it. After, the outlet is in the wall and the client remembers it as a small favour. The builder is now asking for money for something already delivered. The work and the cost are the same, but the conversation is much weaker.
Memory makes it worse. Six weeks on, the super remembers “they asked for it.” The client remembers “he said it was no problem.” Neither remembers whether price came up. Disputes over extras turn on contemporaneous records: what was written at the time, not what either side recalls later. The same logic applies to site photos that carry a job, a date and a reason. A picture of the moved outlet proves it was moved, not that anyone agreed to pay for it.
Then the small ones compound. A single unbilled extra is rarely worth the argument. A job with fifteen of them is where the margin went, and nobody can say which fifteen.
Check the changes clause in your own contract. Many require written authorization before changed work proceeds. Suppose yours does and the crew built an extra on a verbal yes. The builder has then broken its own contract to do the client a favour, and the client's refusal to pay has a document behind it. The fix is not a better invoice. The fix is a rule that no extra starts without a written record the client has acknowledged, even if the price comes later.
What to capture at the moment of yes
This is not a finished change order. It is a capture record, with enough detail that whoever prices it later is not rebuilding it from memory. Record these in this order:
- What exactly. Write “move kitchen island outlet 18 inches toward the sink, add GFCI,” not “outlet change.”
- Who asked and who agreed, with names and roles.
- When and where: the date, the room or grid line and which job.
- Price status: priced now, priced later with a ceiling or not yet discussed.
- Whether work may start: yes, no or only after client sign-off.
- A photo of the existing condition, taken before anything moves.
Pricing it properly is a separate job: scope first, then rate. That is covered in how to price a change order. The capture record exists so the pricing has something solid to start from.
Give the field three answers, not two
Most field staff think the only choices are yes and no. No feels like bad service, and yes feels free. A third answer removes most of the problem.
- Yes, priced. This is for small, known work, priced on the spot within a limit the super is allowed to quote. The client acknowledges it in writing before work starts.
- Yes, pending price. The request is recorded, and the client acknowledges that it is extra and a price is coming. Work waits for sign-off. Most changes belong here.
- Not now. Log it anyway. A request declined in week 4 often comes back in week 10, and the record shows it was raised and turned down.
The middle answer does the work. It lets the super be agreeable in the room without committing the builder's money.
Decide who can say yes before the job starts
Authority should be written down for each role, not assumed. Here is a workable split for a builder running 5 to 40 jobs:
- Superintendent: can record any request and can approve and quote extras under a fixed ceiling. Cannot start uncaptured work.
- Foreman or lead carpenter: can record requests but cannot approve a price. Routes everything to the super.
- Subcontractors: cannot agree extras with the client at all. Any request goes to the super, and the sub's extra cost is accepted only against a written change.
- PM: prices anything over the super's ceiling and sends it to the client for approval.
- Owner: sets the ceilings. Approves anything that touches the critical path or moves the contract total past a set threshold.
The dollar ceiling is the owner's call, and there is no right number to copy. What matters is that the ceiling exists in writing before the first walkthrough. A super who knows the limit can say yes quickly to small things and route everything else without hesitating.
What software does and does not do here
No software stops a superintendent from saying yes in a hallway. Capture still depends on someone opening a phone within the hour. Software can make that cheap enough that it actually happens. It can also keep the record off one person's phone.
In BuilderSolve, the super can note the request in the daily log. The AI assistant drafts a change order from that note, with description, location and line items from the shared rate library. The draft waits until a person approves, edits or rejects it. Nothing goes to a client on the assistant's say-so. Once approved, the change goes through change orders with an audit trail, which records who created, edited and approved each version. It then goes to the branded client portal, where the client signs off. Budget vs. actual can then show the extra as an approved change rather than an unexplained overrun.
Some limits are worth stating. Purchase orders are in development and not shipped, so a sub's cost on a change is entered as a line item, not issued as a PO. The platform reads from QuickBooks one way and does not write into it. QuickBooks stays the book of record. Sometimes changes get captured but nobody prices them for two weeks. In that case, BuilderSolve's operations and finance team can take on the pricing and paperwork. The field still has to make the capture.
Start with the next walkthrough
Do three things before the next client walkthrough on any active job:
- Write the authority split and the super's dollar ceiling on one page. Hand it to every super and sub lead.
- Agree with the supers that “yes, pending price” is the default answer and that nothing uncaptured starts.
- Pull the last month of daily logs and texts on one job. List every extra agreed in the field, then count how many became signed changes. The difference is the size of the problem on that job.
Then decide where that difference comes from. Extras that were never written down are a capture problem. Extras that were written down but never priced are a pricing problem. The fixes are different, so it is worth knowing which one you have before changing anything else.
Common questions
what causes scope creep in construction
Scope creep is caused by extras agreed in the field and never recorded, not by clients asking for things. A super, sub or PM says yes on site or by text, the crew does the work and nobody writes down what was agreed or at what price. By invoice time, the work is built and the record is gone, so the cost lands on the builder.
how to stop scope creep on a construction project
Control who can say yes and what they record when they do. Write down each role's authority and give superintendents a dollar ceiling. Make “yes, pending price” the default answer. Require a written, client-acknowledged record before any extra starts. Tighter contracts help, but only if the field follows the changes clause they contain.
is a verbal change order enforceable in construction
It depends on the contract and the jurisdiction, and this is not legal advice. Many construction contracts require written authorization before changed work proceeds. A verbal agreement is also hard to prove weeks later, when both sides remember it differently. A short written record made at the time, acknowledged by the client, puts the builder in a far stronger position than recollection.
what should a field change record include
A field change record should hold six things. These are the exact scope, who asked and who agreed, the date and location, and the price status (priced, pending or not discussed). It should also state whether work may start and include a photo of the existing condition. It does not need to be a finished change order, just complete enough to price without guessing.
should a superintendent be allowed to approve change orders
Yes, within a fixed dollar ceiling the owner sets in writing before the job starts. Below the ceiling, the super can quote and approve small known extras with written client acknowledgement. Anything above it, or anything affecting the critical path, goes to the PM or owner. Subcontractors should not agree extras with the client at all.