Construction Change Order Management: Institutional Guide

A construction change does not begin when someone signs a change order. It begins when the project encounters an event that may alter scope, cost, time, sequence, risk or responsibility.

That event might be a revised drawing, owner request, concealed condition, design conflict, late response, material substitution, regulatory requirement, acceleration directive or correction of deficient work. Whether it becomes compensable depends on the contract, facts, notice, causation, documentation, authorization and agreement.

The institutional mistake is to collapse all of those questions into one spreadsheet called “change orders.” A log can list transactions. It cannot, by itself, govern the authority and recovery chain that turns a field event into an executed contractual right and, ultimately, collected cash.

The operating principle is simple: connect every state, but never confuse one state with another.

• An event is not entitlement.
• Entitlement is not an approved price.
• Price does not necessarily settle time.
• Direction is not always contractual authority.
• Incurred cost is not automatically revenue.
• Approved revenue is not billed revenue.
• Billing is not collection.

This article presents change management as an institutional control system: a repeatable operating model with explicit states, accountable decisions, protected evidence, financial discipline and a complete audit chain. It is operational guidance, not legal or accounting advice. The executed contract and advice from qualified professionals control.

The CHANGE control framework

Strong change control can be organized through six linked disciplines:

C — Capture the event and evidence

Create a contemporaneous record of what occurred, where, when, under which document version and with what immediate effect. Preserve the originating RFI, drawing, field instruction, photograph, daily log and meeting record.

H — Honor notice and contract process

Extract the governing notice period, recipient, delivery method, required content and preconditions. Send preliminary notice when facts are incomplete and supplement it as the record develops.

A — Analyze entitlement, cost, time and risk

Determine the causal basis, scope delta, pricing logic, schedule effect, mitigation and contractual position. Keep the analysis evidence-led; a system should not automatically declare every event compensable.

N — Name authority and decision status

Identify who may request pricing, direct work, approve a subcontract change, certify a modification and bind the owner or contractor. Record delegated limits and decision status explicitly.

G — Govern forecast, revenue and billing separately

Recognize probable cost exposure without assuming full recovery. Maintain proposed, probability-weighted where policy permits, approved, executed, billed and collected values as separate fields.

E — Execute, reconcile and close the record

Update the prime contract, downstream commitments, budget, forecast, schedule, schedule of values, billing and audit record. A signature is a transition—not the end of the process.

What a construction change order is—and what it is not

A change order is a written modification recording an agreed change to the construction contract. It typically identifies the scope revision and any adjustment to contract sum and contract time.

Under the AIA G701 process, execution indicates agreement among the owner, contractor and architect on the terms of the change, including any changes to contract sum or guaranteed maximum price and contract time. The form describes the change or references supporting exhibits and shows the resulting commercial adjustment. AIA G701–2017 instructions

That definition is narrower than everyday jobsite language. Teams often call every potential change, quote, directive or disputed condition a “CO.” The convenience creates reporting risk because the records have different legal, operational and financial meanings.

AIA describes G710, Architect’s Supplemental Instructions, as a vehicle for interpretations or minor changes that do not affect contract sum or time. AIA describes G714, Construction Change Directive, as a directive used when the owner and contractor have not agreed on price or time and expeditious implementation is required. AIA G714–2017

The executed contract controls. Do not import AIA terminology into a ConsensusDocs, federal, state, custom or subcontract form without verifying the governing language.

The eight commercial states of change

A mature operating system does not use one field called “approved.” It controls at least eight states:

1. Event: Something occurred that may alter the original agreement.
2. Notice: The event and potential effect were communicated in the required manner.
3. Entitlement: The contractual and factual basis for recovery was analyzed.
4. Pricing and time: Scope, cost, markup, credits and schedule effect were developed.
5. Work authorization: A person with appropriate authority directed or permitted performance.
6. Executed contract value: The modification was signed or otherwise formally determined.
7. Billing eligibility: The executed value was incorporated into the billing structure.
8. Collection and closeout: Cash, commitments, cost, schedule and records were reconciled.

Each transition needs a date, accountable owner, required evidence and permission rule. Without those gates, a subcontractor quote can be mistaken for owner-approved revenue, or an urgent verbal request can quietly become unrecoverable performed scope.

The controlled lifecycle

The lifecycle has two legitimate paths after analysis. If the parties agree, they execute the change and update the control systems. If changed work must proceed before final agreement, the contract may permit a valid directive; the team then segregates cost, preserves time and evidence, reports exposure and continues negotiation. If neither agreement nor valid direction exists, the correct status may be hold, clarify or dispute—not “proceed and sort it out later.”

Step 1: Capture the field event immediately

