Construction change order process from notice to billing

A field instruction, an accepted price, and a revised billing amount can reach approval on different dates.

Kartik Deshpande··6 min read

A construction change order process should carry a proposed scope change from identification through authorized review, agreement, and the resulting contract and cost updates. Keep permission to proceed, agreement on price, and agreement on time distinct. A signed field ticket can document work without establishing every contractual approval needed to change the amount billed to the owner.

Start from the project’s executed agreements. They establish the notice requirements, authority, deadlines, and available change mechanisms. The process below is an operational framework for retaining evidence and assigning handoffs, not a substitute for those terms. AIA documents provide examples of distinct instruments; not every project uses them or the same allocation of responsibility.

Identify the changed work and preserve the notice trail

Have the person discovering the issue record the location, affected work, date, drawing or specification revision, and source of the instruction. Link the RFI, photo, meeting record, or field report that explains the proposed departure from the contract scope. A description such as “extra electrical” leaves reviewers unable to distinguish new work from correction of original work.

The project manager should check the required notice route and assign responsibility for the submission. Record when notice was sent, to whom, and under which contract reference. If the timing or entitlement is disputed, retain that status and the evidence for authorized review. Do not turn a log entry into a conclusion that a notice satisfies the contract.

Use one event identifier to connect the evidence while preserving each document’s own ID. The construction change order log supplies the tracking structure; this process concerns the decisions that move a record between states. A populated row is not evidence that the recipient accepted the request.

Define scope before comparing price and schedule effects

Have the responsible technical reviewer confirm what will change, what remains, and any exclusions. Attach the relevant revision and identify affected trades. Record whether the submission replaces an earlier proposal or adds to it. Keeping both proposals in an active total would count the same scope twice.

Ask the cost owner to separate labor, material, equipment, subcontract, and other applicable charges under the agreed pricing basis. Identify markup, credits, allowances, and taxes as the contract requires. A lump sum can be an agreed basis, but a reviewer still needs to know which scope it settles and whether future claims for excluded work remain possible.

Have the schedule owner assess the affected activities and supporting dates. Additional labor hours do not establish an extension of contract time without showing the schedule effect. Keep a request for more time visible even if the price is agreed, rather than allowing one “approved” field to imply that both questions are settled.

Separate a proposal from authority to proceed

AIA Contract Documents’ G701 change order instructions place execution after the owner and contractor, with the architect’s concurrence, agree on the change and adjustments to contract sum and time. That describes the role of this particular instrument. Check the project agreement and authorized signatories before treating a proposal acceptance or email as equivalent.

AIA’s G714 construction change directive instructions address directed changes when proposed adjustments have not been agreed. This illustrates why directed work and a fully agreed change order need separate statuses. If the applicable contract allows work to proceed while price or time remains unresolved, preserve that authority and the unresolved adjustment together.

Keep separate approval questions visible
Scope evidence
What changes
Proceed authority
Who directs work
Agreed adjustment
Price and time
Work may be directed before its final adjustment is agreed. Retain the applicable authority and unresolved price or time status in the same event history.

For emergency or disputed conditions, use the escalation and notice process in the governing contract. Assign an authorized owner to decide the response and preserve contemporaneous cost and time evidence. A general rule to stop all work until every price is signed can be inappropriate where the contract provides a different direction mechanism.

Track owner revenue and subcontract cost separately

Consider a hypothetical change to reroute a pipe around an unforeseen obstruction. A subcontractor proposes $24,000 and two added working days. The contractor submits a $28,000 owner proposal under the assumed contract pricing rules. Those are separate proposed adjustments to separate agreements, not one approved change because they share an event ID.

RecordExample statusReporting treatment
Field recordWork documentedEvidence of performed scope, subject to review
Subcontract proposal$24,000 proposed; time unresolvedPotential cost exposure, not an executed amendment
Owner proposal$28,000 submitted; no agreement yetPending revenue request, not approved contract value
Executed adjustmentsAmounts and time as finally agreedUpdate each affected agreement from its own approval

