Change Order Logs: How to Track Pending, Approved, Rejected, and Schedule Impacts

What a Change Order Log Actually Does

A change order log is not a formality. It is the single source of truth that tells you, at any moment, what your contract value is, what is still in dispute, and whether your schedule is at risk. Without one, you are running your project on memory and email threads.

Most GCs understand that change orders need to be tracked. Fewer have a log that is actually useful when an owner disputes a line item or an architect asks why the schedule moved. This article covers exactly how to build and maintain a change order log that holds up when it matters.

The Core Columns Every Log Needs

A change order log is only as useful as the fields it captures. Strip out the fluff and make sure every log includes these at minimum:

• PCO / COR number: Your internal tracking number. Assign one the moment scope changes are identified, before anything is signed.
• Description: Plain-language summary of the scope change. Keep it short but specific. "Add (8) electrical outlets, Rm 214" beats "electrical work."
• Date submitted: When you formally submitted the proposed change order to the architect or owner.
• Dollar amount: The total change, including labor, materials, equipment, subcontractor markups, and your overhead and profit. Show the number as positive for additions and negative for deductions.
• Status: Pending, approved, rejected, or on hold. More on this below.
• Schedule impact: Days added or removed from the project schedule as a direct result of this change. Zero is a valid entry.
• Revised contract value: Running total of original contract plus all approved change orders to date.
• Notes / next action: Who needs to respond, what documentation is outstanding, and any relevant dates.

If you are managing more than one active project, add a project number or project name column at the far left so the log stays sortable across jobs.

Status Categories: What Each One Means

The status column carries real weight. Using it consistently across your team prevents a $40,000 item from slipping through as "approved" before the architect signs anything, or sitting as "pending" for six months while time-to-claim deadlines expire.

Pending

Pending means the change order has been submitted and is awaiting a decision. You do not count a pending change order in your contract value. You do not bill it on a pay application. What you do is track it on a separate pending log and review it at every project meeting. A pending item that sits untouched for 30 days is a problem worth escalating.

Many contracts, including those built around the AIA A201 general conditions, set specific time windows within which an owner or architect must respond to a proposed change order. Know your contract. If you submitted a change order on April 2 and your contract requires a response within 21 days, April 23 is not just a date on a calendar. It is the start of a potential dispute.

Approved

Approved means the owner has executed the change order. Not verbally agreed. Not emailed "looks fine." Signed. Once a change order is approved, three things happen immediately: the contract value increases, the item becomes billable on future pay applications, and the approved schedule days are folded into the project baseline. Update all three in the same sitting.

For example, if your original contract is $1,850,000 and you get approvals for CO-003 ($18,400), CO-005 ($7,200), and CO-007 (-$3,100), your revised contract value is $1,872,500. That number needs to match what appears on Line 3 of the AIA G702 cover sheet format in your next pay application. Discrepancies between your log and your billing create questions from owners and architects that slow down payment.

Rejected

Rejected means the owner or architect formally declined the change order. Document the rejection in writing, record the date, and keep the item in your log with a rejected status. Do not delete it. If you later believe the rejection was improper because the scope was genuinely outside your contract, that log entry is part of your claim file.

A rejected change order is not necessarily the end of the conversation. You can resubmit with additional documentation, escalate through your contract's dispute resolution process, or reserve rights while continuing work. What you cannot do is let a rejected item disappear from your records.

On Hold

Some teams add a fourth status: on hold. This is for items where the scope is still being defined, where the owner has asked you to pause pricing, or where there is a design conflict that needs resolution before cost can be calculated. On hold is not the same as pending. Pending means the ball is in the owner's court. On hold means neither side is ready to move yet. Keep them separate.

Tracking Schedule Impact

Dollar amount gets the most attention on a change order, but schedule impact is where GCs leave money on the table. Every approved change order that adds scope also adds time. If you do not document and price that time, you are absorbing extended general conditions costs out of your own budget.

The schedule impact column should reflect calendar days of impact to the critical path, not just work days on that one activity. A change to exterior glazing in week six might push substantial completion by 14 days if it is on the critical path. That 14-day extension carries costs: superintendent time, trailer and equipment rental, bonds, insurance premiums, and potentially temporary utilities. Those are recoverable costs if you documented them properly. They disappear if you approved the change order for scope and price only and never addressed time.

When an approved change order includes schedule days, update your project schedule in the same week. Do not wait for the next monthly update. A schedule that does not reflect approved changes is useless for any conversation about delay or liquidated damages.

Keeping the Log Current

The change order log is a living document. Update it weekly at a minimum, and review it at every OAC meeting. Bring a printed copy or a shared screen. Walk through every pending item, ask for a decision date, and record the response.

Assign ownership clearly. One person on your team is responsible for the log. That does not mean they process every change order alone. It means they are accountable for accuracy, version control, and distribution. On smaller jobs, that is often the project manager. On larger jobs, it belongs with the project engineer or the construction accountant.

When a pay application goes out, reconcile the log against the Schedule of Values continuation sheet. Every approved change order should appear in the SOV. If a change order is approved but not yet in the SOV, that item cannot be billed until the SOV is updated and the architect acknowledges the revision.

A Simple Format That Works

You do not need specialized software to maintain a useful log. A shared spreadsheet with strict column discipline and edit history turned on works fine for many small GC offices. The format matters less than the habit. What kills change order management is not the tool. It is inconsistent updates, missing status columns, and logs that nobody looks at between pay applications.

That said, when your change order log connects directly to your pay applications and Schedule of Values, the reconciliation work disappears. Revised contract totals update automatically, billing periods stay accurate, and you spend less time cross-checking numbers before each application.

One Final Note on Disputes

A well-kept change order log does more than keep your billing accurate. It shortens disputes. When an owner claims a change was never formally submitted, you show the submission date. When an architect says a scope addition was included in the original contract, you show the rejected COR with their written response. The log is your paper trail. Treat it that way from day one of the project, not after the first dispute surfaces.

Tracking change orders across projects does not have to live in spreadsheets. EZBilling ties them directly to your Schedule of Values and pay applications, so your contract totals and billing always stay in sync.