Table of Contents
- Why the Right Document Type Is the GC’s First Line of Defense
- What Is a Change Order (CO), and When Is It the Only Correct Choice?
- What Is an RFI, and When Does It Cross the Line Into a Scope Change?
- What Is a Field Order or ASI, and What Authority Does It Actually Carry?
- What Is a Construction Change Directive (CCD), and How Does a GC Respond?
- The GC Decision Tree: Matching Every Field Condition to the Right Document
- Non-AIA Contracts: How the Decision Tree Shifts Under ConsensusDocs, CMAA, and Custom Owner Contracts
- Downstream Sequencing: What the GC Must Do Within 24 to 48 Hours for Every Document Type
- Frequently Asked Questions
- Conclusion: Pick the Right Document Every Time and Protect the Project From Both Ends
Here’s an uncomfortable truth every experienced project manager already knows: the document you choose in the first 24 hours after a scope change request determines whether you get paid. Not your estimate. Not your crew’s efficiency. The document. Construction scope change documentation isn’t a back-office compliance task. It’s the mechanism that converts field reality into contract rights, and the wrong mechanism costs real money.
Consider a $28 million commercial tenant improvement project in Atlanta. The owner’s rep verbally directed the GC to relocate 140 linear feet of ductwork to clear a beam that wasn’t on the drawings. The field super logged it as an RFI response. Fourteen weeks later, the owner disputed the $62,000 cost claim on the grounds that no change order existed and the RFI hadn’t authorized any work. The GC couldn’t prove otherwise. That’s not bad luck. That’s the wrong document at the wrong moment.
This post gives you a working decision tree: four instruments, five field scenarios, and a clear protocol for matching each situation to the right paperwork before the first shovel moves.
Why the Right Document Type Is the GC’s First Line of Defense
The Cost of Mis-documenting a Scope Change
Mis-documenting a scope change costs U.S. general contractors an estimated 2 to 4% of total project revenue annually, according to industry surveys from the Construction Industry Institute. On a $50 million project, that’s $1 million to $2 million in unrecovered direct costs, not counting schedule claims or subcontractor back-charges.
The failure mode is almost always the same. A GC uses the convenient instrument rather than the correct one. An RFI goes out when a change order request should have followed. A field order gets signed without a reservation of rights. Work starts under a verbal direction with no contemporaneous record at all.
Rather than treating each document type as a bureaucratic option, treat it as a legal instrument with specific rights attached. Each instrument has a distinct role. Each has limits. Crossing those limits doesn’t just create confusion. It creates waiver.
How Document Choice Affects Lien Rights, Claim Windows, and Cash Flow
Every state in the U.S. ties mechanic’s lien rights to contract price. If your change order isn’t executed, the additional scope may fall outside your lien coverage. In most states, the lien window runs from last date of furnishing labor or materials, but disputed scope with no written authorization creates a factual ambiguity that courts regularly resolve against the contractor.
Claim windows are equally document-dependent. AIA A201 Section 15.1.3 requires written notice of a claim within 21 days of the event giving rise to it. The clock starts when the triggering condition occurs: not when you discover the cost impact, not when the owner disputes it. Miss that notice window with the wrong document type and you’ve forfeited the claim. Cash flow follows the same logic. Executed change orders get included in the next pay application. Disputed directives sit in accounts receivable for months.
The best documentation practice is one that creates a clear, timestamped chain from field condition to contract modification. Build that chain from the first hour.
A Quick Primer on the Four Instruments (CO, RFI, Field Order/ASI, CCD)
Four instruments govern scope change documentation on most U.S. commercial construction projects. Each has a specific function in the contract machine.
A Change Order (CO) is a formal, bilateral amendment to the contract. It modifies price, schedule, or scope and requires signatures from the owner, architect, and contractor. An RFI, or Request for Information, is a clarification tool: it asks a question and records the answer, but it does not authorize work or modify the contract. A Field Order or Architect’s Supplemental Instruction (ASI) is a unilateral directive for minor scope adjustments that the architect or owner believes fall within the existing contract price. A Construction Change Directive (CCD) is a unilateral directive for work that cannot wait for price agreement: the owner orders the work, the contractor performs it, and pricing is resolved afterward through a defined process.
Four instruments. Four very different risk profiles. The decision tree below tells you exactly when to use each one.
What Is a Change Order (CO), and When Is It the Only Correct Choice?
Key Components of a Valid Change Order Under AIA G701
A valid change order under AIA G701 contains six required elements: project identification, a description of the change in work, the adjustment to the contract sum (including any agreed markup), the adjustment to the contract time, the method of determining price, and signatures from all three parties. Missing any element doesn’t just make the change order incomplete. It can render it unenforceable in a dispute.
Ask whether your current change order template captures all six elements every time. Most GC-generated templates omit the time adjustment field when the change has no obvious schedule impact. That omission becomes critical six months later when you’re arguing constructive acceleration and the owner points to an executed CO with a blank time field as evidence of schedule waiver.
AIA G701 also requires the change order to reference the original contract. On projects using custom owner forms, verify that the form meets these functional requirements even if it doesn’t use G701 language.
Mutual Agreement Requirement: Why Both Signatures Matter
A change order is not a change order until all parties sign. That’s not a technicality. It’s the legal threshold that separates a binding contract modification from an unexecuted proposal. A GC who performs work based on a countersigned-only-by-the-architect change order has performed work without owner authorization under most AIA contract structures.
Rather than chasing signatures after the work is done, build a policy: no crew mobilizes on change order scope until the document is fully executed or a CCD has been issued. This policy feels like friction. It protects $40,000 claims from evaporating at final billing.
Picture a mid-rise MEP retrofit in Denver where the GC performed $88,000 in added fire suppression scope under a change order signed only by the architect. The owner later claimed the architect lacked authority to bind the contract. Two years of litigation followed. The lesson isn’t that architects can’t be trusted. The lesson is that the change order process exists precisely to ensure the party with the obligation to pay has committed to paying.
When a Change Order Is Required vs. When It Is Merely Convenient
A change order is required whenever the scope, contract sum, or contract time changes. It’s not optional in those circumstances. It is merely convenient when the parties want to document a scope clarification that doesn’t alter any of those three elements: in that case, an ASI or amended RFI response is the appropriate instrument.
The distinction matters because over-relying on change orders for minor clarifications creates administrative backlog and can slow field decisions. Rather than writing a change order for every architect’s answer to a detail question, reserve the CO for genuine contract modifications. Use the lighter instruments for everything else. But use them correctly.
What Is an RFI, and When Does It Cross the Line Into a Scope Change?
The Proper Role of an RFI: Clarification, Not Authorization
An RFI’s proper role is information: it asks a contract question and records a contract answer. It does not create new scope. It does not authorize cost. An RFI response from an architect saying “install per detail 3/A501” clarifies the existing design intent. It does not become authorization to perform work that wasn’t already in the contract. That distinction is the line most GC field teams cross without realizing it.
The change order vs. RFI construction question has a clear answer: if the response to your RFI reveals that the work required is different from what the contract documents contemplated, the RFI has become a trigger event, not an authorization. Stop. Issue a cost and schedule impact notice. Follow with a change order request or a notice of potential claim, depending on whether the owner agrees there’s an impact.
Not a clarification. It is a scope discovery.
RFI Documentation Best Practices That Protect the GC
The best RFI documentation practice creates a factual record that survives a dispute two years after project close. That means every RFI must include: a specific question tied to a specific drawing or specification reference, a clear statement of the field condition that prompted the question, an explicit identification of whether the GC believes a cost or schedule impact may result, and a response deadline that aligns with the construction schedule.
Evaluate your current RFI log for these four elements. Most GC teams write the question but omit the cost impact flag. That omission signals to the owner’s team that the GC didn’t believe there was an impact, which becomes a credibility problem at the claim stage.
RFI documentation best practices also require that responses be formally acknowledged in the log. An unanswered RFI with a missed response deadline is itself a compensable delay event under most AIA contracts. Log the miss. Preserve the right.
How an RFI Becomes a Trigger Event for a Change Order or CCD
An RFI becomes a trigger event the moment its response reveals: additional scope not in the contract, a conflict between contract documents, or a condition that differs materially from what the contract represented. All three scenarios require the GC to act within the AIA 21-day notice window.
The protocol is simple. Close the RFI as answered. Open a change event in your change management log. Issue written notice to the owner that the RFI response has identified a potential cost and schedule impact. Follow with a change order proposal or request for CCD issuance. Don’t let the RFI stay open as a holding category. Open RFIs that have cost implications are the most common source of waived claims in construction disputes.
What Is a Field Order or ASI, and What Authority Does It Actually Carry?
Architect’s Supplemental Instructions (ASI) vs. Owner-Directed Field Orders
An ASI is issued by the architect and covers minor changes in the work that don’t modify the contract sum or contract time. An owner-directed field order is a directive from the owner or owner’s representative for work that the owner believes is within scope. The critical difference: an ASI comes from the design authority, while a field order comes from the contracting party. That distinction affects who has the authority to determine scope and price.
Both instruments carry real risk for the GC if accepted without scrutiny. The field order vs. change order question hinges on one test: does this directive change what the contract already requires, or does it merely clarify how to perform it? If it changes what’s required, the instrument should be a change order or CCD. Not a field order. Not an ASI.
When a Field Order Is Within Contract Scope (and When It Is Not)
A field order is within contract scope when it addresses a means-and-methods question or a minor detail clarification that doesn’t expand the GC’s obligation. It is not within scope when it requires additional labor, materials, equipment, or time that the contract didn’t contemplate. The challenge: the party issuing the field order always believes it’s within scope. That belief is not binding.
The GC’s obligation is to evaluate the directive against the contract documents and make an independent judgment. Rather than assuming the owner’s characterization is correct, review the directive against the scope of work, the specifications, and the drawings. If the directive requires work not covered by those documents, respond in writing within 24 hours with a notice that you believe the directive constitutes additional scope requiring a change order.
The One Step Every GC Must Take Within 24 Hours of Receiving a Field Order
Within 24 hours of receiving any field order or ASI, the GC must issue a written acknowledgment that either confirms the directive is within scope or identifies a potential cost and schedule impact. This single step is the most frequently skipped step in U.S. construction practice and the most expensive omission in disputes.
The acknowledgment doesn’t need to be a formal legal document. An email to the owner’s rep and the architect that says “we’ve received Field Order 14, we’re reviewing for scope and cost impact, and we’ll notify you of any impact within 3 business days” is sufficient to start the clock and preserve rights. Silence is not. Proceeding without that notice is a constructive waiver of your right to claim additional compensation.
Running a GC team that’s buried in field directives, RFIs, and change events? See how Sinq centralizes every instrument in one change management workflow at sinq.co.uk/features.
What Is a Construction Change Directive (CCD), and How Does a GC Respond?
CCD vs. Change Order: The Signature and Consent Distinction
A Construction Change Directive is a unilateral instrument: the owner and architect sign it, but the contractor does not need to agree to it for it to be effective. That’s the essential distinction from a change order. A CCD is issued when the parties agree that the work must proceed but can’t agree on price or schedule impact. It orders work and defers pricing resolution to a defined process.
Under AIA A201 Section 7.3, a CCD may direct changes within the general scope of the contract. The contractor is obligated to proceed. The pricing mechanism defaults to: mutual agreement, or if no agreement is reached, the architect’s determination of reasonable cost, subject to dispute resolution. The GC’s rights aren’t waived by proceeding. They’re preserved precisely because the CCD process is the designated mechanism for disputed-price work.
Not waiver. It is a structured preservation of rights.
Forced Account Work and Time-and-Materials Documentation Under a CCD
When work proceeds under a CCD without an agreed price, the GC must document it as forced account or time-and-materials work from day one. That means daily logs capturing: labor hours by trade and classification, equipment used with hours of operation, materials installed with delivery tickets, and supervisor time allocated to the directive. This documentation is the evidentiary foundation for the cost claim that follows.
Consider a scenario: a $4.2 million concrete parking structure project in Phoenix where the owner issued a CCD for 900 square feet of additional elevated deck. The GC proceeded without daily T&M logs. At final billing, the GC submitted a cost estimate. The owner rejected it and countered with an architect’s determination of $31,000. The GC believed the actual cost was $67,000. Without contemporaneous records, the GC couldn’t disprove the architect’s number. They settled for $44,000. Daily logs would have supported the full claim.
The Cardinal Change Rule: When a CCD Becomes an Improper Directive
A CCD must be within the general scope of the contract. When the cumulative effect of CCDs and change orders fundamentally alters what the contractor agreed to build, the contractor may have a cardinal change claim: a breach of contract theory that the owner has changed the project so materially that the original contract no longer governs.
Courts have found cardinal change where cumulative change order scope exceeded 25 to 30% of original contract value on federal projects. Commercial project thresholds vary by jurisdiction. The GC’s obligation: track cumulative change volume as a percentage of original contract sum and issue a written notice when that percentage reaches 15% as a precautionary marker. This isn’t litigation posturing. It’s project record-keeping that preserves options.
How to Dispute a CCD While Keeping Work Moving
The GC has the right to dispute a CCD’s pricing and scope characterization while continuing to perform the work. The procedure under AIA A201: proceed with the work, maintain T&M records, and submit a written dispute through the claims process. Don’t stop work. Stopping work in response to a disputed CCD exposes the GC to a claim for delay and potentially a termination for default.
Rather than treating the CCD dispute as adversarial from day one, submit a detailed cost proposal within 7 days of receiving the directive. Show your math. Reference your subcontractor quotes. Attach your schedule impact analysis. If the owner and architect reject it, you’ve created the factual record for arbitration or litigation. If they accept it, the CCD converts to a change order and the issue closes.
The GC Decision Tree: Matching Every Field Condition to the Right Document
The decision tree for construction scope change documentation operates on five branches. Each branch maps a specific field condition to a specific instrument, with a default action protocol. Apply it before the work starts. Not after.
Branch 1: Both Parties Agree on Scope and Price: Use a Change Order
When the owner agrees that additional scope is required and agrees to the price and schedule impact, the correct instrument is a fully executed change order. There’s no ambiguity here. The best outcome in any scope change situation is mutual agreement before work starts. Execute the change order. Attach it to the prime contract. Mirror it downstream to affected subcontractors within 48 hours.
Branch 2: Ambiguity or Missing Information, No Cost Impact Yet: Use an RFI
When the field condition reveals an ambiguity or gap in the contract documents, and the GC can’t yet determine whether a cost impact exists, use an RFI. But flag the RFI with a potential cost impact notation. Don’t wait for the response to decide whether to flag it. The flag preserves the 21-day notice window while the question is being answered.
Branch 3: Owner or Architect Directs Minor Work Within General Scope: Use a Field Order/ASI
When the directive covers minor detail clarification that doesn’t expand scope, a field order or ASI is appropriate. Acknowledge it in writing within 24 hours. If your review reveals it’s not minor, escalate immediately to the change order request process. Don’t let a week pass while you decide.
Branch 4: Owner Directs Work, No Price Agreement, Work Cannot Wait: Use a CCD
When the owner directs scope that you believe is additional, there’s no agreement on price, and the project schedule doesn’t allow for a delay in starting the work, request that the owner formalize the direction as a CCD. If they won’t, issue your own written reservation of rights: “We are proceeding with this work under protest and reserve all rights to recover additional compensation.” Start T&M logs immediately.
Branch 5: Differing Site Conditions or Constructive Change: Preserve Rights First, Then Choose the Instrument
Differing site conditions and constructive changes require an extra step before document selection: a written notice of the condition itself. Under AIA A201 Section 3.7.4, the contractor must provide prompt notice before conditions are disturbed. Once notice is issued and the site condition is documented with photographs and logs, the follow-on instrument depends on the owner’s response: a change order if they agree, a CCD if they direct work without agreement, or a formal claim if they deny the condition qualifies.
Evaluate every differing site condition with this sequence: notice first, documentation second, instrument third. Skipping the notice step is the single most common way GCs forfeit otherwise valid differing site condition claims.
Ready to see how Sinq maps every branch of this decision tree into an automated workflow? Explore the full feature set at sinq.co.uk/features.
Non-AIA Contracts: How the Decision Tree Shifts Under ConsensusDocs, CMAA, and Custom Owner Contracts
ConsensusDocs 200: Key Differences in CCD and Change Order Language
ConsensusDocs 200 uses the term “Construction Change Directive” with a process that differs from AIA in two important ways. First, ConsensusDocs gives the contractor more explicit rights to submit cost proposals before proceeding, with a defined 10-day window. Second, the pricing fallback under ConsensusDocs defaults to a cost-plus-overhead-and-profit formula rather than the architect’s determination. Both differences favor the GC in disputed-price scenarios. Know which contract you’re on. The decision tree branches differently.
Rather than assuming AIA protocols apply to every project, read the change management article of every contract before the project starts. Assign a project manager the specific task of identifying: the change order form required, the CCD process and timing, the claim notice window, and the default pricing methodology. This review takes two hours. It can save $200,000.
CMAA and Design-Build Contracts: When the Decision Tree Collapses Into Fewer Instruments
Design-build contracts often collapse the four-instrument framework into two: a contract modification (equivalent to a change order) and an owner directive (equivalent to a CCD). The RFI function moves inside the design-builder’s own design-construction coordination process. There’s no external architect to issue ASIs. This simplification reduces document types but doesn’t reduce the GC’s obligation to document scope changes formally.
On CMAA-administered projects, the Construction Manager’s authority to issue directives and approve change orders varies significantly by project. Some CMs have full change order authority. Others can only recommend. Know the CM’s contract before relying on a CM-approved change order as binding on the owner.
Custom Owner Contracts: Red Flags in Change Management Clauses to Catch Before Signing
Custom owner contracts are the highest-risk document environment for GCs. The most dangerous provisions are: notice windows shorter than 14 days, requirements that change order proposals be submitted before work begins with no CCD mechanism, clauses that make the owner’s representative’s determination of price “final and binding,” and dispute escalation requirements that must be exhausted before any work stoppage is permitted.
Ask your contract counsel to mark every change management clause in a custom owner contract before you sign. The markup takes less time than recovering one disputed change order claim. For reference on how these provisions compare across contract families, see how ‘change order’ maps to ‘variation’ on cross-Atlantic projects for additional context on how contract language shapes rights across project types and geographies.
Downstream Sequencing: What the GC Must Do Within 24 to 48 Hours for Every Document Type
Mirroring a CCD Into Commitment Change Orders (CCOs) to Subcontractors
When a CCD arrives from the owner, the GC’s first downstream obligation is to identify which subcontractors are affected and issue commitment change orders (CCOs) within 24 to 48 hours. A CCO is the mechanism that formally directs the subcontractor to perform the work and preserves the GC’s right to pass costs up to the owner. Without a CCO, the subcontractor may claim they were directed verbally, and the cost documentation becomes fragmented.
The CCO should mirror the CCD’s scope description, reference the CCD number, direct the sub to proceed on a T&M basis pending pricing, require daily cost logs, and confirm the sub’s reservation of rights for additional compensation. Four elements. All required. Many GC teams issue the CCO but omit the T&M log requirement. That omission means the sub’s costs aren’t formatted for the owner’s review process, and the GC absorbs the reconciliation cost.
Avoiding Constructive Waiver Claims When Passing Field Orders Downstream
A field order or ASI that the GC accepts without reservation can create a constructive waiver not just for the GC’s own claim but for the sub-tier claims as well. If the GC’s written acknowledgment to the owner says the field order is within scope, the GC cannot later pass a subcontractor’s additional cost claim up to the owner on the grounds that the field order constituted additional scope. The acknowledgment forecloses that argument.
Rather than issuing blanket acknowledgments of field orders, review each directive before acknowledging it. If the field superintendent can’t evaluate it within 24 hours, send a holding notice: “Received, under review, will respond within 3 business days.” Then get the sub’s input before committing to a scope characterization in writing.
Notice of Intent to Claim: When and How to Preserve Sub-Tier Rights
When a subcontractor identifies a cost impact from a field directive, the GC’s obligation is to pass that notice up to the owner within the prime contract’s notice window. This is the most mechanically complex part of change management: the sub’s notice to the GC may arrive on day 15, and the GC’s notice window to the owner may be only 21 days from the triggering event, leaving 6 days to review, evaluate, and transmit.
Build a workflow that shortens this cycle. Sub notices of potential impact go to the project manager within 24 hours of the sub identifying them. The PM reviews within 48 hours and decides whether to pass the notice up to the owner. If the PM isn’t available, there’s a designated backup. This isn’t bureaucracy. It’s a cash protection machine.
How Sinq Automates Downstream Change Order Sequencing for GC Teams
Sinq’s change management platform is built around this exact downstream sequencing challenge. When a prime-level CCD or change order is logged in Sinq, the system automatically identifies affected subcontract packages and prompts the project team to issue CCOs to each affected sub. Notice deadlines are tracked against the prime contract’s clock. T&M log templates are pre-formatted to match the owner’s required documentation format.
Rather than managing four separate spreadsheets, a change log, a subcontract log, a T&M log, and a notice calendar, GC project managers work from a single change event record that tracks all downstream obligations in real time. For a deeper look at the full change order technology landscape, see the complete 2026 change order software playbook.
Frequently Asked Questions
What is the difference between a Change Order and a Construction Change Directive?
A Change Order requires signatures from all parties and reflects mutual agreement on scope, price, and time. A Construction Change Directive is a unilateral owner directive that orders work when parties can’t agree on price: the contractor must proceed, but pricing is resolved through a defined process afterward.
The practical difference is consent and timing. A CO is consensus before work starts. A CCD is authorization without consensus, with price resolution to follow. GCs who treat them as interchangeable create documentation gaps that collapse claims at final billing. The CCD process under AIA A201 Section 7.3 is specifically designed for the “work can’t wait” scenario. Use it correctly: proceed, document T&M, and submit your cost proposal within 7 days.
Can an RFI be used to authorize additional work on a construction project?
No. An RFI cannot authorize additional work. An RFI is a clarification instrument only. It documents a question and an answer, but it doesn’t modify the contract, authorize new scope, or create a payment obligation for work outside the existing contract documents.
The change order vs. RFI construction confusion arises because RFI responses sometimes describe work that turns out to be additional scope. That’s a trigger event: the RFI has revealed additional scope, not authorized it. The GC must follow with a change order request or notice of potential claim. Performing work based solely on an RFI response and then billing it as additional scope is one of the most expensive reasons U.S. change orders get rejected.
What happens if a general contractor proceeds with work under a Field Order without reserving rights?
If a GC proceeds with field order work without issuing a written reservation of rights, and the work later proves to be additional scope, the GC may have constructively waived the right to additional compensation. Courts in most U.S. jurisdictions will interpret silence, or compliance without objection, as acceptance of the owner’s characterization that the work was within scope.
The reservation doesn’t need to be aggressive. A simple written statement that “we are proceeding with Field Order 12 and reserve all rights to claim additional compensation if this work is determined to be outside the original contract scope” is sufficient to protect the GC’s position. Send it within 24 hours. Every time. Without exception.
Do ConsensusDocs contracts use the same CCD process as AIA contracts?
No. ConsensusDocs 200 uses a similar Construction Change Directive concept but with two key differences: the contractor has an explicit 10-day window to submit a cost proposal before being required to proceed, and the default pricing fallback is a cost-plus formula rather than the architect’s determination.
These differences are significant in practice. The 10-day proposal window gives GCs more leverage to negotiate before work starts. The cost-plus fallback is generally more favorable to the GC than an architect’s discretionary determination. When you’re on a ConsensusDocs project, use both provisions actively. Don’t default to AIA protocols on a ConsensusDocs contract: the two systems have different rights architectures.
How quickly must a GC issue commitment change orders to subcontractors after receiving a prime-level CCD or Change Order?
Best practice is 24 to 48 hours. The GC’s subcontract notice obligations often mirror the prime contract’s notice windows, which means delay in issuing CCOs to subs can result in the sub missing their own notice deadline, leaving the GC holding the cost with no recovery path from the sub-tier.
On projects with complex sub-tier structures, build a contact matrix that maps every change order category to the affected subcontractors and the relevant subcontract notice clause. When a CCD arrives, the PM activates the matrix and issues CCOs the same day. This process feels like overhead. It prevents the scenario where a $35,000 electrical sub claim gets forfeited because the CCO arrived on day 23 of a 21-day sub-notice window.
Conclusion: Pick the Right Document Every Time and Protect the Project From Both Ends
The Decision Tree as a Daily Field Habit, Not a Reactive Fix
Construction scope change documentation isn’t a crisis management tool. It’s a daily field habit that keeps every change event in the correct legal channel from the moment it surfaces. The decision tree in this post doesn’t require a legal degree to apply. It requires discipline: before any crew touches additional scope, someone with authority asks which branch applies and issues the right document.
Teams that build this habit capture an estimated 15 to 20% more of their legitimate change order revenue than teams that document reactively. That’s not a projection. That’s the consistent finding across GC firms that have implemented formal change event workflows with clear instrument-selection protocols. The infrastructure exists. The question is whether your team uses it on every project, every time.
Honest concession: the decision tree doesn’t make every change order dispute go away. Owners will still dispute pricing. Architects will still characterize scope conservatively. But the GC with the right document at the right moment starts every dispute from a position of strength. The GC with the wrong document starts from a position of explanation. Those are very different starting points in arbitration.
Next Steps: Auditing Your Current Change Management Workflow
Start with a simple audit: pull the last 10 change events on your current largest project. For each one, identify which instrument was used, whether it was issued within the required notice window, whether downstream CCOs were issued within 48 hours, and whether T&M documentation exists for any CCD-directed work. Most GC teams find at least 3 of 10 events with a documentation gap. That’s the baseline problem this decision tree solves.
Rather than rebuilding your entire change management process from scratch, implement the decision tree as a one-page field reference for every project manager and superintendent. Combine it with a change event log that tracks instrument type, notice date, sub notification date, and pricing status. These two tools cost nothing to implement. They protect everything.
Want to see how Sinq’s platform enforces this decision tree automatically across your entire project portfolio? Schedule a 20-minute demo with no setup required at sinq.co.uk/contact.
The right document at the right moment. Every time.