Free download, change orders

Free change order log template (Excel)

This free change order log template is an Excel workbook that tracks every change event from the day it is identified to the change order that pays for it. It calculates the written notice deadline, flags late notice, and totals approved and pending amounts and days, so nothing is billed before it is signed. No email, no macros.

Download the template

No sign-up, no email. 3 sheets, no macros, 15 KB. Opens in Excel or Google Sheets. The example sheet uses illustrative Texas project data; the blank sheet is ready to use.

What is in the workbook?

SheetWhat it is for
InstructionsThe steps on this page and what each column means
Change order logThe blank working log: dropdowns for source and status, formulas for notice due and the late-notice flag, approved and pending totals
Example (Texas)Seven change events on an illustrative Austin, TX medical office building

What do the columns mean?

The columns follow AIA A201-2017 Article 7 and the notice rules that decide whether a change gets paid.

ColumnWhat to enterWhy it matters
Change event no., Date identified, Description, SourceEvery potential change, the day you see it: owner request, design change, RFI answer, unforeseen condition, inspectorLogging events before pricing is what keeps notice deadlines from slipping.
Notice days, Notice due, Notice sentThe notice period in your contract, the calculated deadline and the date written notice went outA201 Section 15.1.3 requires a claim to be initiated within 21 days after the event or after the condition is first recognized; many owner contracts are shorter. Late notice is the most common reason claims fail.
Status, COR no.Potential, pricing, submitted, approved, rejected or directedA201 Section 7.2 change orders need the owner, contractor and architect to sign; Section 7.3 construction change directives let the owner direct work before price is agreed.
Amount and days, requested and approvedWhat you asked for and what was signedUnder A201 Section 7.3.4, a CCD without agreement is priced from actual costs plus a reasonable allowance for overhead and profit; track costs daily.
CO or CCD no., Date approved, Billed onThe signed document and the pay application that bills itBill a change only once it is signed, as its own line on the continuation sheet.
FlagNOTICE LATE when notice is missing or went out after the deadlineCatches the event before it becomes unrecoverable.

What does the example look like?

Seven change events from the Example sheet, as the formulas compute them on November 13, 2026. Illustrative data, not a real project.

EventSourceNotice dueStatusRequestedApprovedFlag
CE-003 Owner adds card readers at 6 doorsOwner requestOct 5, 2026Approved$18,400$18,400
CE-005 Rock excavation at east footingsUnforeseen conditionOct 21, 2026Approved$42,750$38,900
CE-007 Deeper footings at grid C4 per RFI-012RFI answerNov 13, 2026Submitted$12,600
CE-008 Revised lobby finish per ASI-04Design changeNov 18, 2026Pricing$9,800
CE-009 2-hour stair enclosure per RFI-018RFI answerNov 27, 2026Potential
CE-010 Added storm line per inspectorCode or inspectorNov 5, 2026PotentialNOTICE LATE
CE-011 Owner deletes canopy, creditOwner requestOct 22, 2026Directed (CCD)$-15,200

Illustrative$57,300 is approved. $22,400 of additions are in pricing or review, against a $15,200 owner credit directed by CCD, so the pending total nets to $7,200. The added storm line was identified on October 15 and nobody sent notice; its 21 days ran out on Nov 5, 2026, so it is flagged NOTICE LATE while the cost may still be recoverable.

How do you use the template?

  1. Log every change event the day you see it. An RFI answer, an owner request, a design change or a condition in the ground. Price later; log now.
  2. Set the notice days from your contract. Enter the notice period your contract requires; the deadline calculates itself.
  3. Send written notice. Before the deadline, in the form the contract requires, and enter the date sent.
  4. Price with backup. Sub quotes, labor, material and equipment, and markup as the contract allows; add the time impact.
  5. Track to signature. Update the status, amounts and days through approval, and record the CO or CCD number.
  6. Bill only what is signed. Add approved changes as their own lines on the pay application and record which one billed them.

For the full process and how markup works, read change orders: process, markup and the AIA G701.

When does a spreadsheet stop being enough?

A log catches the deadline only if someone logs the event. Change events hide in RFI answers, meeting minutes, architect's instructions and emails, across every job at once. Fina, BAU AI's finance and budget agent, tracks each change event from the first notice, pulls sub quotes and costs into the request, checks the markup against your contract, and moves approved changes into the budget and the pay application; your project manager reviews and submits. Fina is offered to the founding cohort and is not part of the published plans.

Frequently asked questions

Is the change order log template free?

Yes. Download it without an email address and adapt it for your own projects. A credit line to BAU AI sits at the bottom of each sheet.

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

A change event is anything that may change scope, cost or time. A change order is the signed agreement that adjusts the contract. Most events are logged long before they become change orders, and some never do.

How many days do I have to give notice?

Your contract decides. AIA A201-2017 allows 21 days for claims; many owner contracts set shorter periods for notice of changes. Enter your contract's number in Notice days.

Does it work in Google Sheets?

Yes. The formulas use IF, AND, SUMIFS and COUNTIF. There are no macros.

See Fina track a change from notice to pay app

Bring one open change event. In 15 minutes Fina builds the request with you, every number tied to its backup.