Start with the approved baseline before touching this month's billing
A change order changes more than the number at the bottom of a log. It can change the approved schedule-of-values baseline, the amount the GC can bill this period, the remaining balance available on the contract, and the retainage held against the work. If the original SOV is overwritten, the review loses the comparison that explains how the contract got from the first approved value to the current one.
Keep the original approved line number, description, scheduled value, and billing allocation as the baseline. Then attach the signed amendment, directive, or other contract-authorized approval and show the delta: what was added, deleted, moved, or repriced. The revised SOV should let a reviewer answer what the owner approved, where the value now sits, and what amount remains without opening five unrelated spreadsheets.
For every approved change, make these four impacts visible:
- Approved SOV baseline: the original line values plus the documented change.
- Current-period billing: the portion earned and supported in this application.
- Remaining balance: the revised contract value less completed and approved amounts.
- Retainage: the contract-defined holdback on eligible amended work, current and to date.
Decide whether the amendment needs redistribution or only a log entry
The practical question is not whether the item has a change-order number. The question is whether it changes what the contract permits the GC to earn, bill, retain, or carry as remaining work. If it does, the approved amendment and the SOV must tell the same story. If it does not, a status-controlled log entry may be all the record needs for now.
The unsafe middle ground is an approved change that appears in the log but nowhere in the revised SOV, or a pending request that is already being billed because a field team expected approval. The change-order log is a control record; it is not a substitute for the contract amendment when the economics or scope have changed.
Reconcile the current draw to the amended SOV
Once the amendment is approved, compare the current G703 to the latest SOV, not the version that happened to be in last month's folder. The current-period amount should reflect supported work on the amended scope, completed-to-date should include prior approved billing, and the remaining balance should fall from the revised contract value—not from an obsolete baseline.
Roll the line items into the G702 and check the payment history. A change can make a line look under-billed while another line is over-billed, especially when work was moved between trades or split into a new line. Reconcile scheduled value, current work, prior work, stored materials, retainage, payments, and balance at the line level before trusting the summary total.
Original approved contract
Baseline SOV totalApproved additions and deletions
Signed amendment deltaRevised contract value
Current approved SOVLess completed, billed, and retainage amounts
Remaining balanceCatch the flags that make an amended packet hard to defend
Change orders are where a familiar monthly billing routine can stop being a reliable control. The reviewer should look for scope, math, and document mismatches that may not change the requested total today but will make the project history impossible to explain later.
Scope creep
Work is being billed or forecast without a signed amendment, approved directive, or documented contract authority.
Line-item drift
Descriptions, values, line numbers, or billing allocations change without a traceable revised SOV and approved delta.
Retainage mismatch
Amended work uses a different rate or base in the G703, G702, or payment history without support in the contract documents.
A clean review does not erase an exception. It describes the issue, cites the source document, assigns the decision to the right person, and keeps the packet from being certified as if the issue did not exist. That exception trail is especially useful when an owner, lender, architect, or auditor asks why a line moved between periods.
Run the admin-support review before the GC signs
Admin support does not replace the GC's certification. It makes the decision easier to make by assembling the approved contract documents, comparing the current packet to the prior cycle, and keeping the change-order history connected to the SOV and pay application. The review should happen in the same order every cycle so a busy month does not turn into a skipped control.
Approval: tie each billed change to its amendment, directive, or approved status.
SOV: compare the latest line numbers, descriptions, values, and allocation to the approved baseline.
Math: reconcile current work, prior work, remaining balance, retainage, G703, and G702.
Exceptions: list scope creep, line drift, missing backup, and unresolved retainage decisions before signature.
Johnston Admin Management Services can run this review at $45/hour, billed to the exact minute through Clockify. The deliverable is a decision-ready packet: source documents linked to the checks, amended values reconciled, and open items separated from the work the GC can certify.
Frequently asked questions.
When does a change order need a signed amendment before it changes the SOV?
Treat the change as an amendment when it changes contract value, scope, time, payment terms, or another term that the owner and GC must approve under the prime contract. The signed or otherwise contract-approved amendment should be the source document for the revised SOV. A field request, estimate, or email asking for a price is not the same as approved authority to bill.
When should an approved change order be redistributed across SOV line items?
Redistribute an approved change order when the new work materially changes the scope, scheduled values, billing sequence, retainage basis, or remaining balance of one or more existing lines. Add a clearly identified new line when that makes the scope easier to audit. The revised SOV should show the original baseline, approved change, and new total without hiding the history in a single overwritten number.
When is a change-order log entry enough without changing the SOV?
A log-only entry can be enough for a request, pending pricing, rejected item, or approved administrative clarification that does not change contract value, scope, billing sequence, or the SOV allocation. Keep the log status and decision date visible, and do not bill the item until the contract documents authorize it. If the entry changes what can be earned or retained, it belongs in the approved amendment and SOV review.
How do I catch schedule-of-values line-item drift after a change order?
Compare the current G703 line number, description, scheduled value, prior completed amount, current work, stored materials, and balance with the latest approved SOV—not with last month’s spreadsheet alone. Flag lines that were renamed, split, merged, rounded, billed ahead of sequence, or increased without a matching approved change. Reconcile the revised line totals to the amended contract value and the G702 summary.
How should retainage be calculated on amended work?
Read the contract and approved amendment for the retainage rate, eligible base, treatment of stored materials, and any release or reduction. Apply the governing basis consistently to the new work, show current retainage and retainage-to-date, and reconcile those figures between the G703 and G702. Never assume amended work inherits a rate or exemption that the signed documents do not support.
What should admin support review before the GC signs a pay application with change orders?
Admin support should tie each billed change to its approval status, amendment or directive, revised SOV line, current-period amount, remaining balance, retainage basis, and backup. The reviewer should also compare the change-order log with the contract value, check for scope creep or line drift, reconcile G703 to G702, list unresolved exceptions, and return a signature packet that lets the GC make the final certification decision with the trail in view.
The pre-signature version.
- Freeze the original approved SOV as the baseline, then show every approved change separately before calculating the revised contract value.
- Decide whether the change affects contract value, scope, billing sequence, remaining balance, or retainage before treating it as log-only.
- Use the amended SOV to reconcile current-period billing, completed-to-date work, remaining balance, and G702/G703 totals.
- Flag scope creep without an amendment, renamed or drifting line items, and retainage math that does not follow the signed documents.
- Give the GC an exceptions list and a source-backed signature packet before certification.