Every change order shows the original contract, all previous COs, this CO's amount, and the new running total — the feature no template gets right.
Client and contractor signature blocks on every document. No verbal agreements — scope changes are legally documented.
Document exactly how many days are added or removed from the project timeline. No surprises at deadline.
Start with a quote in BuildQuotes, convert to invoice in BuildInvoice, and document changes here.
Issue the CO before doing the work
A change order written after the work is done is a request for retroactive approval — much harder to get signed. Issue it the moment scope changes, before you lift a finger.
Document the reason for the change
"Client requested" vs. "unforeseen condition" matters legally and relationally. Being specific about why scope changed helps everyone remember the conversation accurately months later.
Show the running contract total
Clients who see "original contract: $10,000 + CO #1: $1,500 = $11,500 total" rarely dispute it. Clients who see a final bill of $11,500 they weren't tracking often do. Transparency is your protection.
Track schedule impact separately from cost
Scope changes often affect timelines too. Documenting "+5 days" protects you from late-penalty claims. If the change adds time, put it in writing — separately from the dollar amount.