How to handle scope creep with a scope change log
A scope change log turns "can you also..." into a recorded, priced decision instead of a silent extra week of work.
Handle scope creep by logging every request that falls outside the brief before you start it: note who asked, what they asked for, the extra hours and fee, the days it adds, and the client's decision. A request stays Pending, and unstarted, until someone decides. The log is a record of decisions, not a legal document.
What is scope creep?
Scope creep is work added to a project after the brief was agreed, without a matching change to price or dates. It rarely arrives as one big demand. It arrives as small additions that each feel too minor to mention, and the total becomes a project nobody quoted.
How does a scope change log work?
You keep one table per project. Each outside-the-brief request gets one row, and the row moves through a fixed set of statuses. The process has five steps, in this order:
- Notice. Compare the request with the brief's deliverables and exclusions. If it is covered, it is not a change.
- Log it before starting. Add the date, who asked, and what they asked for in their own words.
- Price it. Estimate the hours, multiply by your rate, and note any days it adds to the schedule.
- Send the options. Tell the client what it costs and what it does to the dates, and let them choose: add it, swap it for something in the brief, or leave it.
- Record the decision. Mark it Approved, Declined or Pending, with who decided and when. Update the project dates if it was approved.
The fee is simple arithmetic, and it helps to write the formula down so the client can follow it:
Extra fee = extra hours x hourly rate
What does a scope change log look like?
This is a sample with invented data, at a rate of 65 per hour. It matches the example in the kit's workbook.
| ID | Request | Original scope | Extra hours | Extra fee | Days added | Status |
|---|---|---|---|---|---|---|
| SC-01 | Add a catering page with a separate enquiry form | Not in brief (exclusions) | 5.0 | 325.00 | 4 | Approved |
| SC-02 | Add an online payment option for orders | Brief, exclusions: online payments | 12.0 | 780.00 | 10 | Pending |
| SC-03 | Change the menu photo crop on the home page | Within revision round 1 | 0.0 | 0.00 | 0 | Declined |
Read the last row carefully: SC-03 was logged as a request but declined as a change, because it is a normal revision handled inside the included rounds at no charge. Logging it still shows the client that you checked. In the sample, one request is Pending, worth 780.00, and nothing on it has started.
How do you tell a revision from a scope change?
A revision changes how something already in the brief looks or reads. A scope change adds something the brief did not include. If you can point to a deliverable in the brief and the request improves that deliverable, it is a revision. If you cannot, it is a change.
| Request | Usually | Why |
|---|---|---|
| Make the heading larger and change the button colour | Revision | Adjusts an existing page. |
| Rewrite the About text we already approved | Revision or change | A revision if it is within the round limit; a change if the copy was approved and a new round is needed. |
| Add a booking form | Scope change | A new feature that is not in the brief. |
| Add three more pages | Scope change | New deliverables, new hours. |
| Redo the layout after sign-off | Scope change | Approved work being reopened. |
Your brief and your revision allowance decide the borderline cases, which is why they should be written down at the start. Count review rounds the same way each time: one consolidated set of feedback on one version is one round.
What should you say to the client?
Keep it factual and give them a choice. For example:
Hi [Client first name], thanks for the idea about [request]. It is outside the agreed brief, so I have logged it as a change rather than fitting it in quietly. I estimate [hours] hours, which is [fee], and it would move the launch date by [days] days. A) Add it, with that fee and date. B) Swap it for [item in brief]. C) Leave it out for now. Tell me which you prefer and I will not start until you do.
Option B matters. Often the client has a fixed budget and would happily trade one item for another, but never realised that was possible.
What if the client does not answer?
The request stays Pending and you do not start it. A Pending row keeps its value visible in the log summary, so the unanswered decision does not disappear. If the missing decision blocks a milestone, say so: "The launch date depends on SC-02. If I do not hear by [date], I will leave it out and keep the original date." Then do exactly that.
What does a scope change log not do?
- It does not replace a contract. A log entry is a record of a decision, and it is not a legally binding change order. Any terms you agree with clients should be reviewed by your own qualified adviser.
- It does not make a client accept a price. It makes the price and the date visible before the work, which is when disagreement is cheapest.
- It does not fix an unclear brief. If the exclusions were never written down, the log will have more borderline cases.
Where can you get a ready-made scope change log?
The Client Delivery Kit includes a Scope changes sheet that calculates each extra fee, summarises Pending and Approved value and totals the days added, plus a Scope change message script. It pairs with the Brief sheet, so the exclusions you wrote at the start are the ones you check requests against. The kit's quote logic is also available to try on the kit page, and the first week of a project is covered in the client onboarding checklist. I built the workbook myself and verified its formulas against an independent calculation in LibreOffice; it has not been opened in Excel or Google Sheets by me, so check dropdowns and date formats if you use it there.