Scope Change Log Template for Client Projects

Download the blank scope change log spreadsheet. No account is required. Save a copy before adding your project details.

Every change record needs a unique ID, request description, origin, classification, estimated impact, decision-maker, decision, and the date it was agreed. Store links to the relevant estimate and written approval. For small projects, one spreadsheet is often sufficient.

The Project Management Institute's scope change control guidance emphasizes first defining scope, then evaluating and approving changes before including them in the project. You do not need enterprise bureaucracy to apply that idea to a freelancer's website or branding project.

The fictional example below involves Juniper, a small business commissioning a website redesign. The values are illustrative estimates, not Noddis customer results.

Use a separate implementation status column if you also want to track whether an approved change is complete. Approval and completion are different events. An unapproved request should not become a scheduled work item merely because someone entered it into the log.

Compare the request against the project baseline: the documented deliverables, exclusions, accepted design direction, and revision allowance. A new output may be outside scope, while correcting work that fails an agreed requirement may be included. This depends on the actual agreement and is not decided by how small the client says the request is.

Use four categories:

1. Correction: Existing work does not meet an agreed requirement.
2. Included revision: A requested adjustment fits an agreed review allowance.
3. Potential change: The request adds or alters an outcome, or uses more review rounds than agreed.
4. Clarification: The request cannot be estimated until the intended outcome is defined.

A potential change requires a decision, not an automatic “no.” The guide to handling out-of-scope requests provides language for discussing those options with clients.

Calculate the effort needed to design, produce, review, revise, and release the added work. Consider whether the change interrupts a dependent task or pushes a milestone. Estimate new fees using the pricing agreement, not an arbitrary charge added after completion.

For CR-01 above, assume a fictional agreement charges $100 per additional production hour. Six hours would add $600 before any separate expenses. If those hours cannot fit into existing capacity, the launch could move by two working days. That is an example of a transparent negotiation, not a claim that all added pages cost $600 or delay projects by two days.

Present options when possible: accept the additional fee and timeline, swap the new work for something of comparable effort, or defer it to a later phase. The client should be able to choose knowingly.

Approval identifies the exact request and estimate, the person authorized to agree, and the effect on deliverables and dates. Save a written decision and link it in the log. For material contractual changes, use the amendment or change-order process required by the agreement.

A simple response might be:

Adding the FAQ page is a change to the original scope. The estimate is six hours, an additional $600, and a proposed two-working-day shift to final review. Would you like us to proceed under those terms or include the page in a later phase? We will hold the request until you confirm.

Avoid reclassifying an unanswered request as approved. If an executive or legal review is required, a casual chat acknowledgment may not be sufficient authorization.

Preserve version one of the scope agreement and append approved changes, rather than rewriting history. The PMI discussion of baseline control describes why recording baseline changes makes performance comparisons meaningful. For a small client project, the same principle is simpler: you should be able to answer what was originally promised and which additions were later authorized.

Noddis is a project management app that keeps client projects and their work connected. Its Drift feature measures scope growth against a baseline, helping make additions visible. This log provides the approval and commercial context that a scope-growth measure cannot decide for you. Connect it to the client project tracker and try the Noddis demo.

Create one change log for an active engagement. Record the next request before estimating or assigning it. That single boundary can make subsequent scope discussions more precise.