Change Order Log Management for Subcontractors

A change order log is the single running record of every change request on a project: what changed, what it costs, what it does to the schedule, and whether anyone has signed. Managing it well means one entry per change, opened the day the change is identified, updated at every status change, and reconciled before final billing. This guide shows commercial subcontractors what to put in the log, how to run it week to week, how to build one in Excel, and when a spreadsheet stops being enough.

TL;DR

• A change order log is a central register of every change request, with its cost, schedule impact, approval status and a running total against the original contract sum.
• Open an entry the moment a change is identified, not when the paperwork arrives. Late entries are where unbilled work comes from.
• Track at least: number, date, description, reason, cost (additive or deductive), days of impact, status, approval dates and attachments.
• Do not start changed work until the change is signed by all parties. If the field must proceed, record the direction and track time and materials daily.
• Excel works for a handful of changes. Once field tickets, several projects and several people are involved, a connected tool saves double entry.

Table of Contents

• What a change order log is
• Why subcontractors need their own log
• What to put in the log: the fields
• A status workflow that keeps entries moving
• Controlling approvals before work begins
• Assembling the change order package
• How to build a change order log in Excel
• Weekly habits that keep the log honest
• Our perspective: the log is a field habit, not an office report
• When a connected tool makes sense
• FAQ
• Sources

What a change order log is

The log is a table, one row per change, that sits above the individual change order documents. The documents hold the detail: pricing backup, drawings, correspondence. The log holds the status of all of them in one view, so a project manager can answer “what is pending, what is approved, and what is it worth?” in thirty seconds.

Owners use logs too. Colorado’s Office of the State Architect, in its July 2022 contract modification guidelines, says a change-order log should be maintained for each project and monitored from initiation and approval through implementation and reconciliation. The same guidelines recommend keeping the log and all change orders together in one central project file.

For a subcontractor the log has a different job than it does for an owner. Your log is also your protection. It shows which changes you flagged, when you flagged them, what you priced, and what is still sitting unsigned with the general contractor while your crew works.

Why subcontractors need their own log

The general contractor keeps a log for the whole project. It usually shows what the GC has processed, and it may not show the changes you identified but never submitted, or the ones you submitted that are waiting in someone’s inbox. Your own log closes that gap.

Three problems show up again and again when a sub relies on the GC’s log alone:

• Missed costs. A field foreman reroutes work after a verbal direction and nobody opens an entry. The hours are logged on a timesheet, but never tied to a change.
• Unapproved work. The crew starts because the schedule is tight. The change order is signed weeks later, or not at all.
• Slow approvals. Without dates on each status, nobody can see that a request has sat for three weeks, and nobody chases it.

If you want the deeper dive on the cost of waiting, our post on change order backlog and lost margin covers how pending items quietly pile up.

What to put in the log: the fields

Public owners publish the forms they require, and those forms are a good guide to what a complete record contains. Cook County’s construction change order form asks for a specific reason and description, any extension of the completion date, itemized amounts, the original contract value, prior change orders, the total order amount, the net contract value, and dated approvals. A log that tracks those same elements will line up with what an owner’s side expects to see.

An architecture training guide from Young Architect describes a log that tracks the order number, date, description, additive or deductive cost impact, schedule impact, approval status, and a running total against the original contract sum.

Here is a practical column set for a commercial subcontractor:

BuildVisionAI’s 2026 change order template guide lists a similar set, including itemized labor, material, equipment, subcontractor and markup costs, plus attachments and signatures.

Our own post on the fields every construction change order needs goes through six of them with editable templates.

Keep pending and approved money apart

The most useful habit is separating the dollars by status. Show three totals at the top of the log: approved, pending and rejected. Approved changes revise your contract value. Pending changes are exposure, because your crew may already be spending against them. If you add them together, you will overstate what is safe to bill.

A status workflow that keeps entries moving

A log with no defined statuses turns into a list of notes. Give every entry a status from a short, fixed list and a date for each move. A workable sequence:

