How to Track Change Orders in Job Cost Reports

Track change orders in job cost reports by giving every proposed change its own ID, preserving the original estimate, and showing approved budget revisions separately from pending exposure. Link the same ID to field records, commitments, bills, billing requests, and approval documents. This lets an owner see what changed, what it will cost, and what remains unresolved.

A revised contract amount alone cannot answer those questions. For an established contractor, the reporting objective is to connect scope decisions with the expected cost to finish, while keeping customer approval, accounting revenue, invoices, and collections in distinct fields.

Preserve the original job baseline

Retain the accepted estimate and original cost budget with their version dates. Then create a register containing the change ID, scope description, customer price requested, estimated cost by phase, time impact, document links, status, responsible person, and next action date. Include deductive changes as well as additions.

The AIA G701–2017 change-order sample distinguishes the original contract amount, previously authorized changes, the current change, and the resulting amount. It also provides for a time adjustment and signatures. That is a useful document-specific model for preserving a contract bridge; your own contract governs its approval process and required notices.

For management reporting, keep the cost-budget bridge beside that contract bridge. A $20,000 customer price addition does not imply a $20,000 increase in the cost budget. Estimate the labor, materials, subcontract work, equipment, and other attributable costs separately. Our contractor cost-code guide explains how to keep phases and cost types consistent.

Use status fields that describe separate decisions

Define statuses such as identified, priced, submitted, approved, rejected, and withdrawn. Store the date and supporting document for each transition. Also maintain separate fields for authorization to proceed, agreement on price, and agreement on time. A field instruction can create an immediate operational issue while compensation or schedule remains disputed.

Do not make the register's approved label a legal conclusion. Ask the project lead to check the contract and obtain appropriate advice for disputed direction, notice deadlines, or signatory authority. AIA's sample is one form, not a universal rule that every change needs the same signatures.

Give accounting a separate review field for financial-statement treatment. Neither an internal status nor customer approval automatically determines recognized revenue. The report described here tracks operational budgets and exposure; it does not prescribe a revenue-recognition method or determine an enforceable payment right.

Capture pending costs while approval is unresolved

Require timesheets, purchasing records, and subcontract amendments to carry the job and change ID. Retain the underlying invoice, receipt, or time record. The IRS recordkeeping guidance explains that supporting documents substantiate book entries. This proposed change register is a management procedure, rather than an IRS reporting format.

Show pending costs incurred, remaining commitments, and additional estimated work in separate columns. Define remaining commitments as the unincurred portion of purchase orders or subcontracts. When a bill becomes incurred cost, reduce the remaining commitment for that same work. Reconcile those columns so a subcontract is not counted both as a full commitment and as posted invoices.

Pending work still needs visibility if the customer has not approved its price. Have accounting assess how incurred amounts belong in the books under the reporting basis. Keeping a request out of the approved budget is not a reason to hide actual activity or omit it from the final-cost forecast.

Original example: approved budget and pending exposure

Hypothetical management worksheet: assume an established specialty contractor starts a job with a $200,000 contract amount and a $150,000 cost budget. Approved Change 01 adds $20,000 to the contract and $14,000 to the cost budget. Pending Change 02 requests $15,000 from the customer, but no price agreement has been reached. Figures are illustrative dollars, not client results or suggested margins.

Budget bridge	Contract amount	Cost budget
Original baseline	$200,000	$150,000
Approved Change 01	$20,000	$14,000
Current approved total	$220,000	$164,000
Pending Change 02, separately tracked	$15,000 requested	$11,000 forecast exposure

Assume original scope plus Change 01 has $100,000 incurred cost, $40,000 remaining commitments, and $24,000 additional uncommitted cost to finish. Its forecast is $164,000. Separately, Change 02 has $4,000 incurred, $5,000 remaining commitments, and $2,000 additional cost to finish: $11,000 total exposure. None of the commitments overlaps incurred cost or the additional estimates.

The full cost forecast is therefore $175,000: $104,000 incurred, $45,000 remaining commitments, and $26,000 additional estimated cost. Pending exposure is already included in that total; adding another $11,000 would double count it. The approved cost budget remains $164,000 in this worksheet, leaving $11,000 forecast cost above that budget.

The approved contract amount less all forecast cost is $45,000: $220,000 less $175,000. If Change 02's full requested price is ultimately agreed, and no costs change, the hypothetical contract amount would become $235,000 and that planning difference would become $60,000. Neither figure is earned revenue, recognized gross profit, or collectible cash. Both are management scenarios requiring the stated assumptions.

Reconcile the register with the job report

Review one change from start to finish: its field request, priced scope, approval record, cost detail, remaining commitment, and billing status. Investigate missing IDs, duplicate entries, and costs charged to the original scope. Preserve corrected mappings so a later reviewer can explain the movement.

When a change becomes approved, transfer its budget and forecast classification without adding its existing costs again. Retain the original proposed amount and decision history. If rejected, remove unsupported expected recovery from management scenarios and continue to show incurred cost and any unavoidable commitments for review.

Give every unresolved change an owner and next action date, and reconcile totals at each reporting cutoff. Our construction job gross-profit guide covers the separate calculation using recognized revenue and attributable cost. TaxBowl's contractor job-costing service can help connect your change register, source documents, and accounting reports for a clearer owner review.

Video: change orders and job-cost reporting

This AktionReplay tutorial demonstrates an older Sage 100 Contractor example connecting approved changes, revised cost budgets, cost codes, and posted costs. Screen layouts and workflows may differ in current systems. Use it as a reporting illustration; your contract and accounting policies determine actual approvals and financial-statement treatment.