Catch the change order that never got signed.
Missed change orders are the single biggest source of margin loss on residential builds. Kiron’s Ella tracks every CO against scope, approvals, and sub invoices — and blocks payment when an extra has no signed change order on file.
What change order verification actually means
Every residential build runs on three financial documents: the original contract, the approved change orders, and the sub invoices billed against them. Most builders manage the first two carefully and hope the third matches. It usually doesn’t.
Change order verification is the work of making sure those three documents stay aligned: every extra has a signed CO, every CO has a verified price, every sub invoice references work that’s in scope (contract or CO) and at the agreed price. Done manually across 15 vendors and three active projects, this is a part-time job for a senior PM. Ella does it automatically.
Four change order scenarios Ella catches
These are the four patterns we see most often on residential projects. Each one slips past manual review. None of them slip past Ella.
The verbal change order
Homeowner asks for upgraded fixtures on a walkthrough. PM says yes on-site. Three weeks later the plumber invoices for the upgrade — no signed CO, no approved price. Ella detects the invoice references work outside the original quote and blocks payment until the CO is signed.
The change order with a wrong price
Framing sub submits a $4,200 CO for added structural work. It's signed and filed. The invoice arrives at $4,800. Ella matches the invoice line items to the approved CO, finds the $600 delta, and flags it before approval.
The change order that never got signed
Architect issues a revised drawing requiring extra electrical work. Sub does the work. Owner never formally signs the CO. The invoice gets paid, but when the owner pushes back on the draw, the GC has no signed authorization. Ella flags work-in-progress against unsigned COs so this gets resolved before payment.
The cumulative CO creep
Twelve small COs across the project, each one reasonable. Together they push the contract from $1.4M to $1.62M — and nobody noticed because they were never totaled in one place. Ella tracks cumulative CO impact in real time so the surprise never happens.
How Kiron tracks change orders
Reads every CO and contract
Ella extracts CO number, description, price impact, schedule impact, and signing authority from every change order — AIA G701, custom forms, or plain email.
Tracks running totals per project
Original contract + every approved CO + every CCD pending price. Ella shows the cumulative impact in real time, so nobody is surprised at draw time.
Blocks invoices without a CO
When a sub invoice references work outside the original quote, Ella checks for an approved CO on file. If there isn't one, payment is held until the CO is signed.
Change order questions, answered
What is a construction change order?
A construction change order is a written modification to the original construction contract that documents a change in scope, price, or schedule. Common types include client-driven changes (homeowner upgrades), field-driven changes (existing conditions requiring rework), and design changes (architect or engineer revisions). The AIA G701 form is the most widely used standard change order document in U.S. residential and commercial construction.
Why do missed change orders cost so much?
When a subcontractor performs extra work without a signed change order, three things happen: the work gets billed on the next invoice, the GC or builder pays it because the work was actually done, and there's no formal authorization to bill the owner — leaving the cost stuck on the GC's P&L. A single missed CO of $5,000 wipes out the margin on a typical residential trade scope. Across a build with 15–25 trades, missed COs are one of the top sources of margin erosion.
How does Kiron track change orders?
Kiron's Ella reads every document that lands in your project inbox — contracts, change orders, sub quotes, and invoices. When a sub invoice references work beyond the original scope, Ella checks whether an approved change order exists on file. If it doesn't, she blocks the payment and flags it for review. If a change order exists but the price doesn't match the invoice, she flags the delta. Every flag is backed by the source documents, so your team has the evidence to push back or approve.
Does Kiron handle AIA G701 change order forms?
Yes. Ella reads AIA G701 change orders automatically — extracting the change order number, description of change, original contract sum, sum prior to this CO, adjustment, and revised contract sum. She matches each CO to the contract, validates the running totals, and tracks the cumulative impact across all approved COs on the project.
What's the difference between a change order and a change directive?
A change order is a fully executed modification — agreed in price and scope, signed by both parties before work begins. A construction change directive (CCD) authorizes work to start before final price agreement, typically when timeline can't wait for negotiation. Kiron tracks both: CCDs are flagged as pending price resolution, and sub invoices against them are held until the price is locked in.
How do I prevent change order disputes with subs?
Three habits matter: (1) require written change orders before extra work begins — Ella flags sub invoices without a CO on file so this gets enforced, (2) match every line item on every invoice to the original quote or an approved CO — Ella does this automatically, and (3) keep cumulative spend per vendor visible against the total of contract + approved COs — Ella shows this in real time. Most disputes start with one missed CO. Catch it at the document stage, not at the invoice stage.
How fast does Kiron start verifying change orders?
Most teams are live in a day. Forward your project email inbox to Ella and she begins reading every change order, quote, contract, and invoice immediately. Within 30–60 days she has a full baseline of your subs, contracts, and approved scope — and her flags get more precise the more documents she sees.
See Ella catch a missed change order on your project
Book 30 minutes. We’ll review your active projects and show you exactly where the COs are out of sync.
Book a 30-min demo