How to Prepare a Project Change Log Without Losing the Scope

A project change log connects a proposed change to its reason, likely effect and approval decision. Keep the current scope separate from requests that have not been accepted. Give each request a stable reference, identify who can decide, and record what the approved decision changes before work starts.
This guide describes a preparation workflow. The fictional reading-group website example is a desk exercise, not a real managed project, a client success story or a claim that a particular tool prevents delay.
1. Name the current baseline
Start with the version of the brief or plan that the requester currently considers approved. Record its date or version identifier and the work it includes. A change log is hard to interpret when nobody can tell what the proposed change is being compared with.
In the fictional exercise, the approved website plan includes an announcement page and a contact instruction. A later suggestion to add event registration is a new request. It doesn't become part of the baseline merely because someone mentions it during a meeting.
Use the website project brief guide to define the original assignment. The change log then records decisions made after that baseline, rather than quietly rewriting the brief and losing the reason for a different outcome.
Using a spreadsheet as the change log
If you keep the log in Google Sheets, record the baseline and approval decision in the log itself. Google's file-history guidance says a cell's edit history can omit added or deleted rows and columns, formatting changes and changes made by formulas. A reviewer cannot reconstruct those decisions from a cell's history alone.
Check the recovery method before rolling a shared log back. Google says restoring an earlier spreadsheet version clears cell-by-cell history for changes made before that restore, and advises making a copy instead when that history needs to be tracked. Inspect a copy of the older version before deciding how to recover the working log. Keep the request ID and approval record connected to the version being reviewed.
2. Capture a request before treating it as work
Record the request in plain language: what should change, why it is being requested and which part of the current plan it affects. Separate the desired result from a suggested implementation. The requester may need a way to register interest without yet having chosen a registration system.
GitHub's issue creation guidance explains that issues can track bugs, enhancements and other requests. People with read access can create an issue where issues are enabled, while administrators can disable that feature. Creating an issue therefore records a request in an available tool; it doesn't establish approval to expand a project.
A simple document can serve the same proposed workflow. Use a stable request ID and a link to the relevant baseline. Don't require a new account or move an existing team's information into a different service without authorization.
3. Describe the effect without inventing an estimate
List the work areas the request might affect: content, design, implementation, review or an external dependency. Identify what you know and what needs investigation. A request to add registration could involve the questions asked, who receives responses and what happens after submission.
Keep an estimate separate from a confirmed commitment. If the person responsible for implementation has not assessed the work, mark the timing or cost question unresolved. Don't insert a confident number simply because the change-log template has an empty column.
For the fictional example, an impact note might say: “Registration questions and response handling need an owner; implementation effect not assessed.” That note is useful because it identifies a decision required before anyone promises a delivery date.
4. Record who can accept the tradeoff
Give the request a decision state such as awaiting information, awaiting approval, approved or declined. Define who can move it between those states. A colleague explaining a possible solution is not necessarily the person authorized to accept a larger scope.
An original compact log could use these columns:
| Field | What the reviewer should find |
|---|---|
| Request ID | A stable reference used in discussion |
| Baseline link | The approved version being changed |
| Requested outcome | The problem the requester wants solved |
| Impact questions | Work or dependencies still unresolved |
| Decision and owner | Who approved or declined which version |
| Follow-up | The next authorized action |
When a request is approved, record the actual decision and its conditions. If the decision is to replace one feature with another, name both sides of that tradeoff. Avoid leaving the original feature in the plan while adding its replacement elsewhere.
5. Connect approved changes to a milestone
GitHub's milestone guidance describes grouping issues and pull requests and viewing open and closed counts, a completion percentage and a due date. Those indicators help organize recorded work. They do not by themselves demonstrate that a requester has accepted the finished result.
For the practice project, connect an approved request to the relevant delivery checkpoint and name the acceptance question. If the checkpoint is a registration preview, say who reviews the wording and how the response path will be checked. Don't mark the business outcome complete simply because a tracking item is closed.
Use the recurring dashboard guide when someone needs a later summary of progress. Agree what each status means before presenting totals, so the dashboard doesn't turn an unresolved decision into an apparently completed task.
6. Close the loop with evidence
When work is ready for review, point to the actual deliverable version and the agreed check. Record the review result, any remaining question and the next authorized action. Keep the change request, approval and delivery evidence connected through the same request ID.
If the result is rejected, preserve the reason and the version reviewed. A new revision should not erase the fact that the earlier one was not accepted. If the requester changes the requirement again, record that new decision rather than making the history appear simpler than it was.
The meeting coordination workflow can help capture decisions from a review meeting. The change log remains the record of what those decisions did to the approved scope.
When is the change log useful enough?
It is useful when a new team member can distinguish current commitments from suggestions and can find who approved a change. The log should reduce reconstruction work, not create a second competing project plan.
Try the method with the fictional registration request. Trace it from the original brief through an unresolved impact question to a stated decision. If you cannot identify the point at which the scope changed, improve the record before relying on it for a real assignment.