← Back to blog

Change Log Template: Fields, Format and Examples to Copy

November 19, 2026
Change Log Template: Fields, Format and Examples to Copy

A good change log template is a single table with one row per change and eight to twelve columns: ID, date, requester, description, impact, priority, status, decision and notes. Copy the layout below into Excel or Google Sheets, log every request (including the ones you reject), and review it weekly. That habit is what protects a freelance project manager's scope, budget and client relationship. At The Freelance PM Club we give members a library of templates and tools for exactly this kind of project paperwork, but the log itself is simple enough to build in ten minutes.

The Freelance PM Club
thefreelancepmclub.com
Keep Project Work on Track
The Freelance PM Club offers templates and tools to help freelance project managers streamline project management tasks and deliver high-quality work.
Visit

TL;DR

  • A change log is a running record of every requested or made change to a project: what, when, why and who decided.
  • Start lean: ID, date, requester, description, impact, priority, status, decision and notes. Add columns only when you feel the gap.
  • Log one change per row, and record rejected and deferred requests too.
  • Review the log at least weekly, and share it with the client so decisions stay visible.
  • The format below works in Excel or Google Sheets and takes about ten minutes to set up.

Table of Contents

What a change log is and when you need one

A change log is a project document that records modifications to scope, schedule, budget or deliverables, along with the reason for each and who approved it. It answers four questions months later, when memory has faded: what changed, when, why, and who agreed.

The CDC's Unified Process guide says that all projects, regardless of type or size, should maintain a change log and manage requested changes regularly. That includes a two-week website build for one client. If you work alone, the log is also your evidence when a client says "I thought that was included."

One naming point trips up newcomers. In software, a "change log" often means a public list of what shipped in each version (added, fixed, removed). In project management it means the internal record of change requests and their outcomes. This article covers the project management version. If your project is Agile, note that a backlog usually does the job of a change log, while the change log is used primarily on predictive (waterfall) projects, according to O'Reilly's A Project Manager's Book of Templates. Many freelancers on fixed-scope client work use the change log anyway, because clients pay for defined deliverables.

Two meanings of change log compared

The fields every change log template needs

Templates in circulation range from 8 columns to more than 18. More columns do not mean better control. They mean a log you stop filling in. Here is a core set that covers what most freelance and small-team projects need.

ColumnWhat goes in itWhy it matters
Change IDCR-001, CR-002 and so onLets you refer to one change in an email without describing it
Date requestedThe day the request reached youStarts the clock on your response time
RequesterName and roleShows who is driving scope
DescriptionOne or two plain sentencesAnyone should understand it without context
ReasonThe business need behind itHelps judge whether it is worth doing
ImpactEffect on scope, schedule and budget, with numbersThe basis for the decision
PriorityLow, medium, high, criticalSets the order of review
StatusPending, approved, rejected, deferred, implementedShows where each request stands
Decided by / dateName and dateProof of approval
NotesRationale, follow-ups, linked documentsKeeps the history readable

This lines up with what published guidance lists. A lean template from a project-tracking vendor's blog uses eight fields, and the Projectoolkit how-to guide lists thirteen components such as category, planned actions, owner, due date and closed timestamp. Treat those extras as options, not requirements.

Optional columns worth adding

Add a column only when a real problem asks for it:

  • Owner: when more than one person carries out changes.
  • Version before and after: when you maintain a requirements document or a design file.
  • Estimated cost and days: when clients pay by deliverable, so you can quote the change quickly.
  • Implementation date: when approval and delivery happen weeks apart.
  • Linked document: a path or URL to the signed change request form.

A worked example you can adapt

The entries below are illustrative, written for a fictional website project with a fixed fee. Replace the figures with your own.

IDDateRequesterDescriptionImpactPriorityStatusDecision and notes
CR-0013 MarClient marketing leadAdd a blog module to the site+$4,200, +12 daysMediumApprovedApproved by client sponsor 5 Mar. Launch date moves two weeks.
CR-0026 MarProject managerDrop 60 legacy pages from migration-40 hoursLowApprovedPages have had no traffic in a year.
CR-00311 MarClient IT leadAdd two-factor sign-in for adminsNo schedule impactHighApprovedFits within existing contingency.
CR-00419 MarClient sales leadAdd live chat widget+$6,500, +3 weeksLowDeferredMoved to a possible phase 2. Revisit after launch.

Notice three habits in this table. Every row has a number attached to its impact, even if it is zero. The deferred request is still in the log. And each decision names a person, so approval is never ambiguous.

Entry format: how to write a row people can use

Format matters as much as columns. A few rules keep the log readable a year later:

  1. One change per row. The CDC guide says to record each request as a single line item and never combine several under one ID. Otherwise you cannot approve half of a bundle cleanly.
  2. Describe the change from the client's side. "Customers can pay in two installments" beats "Update checkout.js."
  3. Put numbers in the impact column. Hours, dollars and days. "Some delay" is not an impact.
  4. Use fixed status values. A dropdown with four or five options lets you filter and count.
  5. Use one date format across the whole log, such as 17 Jun 2026, so sorting works.

If you write a public product-style change log instead, the same logic applies: short, specific entries such as "Remove support for older mobile web browsers" tell readers exactly what moved.

How to build the change log in Excel or Google Sheets

A spreadsheet is enough for most freelance projects. Here is a ten-minute setup.

  1. Create the header row with the columns from the table above and freeze the top row so it stays visible as you scroll.
  2. Add dropdowns to the Status and Priority columns using Data Validation (in Excel, the Data tab; in Google Sheets, Data, then Data validation). This stops "Approved," "approved" and "OK" from becoming three different statuses.
  3. Color the status cells with conditional formatting: amber for pending, green for approved, red for rejected, blue for implemented. A glance at the sheet then tells you what needs attention.
  4. Add a small summary block above or beside the table that counts rows by status with a COUNTIF formula, so you can report "3 pending, 5 approved, 2 deferred" in seconds.
  5. Turn on filters so you can show the client only pending items, or only changes with a budget impact.
  6. Save it where the client can see it. A shared file removes the "I never saw that" conversation.

