Every superintendent has a story about the change order that ate a job. Mine was a podium-deck deal where the structural engineer revised the shear-wall nailing after the framers were already three floors up. The change was legitimate, the money was fair, and it still cost us eleven days — not because of the work, but because the paperwork sat in somebody's inbox while the crew stood around waiting to be told whether to keep going. The work was a day. The decision was ten.
That's the real lesson about change orders: the physical scope is rarely the problem. The problem is the gap between the moment a change shows up in the field and the moment somebody with authority says "yes, build it, here's the number." Software doesn't make that gap disappear, but the right tools shrink it from days to hours by keeping the paper trail moving and the schedule honest. Here's how that actually works on a jobsite, and where scheduling and field tools genuinely help.
Why change orders turn into chaos
A change order is just a modification to the contracted scope, price, or time. On paper it's clean. In the field it gets ugly for a handful of predictable reasons, and if you've run jobs you've hit all of them:
- The change is discovered by the person with the least authority to price it. A framer finds a beam that conflicts with a duct chase. He's the one who sees it first and the last one who can approve fixing it.
- Nobody documents it while it's fresh. Two weeks later, when the RFI answer finally lands, the exact condition — what was there, what was buried, who was standing on it — is a memory instead of a photo.
- The work proceeds before the money is settled. This is the classic. The GC says "just keep going, we'll figure out the change later." Later, "later" becomes a dispute.
- The schedule impact gets ignored until it's a delay. Everyone argues about the dollar value of the change and nobody asks the more expensive question: how many days does this push the finish?
Fix those four failure modes and you've fixed most change-order pain. Each one maps to a specific piece of process, and each piece is something a decent field and scheduling system can carry.
Capture the change the moment it's found — in the field
The single highest-leverage habit is documenting a potential change the instant a foreman or crew leader trips over it, before anyone touches it. Not at the end of the day. Not in the next OAC meeting. Right then.
What "capture" means in practice is short: a couple of photos with something for scale in frame, a one-line description of the condition, the location (grid line, room number, floor), and the date and time. That's a defensible record. The reason to do it on a phone in the field rather than a laptop back in the trailer is simple — the condition gets covered up. Once the slab is poured or the wall is closed, your photo is the only proof the conflict ever existed. A mobile-first workflow, where the crew leader captures the condition on the same device they're already carrying, is worth more than any elaborate approval routing you bolt on later.
Tie that capture to a number immediately. Give it a PCO (potential change order) log entry the day it's found, even before you know the price. What you're building is a running list that answers, at any moment, "what's open, what's it worth, and what's it doing to my schedule." A superintendent who can pull that up in a meeting controls the meeting.
Route it fast, and know exactly where it's stuck
The reason change orders die in inboxes is that nobody can see where they are. A PCO typically has to walk a path: field identifies it, the GC or CM validates it, the architect or engineer weighs in if it's a design question, the sub prices it, the owner approves the money, and it becomes an executed CO. Six or seven hands, any one of which can sit on it for a week.
The value of a workflow tool here is not the fancy multi-level approval routing. It's visibility into the bottleneck. When you can look at your log and see that four of your eight open PCOs have been "awaiting architect response" for nine days, you have a specific, nameable problem you can escalate with a name and a date attached. "The architect owes me pricing direction on PCO-0034 since the 12th" is a sentence that gets action. "Change orders are slow" is not.
Set aging thresholds and escalate on them. A PCO that's sat in one status for more than five business days should raise its hand automatically. On a fast-moving job, three days. The goal is that no change quietly rots.
Price it before you build it — and get the schedule impact in writing
Here is the discipline that separates the supers who get paid from the ones who eat it: whenever it's physically possible, settle the price and the time before the work goes in. When you're forced to proceed on a T&M or not-to-exceed basis because the schedule can't wait — and sometimes it genuinely can't — then the daily tickets, signed by the GC's rep each day, become your contract. Track hours, equipment, and material against that ticket contemporaneously. A stack of unsigned T&M tickets produced at the end of a job is where money goes to die.
And do not let anyone process a change order that touches sequence, access, or duration without a written time-impact statement. This is the part everyone shortcuts. A change worth eight thousand dollars can carry an eight-day delay if it lands on the critical path, and eight days of general conditions plus your subs' remob costs will dwarf the direct price every time. Two rules of thumb worth internalizing:
- If a change interrupts a trade mid-flow, budget for demobilization and remobilization — a crew that gets pulled off and brought back rarely restarts at full production for a day or two.
- If a change adds an inspection hold, add the inspector's realistic lead time, not the optimistic one. A next-day re-inspection is a fantasy on most jurisdictions; a 2–3 day buffer is honest.
Where the change order meets the look-ahead
This is the part most articles about "change order software" skip entirely, and it's the part that actually protects your finish date. A change order is a schedule event, not just a financial one. The moment it's approved — sometimes the moment it's even likely — it has to show up in your short-interval plan, because it's going to move real crews next week.
When you run a rolling three- or four-week look-ahead, a change order forces you to re-ask the questions that plan already answers: Which trade does this affect? Does it break an established trade-flow sequence — does the electrician now have to come back after the drywaller you already released? Does it create a new predecessor that has to finish before the next crew can start their location? Those are exactly the relationships a visual, location-based weekly work plan is built to show. In a tool like LookAheadWall, where the plan is laid out by location and the trade-flow connections are drawn between activities, you can see the ripple immediately: this change adds a day of rework in Area C, which pushes the flooring crew's start in Area C, which pushes their move to Area D. You catch the collision in the plan instead of on the floor.
The practical habit: when a change is approved, don't just file the executed CO. Re-baseline the affected activities in the look-ahead the same day, notify the trades whose start dates moved, and confirm they saw it. A change order that updates the contract but not the weekly work plan is how you end up with a crew showing up Monday to a location that isn't ready.
Communicate to the trades — and prove they got it
A change is only real to a subcontractor when they've acknowledged it. The two things worth being disciplined about are distributing the current documents — the revised detail, the new spec section, the updated area of the plan — and capturing confirmation that the affected sub received them. That receipt is not bureaucracy; it's the difference between "the demo scope changed and the plumber knew" and "the plumber says nobody told him, and now he wants a change order of his own for the rework."
When the change touches sequence, the crew leaders working that area need the updated look-ahead in their hands, not a verbal "hey, things shifted." A companion mobile view that lets a foreman see the current week's plan for his crew — including the activities the change just moved — closes the loop that a paper CO never touches.
Keep the records that win the argument
Most change-order disputes aren't won by the party who's right. They're won by the party who documented it while it was happening. Contemporaneous records — dated photos, the daily log entry noting the condition, the RFI that triggered the change, the signed T&M tickets, the schedule showing the impacted activities — are worth more than any argument you can construct after the fact. If your process produces those records as a natural byproduct of doing the work, you're covered. If producing them requires a special end-of-project effort, they won't exist when you need them.
The through-line across all of this is that good change-order management isn't a piece of software you buy — it's a habit of capturing fast, routing visibly, pricing before you build, and reflecting every approved change in the schedule your crews actually work from. The tools earn their keep by making the honest version of that process the easy version. Field capture on the device the crew already carries, a PCO log that shows you the bottleneck, and a look-ahead that turns an executed change order into an updated Monday plan — string those together and the change order that used to eat eleven days costs you a phone call and a schedule update.
Changes are coming on every job. They're not the enemy. The days you lose deciding what to do about them are.