Change-order log template

The 19-column change-order log commercial GCs use to track every COR, CCD, and executed CO from origin through pay-app. With live formulas for forecast vs. executed differential, schedule-impact days, running CO total, and percent of original contract.

Why this template exists

Every commercial general contractor on every active project is running a change-order log. The question is whether it’s being run as a managed system or as the kind of half-tracked spreadsheet that gets remembered for the first three months of a project and then quietly drifts out of date until the closeout reconciliation reveals a six-figure exposure that nobody saw coming. Change orders are the highest-velocity, highest-risk financial document in commercial construction. They’re how the contract value moves, they’re how schedule impacts get paid (or don’t), they’re how subcontractor scope creep gets captured (or doesn’t), and they’re the single biggest source of disputes when a project closes out without a clean reconciliation between forecast cost and executed cost. The log is the artifact that tells the truth about all of it.

The pain is structural. A project engineer fields an RFI on day 47 that exposes a design conflict. The architect issues a sketch (SK-12) that resolves the conflict with a change in scope. The GC’s PM walks the change with the affected sub, gets a Change Order Request (COR) back at $48,400 with 6 days of schedule impact. The COR sits in the GC’s inbox for 9 days while the PE chases the cost backup, then goes out to the owner for review. The owner’s project manager negotiates the price down to $42,800, the schedule down to 4 days, and issues a Construction Change Directive (CCD) authorizing the work to proceed under the new pricing while the formal CO gets papered. Three weeks later the CO is executed at $42,800 / 4 days. Then four months later in pay-app review, the GC discovers the executed CO was never actually papered against the sub’s subcontract and the sub has been billing under the original contract value with no flow-down. Multiply by 80 change events on a $40M project and you have the kind of exposure that turns a profitable job into a margin-eroding mess.

The fix is a working change-order log. A live tracker that captures every change event the moment it originates (RFI, owner directive, field condition, scope clarification), classifies the event correctly (COR vs. CCD vs. fully-executed CO vs. owner-directed change), tracks the dollar value at every stage (forecast at COR, negotiated at CCD, executed at CO, billed at pay-app), captures schedule impact in calendar days, distinguishes pricing basis (T&M vs. lump-sum vs. unit-price vs. allowance), and rolls all of it up to a running CO total and percent-of-original-contract metric that the project executive can read on Monday morning. Most generic templates floating on the SERP do not do this. They give you 8 columns, number, date, description, amount, status, and call it a change-order log. That is not a change-order log. That is a notepad with a dollar column.

This template is the operator-built alternative. The 19 columns capture what a commercial GC’s project-controls team and project-management team actually need to manage change orders as a managed system across a multi-million-dollar commercial project: the CO number, the originating event reference (RFI, ASI, FC, or owner directive), the spec section or scope reference, the affected subcontractor or trade, the CO type classification (COR / CCD / CO / OCO / TBD-pending), a one-line scope description, the date the change was identified, the date submitted to the owner, the date executed, the forecast amount captured at COR, the executed amount captured at final CO, the differential between the two, the schedule impact in days added or removed, the pricing basis (T&M / lump-sum / unit-price / allowance), the markup applied, the pay-app reference where the CO is being billed, the status, the backup-documentation reference, and the approving authority on each side. The XLSX runs working formulas on the differential, the running CO total, and the percent of original contract, with conditional formatting on rows where forecast and executed diverge by more than 10%.

What this log is NOT: it is not the prime contract amendment. The prime contract amendment is the legal instrument that formalizes the cumulative change in scope and contract value between the GC and the owner; the log is the operational record of every change event that feeds the amendment. It is also not the subcontract change-order log run by each sub on their own. The GC’s change-order log is the master log that captures the GC-to-owner change events; each sub maintains their own subcontract-level CO log against their subcontract. A well-run project reconciles the two on every pay-app cycle.

Use this log on every active commercial project. Open it the first time a change event is identified, typically within the first 30 days of construction once early-condition discoveries hit, and don’t close it until the final reconciliation at substantial completion. Update it the moment a change event originates, the moment a COR comes back from the sub, the moment a CCD is issued by the owner, the moment the CO is executed, and the moment it’s billed in a pay-app. The discipline is continuous. A weekly cleanup is too late.

