Change Orders 101: How to Price and Document Mid-Job Scope Changes

The Job You Priced Isn't the Job You're Doing

You bid the kitchen remodel at $18,000. Two weeks in, the customer asks you to move an outlet, swap the faucet to a different model, and "just while you're in there" add a pot filler above the stove. None of that was in the original estimate. None of it gets written down. By the time you invoice, you've eaten twelve hours of extra labor and $400 in materials you never billed for — and the customer thinks that's just what a good contractor does.

That's not goodwill. That's margin walking out the door, one verbal favor at a time. Unbilled change orders are one of the most common and most invisible ways contractors lose money on jobs they otherwise priced correctly. The fix isn't charging customers more for every little thing — it's having a system so scope changes get written down and priced before the work happens, not absorbed after.

Why Change Orders Get Skipped in the First Place

Nobody skips change orders because they're trying to lose money. They skip them because stopping mid-task to write up paperwork feels like friction, especially for a small add like moving an outlet. The contractor does the math in their head — "this'll take twenty minutes" — and just does it. The problem is that twenty-minute changes stack. A job with six small "while you're here" requests can add four or five hours of unbilled labor plus materials, and the contractor never notices because it's spread across the whole project instead of showing up as one obvious number.

• No system for capturing a scope change in writing when it's requested verbally on-site
• Underestimating the real cost — not just the task, but the disruption it causes to the planned sequence of work
• Discomfort asking an existing customer to pay more mid-project, so the request gets absorbed instead of billed
• No record at invoicing time, so the change simply doesn't make it onto the final bill

The Three-Step Flow: Describe, Price, Approve

The whole system is three steps, and all three have to happen before work continues — not after.

Describe. Write down exactly what changed and why, in plain language. "Customer requested moving kitchen outlet from east wall to north wall, 6 feet, to accommodate new island placement." This protects you later if there's any dispute about what was actually asked for.

Price. Price the labor, materials, and any disruption to the schedule this change causes — not just the task in isolation. A ten-minute job that requires you to stop, re-route, and re-sequence the rest of the day isn't a ten-minute charge. More on pricing disruption below.

Approve. Get a signature or a clear written "yes, go ahead" — a text message confirming the price is fine, as long as it's dated and saved. The rule that matters most: work doesn't continue on the changed scope until approval is in hand. If a customer wants it done right now while you're standing there, get a quick verbal yes and follow up with the written confirmation same day. Never let "we'll sort it out at the end" be the plan.

Pricing the Disruption, Not Just the Task

This is the part most contractors get wrong. They price the physical task — the labor hours and the materials — and stop there. But a mid-job change almost always costs more than the task itself because it disrupts a sequence you already planned around.

Moving that outlet after drywall is scheduled for tomorrow means someone has to delay drywall, possibly re-order material, and come back to a job site that's no longer in the state you left it. That's real cost, even if the outlet move itself takes twenty minutes. A fair change order price accounts for:

• The direct labor and materials for the new task
• Any demo or rework needed on items already completed
• Schedule disruption — delayed trades, re-mobilization, an extra trip
• A reasonable markup, same as you'd apply to the original estimate — change orders aren't favors, they're new scope

If you want a refresher on how markup should work across your pricing generally, markup vs margin for contractors breaks down the math so you're not guessing on change orders either.

Sample Change Order Language

You don't need a lawyer-drafted document. You need something short, clear, and consistent every time. A simple template:

"Change Order #[number] — [Job name], [date]. Original scope: [brief reference]. Requested change: [description]. Additional cost: $[amount] (labor $[x], materials $[x]). This amount will be added to the final invoice. Estimated schedule impact: [none / X days]. Approved by: ___________ Date: ___________."

Keep every change order attached to the job file, not buried in a text thread. When you get to the final invoice, those approved change orders should roll straight into the total — no searching your messages trying to remember what you agreed to three weeks ago.

Why This Connects to How You Actually Make Money

Change orders aren't a side issue from estimating — they're part of the same discipline. If your estimating process is already casual, your change order process will be too, and the two gaps compound each other. For the bigger picture on where contractor profit actually comes from and why margin discipline matters more than volume, see how contractors make money and why margin beats volume.

How Trusso Helps

Trusso keeps change orders from getting lost in a text thread. Because estimates are built against your own price book, adding scope mid-job means pricing the change at the same rates you already trust — not guessing on the fly. Updated estimates and approvals live on the job record, so when you invoice, every approved change rolls into the final total automatically instead of relying on memory. It won't chase down a signature for you, but it gives you one place where the described, priced, and approved change order actually lives next to the job it belongs to.