A simple routine pairs the log with a one-page change request form: raise the request, describe it and the reason, assess impact on scope, time and cost, list options (including doing nothing), take the decision, log it, then implement and mark it done. The log is the register. The form carries the detail.

Change log, decision log or RAID log?

Freelancers often ask whether they need all three. Short answer: you need one place where changes are recorded consistently, and the choice of container is yours. Some project managers prefer one decision log with a column that marks the nature of the change. Both approaches work as long as nothing goes unrecorded.

A practical split for a small engagement:

  • Change log for requests that alter scope, schedule or budget.
  • Decision log for choices that do not change the contract. Our decision log template shows the fields.
  • RAID log for risks, assumptions, issues and dependencies. See our RAID log examples.

Logs also feed each other. An assumption that proves false can become a risk, a risk that happens becomes an issue, and an issue can trigger a change request. O'Reilly's guide suggests closing the item in one log with a note that it moved, and recording its origin in the new entry's notes. That way the trail never breaks.

Setting up a change control board for a small project

A change control board (CCB) is the group that approves or rejects change requests. On a large program it is a formal committee. On a freelance engagement it can be two people: you and the client sponsor.

A light CCB charter fits on half a page:

  • Purpose: decide on requests that affect scope, schedule or budget.
  • Members and roles: the sponsor (decides), the project manager (assesses and records), and a technical lead if needed (advises).
  • Approval thresholds: for example, you can approve changes under four hours and no cost, while anything larger goes to the sponsor. The CDC guide says a formal change system should set agreed approval-authority thresholds with impact analysis covering scope, time and cost.
  • Meeting rhythm: weekly, or inside your existing status call.
  • Output: every decision recorded in the change log within a day.

A 20-minute CCB agenda is short: review new requests, review pending items and their impact numbers, record decisions, confirm who communicates each outcome. If you already run a weekly check-in, add it as a standing item to your status meeting agenda. For the full setup, see our guide to the change control board.

Keeping the log current

A log that is two weeks stale is worse than none, because it gives false comfort. Build these habits:

  • Review on a schedule. The CDC guide says to review change requests regularly: daily on complex projects and at least weekly even on the simplest.
  • Update promptly. A PMI article on project logs advises updating promptly but at least weekly, showing the revision date, and giving logs the same care as the schedule.
  • Record the no's. Rejected and deferred requests are real outcomes. Writing down the reason shows the client their idea got a fair hearing and saves you from re-arguing it in month three.
  • Close the loop. When a change is delivered, set the status to implemented and note the date.
  • Watch for informal changes. Requests made in chat or on a call are where scope creep begins. If it is not in the log, it was not agreed. Our guide to scope creep control covers how to turn those asks into logged requests politely.

Editing an existing template to fit your project

Downloaded templates usually have too many columns. Before using one:

  1. Decide what the log is for. Scope changes only, or also bug fixes and document updates?
  2. Delete columns nobody will fill in. If you are the only person working on the project, an owner column is noise.
  3. Standardize the format for date, requester, description, reason and status.
  4. Rename statuses to match how you and your client talk.
  5. Run it for a few weeks, then adjust. A log the team finds friendly to fill in is a log that stays current.

Where The Freelance PM Club fits

If you are moving from a corporate role into freelance project management, templates like this are the easy part. The harder part is knowing when to enforce change control with a paying client, how to price a change, and where the next engagement comes from.

The Freelance PM Club is built for independent project managers and consultants. Membership includes a library of templates and tools, expert-led courses, a community of other freelance PMs, virtual events and a job board. Plans are published on our subscriptions page: Job Board Access is $5 per month, Freelancer Pro is $10 per month and Freelancer Elite is $20 per month. If you would like one-to-one guidance on your own client situations, we also offer career coaching.

The Freelance PM Club

Our perspective

Most freelancers do not lose money on the work they plan. They lose it on the small yeses: one more page, one more report, one more round of edits, each agreed in a hurry because it felt rude to hesitate.

A change log fixes that without a confrontation. When a request arrives, you do not say no. You say "let me log that and send you the impact." The conversation moves from personal to procedural, and clients tend to respect it.

This is why we pair templates with community and coaching at The Freelance PM Club. A template gives you the columns. Other independent PMs show you how they word the impact note, how they price a change, and when they let a small one through for goodwill. That judgment is what turns a spreadsheet into professional practice, and it is what a structured path from corporate employee to independent consultant is meant to build.

Start small, keep the log honest, and let it make your next client conversation easier.

Ashanti

FAQ

What is the difference between a change log and a change request form?

The form describes one change in detail: the reason, the impact analysis, the options and the decision. The log is the one-page register of all forms, with a row for each. You use the form to decide and the log to track and report.

Should I log changes that were rejected?

Yes. A deferred or rejected request is still a decision, and recording it with the reason gives you transparency and a ready answer if the client raises it again. Keep a status value such as rejected or deferred so you can filter them out of the active view.

How often should I update a change log?

Update it as soon as a request arrives or a decision is made, and review it at least weekly. Federal guidance puts the minimum review rhythm at weekly for the simplest projects and daily for complex ones.

Do I need a change log on a small project?

Yes, in a light form. The CDC guidance says all projects should keep one regardless of size. On a small engagement it can be five columns in a shared spreadsheet, reviewed in your weekly status call.

Sources