Who uses this

• Project executives at commercial general contractors managing $20M-$200M projects who need a Monday-morning view of change-order health across the portfolio
• Project managers running active commercial work who own change-order origination, sub coordination, and owner negotiation day-to-day
• Project-controls and cost engineers maintaining the running CO total, forecast-vs-executed reconciliation, and pay-app integration
• Federal GCs and prime contractors managing FAR-driven change orders, REAs, and equitable adjustments under federal contract clauses
• Owner’s representatives and construction managers auditing GC change-order activity for pattern recognition (scope creep, T&M abuse, schedule-impact float consumption)

What’s included. 19 columns the project-controls team runs

The change-order log captures 19 columns for every change event on every project. Opened at the first change identified, updated continuously through final reconciliation at substantial completion:

1. CO number with project-level uniqueness. Format: CO--, e.g., CO-001-0 for the first executed CO, revision 0; or COR-001-0 for the first Change Order Request still pending owner action; or CCD-001-0 for the first Construction Change Directive issued by the owner. The numbering is project-unique (not company-wide) and is the primary key the entire log keys off. Every pay-app, RFI cross-reference, and subcontract change order references this number. Assign sequentially as change events enter the system; never skip numbers, even for void or rejected events (mark them as Closed-no-cost and keep the row for audit).
2. Originating event reference. The RFI number, ASI (Architect’s Supplemental Instruction) number, FC (Field Condition) report, owner directive memo, or proposal request that triggered the change event. Format: RFI-047, ASI-12, FC-003, OD-2026-04-22, PR-08. This column is the trace-back link that lets the project team, and the audit team in any future dispute, reconstruct why the change was issued. Every legitimate change order has an originating event; if a CO has no originating reference, that is a red flag that the change was authorized verbally and is at risk of dispute.
3. Spec section or scope reference. The CSI MasterFormat spec section (e.g., 03 30 00 for cast-in-place concrete, 09 51 13 for acoustical panel ceilings, 26 09 23 for lighting control devices) or, for changes outside the original spec, the schedule-of-values line item or the original scope-narrative reference the change is modifying. This column ties the CO back to the contract documents and is essential for the closeout reconciliation that proves the CO was within the spec scope of the affected sub.
4. Affected subcontractor or trade. The sub-tier or supplier whose subcontract is being modified by the CO. Capture the company name and the trade designation (e.g., “Acme Mechanical, HVAC,” “Riley Steel, Structural Steel”). For changes affecting multiple subs, create one row per sub and use a parent-CO-number convention (CO-014a, CO-014b) to keep the rollup clean. Owner-directed changes that the GC self-performs get the GC’s own self-perform crew listed here.
5. CO type classification. One of: COR (Change Order Request, sub or GC has proposed a change, owner has not yet accepted), CCD (Construction Change Directive, owner has authorized work to proceed at a not-to-exceed amount or T&M basis, formal CO pending), CO (Change Order, fully executed, signed by owner / GC / sub, modifying the contract), OCO (Owner Change Order, owner-directed change with formal modification, common on federal work as a Mod), TBD-pending (event identified but not yet submitted as a COR). The type drives the financial treatment. CORs are forecast-only, CCDs commit cost authorization but not final price, COs and OCOs are executed.
6. One-line scope description. A plain-English description of what the change covers: “Added storefront type SF-3 at corridor 1.07 per ASI-12,” “T&M for unforeseen rock at footing F1.7 per FC-003,” “Deduct: deleted secondary backup generator per owner VE memo 2026-04-15.” Descriptions matter because they’re what the project executive scans on the running CO total report and what the dispute team scans during closeout reconciliation. Avoid acronym-only descriptions; the description should be readable two years later by someone who wasn’t on the project.
7. Date change identified. The date the change event was first identified by the field team, the PM, the sub, the architect, or the owner. This is the start of the change-event clock. Capture even when the event is informal or verbal at first; the identification date sets the baseline for any schedule-impact analysis and proves the GC was tracking the change in real time, not retroactively.
8. Date submitted to owner (as COR). The date the GC’s PM submitted the COR to the owner for review. The gap between column 7 and column 8 is the GC’s internal cycle time. Typically 5-10 business days for a fully-priced COR with sub backup. Longer gaps signal either an overloaded PM or a sub turning in COR pricing slowly. On federal work, this date triggers the contracting officer’s review window per the FAR 52.243 changes clause.
9. Date CO executed (signed by all parties). The date the formal CO was fully signed by owner, GC, and (where flow-down is required) the affected sub. This is the date the CO becomes contractually binding and the date the executed amount is locked. CCDs do not have an execution date until they’re papered into a formal CO; track the CCD authorization date separately in the notes column. The gap between column 8 and column 9 is the owner’s review-and-execution cycle. Typically 14-45 days on commercial work, sometimes 60+ days on federal.
10. Forecast amount (initial COR pricing). The dollar value the COR was originally submitted at, including all sub backup pricing, GC general conditions impact, and GC markup. This is the captured-at-origin number. Do NOT overwrite it when the price gets negotiated down at CCD or executed at a different number. The forecast number is what the project executive uses to forecast cumulative CO exposure on the running total; the executed number (column 11) is what gets paid. The differential (column 12) tells you how much value the GC is losing in negotiation vs. holding the line.
11. Executed amount (final CO value). The dollar value the CO was actually executed at. This is the number that flows into the prime contract amendment, the schedule of values, and the pay-app. For CORs and TBD-pending events still open, this column reads $0 or remains blank until execution. For CCDs authorized but not yet executed, populate with the CCD not-to-exceed value as the working forecast and update on execution. The XLSX uses this column as the input for the running CO total formula.
12. Differential (forecast vs. executed). Live formula: =column11 - column10. Negative differential means the GC accepted a lower executed number than the COR forecast. Typically a negotiation loss on the GC’s side. Positive differential means the executed number came in higher than the original COR. Rare but happens when scope expands during negotiation. Conditional formatting in the XLSX flags rows where the absolute differential exceeds 10% of the forecast, which is a signal that the original COR pricing was either inflated or the negotiation gave away material margin.
13. Schedule impact (days added or removed). Calendar days the CO adds to (or, in deduct cases, removes from) the contract substantial-completion date. Capture both the COR-claimed schedule impact and the executed-CO schedule impact; the executed number is what counts contractually but the COR claim is what the GC fought for. Cumulative schedule-impact days roll up at the bottom of the log as the running schedule-extension forecast against the original contract substantial-completion date.
14. Pricing basis. One of: Lump-sum (fixed-price CO, most common), T&M (time and materials, capped at not-to-exceed where applicable), Unit-price (per the unit-price schedule in the original contract, common on civil work), Allowance (against an existing allowance line item, does not change the contract value if within allowance), Cost-plus (cost-reimbursable with fee, common on federal). The pricing basis drives the documentation requirement. T&M needs daily T&M tickets, unit-price needs verified field measurements, lump-sum needs sub backup and a build-up sheet.
15. Markup applied. The GC’s markup percentage applied on top of sub costs and direct costs, typically defined by the prime contract (most commercial contracts allow 5%-15% on subcontracted work and 10%-15% on self-performed work). Capture both the contractual markup and the actual markup applied; on negotiated CORs the actual markup sometimes gets compressed as a negotiation concession. Track the gap between contractual and actual as a margin-leak signal.
16. Pay-app reference. The pay-app number the CO was first billed in (e.g., Pay App #07) and any subsequent pay-apps it appears in for retainage release or final billing. This column is the bridge between the change-order log and the schedule of values. Every executed CO must appear on a pay-app with the executed amount and the corresponding G703 line. Mismatches between this column and the actual pay-app are the single most common audit finding at closeout.
17. Status. One of: Pending GC review (sub has submitted COR, GC is pricing/validating), Pending owner approval (COR submitted, owner reviewing), Pending sub acceptance (CO terms negotiated, awaiting sub signature on subcontract change order), Executed (fully signed), Rejected (owner declined the COR or the change was determined to be within original scope), Closed-no-cost (event identified but resolved at no cost change). Conditional formatting in the XLSX colors each status row distinctly so the project-controls weekly review surfaces stuck items at a glance.
18. Backup documentation reference. The link or file path to the supporting documentation: the COR PDF with sub pricing build-up, the T&M tickets log for T&M COs, the field-measurement sheets for unit-price COs, the architect’s sketch (SK-#) referenced in the originating ASI, the owner directive memo, the field photographs documenting the unforeseen condition. On federal work this column also captures the REA (Request for Equitable Adjustment) reference number and any contracting-officer correspondence.
19. Approving authority and notes. The named owner’s representative who approved the CO (typically the owner’s project manager or construction manager), the GC’s approving authority (typically the project executive for over-threshold COs and the PM for under-threshold COs per the prime contract’s approval matrix), and any free-text notes. The notes column captures negotiation history, dispute risk flags, and the rationale for any unusual differential between forecast and executed values.

How to use the log

Open the log at the first change event identified. Usually within the first 30 days of construction once early-condition discoveries hit. Pre-populate the originating-event column (column 2) by walking through every active RFI, ASI, FC report, and owner directive on the project and creating one row per change event whether or not pricing has been developed. For a $40M commercial project this is typically 60-120 change events over the life of the job, of which perhaps 70-90% become executed COs and the balance get rejected, withdrawn, or absorbed as in-scope clarifications.

Update the log continuously. The moment a change event is identified, the moment a COR is priced and submitted, the moment a CCD authorizes proceed, the moment a CO is executed, the moment it shows up on a pay-app. The discipline is “no change event goes unlogged for more than 24 hours, and no status change goes unlogged for more than the same business day.” If you fall behind by a week, the running CO total stops being trustworthy and the project executive loses the Monday-morning view that drives portfolio-level decisions.

Run the log in three views every Monday morning.

View 1: filter for status = Pending owner approval sorted by date submitted ascending. These are the CORs sitting at the owner running long, where escalation is needed.

View 2: filter for type = CCD and status ≠ Executed. These are the CCDs with cost authorized but no formal CO yet, the highest-risk financial exposure on the project.

View 3: filter for the differential column where the absolute value exceeds 10% of forecast. These are the negotiation losses (or wins) that warrant a project-controls deep-dive. Bring all three filtered views to the weekly OAC meeting and to the internal monthly project-review with the project executive.

At pay-app time, reconcile the change-order log against the pay-app line items. Every executed CO with a pay-app reference (column 16) must match the G702/G703 entry; every CO without a pay-app reference is either too new to bill or has been missed by the cost engineer. At substantial completion, run a final filter for any rows not in status Executed, Rejected, or Closed-no-cost. These are the open events blocking final reconciliation and the closeout amendment to the prime contract.

Stop running the change-order log in someone’s head.

The 19 columns above take a commercial GC project-controls engineer 45-60 minutes a day to maintain across a project running 60-120 change events over its life, plus 2-3 hours of weekly cleanup before the OAC meeting and the internal monthly project review. Multiply by 3-4 active commercial projects per project-controls engineer and the change-order log alone is consuming 15-25 hours a week per engineer, and that’s when it’s being run with discipline. When it slips (and on most projects it slips), the cost shows up at closeout when the executed CO total doesn’t reconcile to the prime contract amendment, the deducts weren’t flowed down to the subs, and a margin leak that started in month four becomes a six-figure exposure at month eighteen. Contracts Connected’s approval-workflow engine routes every COR, CCD, and CO through the right reviewers automatically, captures forecast and executed values at every stage, fires the pay-app cross-reference the moment a CO is executed, and surfaces forecast-vs-executed differentials before they become margin leaks.

For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.

Frequently asked questions about the construction change-order log

Related templates

• Subcontract package checklist (commercial)Every document the subcontract package needs before the sub starts work. Bonds, COIs, W-9s, signed scope.
• Pay-app G702/G703 review checklistThe line-by-line review every PM runs on the AIA G702/G703 application for payment.
• Submittal log template20-column commercial-construction submittal log with live days-in-review formulas, long-lead flagging.
• Prevailing wage rate lookup tracker (state-by-state)State-by-state Davis-Bacon and state prevailing-wage rate lookup tracker.