TMIThe customer said yes to the original bid without much friction. The change order for $2,800 of additional work that showed up in the wall turns into a forty-minute conversation, a delayed payment, and a relationship that's cooler than it was before. The price for the original job was $18,000. The change order is 15% of that. The original bid was accepted in minutes. The change order turned into a negotiation.
This pattern repeats constantly in the trades, and it's usually interpreted as a price sensitivity problem. It almost never is. The customer isn't objecting to the price. They're objecting to the process - specifically, to being surprised at invoice time by work they don't clearly remember authorizing, or don't fully understand was outside the original scope. The framing problem precedes the price problem, and solving the framing problem makes the price problem mostly disappear.
Why change orders feel adversarial when they don't have to
A change order presented at the time the scope change happens - while the tech is standing in front of the customer, phone in hand, with the original wall open behind them showing exactly what was found - lands completely differently than a line item on an invoice three weeks later. In the first scenario, the customer has context. They can see the unexpected condition. They understand why the additional work is necessary. They make a decision with full information and give approval. In the second scenario, they're reviewing a document that references a conversation they vaguely remember and work that's already done, and they're being asked to validate something they can't verify.
Most change order disputes happen because the second scenario is the default. The tech does the additional work - because the foreman said it was fine, because the customer said "sure, while you're here" - and the paperwork catches up later, or doesn't catch up at all. By invoice time, the customer's memory has softened, their goodwill has moved on to the next project, and the change order looks like a surprise rather than a confirmed commitment.
"Most change order disputes aren't about the money. They're about the customer not remembering approving the work."
Digital change order approval - what it actually looks like
A digital change order process at the point of discovery closes the gap between approval and billing. When the tech finds the unexpected condition, they open the job in their phone, document the condition with a photo, enter the additional scope as a line item with pricing pulled from the rate schedule, and turn the phone to the customer for a signature or an email approval. The change order is in the job record before the additional work starts. The customer's approval is timestamped and attached to the photo documentation of what was found.
This process does several things simultaneously: it gets written approval before work begins (not after), it creates a defensible record in the event of a dispute, it captures the revenue in the job record at the moment it's generated rather than hoping someone remembers it at invoice time, and it frames the change order as a customer service moment rather than a billing surprise. The tech explaining what was found and presenting a clear price for the fix is a professional interaction. The line item appearing on an invoice three weeks later is not.
Pricing change orders from data rather than gut
One underappreciated benefit of a digital change order process is that it generates data. When change orders are captured consistently, patterns emerge: which job types generate change orders most frequently, what the average change order value is by category, which unexpected conditions show up repeatedly. That data is pricing intelligence. If a certain type of job generates change orders on 40% of completions at an average of $1,200, there's an argument for building a contingency into the original estimate that accounts for the expected scope expansion. The customer gets a slightly higher original bid with an honest explanation of what it covers, rather than a series of change orders that erode the relationship throughout the job.