The first record should state facts, not conclusions:

• date and time discovered;
• location and affected work;
• drawing, specification, RFI, submittal or contract reference;
• document revision in force;
• observed condition or instruction;
• person communicating the instruction;
• current crew, equipment and material status;
• immediate safety or protection needs;
• photographs and marked-up documents;
• potential cost or schedule effect; and
• required response date.

“Owner changed wall” is weak. “At 10:20 a.m. on July 14, the owner’s representative requested relocation of partition A-12 by four feet at Level 2, Room 214; framing was 70% complete under A-201 Revision 3” is traceable.

Daily logs, meeting minutes, RFIs, emails and photographs can corroborate the event, but they do not necessarily satisfy contractual notice.

Step 2: Preserve contractual notice

Change provisions commonly require written notice within a defined period, to a named recipient, through a stated channel and often before affected work proceeds. Requirements vary materially.

A strong preliminary notice:

• identifies the event and relevant contract provision;
• states that cost and/or time may be affected;
• distinguishes known facts from unresolved facts;
• reserves the right to supplement;
• requests direction;
• identifies immediate protection or mitigation; and
• uses the required delivery method.

Avoid two extremes. Waiting for perfect backup can allow a notice period to expire. Treating every clarification as a dramatic claim damages credibility. The controlled response is a factual preliminary notice followed by documented supplements. Counsel should review project-specific notice requirements and templates.

Step 3: Establish cause and contractual basis

Classify the event before pricing it:

• owner-directed scope;
• design revision, omission or conflict;
• differing or concealed condition;
• code or authority requirement;
• delay, disruption or suspension;
• acceleration or resequencing;
• substitution or value engineering;
• allowance reconciliation;
• quantity variation;
• contractor-requested convenience;
• corrective work;
• force majeure or another excusable event; or
• disputed responsibility.

This is not clerical labeling. Classification affects entitlement, required evidence, allowable markup, schedule treatment and likely cost bearer.

Stress-test the position. Was the work already required? Was the issue reasonably inferable at bid time? Did the contractor contribute? Was notice timely? Did an authorized person direct the work? Can causation be demonstrated? Was mitigation reasonable? Does the contract waive or limit recovery?

The output is not a binary legal conclusion generated by software. It is a documented commercial position with evidence, open questions, owner and next decision.

Step 4: Define scope before price

Ambiguous scope produces ambiguous pricing and later dispute. A proposal should identify:

• exact added, deleted or revised work;
• source drawings, specifications, sketches, RFIs and directives;
• assumptions, exclusions and boundary conditions;
• demolition, rework, protection, access, temporary work and cleanup;
• adjacent-trade effects;
• design, permit, testing, commissioning and closeout effects;
• procurement and lead-time effects;
• schedule and sequencing assumptions; and
• validity period.

For deletions, assess avoided direct cost and cost already incurred. A deductive change is rarely the original estimate run backward: procurement commitments, mobilization, cancellation, restocking and completed work can alter the credit.

Step 5: Price direct and indirect effects

A transparent estimate separates labor, burden, material, equipment, subcontract work, freight, tax, bonds, insurance, supervision, project overhead, recoverable home-office overhead, escalation, time-related general conditions, markups, allowable contingency and credits.

These percentages are examples, not recommended rates. Contract definitions control recoverable cost and markup. Do not apply markup to a base that already contains the same burden or fee.

Segregate changed-work cost

Once work begins, use a dedicated cost code, work order or verified ticket. FAR 43.203 explains in the federal context that changed-work costs may require separate accounting and identifies categories including nonrecurring engineering or rework, distinct added work, labor and material. FAR 43.203

Private projects may not follow FAR, but the control principle is sound. Without segregation, the contractor cannot reliably price actual cost, defend the proposal or prevent the base contract from absorbing the change.

Step 6: Quantify time—not merely dollars

A proposal that says “zero days” without analysis may surrender a legitimate time position. A proposal that automatically adds days equal to work duration is equally weak.

Evaluate the affected activity or milestone, status at the event date, remaining float, critical or near-critical path effect, procurement lead time, resequencing, stacking and congestion, overtime or acceleration, seasonal effect, inspection and commissioning, cumulative effects and mitigation.

Possible positions include no time effect, a defined extension, a reservation pending schedule analysis, concurrent delay, acceleration cost without extension, extension without direct added cost or disputed impact. Tie the analysis to the contemporaneous accepted schedule and preserve the update used.

Step 7: Verify authority before proceeding

The person requesting work may not have authority to change the contract. Field urgency does not enlarge contractual authority.

Configure an authority matrix by action, role and dollar limit. Separate the ability to:

