Change Order Management for Contractors: Stop Losing Money on Verbal Approvals
Change order management for contractors doesn't require expensive software. The process that stops unbilled work, cash flow gaps, and field disputes.
An electrical subcontractor's foreman got a nod from the property manager: run an extra circuit out to the loading dock, no big deal, we'll sort out the paperwork later. Sorting out the paperwork later meant showing up at the final invoice with $4,200 in extra materials and labor nobody had signed off on in writing. The property manager didn't remember agreeing to anything beyond "go ahead and check on it." Six weeks had passed. Memory is a terrible contract, and the subcontractor ate the cost.
That's what change order management for contractors is actually supposed to fix, and it's not really about the changes themselves. Changes happen on every job, every week, on every crew. The failure point is the gap between someone saying yes in the field and someone writing it down in a form the client can't walk back later. We've watched this exact pattern eat margin project after project, and it's almost never because the crew did something wrong on site. It's because nobody closed the loop before the memory got fuzzy.
Why Verbal Approvals Cost More Than They Look Like They Cost
A nod in the field feels efficient. It keeps the job moving, nobody wants to stop and pull out paperwork while a client is standing right there, and most of the time it works out fine. The problem is that "most of the time" is doing a lot of heavy lifting in that sentence.
Industry data on this is remarkably consistent. Roughly 25% to 40% of change order work goes unbilled because documentation was incomplete, the approval window passed, or the contractor simply decided the dispute wasn't worth having. On a typical project, unbilled change orders routinely reach 10% to 20% of total project value. Specialty contractors feel it hardest: 83% report that the change order process directly hurts their cash flow, and 77% have written off change order work they were never able to collect on at all.
The lag is the real culprit. Specialty contractors average about 22 days to process a change order internally before it even reaches the general contractor, who then takes another 26 days on average to approve it. That's roughly seven weeks between a verbal yes in the field and money actually changing hands, assuming it gets approved at all. A 2026 industry survey from Dodge Construction Network and Clearstory found only 1 in 3 contractors say their change order process actually works. Two out of three know it's broken and haven't fixed it yet.
What Change Order Management for Contractors Actually Requires
None of this gets fixed by asking crews to "be better about writing things down." That's not a process, it's a hope. A change order process that actually holds up has three parts, and none of them require new software to start.
- Document the moment, not the memory. The second a verbal change gets approved in the field, someone takes a photo of the work location and writes a one-line description with a timestamp. This isn't a full change order yet. It's proof the conversation happened, captured before anyone's recollection has a chance to soften.
- Turn it into a written change order the same day. Not end of week, not "when we get back to the office." A same-day form with the scope, the cost, and a signature line closes the gap while everyone still remembers the conversation the same way.
- Get the signature before the next day's work starts on that scope, if at all possible. A change order sitting unsigned for two weeks is a change order that's much easier to dispute later. Same-day sign-off, even a quick photo of a signed printed form or a text confirmation, beats a clean digital system that takes ten days to route.
A GC or specialty contractor who nails these three steps with a $0 template and a phone camera will out-collect a competitor running expensive software badly. The tool matters less than most vendors want you to believe. The speed of the loop is what actually protects the money.
Rolling This Out Without Slowing Down the Crew
The biggest objection we hear before anyone even gets to the software question is that a three-step process sounds like it'll slow down a crew that's already moving fast. It won't, if you roll it out in the right order.
- Start with one form, not a system. A single-page change order template, PDF or paper, with fields for scope, cost estimate, photo reference, and a signature line. Don't build or buy anything until the crew has used a plain form for a month.
- Put the photo step on the foreman, not the office. The person standing at the change is the only one who can capture it in the moment. Waiting until end of day means the photo, if it happens at all, is disconnected from the actual approval conversation.
- Set a same-day rule and actually enforce it. Not "try to get it in by end of week." A change order that isn't documented by the end of the shift it happened on has already started the slide toward becoming an unbilled dispute six weeks later.
- Review the backlog weekly for the first month. Not to punish anyone, just to catch where the new habit is slipping before it becomes the old habit again. Most crews get this right after two or three weeks once they see a change order actually get paid faster because of it.
None of that requires a system purchase. It requires a habit change, and habit changes are cheap to test before you spend money making them official.
When a Spreadsheet Still Works, and When It Doesn't
Once the habit is in place, the question of whether you need software at all becomes a lot easier to answer honestly. Some contractors run this entire process on a shared spreadsheet and a stack of signed PDFs for years without a problem. Others hit a wall within a few months because the volume of changes outpaces what one person can manually track and chase.
The break-even point here isn't company size. It's how often a change gets approved verbally in the field before someone writes it down. A two-crew operation with frequent field changes hits this problem as often as a twenty-crew operation running a slower pace of change requests.
| Approach | Best fit | Typical cost | Where it breaks down |
|---|---|---|---|
| Verbal only, no documentation | Nobody, ever | $0 | Unenforceable if a client's memory gets convenient at invoice time |
| Spreadsheet plus a signed PDF template | 1-3 crews, occasional field changes | $0-$20/month | Still requires someone to manually chase signatures and re-enter totals into your accounting system |
| Off-the-shelf change order software | Frequent changes, need mobile approvals across several PMs | $50-$160/month base, plus per-user fees | Built for someone else's approval chain, and you're still copying data into your CRM and invoicing by hand |
| Change order flow built into your own systems | Frequent field changes across multiple crews, need it tied to your CRM, invoicing, and job costing directly | Custom, priced against the hours it replaces | Requires upfront investment, only pays off once volume justifies it |
The middle two tiers aren't wrong choices. They're the right call for a lot of contractors, and we'd rather tell you a $20 template is enough than sell you something bigger than you need. The fourth tier makes sense once you're paying more in chased signatures and re-keyed data than the build would cost, and that's a real number worth calculating before you sign up for another monthly subscription that only solves half the problem. We've built workflow automation for contractors that turns a field photo into a routed, signed, invoiced change order without anyone touching a spreadsheet twice, and it's the same pattern we used on the Grit Construction build, where getting field approvals out of someone's head and into a system that didn't drop them saved real hours every week.
Common Objections We Hear
"We've always done change orders on paper and it's fine." It's fine until a client's memory of a verbal approval gets conveniently fuzzy at invoice time. The cost of a broken process doesn't show up as a line item. It shows up as work you did and never got paid for, which is exactly why it's easy to underestimate until you actually add it up.
"Software won't fix a problem that's really about trust with the client." That's true in isolation. But a same-day, photo-attached, signed change order removes the ambiguity that turns a trust problem into a dispute in the first place. You're not trying to fix the client's honesty. You're removing the six-week gap where honest people genuinely remember things differently.
"We're too small to need dedicated software for this." Company size isn't the variable that matters. Frequency of field changes is. A GC running two crews with constant scope tweaks hits this problem as often as one running twenty, and the fix scales down just as easily as it scales up.
The Bottom Line
Change order management for contractors isn't really a software decision. It's a speed decision. The faster a verbal yes turns into a written, signed, dated record, the less of it ever turns into an argument six weeks later. Start with the three-step process above using tools you already have. If you're chasing signatures and re-entering the same data across three different systems every week, that's the signal it's time to talk about custom software built around how your crews actually work in the field, not how a vendor assumed they would.
If change orders are quietly costing you money and you can't tell how much, we're happy to look at your current process and tell you honestly whether you need a template or a build. Get in touch and we'll walk through it.