Worked scenario — illustrative, not a customer result
Illustrative case: a strategy client asks the consultant to configure the recommended system. A roadmap identifies work; it does not necessarily include doing it. Define who operates, configures, trains, and supports the implementation.
Contract checkpoint before production
Separate workshops, analysis, and recommendations from execution, operational responsibility, training, and post-launch support.
Document the actual scope change
Change record: implementation deliverables; decision authority; client resources; acceptance criteria; rollout milestones; fee; support boundary; approval of a distinct implementation phase.
Copy-and-customize wording
Use this as a practical starting point. Replace every placeholder with a fact from the approved project.
Free editable sample
No purchase or email required.
This engagement covers advisory work and the roadmap. Implementation is a separate phase; I can provide a statement of work for [deliverables, fee, timeline].
How to apply it
- Check the approved scope when: recommendations trigger execution asks
- Check the approved scope when: stakeholders expect hands-on delivery
- Check the approved scope when: support continues after the roadmap
- Estimate the changed outcome and obtain written approval of the current version
Use with care
- Match the message to the signed scope
- Estimate hidden review, QA, and coordination time
- Preserve written approval before changing delivery
Frequently asked questions
- When should I use this wording?
- Consultants should separate analysis and recommendations from implementation, ownership, and ongoing operational support in distinct statements of work.
- Is this legal advice?
- No. This is practical business wording, not legal advice. Adapt it to your agreement and ask a qualified lawyer about legal requirements in your jurisdiction.
Continue with the next decision
Scope creep for consultants
Consultants face expanding advisory scope, implementation asks, and stakeholder sprawl. This guide gives consultants triggers, scripts, and engagement checkpoints.
Contract clause libraryAdditional Work Clause for Freelance Agreements
An additional-work clause separates helpful incidental discussion from billable services and requires approval before extras begin.
Client script libraryHow to Tell a Client Extra Work Costs More
Connect the added fee to the changed work and its impact, then ask for explicit approval before starting.
Role × problem guidesScope-control solutions by client problem
Solve the exact boundary problem your profession creates. These guides combine role-specific triggers, precise wording, contract checkpoints, and a documented approval path.