Change Order Agreement — a real contract for extra work

New work mid-build gets its own branded, signable agreement — description, reason, cost adjustment against the original contract price, schedule impact, and signatures — instead of a verbal yes.

What it is

A generated document modeled on a paper Change Order Agreement: the builder's logo and name, a meta block (project, address, owner, original contract date, CO number, date issued), then six numbered sections — Description of Change, Reason for Change, Cost Adjustment, Schedule Adjustment, the Agreement clause, and Signatures. It is a pure presentation component so the same document renders in the customer portal, in the admin preview and in print.

Also called: change order · extras · customer wants to add something · scope change · variation

See it
New Change Order — Line Items
Line Items+ Add Line
KindDescriptionSupplierQtyUnitUnit PriceTotal
Material12×12 insulated overhead doors (2)Kaufman Door Supply2ea2480.00$4,960.00×
LaborFrame openings, headers, jamb & track installUnassigned18hr68.00$1,224.00×
Credit (subtracts)Delete one 3068 walk door from base scopeUnassigned1ea640.00-$640.00×
Markup %
12
Tax %
6
Subtotal$5,544.00
Markup (12%) + Tax (6%)$1,037.84
Total$6,581.84
Schedule+3 days
The full agreement: builder logo header, meta block, then the six numbered sections down to the signature blocks. ChangeOrderAgreementDoc.tsx. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
How it works
  1. 1Create the change order with a title, description, reason and days impact; add line items by kind (material, labor, markup, credit).
  2. 2Send it — the status locks to 'sent' and the customer is notified.
  3. 3The customer opens the agreement in their portal and either signs on the document or declines with a reason.
  4. 4Signing captures the signer name, drawn signature and the exact agreement text shown.
  5. 5Approved change orders can be invoiced separately, given their own payment plan, or folded into the existing schedule.
Why we built it

Migration 156 sets out the scenario without abstraction: 'a build is underway, the customer decides they now want a concrete slab for the back deck. That is not a line item on the existing invoice. It is new work, at a new price, that they have not agreed to yet — and it can be large enough to need its own signed contract.' It also names what was missing: 'a change order cannot currently have a contract of its own, so the only way to get one signed is to amend the original, which rewrites the terms of work the customer already accepted.'

The problem
  • Verbal scope changes with no signed authorisation
  • Extras billed at the end and disputed
  • Schedule slippage from added work never acknowledged in writing
  • Amending the original contract just to add work beside it
Sound familiar?
What you get
Extra work is authorised in writing before it starts
The cost adjustment is shown against the original contract price
Schedule impact stated and agreed
The original agreement stays intact
What's inside
The change order you review is the one they sign
Admin and customer render the exact same agreement component — after a period where the two screens showed materially different documents for the same change order.
Why the change is happening, on the record
Section 2 is a checklist of seven reasons with the chosen one ticked — customer request, code required, site condition, error correction, scope addition, scope reduction, other.
Original price, add or deduct, new contract total
Section 3 shows the original contract price, the ADD or DEDUCT amount, the resulting new contract total, the payment terms, and the itemised lines behind the number.
Days added to the schedule, agreed in writing
Every change order carries a days-impact figure that renders as its own section of the signed agreement.
Customer signs the change order on the document
From their portal the customer approves and signs the change order inside the document itself, or declines with a reason that lands on the record.
Split a change order across suppliers, sign each block
When a change order's line items belong to different suppliers, each supplier block gets its own signature — and the change order sits at 'Partially Signed' until they're all in.
A signing threshold so small extras don't need a ceremony
Set a dollar threshold above which a change order must be signed before work starts — and until you set one, every change order asks.
Three ways a change order reaches the customer's bill
Bill it on its own, give it its own payment plan, or fold it into the agreed schedule — each explained in plain language before you choose.
Change order vs amendment — and the chain between them
A contract knows whether it's the original project agreement, a change-order agreement, or an amendment of an earlier contract — and an amendment records which contract it replaces and why.
Change-order acceptance text frozen at signing
The acceptance wording the customer actually read is stored on their signature row, so later edits to the standard text never rewrite history.
Crew must acknowledge new scope before rolling stages
An approved change order has to be acknowledged by the crew lead before they can mark later stages complete.

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 →