• report a potential change;
• request pricing;
• direct emergency protection;
• direct changed work;
• approve a subcontract change;
• concur or certify in a professional role;
• bind the contractor; and
• change prime contract sum or time.

On federal contracts, FAR 43.202 assigns issuance of change orders to the contracting officer unless authority is properly delegated to an administrative contracting officer. That provision does not govern private work, but it illustrates why authority cannot be inferred from presence, title or urgency. FAR Subpart 43.2

Proceeding before final agreement

Sometimes waiting for full negotiation would delay the project. The contract may provide a directive mechanism. AIA’s G714 instructions describe a process for directing work before agreement on contract sum or time; the contractor proceeds under the directive, while the adjustment remains to be resolved. AIA G714–2017 instructions

When properly directed work begins before agreement:

• verify the directive and authority;
• state objections or reservations promptly;
• assign separate cost codes;
• use daily force-account or time-and-material tickets;
• obtain daily verification where possible;
• photograph progress;
• track equipment and material;
• record schedule effects;
• submit periodic exposure updates; and
• price the work before closeout.

Silence creates symmetric risk: the owner loses visibility into growing exposure, while the contractor loses contemporaneous proof.

Cost exposure and revenue must remain separate

Every potential change has multiple financial states: forecast or incurred cost, proposed revenue, approved revenue, executed contract value, billed revenue and collected cash.

The approved contract value is $144,000—not $240,500. Yet the project forecast must still recognize the supported $216,000 cost exposure. Waiting for revenue approval before acknowledging probable cost overstates margin. Treating all proposed revenue as certain does the same.

Accounting treatment and revenue recognition depend on the company’s reporting framework and professional judgment. The commercial system should supply clean facts and controlled states; it should not silently make the accounting conclusion.

Aging is a governance signal

Pending changes become harder to resolve as memories fade, personnel change, costs accumulate and billing windows pass. Track event-to-notice time, pricing cycle time, response age, days since last action, work performed before approval, unapproved cost, schedule decisions outstanding and billing lag after execution.

A small disputed change at 120 days may be more dangerous than a large seven-day proposal. Aging should therefore be paired with value, exposure, evidence quality and next-action ownership—not used as a decorative dashboard metric.

The executive change register

Executives need a register that answers four questions:

1. What happened and what evidence supports it?
2. Who can decide, and what decision is due next?
3. What cost, time and recovery exposure exists now?
4. What has become contract value, billable value and cash?

Required fields include unique ID, title, source event, cause, responsibility, notice status, scope owner, pricing due date, forecast cost, proposed and approved revenue, requested and approved days, work authorization, execution status, billed and collected value, aging, risk classification, next action, owner, due date and links to authorization.

Avoid one vague status called “pending.” Controlled states may include identified, notice issued, pricing, internal review, submitted, under review, revision requested, partially approved, approved, rejected, disputed, executed, billed, collected and closed. Not every project needs every state; every project does need explicit authority over status transitions.

Common change-order failures

Verbal work without confirmation. The field proceeds from a conversation, then the parties disagree about scope, price or authority.

Late notice. The team waits for complete backup while a contractual deadline expires.

Pricing before scope. Negotiation begins before assumptions, exclusions and affected documents are fixed.

Dollars without time. Price is settled while schedule impact remains silent.

Time without cost. An extension is granted without addressing extended supervision, equipment, escalation or other recoverable time-related cost.

Upstream approval without downstream change. The owner approves a change but related subcontracts remain unmodified—or the reverse.

Changed cost hidden in the base job. Performed work is charged to original cost codes, weakening both forecast and recovery evidence.

Pending revenue treated as certain. The forecast reports margin that may never be approved.

Permissions too broad. A field or subcontract user can set approved or executed status without delegated authority.

Closing at signature. Contract, budget, schedule, commitments, billing and collection remain unreconciled.

A decision-oriented weekly change-control meeting

The meeting should review new events and notice deadlines, work proceeding without price, proposals due, overdue design or owner responses, items aged 30/60/90 days, largest unapproved exposures, schedule decisions, approved-but-unexecuted changes, executed-but-unbilled changes and unreconciled downstream commitments.

Every item leaves with a decision, named owner and due date. Reading the log aloud is administrative theater; resolving the next constraint is governance.

Performance metrics that support judgment

Interpret them carefully. A low conversion ratio may reflect weak entitlement, missing evidence, owner behavior, early-stage submissions or aggressive pricing. Metrics locate the investigation; they do not replace commercial judgment.

What change-order software should do

A risk-aware platform should create a potential change from an RFI, drawing revision, field log, meeting item or instruction while preserving the source record and version. It should:

