Change Order Management: The Documentation Gap That Produces Construction Disputes

Where construction disputes actually originate When a construction firm engages litigation counsel over a contested change order, the dispute is rarely about whether the change happened. The work was performed; the customer used the result; the cost was real. The dispute is almost always about whether the firm has the documentation to prove the change was authorized, the price was agreed (or was reasonable in the absence of explicit agreement), and the work performed matched what was authorized. The litigation outcome turns on the documentation, and the documentation was either built during the project or it does not exist now. There is no retrospective fix. The construction firms we audit, when we are engaged on a back-office diagnostic or in the context of a sponsor-side investment review, almost universally have a change-order process that exists on paper and degrades under operational pressure. The process specifies that all changes require written authorization before work proceeds. The process specifies that pricing be submitted within a defined window, with cost detail and schedule impact. The process specifies that the change order be executed using AIA G701 or an equivalent contract-modification form. In practice, the process is followed when the conditions are favorable, and bypassed when they are not. The bypass is where the dispute originates. This guide describes the change-order lifecycle that holds under pressure, the AIA documents and their relationship to progress billing, the documentation expectations that survive litigation and audit, the two failure patterns we see most often, and the linkage between change-order management and the ASC 606 revenue-recognition discipline that determines whether change-order revenue can be recognized in the financial statements. The change-order discipline pairs with the job-cost discipline and the WIP schedules, change orders flow into both, and weakness in change-order documentation surfaces in both. The construction industry has a name for the work that proceeds without proper authorization: constructive change. The legal theory is that the customer's actions or inactions constructed an effective change to the contract, even without a formal written change order. The constructive-change claim is a real legal pathway and is sometimes the only pathway available to a firm that performed authorized work without documentation. It is also a pathway with substantial litigation risk, time investment, and uncertain outcome, and the firms that scale cleanly through the mid-market band are the firms whose process discipline keeps them off the constructive-change pathway in the first place. The change order lifecycle A clean change-order lifecycle has six stages: notice of change, RFI or PCO documentation, owner-side approval, pricing, contract modification, and billing-and-recognition. Each stage has documentation requirements, time constraints, and named owners. The lifecycle works when the stages are sequenced correctly and each stage produces the documentation the next stage requires. Stage 1: notice of change. The change is identified by either the firm or the customer (or the customer's representative, architect, owner's representative, construction manager). The notice is delivered in writing, typically an email, a written notice on the firm's letterhead, or an entry in the project-management system's change-tracking module, and it identifies the change, the source (drawing revision, field condition, customer request), and the firm's preliminary view on schedule and cost impact. The contract-specified notice window is critical: most construction contracts require notice within a defined number of days after the change is identified, and missing the notice window can extinguish the firm's right to recover for the change. The discipline is to deliver the notice immediately upon identification, even when the cost and schedule impacts are not yet quantified. Stage 2: RFI or PCO documentation. Depending on the source of the change, the firm produces either a Request for Information (RFI), when the change requires a clarification or decision from the customer or the design team, or a Proposed Change Order (PCO), when the change is a proposed modification with cost and schedule details. The RFI/PCO is the documentation that supports the eventual change order, and it includes the technical detail of the change, the cost basis (labor hours, material quantities, subcontractor pricing, equipment time), the schedule impact in days, and any conditions that affect the change (weather, sequencing dependencies, supply-chain delays). The RFI/PCO is submitted through the contract-specified channel, typically the architect's office on a traditional design-bid-build project, the construction manager on a CM-at-risk project, or directly to the owner on a design-build project. Stage 3: owner-side approval. The customer or the customer's representative reviews the PCO and either approves, rejects, or returns it for revision. The contract specifies the approval timeline, and the firm tracks the elapsed time against the contractual window. The most consequential discipline at this stage is what the firm does when approval is delayed beyond the contractual window. Most contracts give the firm a remedy for delayed approval, typically the right to direct the customer to make a decision within an additional defined window, with the firm's right to proceed at the customer's risk if the decision is not made. The firm's project manager and controller must know the remedy and use it; firms that wait indefinitely for approval are firms whose change orders age into disputes. Stage 4: pricing. Once the change is conceptually approved, the pricing is settled. Pricing methods include lump-sum (a fixed price for the change), unit-price (price per unit of work, with the unit defined in the contract), time-and-material (cost-plus-markup), or not-to-exceed (T&M with a cap). The pricing method is typically specified in the contract, and the change order documents the method and the agreed price. The firm's pricing must be supported by cost detail, labor hours by trade, material quantities and unit prices, subcontractor proposals, equipment time at the firm's published rates, that the customer can review and that survives audit if the change is later contested. Stage 5: contract modification. The change is executed as a formal contract modification using the AIA G701 Change Order form (or the equivalent form specified in the contract). The G701 names the contract, the change number, the description, the price impact, the schedule impact, and the signatures of the contractor, the architect (where applicable), and the owner. The G701 is the primary legal document evidencing the change, and it is what the firm references in subsequent billing and what the auditor reviews in revenue-recognition testing. The signed G701 also updates the contract value, both the original-contract-value column and the current-contract-value column on the WIP, and triggers the cumulative-catch-up adjustment to the percentage-of-completion calculation under ASC 606's contract-modification framework. Stage 6: billing and recognition. The change-order amount is billed against the master contract on the next progress-billing cycle, using the AIA G702 Application and Certificate for Payment and the G703 Continuation Sheet. The billing references the change order number and shows the change-order amount as a line item on the G703. Revenue is recognized in the financial statements based on the percentage of completion applied to the modified contract value, with the cumulative-catch-up adjustment posted in the modification period. The lifecycle, applied with discipline, produces a change order that flows cleanly from identification through recognition with documentation at every stage. The discipline holds when the project manager treats the lifecycle as a non-negotiable process, the controller monitors the process for stage-to-stage progression, and the field staff understand that work cannot proceed without owner-side approval, even when the customer is verbally directing them to proceed. The AIA documents and progress billing The American Institute of Architects (AIA) publishes a family of contract documents that are the de facto standard for commercial construction in the United States. The AIA documents most relevant to change-order management are the G701 Change Order, the G702 Application and Certificate for Payment, the G703 Continuation Sheet, and the A201 General Conditions that defines the contractual relationship and the change-order procedures. The G701 Change Order is the formal document that modifies a construction contract. It is signed by the contractor, the architect (where the contract specifies architect involvement), and the owner, and it adjusts the contract sum, the contract time, or both. The G701 references the underlying contract by date and number, identifies the change order by sequential number within the contract, and specifies whether the change reflects a credit (price reduction) or a debit (price increase). The G701 is the document the auditor reviews in ASC 606 revenue recognition testing, the document the bonding agent references in WIP review, and the document litigation counsel relies on in any contested change-order matter. The G702 Application and Certificate for Payment is the document the contractor submits to request payment for completed work. It summarizes the contract value (including approved change orders), the work completed to date, the retainage withheld, and the amount due in the current pay application. The G702 is signed by the contractor and certified by the architect (under traditional AIA contracts), and it is the basis on which the owner releases payment. The G702 ties to the WIP schedule's billings-to-date column and is the source document for the firm's accounts-receivable balance. The G703 Continuation Sheet is the line-item detail that supports the G702. It lists each line of work in the contract, typically by cost code or scheduled-value line, and shows the original-contract value, the change-order adjustments, the revised contract value, the work completed this period, the work completed to date, the percentage complete, the materials stored, the total earned, the retainage, and the amount due. The G703 is updated for every approved change order; a change order that is approved but not added to the G703 is a change order that has not been billed and not been recognized as revenue. The discipline of updating the G703 with each approved change order, before the next monthly G702 is submitted, is what closes the loop between the change-order lifecycle and the firm's cash collection. The A201 General Conditions is the broader contractual framework that defines the change-order procedures, the notice requirements, the dispute-resolution process, and the related contract-administration mechanics. The A201 is the document the project manager and the controller should read in full at contract execution and reference whenever a change-order question arises. The most common A201 references in change-order disputes are the notice provisions (Article 7 in the standard A201), the disputed-change-order pricing mechanics, and the claims procedure for changes the firm believes are owed but the customer disputes. The relationship between the G701 and the G702/G703 is what the firm must operationalize. An approved G701 increases the contract value; the G703 must reflect the increased value in the next billing cycle; the G702 references the increased contract value; the customer reviews and approves the payment application; the cash arrives on the contractually specified timeline. The discipline of immediately updating the G703 upon G701 approval is what prevents approved change orders from sitting unbilled, the second of the two failure patterns we discuss in the next section. The two failure patterns Across the construction firms we have audited on change-order discipline, two failure patterns recur often enough to deserve specific treatment. The patterns are largely independent, a firm can suffer from one without the other, and each has a different remediation path. Failure pattern 1: work proceeds before approved change order ("constructive change" risk). A change is identified, typically a field condition, a customer request, or a design clarification, and the work cannot wait for the formal change-order lifecycle to complete. The customer's representative verbally directs the firm to proceed. The project manager, under schedule pressure, agrees to proceed. The work is performed. Weeks or months later, the formal change order is requested, and the customer's office disputes the price, the scope, or even whether the change was authorized in the first place. The legal theory the firm relies on in this scenario is constructive change, the customer's actions or representatives' verbal directions constructed an effective change to the contract. The legal theory exists, and constructive-change claims are sometimes successful, but the litigation cost is substantial and the outcome is uncertain. The firms whose change-order discipline holds avoid the constructive-change pathway by enforcing a no-work-without-written-authorization standard, even when written authorization slows the work. The discipline that holds the standard has three components. The first is a defined fast-path for urgent changes. The contract or the firm's project-execution procedures specify a fast-path authorization process for urgent changes, typically a written authorization from the owner's representative within 24-48 hours, with formal G701 execution to follow. The fast-path lets the firm proceed with documented authorization rather than verbal direction, and the documentation is what supports the eventual G701. The second is field-staff training that work without written authorization is not work. Field supervisors and project managers must understand that proceeding on verbal direction is a violation of the firm's process, regardless of who issued the verbal direction. The training is reinforced by controller-level review of any work that surfaces in the job-cost ledger without a corresponding change-order reference; the surfacing produces accountability and reinforces the process. The third is escalation when authorization is delayed. When the customer's representative is unresponsive and the work cannot wait, the project manager escalates to the controller, the COO, or the firm's principal, and the escalation includes the contractual basis for the escalation (the A201 notice provisions, the customer's contractual obligation to make decisions within a defined window). The escalation forces a decision, and the decision is documented even if the documentation is "the customer's representative authorized proceeding by email at this date and time." Failure pattern 2: approved change order not billed against the master contract. The firm receives an approved G701 from the customer. The change-order amount is real and authorized. The firm's project manager files the G701 and moves on to the next item. The G703 is not updated. The change-order amount is not added to the next G702. Revenue is not recognized in the financial statements. Months later, the firm discovers that an approved change order has been sitting unbilled, and the cash is months delayed. The discipline that prevents this pattern is a closed-loop process between the change-order lifecycle and the billing cycle. Specifically, every approved G701 triggers an action item to update the G703 before the next G702 is submitted, and the controller reviews the G703 line items at the start of each billing cycle to verify that all approved change orders are reflected. The closed-loop process is straightforward to install but requires named accountability, typically the project accountant or the controller, depending on the firm's size, and a checklist that is run on every billing cycle. The pattern is more common than firms expect because the project manager's attention shifts to the next change once the current one is approved, and the back-office handoff to billing is often informal. The closed-loop process formalizes the handoff and produces the cash collection that the change-order approval was supposed to enable. The two patterns also produce ASC 606 issues. Failure pattern 1, work that proceeded without approval, creates a variable-consideration question: can the firm recognize revenue on work performed without a formal change order. The conservative position, and the position the auditor will support, is that revenue is not recognized until the change is approved or the firm has documented evidence that approval is highly likely. Failure pattern 2, approved changes not billed, does not affect revenue recognition (revenue is recognized based on the contract value including approved changes, regardless of whether the firm has billed) but creates a working-capital problem and an over-billings/under-billings inconsistency on the WIP. Both patterns produce findings in audits and in WIP reviews by the bonding agent. Documentation expectations that survive The change-order documentation that holds up in litigation, in audit, and in surety review has consistent properties across the construction firms we engage. The documentation is contemporaneous, produced at or near the time of the events, not reconstructed later. The documentation is specific, names the work, the cost basis, the schedule impact, the parties involved, the dates. The documentation is complete, covers every stage of the lifecycle, with the supporting detail at each stage. The documentation is filed and retrievable, stored in a location the project manager, the controller, the auditor, and litigation counsel can all access without effort. The contemporaneous standard is what most often fails. A change-order file that is built during the project, stage-by-stage, with the RFI dated when the RFI was issued, the PCO dated when the PCO was submitted, the email correspondence dated when it was sent, and the G701 dated when it was signed, is a file that survives litigation. A change-order file that is assembled retrospectively when a dispute arises, with reconstructed emails, dated-from-memory authorizations, and gaps in the chronology, is a file that produces unfavorable inferences in court. The discipline of building the file as the project runs is the discipline that pays off when, three years later, the firm needs to defend the change order in a contested matter. The specific standard means named individuals, dated communications, and dollar-precise pricing. "The owner authorized the change" is not specific. "John Smith of [Owner Entity], in an email dated [date], authorized the change at the price quoted in PCO #14" is specific. The specificity is not paranoia; it is the level of detail that survives cross-examination if the matter ever reaches a deposition or a trial. The complete standard means every stage of the lifecycle has documentation. Notice of change: written notice. RFI/PCO: the technical detail and the cost basis. Owner-side approval: the email, the meeting minutes, the signed PCO, or the G701. Pricing: the cost-detail workpaper. Contract modification: the executed G701. Billing: the G702/G703 reflecting the change. Recognition: the WIP entry and the GL posting. A file with documentation at every stage is a file the auditor and litigation counsel can read end-to-end; a file with gaps is a file that produces questions. The filed-and-retrievable standard means the documentation lives in a structured location with a defined naming convention. Most mid-market construction firms install a project-management system (Procore, Foundation Software's project module, Sage 300 CRE's project module, BuilderTREND, CMiC) that handles change-order documentation natively. The system enforces the structure, names the files consistently, and produces the auditable trail. Firms that run change-order documentation in a project manager's email folder, a shared network drive without naming conventions, or a paper-based filing system are firms whose documentation will be reconstructed under deadline pressure when the dispute arises. The audit-side review The auditor's review of change-order documentation is increasingly central to the construction-firm audit, both because change orders are the most common source of variable-consideration estimates under ASC 606 and because change-order revenue is a high-judgment area where errors are easy to identify in audit testing. The auditor selects a sample of change orders from the active and closed populations, weighted toward larger change orders and change orders with unusual features (very high markup, unusual pricing methods, change orders submitted near year-end, change orders that were disputed and later settled). For each sampled change order, the auditor verifies that the documentation chain is complete: notice-of-change, RFI/PCO, owner-side approval, pricing detail, signed G701, G702/G703 billing, and GL recognition. The verification is a paper-trail test, and the firm's documentation discipline is what produces a clean test or a finding. The auditor also examines change orders that exist in the firm's records as approved-but-not-billed and as work-performed-but-not-approved. The first category creates a working-capital question, why has approved change-order work not been billed, and what is the cash impact. The second category creates a revenue-recognition question, has the firm recognized revenue on work that does not yet have approved change-order support, and is the variable-consideration treatment appropriate. The findings most commonly produced from change-order testing, in approximate frequency order: revenue recognized on uncosted change orders without variable-consideration analysis (an ASC 606 finding); approved change orders not reflected in the G702/G703 billing (a working-capital finding and a control finding); change orders with incomplete documentation chains (a control finding); pricing detail that does not reconcile to the change-order amount (a control finding); and change orders signed by parties without contractual authority to sign (a contract-administration finding, occasionally rising to a control finding). Each finding is preventable with the documentation discipline this guide describes. The construction firms whose audits run cleanly, whose management letters do not carry change-order findings, whose auditors complete fieldwork without follow-up requests, are the firms whose project managers and controllers run the lifecycle with discipline and whose project-management system enforces the documentation chain. What we recommend Change-order management is one of the highest-leverage operational disciplines in construction back-office. Done well, it produces a firm that gets paid for the work it performs, recognizes revenue cleanly, defends its positions when challenged, and grows its bonding capacity because the WIP and audit documentation reflect a disciplined operating posture. Done poorly, it produces a firm that fights for cash on completed work, files variable-consideration estimates the auditor questions, and watches its bonding capacity stall because the underwriter cannot read confidence into the firm's documentation. We recommend three concrete actions for any construction CFO, controller, or operations leader who wants to evaluate whether the firm's change-order discipline is doing its job. Audit the change-order chain on the last twenty change orders the firm processed. For each change order, walk through the documentation: notice-of-change, RFI/PCO, owner-side approval, pricing detail, signed G701, G702/G703 billing, and GL recognition. Identify the change orders with gaps in the chain. The audit produces a concrete inventory of where the discipline is slipping and a target list for process tightening. Audit the open change orders against the WIP. Every job on the WIP has a current contract value, and the difference between the original contract value and the current contract value is the cumulative approved change orders. Reconcile the cumulative approved change orders for each job to the change-order log. Identify the change orders that are in one record but not the other. The reconciliation surfaces both approved-but-not-recorded change orders (failure pattern 2) and recorded-but-not-approved change orders (a different control gap, where the WIP is reflecting unapproved changes). Audit the variable-consideration treatment. For every job with significant unapproved change-order work or pending claims, examine the variable-consideration analysis the firm has applied under ASC 606. Verify that the documentation supporting the recognition (or non-recognition) is complete, that the "probable, no significant reversal" constraint has been applied, and that the amounts recognized are consistent with the firm's policy memo. The variable-consideration audit closes the loop between change-order documentation and revenue recognition. The Change Order Lifecycle + Documentation Procedure paired with this guide includes the six-stage lifecycle template, the AIA G701/G702/G703 documentation framework, the contemporaneous-documentation checklist, the fast-path authorization procedure for urgent changes, the closed-loop billing-cycle process, and the variable-consideration treatment framework that ties to the firm's ASC 606 policy memo. It is the reference set we install when we engage with construction firms on the Build-Construction-Back-Office Diagnostic, and it is paired with the WIP schedules guide and the job cost discipline guide to address the integrated documentation set the firm needs to defend. The construction firms whose change-order management is consistently clean are the firms that have made the lifecycle non-negotiable, the firms where work does not proceed without written authorization, where approved change orders are billed in the next cycle as a matter of process rather than memory, and where the documentation chain is built during the project rather than reconstructed during a dispute. The discipline is the operational difference between a firm that gets paid for what it builds and a firm that fights for what it has already delivered. The discipline is not a software purchase, although the right project-management system supports it; it is a process commitment that the firm either makes deliberately or pays for in disputes, audit findings, and constrained working capital.