If the contractor authorizes the subcontract adjustment before the owner agrees to the revenue change, the cost commitment can exist while owner recovery remains uncertain. That status difference needs to remain visible in the margin review. The illustrative $4,000 spread between proposals is $28,000 - $24,000; it is not earned margin, cash received, or proof of recoverability.

When the owner accepts a revised amount, link that executed record to the event and supersede the pending proposal in the active revenue total. Apply the same discipline to the subcontract side. If only part of the scope is settled, identify the agreed part and leave the remainder open rather than closing the entire event.

Inspect one change event

Bring the proposal, field evidence, and approved records for one event into a workspace and check whether their amounts and states reconcile.

Update commitments, cost outlook, and billing from evidence

After each agreement is executed under the project’s rules, the responsible owner updates its contract or commitment record. Retain the executed amount, effective date, time adjustment, and superseded version. Compare the update with the signed record rather than assuming that document completion also updated every financial application.

The controller should distinguish costs already incurred from remaining exposure, while the project manager updates remaining work assumptions. The committed costs article explains why commitments and actual costs cannot be added without accounting for their overlap. A change can affect both categories as work progresses and invoices arrive.

For billing, check the governing requirements and any agreed payment treatment for unresolved work. An approved cost or field ticket does not by itself establish an owner billing entitlement. Keep the schedule of values, prior billings, and current application tied to the relevant contract records, and retain any amount still under review.

Close an event only after its unresolved parts are assigned

At the change review, identify missing notices, unpriced work, unresolved time requests, and approvals awaiting downstream entry. Give each issue an owner and next action. Age the relevant status from its own event date; resetting a due date should not erase how long a proposal has awaited a decision.

Closing the documentation record should not erase a remaining dispute or unpaid amount. Preserve the final scope, accepted adjustments, rejected amounts, and outstanding obligations with their separate statuses. A partial revision (when it settles only part of an original proposal) needs a clear link to the scope and amount that remain unresolved.

Where Permute connects change and cost evidence

Permute sells connected business data and custom applications. We can combine supplied change logs, approved documents, and accounting exports, matching project and event references under declared rules. The review can retain separate owner and subcontract statuses rather than forcing them into one approval column.

We can apply definitions for pending exposure, approved adjustments, and incurred cost across repeated project reporting. A controller can ask which approved changes have no matching financial update and inspect the event, signed record, and source transaction. What a context layer actually does describes the connection and evidence mechanism behind that review.

Leave contract authority and entitlement with authorized reviewers

This reporting workflow does not determine entitlement, satisfy notice requirements, authorize changed work, or execute contract amendments. Your project team and its advisers must interpret the governing agreements and resolve disputes. Missing approvals stay unresolved in the analysis; neither a matched document nor an AI summary can supply the authority absent from the source record.

Move the evidence with each change decision

A working change order process keeps the scope, proceed authority, price, and time evidence connected while preserving their separate states. Update owner and subcontract agreements from their own authorized decisions. Reconcile those changes with commitments, remaining cost, and permitted billing. Close the event with the record of what was settled and an owner for anything that remains open.

Review a change-to-cost handoff

Bring one event whose field, contract, and accounting records disagree to a focused data review.

Questions about construction change order process

Does an RFI become a change order?

An RFI can identify a condition or clarification that leads to a proposed change. Its existence does not establish an agreed contract adjustment. Follow the applicable notice, authorization, and agreement process and preserve the RFI as supporting evidence.

How should deductive changes be handled?

Retain the same scope and authority evidence for a reduction as for an addition. Preserve the agreed sign of the adjustment and identify any related credits or removed commitments. Do not net an unresolved addition against a proposed deduction and label the result approved.

Is a signed field ticket enough to bill the owner?

A ticket can support evidence of the work and quantities recorded, subject to its wording and authority. Whether it supports billing depends on the governing agreement and the approvals it requires. Keep its signature purpose separate from agreement on contract value or time.