What Is a Change Order Log?
A change order log is the systematic record of every modification, addition, deletion, or substitution to a construction or project contract — organized by project and tracked from the moment the change is identified through the moment it is billed and collected. It is the revenue protection tool that ensures every dollar of change order work performed is eventually invoiced and paid.
In construction, changes are inevitable. Owners request scope additions. Designers issue clarifications that expand the work. Site conditions differ from what was anticipated. Schedule changes require acceleration or extended general conditions. Material substitutions alter cost. Each of these events has a cost consequence that the contractor must track, price, document, negotiate, and bill — or absorb as a margin hit.
The change order lifecycle moves through several distinct stages:
- Identification — A change to the original scope is identified on the job site or through a formal owner request
- Pricing / Estimating — The contractor prices the change — direct labor, material, subcontractor impact, general conditions, overhead, and profit
- Submission — The priced change order request (COR) or change order proposal (COP) is formally submitted to the owner or GC
- Negotiation — Owner and contractor negotiate the scope, price, and schedule impact
- Approval — Owner formally approves the change order (CO) in writing
- Contract Execution — The approved CO is incorporated into the contract and the revised contract value is updated
- Billing — The approved CO amount is included in the next progress billing or separate invoice
- Collection — Payment is received for the change order work
A change order log tracks every active change order across all stages simultaneously — surfacing which changes are pending submission, which are submitted but not yet approved, which are approved but not yet billed, and which are unapproved (work performed and costs incurred, but no formal submission made). The sum of these positions represents the contractor’s total change order exposure — revenue at risk if any of these change orders are not ultimately collected.
Why Construction Companies Use Change Order Logs
- Protecting Contract Revenue The most fundamental purpose of a change order log is revenue protection. Without a systematic tracking system, change order work disappears — costs are posted to the job, margin erodes, and the change order is never billed because no one tracked it from request to approval to invoice. A contractor with 50 active projects and an average of 15 change orders per project has 750 change order items to track simultaneously. Without automation, items fall through the cracks every month.
- Revised Contract Value Accuracy The revised contract value — the original contract plus all approved change orders — is the revenue denominator used in the WIP percentage-ofcompletion calculation. If approved change orders are not recorded promptly, the revised contract value is understated, the percent complete is overstated, and the WIP report produces an incorrect overbilling or underbilling position. Change order log accuracy directly affects WIP report accuracy and balance sheet accuracy.
- Pending Change Order Exposure Management Change orders that have been submitted but not yet approved represent a specific financial risk — the contractor has often already performed the work and incurred the cost, but has not yet secured approval to bill for it. The pending change order balance across all active projects is a key indicator of financial exposure and negotiation pipeline. Operations leadership needs visibility into this exposure to manage client relationships, identify stalled negotiations, and decide whether to escalate or write off unapproved items.
- Unapproved Change Order Risk Unapproved change orders — work performed but not yet formally submitted — represent the highest-risk change order category. This is directed work, verbal authorizations, owner-changed specifications, and differing site condition responses that the contractor has executed without a signed change order. Every dollar of unapproved change order work is revenue at risk. A change order log that surfaces unapproved items forces the project team to submit them before the project closes — rather than discovering at job close that $200,000 of work was never formally submitted.
- Claims Avoidance and Documentation A well-maintained change order log is the first line of defense against owner disputes and claims. When an owner disputes a change order, the log provides a complete documented history — when the change was identified, when it was priced, when it was submitted, what the owner’s response was at each stage, and the basis for the price. Contractors with organized change order logs resolve disputes faster and with better outcomes than those who reconstruct the history from email threads and field notes.
- Cash Flow Impact Tracking Approved but unbilled change orders represent earned revenue that has not been invoiced — a cash flow impact. Change orders that are approved but billing has not been generated may represent significant working capital tied up in unbilled work. The change order log identifies the billing lag on approved change orders and enables the AR team to ensure billing is generated promptly after approval.
- Subcontractor Change Order Pass-Through When an owner approves a change order that involves subcontractor work, the contractor must issue a corresponding change order to the affected subcontractor. Change order log systems that track both the owner-side change order and the corresponding subcontractor-side change order ensure that the contractor’s back-toback change order obligations are managed systematically — preventing situations where the contractor receives payment from the owner but delays or forgets the corresponding subcontractor payment.
Common KPIs and Change Order Log Data
Per-Change-Order Data
- Change Order Number (CO-001, CO-002, etc.)
- Job Number and Job Name
- Change Order Title / Brief Description
- Owner Request / Reference (RFI, ASI, PCO, COR reference)
- Date Identified
- Date Priced / Estimated
- Date Submitted to Owner / GC
- Quoted / Submitted Amount
- Date of Owner Response
- Negotiated Amount (if different from submitted)
- Approval Status (Pending / Approved / Rejected / Disputed / Withdrawn)
- Date Approved (if approved) Approved Amount
- Date Added to Contract
- Date Billed
- Amount Billed
- Date Collected
- Amount Collected
- Outstanding Balance (Approved minus Collected)
- Change Order Type (Scope Addition / Scope Reduction / Acceleration / Differing Site
- Condition / Design Error / Owner-Directed / Claim)
- Cost Impact (labor, material, subcontractor, general conditions)
- Schedule Impact (days added to contract duration)
- Associated Subcontractor Change Order Status
Portfolio-Level Change Order Summary
Total Number of Active Change Orders Across All Jobs Total Original Contract Value (all active jobs)
Total Approved Change Orders (by job and portfolio total)
Total Revised Contract Value (Original + Approved COs)
Total Pending Change Orders (submitted, not yet approved)
Total Unapproved Change Orders (performed, not yet submitted)
Total Disputed Change Orders
Total Approved but Unbilled Change Orders
Change Order Approval Rate (approved ÷ submitted)
Average Days from Submission to Approval
Average Days from Approval to Billing
Change Order Revenue as % of Total Contract Revenue
Risk Classification Summary
- Approved and Billed — No risk, in AR
- Approved, Not Yet Billed — Low risk, billing lag only
- Submitted, Pending Approval — Moderate risk, negotiation in progress
- Disputed — High risk, requires management attention
- Unapproved (Not Yet Submitted) — Highest risk, must be submitted before project closes
- Rejected — Revenue lost, determine whether to escalate to claim
Common Filters and Parameters
- Job Number / Job Name — single project detail or all-projects summary
- Approval Status — all, pending, approved, rejected, disputed, unapproved
- Billing Status — all, approved-not-billed, billed-not-collected
- Change Order Type — scope addition, acceleration, differing site condition, claim
- Project Manager — all COs for a specific PM
- Division / Branch — filter by business unit
- Customer / Owner — all COs for a specific client
- Date Range — submitted within, approved within, or outstanding as of a date
- Dollar Threshold — show only COs above a defined dollar threshold
- Risk Tier — show only high-risk categories (unapproved, disputed)
- Subcontractor Pass-Through Status — show COs with open subcontractor obligations
- Age of Pending COs — show COs that have been pending for more than X days
Common Reporting Challenges
Change Orders Tracked in Disconnected Systems
Most contractors track change orders in some combination of: the project accounting system (for approved COs after contract execution), a separate Excel log (for pending and unapproved COs), project management tools like Procore or Autodesk Construction Cloud (for RFI and submittal tracking), and email threads (for verbal approvals and negotiation history). None of these systems talk to each other, and the complete picture of change order status across all projects requires manual consolidation — which happens inconsistently, if at all.
Verbal Approvals and Directed Work
Construction project reality includes significant amounts of verbally directed work — an owner's representative on the job site tells the superintendent to "just do it" and the contractor proceeds without a signed change order. This work gets performed, costs get posted to the job, and no one creates a change order request because everyone assumes the formal paperwork will follow. It often does not. Unapproved change orders from verbally directed work are a chronic source of revenue loss on construction projects.
Change Order Log Not Updated in Real Time
Excel-based change order logs are only as current as the last time someone updated them. A log that was current two weeks ago does not reflect approvals, rejections, or submissions made since then. Project managers who rely on a stale log miss billing opportunities, make decisions on incomplete information, and walk into owner meetings without an accurate picture of the change order negotiation status.
No Portfolio-Level Visibility
A project manager can tell you the change order status on their job. An operations director or CFO managing 50 active projects cannot easily aggregate that information into a portfolio-level view of total pending exposure, total unapproved risk, and total approved-but-unbilled change order backlog — unless there is a systematic reporting infrastructure that consolidates change order data across all jobs automatically.
Subcontractor Change Order Tracking
On projects with multiple subcontractors, each approved owner change order may require corresponding change orders to one or more subs. Tracking these back-to-back obligations — ensuring that subcontractor change orders are issued, priced, and executed at the same time as the corresponding owner change orders — requires a data model that links owner-side and sub-side change orders. Without this linkage, contractors may receive owner payment but delay or miss corresponding subcontractor obligations, or vice versa.
Change Order Revenue Not Captured in Financial Reports
When approved change orders are not promptly added to the revised contract value in the accounting system, they are missing from the WIP calculation, the job cost summary, and the financial statements. Revenue from approved changes may be earned but not recognized until the accounting entry catches up — creating timing differences between economic reality and financial reporting.
Automation and Scheduling Options
- Centralized Change Order Database We build a SQL Server change order tracking database that consolidates all change order data — from initial identification through final collection — in a single, structured system. Change orders can be entered through a web interface, imported from Procore or other PM systems, or synced from the accounting system when COs are executed in contract.
- Real-Time Status Tracking We build change order status workflows that move each CO through defined stages — identified, priced, submitted, pending, approved, billed, collected — with date and amount tracking at each stage. Status updates from project managers, accounting, and billing are captured in real time, eliminating the stale-log problem.
- Portfolio-Level Change Order Dashboard We build Power BI change order dashboards that give operations directors and CFOs a real-time portfolio view — total pending exposure, total unapproved risk, largest single CO items, oldest unresolved COs, approval rate trends, and billing lag analysis — across all active projects simultaneously.
- WIP Integration We build direct integration between the change order database and the WIP calculation engine — so that when a change order is approved, the revised contract value in the WIP system is automatically updated on the same day. Approved COs no longer lag the WIP report by weeks waiting for manual accounting system entry.
- Billing Trigger Automation We build billing trigger logic that alerts the billing team when a change order moves from “approved” to “ready to bill” — preventing the billing lag that leaves approved change order revenue uncollected for extended periods.
- Automated Change Order Log Delivery Weekly or monthly change order log reports — showing every active CO by project, status, and aging — delivered automatically to project managers, operations directors, and the CFO, without manual report preparation.
Delivery Methods
SSRS (SQL Server Reporting Services)
Parameterized change order log reports by project, by PM, by status, or across all active jobs — with drill-down from portfolio summary to individual CO detail. Scheduled weekly subscriptions deliver change order status reports to project managers automatically.
Crystal Reports
Modernization of legacy Crystal Reports change order templates from Sage, Viewpoint, or other project accounting platforms.
Power BI
Interactive change order dashboards with portfolio-level status distribution charts, unapproved CO risk heat maps, approval timeline analysis, PM performance comparison, and project-level CO history — refreshed daily from the SQL Server CO database.
Excel Automation
Excel change order log workbooks driven by live SQL Server data — for teams that need Excel format for client meetings, bid reviews, or project close-out — automatically populated without manual entry or copy-paste from the project management system.
Scheduled PDF Reports and Email Delivery
Weekly change order status PDFs automatically delivered to project managers and operations leadership — surfacing the highest-risk items (unapproved, disputed, aging) at the top of every report.
Related Report Pages
Job Cost & WIP Pages
Job Cost, WIP & Project Reporting Hub — Overview of all job cost, WIP, and project reporting solutions from ReportingGuru.
Job Cost Summary — Job-level cost vs. estimate reporting — change order costs flow into the job cost summary as the contract scope evolves.
Work in Progress (WIP) Report — Approved change orders update the revised contract value that drives WIP percentage-of-completion calculations.
Financial & GL Reporting Pages
Balance Sheet — Automate point-in-time financial position reporting alongside period P&L production — both derived from the same GL data model.
Statement of Cash Flows — Reconcile net income to operating cash flow using the indirect method — the income statement is the starting point for every cash flow statement.
Trial Balance — The foundational GL data that drives every revenue and expense line on the income statement — extracted, validated, and exception-checked at every close.
Budget vs Actual — P&L actuals vs. budgeted revenue and expense with variance analysis, departmental accountability, and rolling forecast integration.
Inventory & Warehouse Pages
Inventory & Warehouse Reporting — Overview of all inventory and warehouse reporting solutions from ReportingGuru.
Inventory On Hand — The quantity foundation of every inventory valuation — on-hand units by SKU and location that the valuation cost method is applied to.
Inventory Valuation — The financial value of aged inventory — cost method valuation by lot that determines the dollar impact of the obsolescence reserve.
Investor & Fund Reporting Pages
Financial Statements & KPI Reporting — Fund and portfolio company financial statements incorporating inventory on-hand balances and turnover metrics.
Fund Performance Reporting — Days-on-hand, stockout rates, and inventory turnover tracked as PE portfolio company operational KPIs.
Frequently Asked Questions
What is the difference between a pending change order and an unapproved change order?
A pending change order is one that has been formally priced and submitted to the owner or GC for approval — the contractor has done the documentation work and the ball is in the owner’s court. An unapproved change order is work that has been performed (and costs incurred) but has not yet been formally submitted — the contractor has not yet created or submitted a written change order request. Unapproved change orders represent the highest risk category because there is no formal submission on record, and they become harder to collect the longer they go unsubmitted.
How should change orders be tracked in construction?
Change orders should be tracked in a centralized log that records: the CO number, description, job, date identified, date submitted, submitted amount, approval status, approved amount, date approved, date billed, and collection status. Every change — including verbal directions and informal approvals — should be entered into the log immediately, before the work is performed if possible. The log should be reviewed weekly by the project manager and monthly by operations leadership.
What is a change order in construction?
A change order in construction is a formal written amendment to the original construction contract that modifies the scope of work, the contract price, the schedule, or any combination of the three. It must be signed by both the owner and the contractor (and sometimes the architect or engineer) to be legally binding. Before a formal change order is executed, a Contractor may issue a Change Order Request (COR) or Potential Change Order (PCO) to document the proposed change and its pricing for owner review and approval.
Why do contractors lose money on change orders?
Contractors lose money on change orders for several reasons: (1) change order work is performed before formal approval is secured, and the owner later disputes the scope or price; (2) the change order is priced without fully accounting for schedule impact, acceleration costs, and general conditions; (3) the change order is approved but never billed because no one tracked it to the billing stage; (4) subcontractor change orders are not issued promptly, and subs perform work without a formal change order; and (5) unapproved change orders are allowed to accumulate until project close-out, when owners are less willing to negotiate.
How does the change order log connect to the WIP report?
The change order log connects to the WIP report through the revised contract value. When a change order is approved, it increases the total contract value — which is the revenue base used in the WIP percentage-of-completion calculation. If approved change orders are not promptly added to the contract value in the WIP system, the WIP report understates the revised contract value, overstates the percent-complete calculation, and produces an incorrect overbilling or underbilling position. Keeping the change order log and the WIP system synchronized is an essential data integrity requirement.
Can change order tracking be automated from Procore?
Yes. ReportingGuru builds data integration pipelines that extract change order data from Procore — including PCOs, COs, owner change requests, and subcontract change orders — and load it into a centralized SQL Server change order tracking database. Change order status, approval history, and billing positions are then available for SSRS and Power BI reporting across all active projects, without manual data entry or log maintenance.
What should a change order log report include?
A complete change order log report should include: CO number and description, job reference, date submitted, submitted amount, current status (pending/approved/rejected/disputed), approved amount (if applicable), date approved, date billed, amount billed, and outstanding balance. At the portfolio level, it should summarize total pending exposure, total unapproved risk, total approved-not-billed backlog, and the oldest unresolved items by age — organized so that the highest-risk items are immediately visible at the top of the report.