Branded Change Order Agreement document

Every change order renders as a real agreement on the builder's letterhead: description, reason, cost adjustment, schedule adjustment, the binding clause and signatures.

What it is

A six-section document modelled on a paper Change Order Agreement but fully generated. Header with the tenant's logo and name, a meta block with project, owner, original contract date and CO number, then Description of Change with attachments, Reason for Change as a checklist with the chosen reason ticked, Cost Adjustment showing original price, ADD or DEDUCT and the new contract total with line items, Schedule Adjustment, the agreement clause, and the signature blocks.

Also called: change order form · variation agreement · written change order

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 scrolled to section 3 showing original price, ADD amount and new contract total. src/components/changeOrders/ChangeOrderAgreementDoc.tsx. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
How it works
  1. 1Every fact arrives via props so the same document renders in the portal, an admin preview and print
  2. 2Brand and contract facts are threaded from the tenant profile and the project
  3. 3It always renders light, because it is a paper document
  4. 4The signature area accepts a live pad or displays a recorded signature
Why we built it

A scope change mid-build used to produce a paper form filled in on a tailgate, or nothing at all. The customer gets the same document a builder would have handed them on site, generated in the builder's own branding rather than the platform's. It renders identically in the customer's view, the office preview and in print, so the two parties are never comparing different versions of the same agreement.

The problem
  • Change orders as informal notes rather than agreements
  • The customer, admin and printed versions of a change disagreeing
Sound familiar?
What you get
A branded, legally structured agreement for every change
Original price, adjustment and new total shown as explicit maths

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 →