The four-step loop
Every change, big or small, runs through the same four steps in the same order. The order is the whole point.
1. Capture
The moment a change surfaces, whether a homeowner request, a hidden condition, or a design tweak, write it down immediately. Not tonight, not at the weekly meeting. Now. Most changes start as a casual comment on site, and the ones you don't capture in the moment are the ones you forget to bill. A one-line note with a photo is enough to start: *what changed, who asked, when.*
2. Price
Turn the captured request into a number. Because a change order is essentially a mini-estimate, price it the same way you price original work (labour, materials, equipment, subs, and your markup) applied to the delta. Don't guess a round number to keep the peace; that's how you end up eating the difference. And don't forget the schedule impact: if the change moves your completion date, that's part of the price of the change.
3. Approve, in writing, before you build
This is the step that separates getting paid from arguing later. Present the priced change and get a signature (or a clear digital approval) *before* any of the work happens. Once it's built, your leverage is gone. Written approval protects both of you: you're certain you'll be paid, and the homeowner is certain what they're buying. Verbal "go aheads" don't count. For how to convert those, see handling verbal change requests.
4. Build, and fold it into the job
Only now does the work happen. And the change shouldn't live as an orphan PDF. It should fold into the job: the new scope adds to the budget, the new total updates the contract, and the added amount flows into the next invoice. If your approved changes don't automatically update the budget and billing, you're re-entering everything by hand, which is exactly where things fall through the cracks.
Why the order matters
Run the steps out of order and the process fails. Build before you price, and you're guessing. Build before you approve, and you're begging. Approve but never fold it into the budget, and you get to close-out with a stack of signed changes you forgot to invoice. The sequence (capture, price, approve, build) is what keeps every dollar accounted for.
Set the expectation up front
The smoothest change-order processes start before the first change. Tell the homeowner at contract signing how changes work: "Anytime you want to add or change something, I'll write it up with a price and a schedule impact, you approve it, and then we build it. Nothing changes on your home or your bill without your sign-off." Framed that way, change orders sound like professionalism and protection, not nickel-and-diming. When the first change comes, you're following a process you both already agreed to, not springing a form on them.
Keep the changes small and frequent
A common mistake is batching changes, saving them up to present as one big change order later. Don't. Batching means unbilled work piling up and a large, alarming number landing on the homeowner all at once. Issue changes small and often, as they happen. Each is easy to approve because it's fresh and specific, and your billing never drifts far from the work.
The process only works if it's fast
Every step above assumes issuing a change order takes minutes, not an evening at a desk. If it's slow, you'll skip the small ones, and the small ones are the leak. That's the case for running change orders inside a connected construction project management system rather than a document folder: capture on your phone, price against your real cost data, get approval by link, and let the approved change update the budget and the invoice on its own.
TradesMetrics treats each change order as a standalone estimate that merges into the job's budget on approval, so the four-step loop takes minutes and nothing reaches close-out unbilled. See how the change-order feature works, or start with the change orders hub.