Change Order Log: How to Track Changes on a Project

On a busy project, changes come faster than the paperwork. A dozen potential change orders can be in flight at once — some priced, some pending approval, some already being built. Without a single place to track them, changes slip through: work gets done that never gets billed, approvals stall, and the project's cost picture blurs. A change order log is the tool that keeps all of it straight. This guide covers what a change order log is, what it should contain, and how to use it so no change goes unpaid.

What is a change order log?

A change order log is a running register of every change on a project — from the moment a potential change is identified through pricing, submission, negotiation, and final approval. It's the single source of truth for the status and value of all changes, so anyone can see at a glance what's pending, what's approved, and what it all adds up to.

Where an individual change order is one document, the log is the index that tracks them all — and it's what stops changes from falling through the cracks.

What a change order log should include

For each change, track:

Field	Purpose
CO number	Unique reference
Description	What the change is
Origin	RFI, owner request, field condition, etc.
Date identified	When it arose
Status	Potential / Priced / Submitted / Approved / Rejected
Cost impact	The value of the change
Schedule impact	Days added or removed
Date submitted	When the proposal went out
Date approved	When it was signed
Notes	Negotiation status, related documents

A running total of approved and pending change values gives you the project's real cost picture at any moment.

Why the log matters

The change order log does three important jobs. It prevents lost changes — every potential change is captured the moment it's identified, so nothing gets built and forgotten. It shows the true project cost — the sum of approved and pending changes, next to the original contract, is the real number, not the stale contract figure. And it surfaces stalled approvals — changes sitting in "submitted" for weeks are visible and can be chased before the work is needed or the cost grows.

The link to field documentation

A change order log tracks the status and value of changes; your daily reports capture what actually happened in the field — the directed change, the extra work, the photos. The two work together. When a change on the log is questioned during negotiation, the field record from the day the change was directed is the evidence that supports it. A log entry that says "field condition, grid C, June 3" is far stronger when the June 3 daily report shows the condition, the direction, and the work.

BuildLog is where that field evidence lives. Capture each directed change the day it happens — the instruction, who gave it, the extra work, and photos — in your daily report. When you log the change and negotiate it later, you have a dated, contemporaneous record backing every entry, instead of relying on memory. It works offline and exports branded PDFs, with a free tier to start.

Frequently asked questions

What is a change order log? A running register of every change on a project — tracking each from identification through pricing, submission, and approval — so their status and total value are visible in one place.

What should a change order log track? CO number, description, origin, dates, status, cost and schedule impact, and notes, plus running totals of approved and pending change values.

How does a change order log prevent lost money? By capturing every potential change immediately and tracking it to resolution, so no directed work gets built and forgotten, and stalled approvals get chased before they're needed.

---

Back every change with a field record. Try BuildLog free.