Construction Change Order Approval Workflow: A Record-First Guide

Start with the contract, not the form

Before work is priced or directed, identify the contract clause, authorized representatives, notice procedure, required supporting records, pricing method, schedule-analysis requirement, and rules for emergency or disputed work. Private projects, public projects, and different jurisdictions can use materially different procedures.

FAR 43.102 provides a bounded federal example: only contracting officers acting within their authority may execute federal contract modifications. FAR 52.243-4 provides a federal construction example built around written change orders and written contract modifications. These provisions do not create a universal private-project rule or replace the actual project contract.

• Name the people who may request, direct, price, review, approve, reject, and implement a change.
• Separate a field observation, request for information, proposal request, construction change directive, and executed change order.
• Record notice requirements and timing from the governing contract; do not copy a deadline from another form or federal clause.
• Define when work may proceed before final price or time is agreed, and who may authorize that exception.

The eight-stage record-first workflow

Use one durable change record from first signal through reconciliation. Each stage should preserve the source documents, actor, timestamp, status, open questions, and reason for the next action.

• 1. Identify the trigger and authority: record the event, originating document, contract clause, requesting party, and person authorized to respond.
• 2. Lock current scope and source revisions: preserve the relevant drawings, specifications, addenda, submittals, RFIs, directives, baseline budget, schedule, and accepted scope before comparing a change.
• 3. Preserve notice and directive history: record when notice was given, how it was delivered, what work was directed, whether price or time remained unresolved, and who acknowledged it.
• 4. Quantify scope, cost, and schedule impact: separate added, deleted, substituted, and unchanged work; show quantities, labor, equipment, materials, subcontractor quotes, markups, credits, lead times, and schedule logic.
• 5. Route technical and commercial review: assign design questions, field verification, cost validation, schedule review, funding checks, and contract compliance to accountable reviewers.
• 6. Record authorized approval or rejection: capture the final scope, amount, time adjustment, reservations, effective date, signatures or approval evidence, and decision rationale.
• 7. Align downstream records and field work: update drawings, budget, commitments, schedule, procurement, work packages, safety planning, and field instructions from the approved revision.
• 8. Separate implementation, invoicing, payment, and closeout: reconcile installed work, pay-application records, credits, retainage, payment-rail results, and as-built or closeout documents without treating one state as proof of another.

Quantify impact without hiding uncertainty

A useful proposal shows the delta from the controlled baseline. It should not bury assumptions in a lump-sum total or present a preliminary estimate as an approved amount.

For federal work, FAR 43.204 describes administration of change orders and prompt definitization, including records of important events. That is a useful public example of preserving the path from an unpriced direction to a supplemental agreement, but project teams must follow the procedures that actually govern their contract.

• Scope: source revision, affected work package, inclusions, exclusions, substitutions, temporary work, and downstream dependencies.
• Cost: quantity and unit basis, labor classifications and hours, equipment, materials, quotes, credits, taxes, bonds, insurance, overhead, profit, and stated assumptions.
• Schedule: affected activities, logic ties, float treatment, procurement dates, access constraints, mitigation options, and the requested time adjustment.
• Uncertainty: open design questions, pending quotes, field conditions, allowances, ranges, escalation exposure, and the date through which the proposal is valid.

Use an authorization matrix

A role appearing in the workflow does not automatically have contract authority. Build a project-specific matrix that distinguishes who can request information, direct work, validate quantities, recommend a commercial position, approve budget, modify the contract, and authorize payment.

The matrix should also define monetary or schedule thresholds, delegation limits, required joint approvals, prohibited self-approval, and what happens when the authorized person is unavailable. Keep the evidence of authority with the decision record.

Keep change and payment states separate

Status labels should describe observable events rather than imply a result. An approved change is not automatically installed, invoiced, paid, or reconciled. A paid invoice does not by itself prove that all closeout obligations are complete.

• Observed: a potential change signal exists, but scope and authority are not yet established.
• Notified: the required notice was issued and its delivery evidence is preserved.
• Directed: an authorized instruction exists, with price or time either agreed or explicitly unresolved.
• Proposed: scope, cost, and schedule impact have been submitted for review.
• Reviewed: technical and commercial reviews are complete or their open exceptions are identified.
• Authorized or rejected: the responsible party recorded the decision and governing terms.
• Implemented and verified: the current approved revision is reflected in field and project-control records.
• Invoiced, paid, and reconciled: each event is recorded separately against provider and accounting evidence.
• Closed: credits, claims, drawings, logs, commitments, schedule, and final records agree or remaining disputes are explicitly preserved.

Watch for common workflow failures

Most record failures occur at handoffs. A conversation becomes a directive, a draft price becomes a budget commitment, or completed field work is treated as proof that contract authority existed.

• Verbal direction with no actor, time, scope, or authority record.
• Pricing against superseded drawings or specifications.
• A change log that stores only a title, amount, and status but no source evidence.
• Cost review completed without schedule, procurement, access, or sequencing impact.
• One party editing another party's submitted commercial record without retaining the original.
• Work proceeding while the unresolved price, time, or reservation is invisible.
• Approval, invoice, payment, and settlement collapsed into one ambiguous status.
• AI-generated summaries or risk scores presented as contract authority or field direction.

A current scale example, with strict boundaries

On August 25, 2026, Louisiana Economic Development announced a planned SpaceX campus in Vermilion Parish that could include multiple launch complexes, propellant facilities, power, vehicle processing, and housing. CBS News, carrying Associated Press reporting, independently confirmed the announcement and its early schedule targets.

The announcement is useful only as a scale illustration: a program with many facilities, utilities, interfaces, and future packages makes revision and authority records important. NEXUS is not involved in the project, the announcement does not establish that the project has a change-order problem, and financing, environmental review, execution, and schedule outcomes remain uncertain.

Where AI and NEXUS fit

AI may compare revisions, draft a scope summary, organize proposal support, identify missing fields, flag inconsistent status records, and prepare a review queue. Reviewers should be able to open the source, correct the output, record uncertainty, and understand why an item was flagged.

AI may not approve a change, bind a party, direct work, alter the contract, certify installed work, or release payment. Those are governed and authorized human actions.

NEXUS is currently a beta, AI-assisted construction-operations platform. Its public product facts support a restrained connection among project documents, field evidence, shared review, records, and human-authorized decisions. The workflow in this guide is an editorial control model, not a claim that every stage is automatically enforced by the current product.

Pilot the workflow on one representative change

Test the model on a completed or representative change with known documents and outcomes. Preserve the existing baseline, run the eight stages, and compare the resulting record with the contract file, schedule, cost report, field documentation, invoice, and accounting evidence.

• Authority coverage: every directive and decision maps to a verified role and delegation.
• Source coverage: every material scope, quantity, cost, and schedule conclusion opens to the controlling revision.
• Exception closure: unresolved questions have an owner, status, due date, and disposition.
• State integrity: proposed, authorized, implemented, invoiced, paid, and reconciled are not conflated.
• Correction effort: material AI or manual corrections remain visible with actor, time, and reason.
• Closeout agreement: change log, budget, commitment, schedule, drawings, field record, invoice, and provider/accounting evidence agree or document the remaining dispute.