Every change order that ever cost somebody money started the same way: a foreman found something that wasn't on the drawings, kept working because the crew was standing there, and told nobody until the pay app came up short. By then the condition was buried behind drywall, the labor was mixed in with base-contract hours, and the owner's rep was asking why he should pay for work he never authorized. The change was real. The paper trail wasn't. That gap — between the moment the field discovers a change and the moment it's properly captured — is where profit leaks out of a job, and it's exactly the gap field management software is built to close.
This article walks through how a change order actually moves from a hole in the ground to a signed, priced, scheduled piece of work, and where a good field tool earns its keep at each step. If you run a jobsite, the mechanics here matter more than any feature list.
The clock starts the second the field finds it
Most subcontracts and prime contracts have a notice provision — you have a set number of days (often 7, sometimes as few as 48 hours for differing site conditions) to give written notice that you've encountered something that changes your scope, cost, or time. Miss that window and you can have a bulletproof claim and still lose it, because you waived your right to it. I've watched a $40,000 rock excavation claim die because notice went out three weeks late.
So the first job isn't pricing. It's notice. The moment a crew hits an unforeseen condition, an owner-directed extra, a design conflict on an RFI, or work that flat-out contradicts the contract documents, that has to be documented that day. This is the single biggest reason to put change capture in the hands of the field instead of routing it through the trailer. A foreman with a phone can log the condition, geotag it, and start the clock in ninety seconds. A change that has to wait for a superintendent to hear about it at the end of the day, remember it, and write it up is a change that's already half-lost.
Capture the condition before it disappears
Conditions in the field are perishable. The differing subgrade gets covered by the mud slab. The mislocated sleeve gets grouted. The conflict between the ductwork and the sprinkler main gets resolved by one trade cutting the other's work and nobody photographing it first. Once it's covered, your evidence is gone and it's your word against theirs.
Good field documentation for a potential change should include, at minimum:
- Photos with a scale reference and a date stamp — a tape measure or a folding rule in the frame, not just a close-up of dirt. Wide shot for context, then tight shots for detail.
- Location tied to the drawings — column line, room number, or a pin on the plan. "Northeast corner" is useless in a claim two years later.
- The contract reference — which detail, which spec section, which RFI or ASI number the condition relates to. This is what turns a complaint into a documented deviation.
- Who was there and what they saw — crew names, and if the owner's inspector or the architect's rep witnessed it, get that on record immediately.
The reason to do this in a system rather than in a text thread is retrieval. Two years later, when the dispute is live, you don't want photos scattered across three foremen's camera rolls. You want them attached to the change, in order, with metadata intact.
Track the work as it happens — the T&M discipline
When you're directed to proceed before a price is settled — and you will be, constantly — you're working on time and materials, and the daily ticket is your invoice. This is where the most money gets left on the table, because field crews hate paperwork and T&M tracking is unforgiving. If the hours aren't captured the day they're worked, they're gone.
A clean T&M ticket for changed work is a discipline, not a form:
- Segregate the labor. The three hours a laborer spent on the extra should never blend into base-contract hours. Tag it to the change, or it's invisible.
- Capture equipment and small tools separately — the mini-ex sitting idle at $95/hour because you're waiting on a direction is a compensable delay, but only if you logged it.
- Get the owner's field rep to sign the ticket daily, acknowledging the hours (not the price). A signature that says "yes, these people worked these hours on this" removes the ugliest argument from the back-end negotiation.
- Photograph the materials consumed. Two hundred linear feet of extra rebar is a lot easier to bill when you shot the delivery ticket and the placement.
The value of doing this in field management software is that the labor hours you're already capturing for payroll and the hours you need for the change ticket come from the same source. You're not double-entering. You tag the time once, in the field, and it flows into both the payroll record and the change documentation.
Price it, and price the time — not just the labor
The direct cost is the easy part: labor, material, equipment, markup per your contract. Where people underprice is the schedule and the ripple. A change that adds two days of work rarely adds only two days of cost. It can push a concrete pour past a weather window, idle a trade you'd mobilized, or bump the work into overtime or a second shift to hold your milestone.
When you build the number, account for:
- Direct labor, material, and equipment at contract rates, with your allowed markup and bond/insurance adder.
- Time-related costs — general conditions for the added days, extended supervision, extended equipment rental.
- Impact and inefficiency — the hardest to quantify and the most often surrendered. Out-of-sequence work, stacking of trades, and acceleration to recover time all carry a real productivity penalty. If you're being told to make up the time, that acceleration cost belongs in the number.
Field supervisors are your best source for the labor estimate because they know the actual production rate on this crew, on this job — not the book rate. Pull them into the pricing.
Trace the schedule impact honestly
This is the step most changes skip, and it's the one that turns a change order into a time-extension fight later. Adding scope to a project doesn't automatically move the completion date — only added scope on the critical path does. Before you claim days, trace the changed activity through your schedule and see whether it actually pushes downstream work or just eats float.
The place this shows up first and most concretely is the short-interval plan — your two-to-six-week look-ahead. A change doesn't hit the master CPM in the abstract; it hits the weekly work plan on the wall, this Tuesday, in the form of a crew that can't start because the changed work isn't done. When you plan location-based, look-ahead schedules in a tool like LookAheadWall, that collision is visible before it happens: you can see the trade-flow sequence break, spot which downstream crews are stranded, and decide whether the change costs you time or just costs you money. Catching a sequence break in the look-ahead is a $500 conversation this week; discovering it after the fact is a $20,000 delay claim next quarter.
Route it for approval — and don't proceed without authorization
Different dollar amounts need different signatures. A field authorization from the owner's on-site rep might cover a small directed change; a formal change order to the contract might need the owner, the architect, and sometimes a lender's approval. The workflow should route each change to the right level and hold there until it's signed — with status visible to everyone, so the PM isn't chasing a paper form around three offices.
The rule that protects you: don't build changed work without written authorization to proceed. A verbal "go ahead and do it, we'll paper it later" is how contractors end up eating unauthorized work. If you must proceed on a verbal direction to keep the job moving, confirm it in writing that same day — "per your direction this morning, we are proceeding with X on a T&M basis" — and let silence be your acknowledgment. A tracked approval workflow makes the "who authorized what, and when" question answerable in seconds instead of arguable for weeks.
Flow it down to your subs — both directions
Changes rarely touch one trade. An owner change to the mechanical room reroutes the electrician's conduit, moves the plumber's drops, and forces the framer to reframe a chase. Your subcontract flow-down has to move in lockstep with your prime change, or you'll agree to a number with the owner that doesn't cover what you owe your subs.
Two failure modes to watch:
- Under-flowing: you settle the prime change without getting each affected sub's number first, then discover their impact exceeds what you collected. Get sub pricing before you sign the prime CO.
- Over-notifying without tracking: you tell four subs a change is coming but never confirm which ones actually have impact and cost. Assess and log each trade's effect specifically, and notify only the affected ones — with the same photo and condition record you built up top.
Keep the log — the change order log is the job's memory
Any project past a few weeks accumulates changes faster than memory can hold them. A running change log is the single most important document for financial control on a job. It should show, at a glance, every change's status: identified, priced, submitted, approved, or rejected; the dollar value pending versus approved; and the running total of contract modifications so the revised contract value is always current.
Two numbers I check every week off the log: total dollars in changes sitting unapproved (that's cash I've spent and can't yet bill), and days claimed but not yet granted (that's schedule risk with no time extension behind it). When either climbs, it's a conversation with the owner before it becomes a crisis.
What the log tells you when you finally read it
At closeout, the change log is also a report card. Sort your changes by cause and patterns jump out. A stack of changes from the same detail means the design had a problem you can flag next time. A run of differing-site-condition changes says your geotech scope was thin. Frequent owner-driven scope adds mean the program wasn't nailed down before you mobilized. None of that helps this job much, but it's exactly the estimating and risk intelligence that makes the next bid smarter.
The through-line
Strip away the software talk and change order management is really one habit repeated: capture reality the moment it happens, tie it to the contract, and never let a day of changed work go undocumented. The tools matter because they move that habit out of the trailer and into the field where the change actually occurs — the phone in the foreman's pocket, the look-ahead on the wall, the log the PM reads every Friday. A change you capture cleanly is a change you get paid for and scheduled around. A change you capture late is a change you argue about. On a jobsite, the difference between those two outcomes is usually about ninety seconds of documentation nobody wanted to do — and the discipline to do it anyway.