• track notice deadlines and delivery evidence;
• separate scope, entitlement, cost, time and authorization;
• collect subcontract proposals without granting approval rights;
• support detailed labor, material, equipment, subcontract, markup and credit;
• segregate forecast cost before revenue approval;
• model requested, determined and approved days;
• enforce role and dollar-limit permissions;
• preserve proposal revisions rather than overwrite history;
• maintain proposed, approved, executed, billed and collected values;
• update prime contracts, commitments, budgets, forecasts, schedules and billing through controlled actions;
• expose aging and unapproved cost at project and portfolio level; and
• retain an immutable audit history.

AI can summarize records, identify missing backup, draft proposal narratives and flag stale items. It should not invent entitlement, approve pricing or replace the authorized commercial decision.

Implementation checklist

Before mobilization

• Extract notice, change, claim, markup and time-impact requirements.
• Build the authority and delegation matrix.
• Agree numbering, definitions and state transitions.
• Map prime and subcontract workflows.
• Establish dedicated change cost codes.
• Configure permissions, dollar limits and audit history.

When an event occurs

• Capture facts, source records and versions.
• Issue timely notice through the required channel.
• Determine immediate safety, protection and mitigation.
• Confirm authorization before changed work.
• Open cost and schedule tracking.

During pricing

• Freeze the scope basis.
• Obtain subcontractor backup.
• Validate quantities, rates, burdens, markup and credits.
• Analyze schedule effect and general conditions.
• Reconcile proposed recovery to forecast cost.

At approval

• Verify signatures and authority.
• Update contract sum and time.
• Modify downstream commitments.
• Update budget, forecast and schedule.
• Incorporate the change into the billing structure.

At closeout

• Confirm changed scope completion.
• Reconcile cost, revenue, billing and collection.
• Preserve unresolved reservations.
• Settle downstream obligations.
• Close only when the control chain is complete.

Frequently asked questions

What is a construction change order?

A written contract modification documenting agreed scope and any stated adjustment to price and time.

What is the difference between a change request and a change order?

A request or proposal seeks agreement. A change order records the agreement once properly executed.

Is an RFI a change order?

No. An RFI seeks information. Its response may reveal or direct changed work, but the contract’s change process must still be followed.

Is a proposal request authorization to proceed?

Usually not. It commonly requests price and time information. Check the governing contract and instruction.

Can a superintendent approve a change order?

Only if documented delegated authority and applicable policy permit it. Many do not have that authority.

Should a contractor proceed without a signed change order?

Only when the contract, a valid directive, emergency duty or other proper authorization requires or permits it. Preserve notice, reservations, cost and schedule evidence.

How should pending change costs affect the forecast?

Supported probable cost should be visible even when related revenue is pending. Proposed, approved, executed, billed and collected values should remain separate.

When is a change closed?

When scope is complete, the modification is executed or the issue formally resolved, cost and revenue are reconciled, billing and collection are addressed, downstream commitments are settled and required records are preserved.

The operating principle

Change orders are not paperwork created after the real work. They are the commercial control system for departures from the original agreement.

The strongest process preserves five separations:

• event from entitlement;
• authorization from negotiation;
• cost from revenue;
• price from time; and
• approval from billing and collection.

When these states remain connected but distinct, owners see exposure before it becomes a surprise, contractors protect legitimate recovery and executives forecast margin with less fiction.

Syntecton’s role as a Construction Operating System is not to make a prettier change log. It is to connect the field event, governing document, notice, commercial position, evidence, authority, cost, time, contract modification, forecast, billing and collection in one controlled chain.

Put one live change through the control test

Select one material pending change and ask:

1. Can the team retrieve the originating event and document version?
2. Is notice compliance visible?
3. Are entitlement, scope, cost and time separate?
4. Is the person directing or approving the work demonstrably authorized?
5. Is performed cost segregated from the base job?
6. Are proposed, approved, executed, billed and collected values distinct?
7. Does the forecast reflect supported exposure without inventing revenue?
8. Is the next decision owned and dated?
9. Will approval update downstream commitments and billing?
10. Can an executive reconstruct the full record without asking the project team?

If the answer to any material question is no, the organization does not have a change log problem. It has a control-system gap.

Sources and editorial notes

• AIA G701–2017 Change Order instructions
• AIA G701–2017 summary
• AIA G714–2017 Construction Change Directive
• AIA G714–2017 instructions
• Federal Acquisition Regulation, Subpart 43.2
• Federal Acquisition Regulation 43.203, Change Order Accounting Procedures

All numerical examples are illustrative. Contract terminology, notice, authority, recoverability, schedule treatment and accounting conclusions are project- and jurisdiction-specific.