Contracts

What is a change log in construction?

A change log is the running list of every change on a project, from first notice to signed change order, with its cost, schedule impact, and status.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

A change log is a single register of every change event on a job. Each row starts the moment someone flags a possible change (an owner request, an RFI answer that adds scope, a hidden condition) and follows it through pricing, submission, approval or rejection, and billing. It answers three questions the project manager and owner both care about: how much has the contract moved, what is still pending, and what has been approved but not yet billed.

What goes in a change log

  • Number and date: a sequential ID and the date the change was first identified.
  • Source: owner request, architect's instruction, RFI response, field condition, or sub request.
  • Description: a sentence a stranger could understand a year later.
  • Cost: the amount priced, the amount submitted, and the amount approved, kept as separate fields.
  • Time: days requested and days granted.
  • Status: identified, pricing, submitted, approved, rejected, or in dispute.
  • Links: the change order request, the signed change order, and the backup.

A change log on a real job

Take a $480,000 tenant improvement. In week three the owner asks for two extra offices. In week five, demo uncovers a rotted floor joist. In week six, an RFI answer moves a duct run that changes the ceiling height in the corridor. That is three changes in a month, each with a different source and a different chance of getting paid.

Example: first three entries on a tenant improvement change log
No.DescriptionSubmittedApprovedStatus
CE-01Add two offices per owner sketch$18,400$17,900Approved, billed
CE-02Replace rotted joist found at demo$3,150Submitted
CE-03Lower corridor ceiling per RFI 14$6,700Pricing

The original contract was $480,000. Approved changes bring it to $497,900. Pending changes add another $9,850 of exposure. Without the log, the PM might know about all three, but the bookkeeper preparing the pay application only knows about the one with a signature.

Common mistakes

  1. Logging only approved change orders. The pending items are where the money leaks, so log the event when it starts.
  2. Overwriting the submitted number with the approved number. Keeping both shows how much you give up in negotiation over a year.
  3. Letting work start on an unpriced change with no log entry. When the dispute comes, there is no record of when the owner knew.
  4. Keeping separate logs for the owner side and the sub side. A change that adds scope to the owner contract usually adds cost from a sub too, and both should tie together.
  5. Forgetting to update the job cost budget when a change is approved, so the job looks over budget when it is not.

Related terms

A change log draws from the RFI log and feeds the contract sum on each billing. For a ready-made layout, use the change order log template, and read how to track change orders across projects. Smart Business Automator keeps change orders, their approvals, and their billing status in one log per job.

Frequently asked questions

Is a change log the same as a change order log?

Mostly. A change order log sometimes lists only executed change orders, while a change log usually tracks every change event from first notice, including ones still being priced or disputed.

Who maintains the change log?

Usually the project manager or project engineer. Accounting reads it to bill approved changes, and the superintendent feeds it with field conditions.

Should rejected changes stay on the log?

Yes. Mark them rejected and keep the record. Rejected items are often reopened as claims, and the original dates matter.

How often should the change log be updated?

Whenever a change event starts or changes status, and at least weekly. A stale log is worse than none because people trust it.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment