A change order is a small document that touches almost every system in the project. When it is processed cleanly, the budget updates, the schedule of values updates, the next draw reflects the new contract sum, the retainage math holds, and the audit trail is intact. When it is processed sloppily, the budget updates and nothing else does, and the resulting mismatch shows up two months later as a draw rejection, a tax surprise, or a buyer dispute. The difference between a clean change order and a sloppy one is twenty minutes of process at the time of signing, and the cost of getting it wrong is consistently larger than the value of the change order itself.
The immediate budget update
A signed change order modifies the contract sum and the budget at the same moment. The line item it affects is either added (a new scope), modified (a revised quantity or unit price), or replaced (a substitution). The contract sum increases or decreases by the net of the change. The budget tree updates so that the cost code for the affected work reflects the new authorized amount, and the prior amount is preserved as a snapshot for variance reporting.
The snapshot is the part most often skipped. Without a pre-change baseline, variance reporting against the original budget becomes impossible after the first change order, because there is no longer a fixed reference point. The right pattern is to keep the original budget as the anchor, the current budget as the working figure, and a clear chain of change orders between them. Every report should be able to ask which figure it wants and get a consistent answer.
The schedule of values update
The schedule of values (SOV) is the breakdown of the contract sum across line items, used by the lender to track draw progress. A change order that modifies the contract sum changes the SOV at the same time. The change is either an addition of a new line, a modification of an existing line, or a replacement.
The SOV update is what the lender uses to compute the next draw, which is why it has to be issued at the same moment the change order is signed. A change order signed on a Monday and an SOV update issued the following Friday is a five-day window in which the budget says one thing and the lender’s reference document says another. Most draw mismatches downstream trace back to a window like that.
The draw impact
The next draw after a change order signing includes the change order’s percent complete on the new or modified line. If the change order is for a $12,000 addition that will be performed over the next month, and the work is 40% complete at the next draw, the draw line for that change order is $4,800. The math is the same as any other line on the draw, with two complications.
The first complication is timing. A change order signed late in a billing period may not have any work performed before the next draw closes. The line on the draw is then 0% complete, which is fine, but the SOV must show the line so that the lender sees the new authorized amount and can plan for the future draw. Skipping the line because it is at zero is a common error and produces a SOV that does not match the contract sum.
The second complication is back-billing. A change order may authorize work that was performed before the change order was signed (the buyer verbally approved a scope change three weeks ago, the framer did the work, and the paperwork is catching up). The first draw after the change order signing then shows the change order line at a high percent complete because most of the work has already happened. This is allowed and sometimes unavoidable, but it should be documented in a note on the draw explaining the timing, because a lender seeing a brand-new line at 80% complete will ask the question.
Retainage on change orders
Retainage on change orders is typically the same percentage as the base contract, usually 5% or 10% depending on the lender and the jurisdiction. The change order document should state the retainage explicitly to remove ambiguity, but in practice the default applies. The retainage on each change-order draw is held back the same way as the base contract retainage and released at the same substantial-completion milestones.
The exception worth noting is the change order that occurs after substantial completion, on punch-list work or owner-requested post-occupancy items. The retainage rules on those change orders depend on the contract language and sometimes need to be renegotiated explicitly, because the base-contract retainage may already have been released. The cleanest pattern is to write the retainage treatment into the change order itself when the timing is unusual.
Tax implications
Change orders are generally treated like the base contract for tax purposes. The amounts are revenue or cost in the period in which they are recognized, the sales tax treatment follows the base contract treatment, and the 1099 reporting on subcontractor payments includes the change-order amounts as part of the annual total to the vendor.
Two patterns sometimes complicate this. A change order that substitutes one scope for another (replace tile with hardwood) at a net of zero may still need to be reflected on the 1099 totals for both the tile sub (negative or refund) and the hardwood sub (positive). The contract sum did not change but the vendor totals did, and the 1099 reconciliation needs to capture both. The other pattern is the change order that crosses a fiscal year. The work starts in December and finishes in January; the revenue recognition follows the percentage-of-completion method, and the change order is split across two tax years. The split is normal and the bookkeeping handles it, but the change order itself should be dated clearly so the period allocation is unambiguous.
The audit trail
Every change order generates a snapshot of the pre-change budget and the post-change budget, with the change order document linked to both. The snapshot is the artifact a lender, a buyer, or a tax preparer asks for when a question comes up six months later. The right structure carries the original contract sum, the running contract sum after each change order, the date of each change order, the parties who signed, and the cost-code allocation of each one.
The snapshot also matters for variance reporting. A budget-to- actual variance is meaningless if the budget figure has been updated multiple times without trace. The right pattern is to report variance against the current authorized budget for operational purposes (is the project tracking against what was approved) and against the original budget for executive purposes (how has the project drifted from the original plan). Both questions are valid; both require the snapshot to answer.
The buyer-facing change order on a custom build
On a custom build, the buyer-facing change order is a separate document from the internal budget change. The buyer document states the scope of the change in plain language, the cost impact, the timeline impact, and the signature blocks for the builder and the buyer. The internal budget change is the cost-code-level adjustment that flows through the accounting system. Both documents reference the same change order number, but they serve different audiences and contain different levels of detail.
The buyer-facing document should always state the timeline impact, even when the timeline impact is zero. A change order with no timeline statement is a common source of disputes later, when the project is two weeks late and the buyer points to a change order as the cause. A documented “no timeline impact” on the change order is the answer to that dispute. A documented “timeline extends by ten business days” is the answer when the change order does push the schedule.
What makes a change order clean
A clean change order has six elements, all of which fit on a single page.
| Element | Purpose |
|---|---|
| Change order number and date | Unique reference for the audit trail |
| Scope description in plain language | What is being added, removed, or substituted |
| Cost breakdown by cost code | Material, labor, equipment, markup, total |
| Timeline impact statement | Days added, removed, or none, with reasoning |
| Retainage treatment | Default to base contract or explicit override |
| Signatures from all parties | Builder, buyer, sub if applicable |
The single most common reason a change order causes problems downstream is that one of those elements is missing. A change order without a cost breakdown produces a budget update that is hard to allocate. A change order without a timeline statement produces a schedule dispute. A change order without all the signatures may not be enforceable at all.
The most common mistake
The single most common error in residential change-order processing is updating the budget without updating the schedule of values and the draw schedule. The budget reflects the new authorized amount, the draw schedule still reflects the old contract sum, and the next draw computes percent complete against the wrong denominator. The lender either rejects the draw because the math does not reconcile, or the lender approves it and the builder discovers at closing that the cumulative draws do not match the contract sum.
The fix is to treat the change order signing as an event that triggers three updates simultaneously: the budget, the SOV, and the draw schedule. All three update at once, the system records the change with a single timestamp, and the artifacts that go to the lender all reference the same contract sum and the same line breakdown. The discipline is procedural, not technical, and the cost of skipping it is consistently larger than the cost of the underlying change order.
Worked example: 926 Stratford
926 Stratford is a 1,784 SF spec build in Sweetwater, Tennessee, at a base contract sum of $430,250. During framing, the buyer requests an upgrade from carpet to hardwood in the great room and primary bedroom (roughly 380 SF). The flooring sub prices the upgrade at $7,200 net (the carpet allowance was $2,800; the hardwood is $10,000). The builder issues change order CO-003 for a net contract increase of $7,200, with no timeline impact because the work happens in the same window as the original flooring scope.
The clean processing on the day of signing: the budget updates so that cost code 09-600 (flooring) increases by $7,200, the snapshot of the pre-change budget is saved with reference CO-003, the SOV is reissued to the lender with the new line breakdown and the new contract sum of $437,450, and the draw schedule is updated so that the next draw computes percent complete against the new flooring line. The buyer-facing change order document is signed the same day, with the timeline statement “no impact to substantial completion date.”
The next draw includes the flooring line at 0% complete (the hardwood has not yet been installed) and the lender sees the new authorized amount on the SOV. Two weeks later, when the install completes, the following draw shows the line at 100% complete, retainage is held at 5% per the base contract, and the math reconciles cleanly against the contract sum of $437,450. At closing, the title work runs against the same contract sum and the same SOV, and there is no discrepancy to resolve.
The sloppy version of the same change order: the builder updates the budget but not the SOV, the next draw computes against the old contract sum, the flooring line is missing from the SOV, and the lender either rejects the draw or approves it with a note that creates an open question. By the time the question is resolved, the project is three weeks delayed in cash flow and the builder is fielding lender calls instead of running the next framing inspection. Same change order, different process, materially different outcome.
How BuilderGrid handles change orders
Every change order is a single record that triggers atomic updates to the budget, the SOV, and the draw schedule. The pre-change budget snapshot is captured automatically and linked to the change order. The buyer-facing PDF is generated from the same record with the plain-language scope, cost breakdown, timeline impact, and signature blocks. Retainage defaults to the base contract percentage and is editable per change order when the timing or scope warrants. The lender draw and the closing package both compute against the same authorized contract sum, and the audit trail traces every dollar back to the change order that authorized it.