1. Identified. Someone saw a change in the field or in a revised document. Entry opened the same day.
2. Documented. Photos, direction received, who gave it, and the time it was given.
3. Priced. Labor, material, equipment and markup calculated, with schedule impact stated.
4. Submitted. Sent to the GC in the form the subcontract requires, with the date recorded.
5. Approved or rejected. Signed by all required parties, or returned with a reason.
6. Executed and billed. Added to the schedule of values and included on a pay application.
7. Closed. Reconciled against the work actually performed.

The last step is often skipped. The Colorado guidelines recommend reconciling each change routinely, including before final contractor settlement. For a sub, that is the moment to confirm that every approved dollar has been billed and every pending item has been either resolved or formally disputed.

For a longer treatment of the stages, see our six stage change order workflow and the step-by-step approval process.

Controlling approvals before work begins

The log is only as good as the discipline behind it. The cleanest rule comes from public owners. Oklahoma’s CAP Form G701 says changed work is not authorized and must not begin until the change order is completed and signed by all parties, and it requires costs to be broken down.

Most commercial subcontracts are not that tidy. The GC’s superintendent says “go ahead, we’ll paper it later,” and the schedule leaves you little room to argue. A few habits protect you when that happens:

• Log the direction immediately. Record who told you, when, and what they said, then send a short written confirmation the same day. Our post on same-hour change order notices explains how fast notice avoids downstream delay.
• Flag the entry as “proceeding at direction.” It stays visible as higher-risk until it is signed.
• Track the work daily. Daily time and materials tickets, signed by the GC’s representative where possible, are your evidence if the price is disputed later. See daily T&M tickets and change order pricing.
• Know your contract’s notice clause. Notice deadlines and waiver language vary by subcontract and by state, so check yours, and ask a construction attorney before you sign anything that waives rights.

A structured substitution or approval process helps here too. This walkthrough of the substitution approval process shows why submittals and sign-off need to land before installation, not after.

Read waivers carefully

When a change order includes a waiver, scope matters. AGC’s 2020 contract administration training says a complete change-order waiver should expressly address direct costs, general conditions, time adjustments, and productivity or efficiency impacts. If a change order you are asked to sign says nothing about the last two, a log note such as “direct cost only, impacts reserved” keeps that open item visible. The same training advises resolving issues early and documenting resolutions fully, and, if a claim cannot be resolved, sending a contemporaneous, well-documented rejection with the contractual basis and an explanation of what the support lacks.

Assembling the change order package

Each log row should point to a complete package. New York City’s Department of Design and Construction publishes a change order document checklist requiring a log entry, a contract change form, a contractor cost proposal, an estimate or review copy, relevant specifications or drawings, and pertinent correspondence. For subcontractor changes, it also lists the approved subcontractor authorization, a subcontractor cost proposal, bids when applicable, and a notarized cost-pricing certificate.

You will not need every one of those on a private commercial job, but the habit transfers: every row in the log should link to the pricing backup, the direction or RFI, the photos and the signed form. When a dispute comes up, the person who can produce the package in an hour usually gets paid first. Our same-day field checklist for change order documentation lists what the crew should capture on site, and this guide to subcontractor deliverables and documenting impacts shows the same principle in a trade-specific project.

How to build a change order log in Excel

A spreadsheet is a fine place to start. Done right, it takes an hour to set up.

1. Create one workbook per project. Name it with the job number. Keep it in a shared folder, not on one person’s laptop.
2. Set up the log sheet with the columns above. Freeze the header row and turn on filters.
3. Use data validation for status. A drop-down list with your seven statuses prevents typos like “aproved” that break filters and totals.
4. Add a number format for money. Use currency format with negative numbers visible, since deductive changes happen.
5. Build a summary block. Use SUMIFS to total cost by status: approved, pending, rejected. Add original contract value and revised contract value (original plus approved).
6. Add an aging column. Subtract date submitted from today’s date so that anything over your threshold, say 14 days, stands out with conditional formatting.
7. Add a second sheet for cost breakdown. One row per cost line (labor, material, equipment, markup) keyed by change order number.
8. Hyperlink the attachments. Each row links to the folder holding backup, photos and the signed form.

Where Excel starts to hurt

Spreadsheets break down in predictable ways:

• Hours live in a timekeeping system or on paper, so someone retypes them into the cost sheet.
• Two people edit different copies and nobody knows which is current.
• The field has no way to open an entry at the moment the change happens.
• Running five or ten projects means five or ten separate workbooks with no combined view of exposure.

None of these is fatal on a small job. Together they explain why changes get logged late, and late logging is the reason money disappears.

Weekly habits that keep the log honest

The structure matters less than the routine. A subcontractor project manager can keep a log current with a short weekly pass:

• Monday: review everything pending. Anything older than your threshold gets a call or email to the GC.
• Midweek: ask each foreman whether any direction was given that has no entry yet.
• Friday: update statuses, refresh the pending total, and confirm that approved changes are on the next pay application.
• Monthly: compare the log against the schedule of values and the GC’s own log. Differences are the conversation to have.

When a change is never signed, the log still helps. It gives you the dates, the direction and the cost you will need to pursue payment, and our playbook for unsigned change orders explains what to do next. To catch problems earlier, read five-step scope creep control and our piece on the 48-hour approach to change order management.

Our perspective: the log is a field habit, not an office report

We build software for subcontractors, and the pattern we see is consistent. Logs fail at the handoff between the field and the office. The foreman knows about the change on Tuesday, the timesheet shows the hours on Friday, and the office hears about it when the pay application is due. By then the entry is a reconstruction, not a record.

So our view is simple: the entry should be opened by whoever sees the change, with the same data the office needs, and the labor tied to it should flow into the same place. That is why we designed CO Hub for change orders and T&M tickets to sit next to Time Budge for labor tracking, under one login. Double entry is where numbers drift and where hours go missing, and a flat per-company price means you can give the whole team access instead of rationing seats.

A log does not get you paid on its own. A clear, dated, complete record of what was directed, done and priced makes the conversation with the GC about facts instead of memory.

— Jen Reese

When a connected tool makes sense

If your log lives in Excel and your labor lives somewhere else, you are the integration. Won2Build Hub brings change orders, labor, bids and takeoff together with one sign-on, so a T&M ticket and the hours behind it are not typed twice.

Current published pricing, as read on our site: CO Hub is $59 per month per company, Time Budge is $199 per month per company, and Bid Track is $199 per month per company. Active field workers are $2 per month each. Takeoff and The Hub are listed at $0 per month. You can compare the options on the pricing page, see Time Budge for labor tracking and job cost, or look at the full product suite. There is a free trial before you subscribe.

FAQ

What is a change order log?

It is a central record of every change request on a project, with its number, date, description, cost, schedule impact, status and approvals. It also keeps a running total against the original contract sum. It sits above the individual change order documents and gives you the status of all of them at a glance.

How do I keep track of change orders?

Open an entry the day a change is identified, give each entry a status from a fixed list, and date every status change. Link the backup, such as photos, tickets and signed forms, to the entry. Review pending items weekly and reconcile the whole log before final settlement.

Can I use an Excel template for a change order log?

Yes. Set up columns for number, dates, description, reason, cost, schedule impact, status, approvals and attachments. Add a status drop-down, a SUMIFS summary and an aging column. It works well for a few changes on one project and gets harder once field time and multiple jobs are involved.

Should work start before a change order is signed?

The safest practice is no. Public forms such as Oklahoma’s say changed work should not begin until all parties sign. If your GC directs you to proceed anyway, log the direction in writing the same day, track time and materials daily, and check your subcontract’s notice terms. For anything with real money at stake, talk to a construction attorney.

Sources

• Colorado Office of the State Architect, Contract Modification Guidelines
• New York City DDC, Construction Change Orders Document Checklist
• Cook County, Form 4CO Change Order for Construction
• Oklahoma, CAP Form G701
• Young Architect, What Is a Change Order in Construction?
• BuildVisionAI, Free Change Order Template (2026)
• AGC, Fundamentals of Subcontractor Risk Management (2020)

Recommended

• Change Orders: Same Hour Notices Help Subcontractors Avoid Delays
• Change Order Documentation: Subcontractors’ Same Day Field Checklist
• Protect Margin With a Six Stage Change Order Workflow for Subcontractors
• Best Change Order Tracking Solutions for Subcontractors