A collapsible card listing change orders with a number, customer-facing status wording, title, total, day impact and date. The subtitle states how many are awaiting review, or the total value of approved changes. Drafts and cancelled change orders never appear. Credits render with a proper minus sign.
Also called: extras during the build · scope change · variation order · customer approves a change
Every change, once sent, is on the customer's dashboard
Number, title, cost, day impact and status, with the running value of approved changes in the card subtitle. Drafts and cancelled ones never appear, so your work in progress stays yours. This is the argument that sours finished jobs — the customer who agreed to extras on site and disputes them at final billing — and it becomes a dated list instead of two memories.
A branded Change Order Agreement, generated per change
Six sections on your letterhead: description of the change with attachments, reason with the chosen one ticked, cost adjustment showing the original contract price, the ADD or DEDUCT and the new contract total with line items, schedule adjustment in days, the binding clause, and the signatures. It replaces the photocopied form on the dash of the truck. The customer's copy, your preview and the printed page are the same document, so they cannot disagree.
They sign on the change order, without leaving their dashboard
The signature inputs sit inside section six of the agreement: an authorisation checkbox, a typed name that must match the owner name, and drawn ink. The agreement text exactly as the customer saw it is frozen onto the signature record, so a later template edit can never rewrite what was agreed to. The card's Pending marker flips to Approved in place, and the work is authorised before it starts rather than after.
A decline comes back with a written reason
Declining goes through a confirmation that names the change order, warns that the builder will be notified, and will not submit without a typed reason. A rejected change with no explanation is just a phone call you now have to make; this one arrives with the why already attached and the decision on the record.
It reads in customer language, and a credit reads as a credit
Internal statuses are mapped for the customer — a change order you have sent reads Pending, not sent — and a change that reduces the contract renders as -$740.52 rather than the $-740.52 a naive money template produces, with the cost section stating DEDUCT instead of ADD. Line items and any recorded signatures come down with the list, so the full agreement opens without a second wait.
- 1GET /api/client-portal/change-orders resolves the link to its project and returns rows from sent onwards
- 2Line items and recorded signatures are batched into the same response so the agreement renders without a second round trip
- 3The org id is re-stamped on the query as defence in depth
- 4Customer-facing status wording maps sent to Pending, with everything after a decision keeping its plain name
Mid-build scope changes were agreed on site and confirmed by text, which works until somebody disputes what was agreed or what it cost. Change orders appear on the customer's dashboard from the moment they are sent, showing what changed and what it costs. Drafts and withdrawn orders stay hidden because internal work-in-progress is not part of the customer's billing story, and a credit reads as -$740.52 rather than the $-740.52 a careless template produces.
- Verbal change agreements with no record
- Cost and schedule impact of changes never communicated
- Draft or withdrawn changes visible to customers
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →