The problem
Scope creep is the silent budget killer in consulting. It rarely happens all at once. It happens in small increments: a request to "just have a look at" something adjacent, a steering committee presentation that was not in the original scope, a stakeholder interview that adds three hours to the analysis phase, a client who keeps moving the goalposts on what the final deliverable should include.
Individually, each request seems reasonable to accommodate. Cumulatively, they can add 20 to 30 per cent to the actual effort on a project without any corresponding revenue. The conversation at the end of the project about billing for the extra work is uncomfortable for everyone — and harder to have when you have not documented the scope changes as they happened.
The professional solution is change request documentation: a brief, written note each time a significant out-of-scope request is made, confirming what has been asked for, how much additional effort is involved, and the commercial implications. Most consultants know they should do this. Few do it consistently because it feels awkward and takes time.
This workflow makes it quick and professional.
The system
Step 1: Log scope change requests as they happen (Notion AI)
Create a simple Notion page titled "Scope Log" for each engagement. Every time a client makes a request that is arguably out of scope, log it immediately with:
- Date
- Who made the request
- What they asked for
- Your estimate of additional effort
- Whether you agreed to do it and on what basis
Use Notion AI to help structure entries if you are capturing them quickly:
"Tidy up this scope log entry into a clear, factual record: [paste your rough notes]"
This takes two minutes per entry. The log becomes your evidence base.
Step 2: Identify billable scope changes (Claude)
At the end of each month, or when the total additional work becomes significant, review your scope log with Claude:
"Here is a scope log from a consulting engagement. Review these entries and identify which ones represent clearly billable additional work (i.e., work that was clearly not included in the original scope). For each, estimate whether the time involved is likely to be significant enough to warrant a formal change request. Group minor items that could be captured together in a single change request.
Original scope summary: [brief description]
Scope log: [paste your log]"
Step 3: Draft the change request letter (Claude)
"Draft a professional change request letter for this consulting engagement. The letter should:
- Reference the original engagement letter and scope
- Describe the additional work requested and completed
- State the additional effort involved (in days) and the fee implications
- Be firm but not confrontational in tone
- Request written confirmation to proceed with billing for additional items
The tone should be professional and collegial — this is a continuing relationship and the letter should make the conversation easy, not defensive. UK spelling, no em dashes.
Details: [paste the relevant scope log entries and any other context]"
Step 4: Maintain your scope log and send updates regularly
Do not wait until the end of the project to raise scope changes. Send brief, conversational scope acknowledgements as you go:
"Write a two-paragraph email to the client noting that the additional stakeholder interviews they requested are outside the original scope, confirming that I am happy to proceed, and noting that I will document these for inclusion in a change request. Tone: friendly and matter-of-fact, not legalistic."
The results
Before: Sporadic scope documentation, uncomfortable end-of-project commercial conversations, and write-offs on additional work that was never properly captured.
After: A systematic log that makes change conversations normal and well-evidenced.
The behavioural shift is significant. When scope changes are documented routinely and change requests sent regularly (not just at the end of the project), clients begin to understand that additional work has commercial implications. The conversations become less charged because neither party is surprised.
One consultant using this system reduced their annual write-off rate by documenting scope changes consistently across a year of engagements. The change request letters were rarely contested because they were grounded in a clear, real-time log.