In this guide
The short answer
Manage a scope change by comparing the request with the current agreement, assessing its impact, and obtaining the authorized decision before changing commitments. Record revised deliverables, timing, commercial implications, and the next action, then update the people and records affected.
Recognize the request before changing the work
A scope change is a proposed adjustment to the agreed deliverables or responsibilities that may affect effort, timing, cost, or dependencies. The first task is to understand the request and compare it with the current agreement.
Not every piece of feedback is a scope change. Correcting an item so that it meets the agreed brief is different from requesting an additional deliverable. When the boundary is unclear, review the brief and agreement with the people who can resolve it.
Use the free scope change request template to record a request, assess its impact, and capture the decision. It is an operational record, not a legal contract or automatic approval.
Capture enough detail to assess the impact
Record what is being added, removed, or changed and why the client needs it. Refer to the current scope or brief version. Identify which part of the work is affected and what remains unchanged.
A request such as “Can we add a case study?” leaves important questions open. Does the client need a new page, a reusable layout, copywriting, customer interviews, or simply the placement of supplied material? Clarify the output before estimating it.
Keep the request and the decision separate. A helpful account conversation should not accidentally become a commitment the delivery team has never assessed.
Ask the delivery owner to assess consequences
Use the scope creep calculator to compare the request’s added cost with the baseline fee and margin. Include approved extra fees once. Separately check the team capacity calculator for role shortages before promising a revised delivery date.
Review the impact with the people who would do the work. Consider the additional production, review, dependencies, and effects on already scheduled tasks. State the assumptions behind estimates and distinguish a proposed date from an agreed date.
The following example is illustrative, not a customer result.
| Question | Example assessment |
|---|---|
| What changed? | A sixth case-study page is requested for a five-page website engagement |
| What input is needed? | Client-supplied story, approved assets, and permission for named customer material |
| What work is affected? | Content coordination, page design, implementation, and review |
| What needs a decision? | Revised deliverables, any fee adjustment, and the effect on the launch date |
| Who updates the work? | Delivery owner after the authorized client decision is recorded |
Avoid giving a precise effort or commercial commitment simply because the request sounds small. A new page can introduce dependencies or review work that are not visible in its name.
Offer understandable options
Explain the practical choices in language the client can use. Depending on the engagement, options might include adding the work with a revised schedule, exchanging it for another deliverable, or deferring it to a later phase.
Each option should say what it includes and what decision is needed. If an option depends on content arriving by a particular date, make that dependency explicit. Use your agreement's process to resolve commercial terms rather than treating a project comment as universal authorization.
The aim is to reach a shared decision. Explain the consequences without assuming that every change must be rejected or that every request should be included for free.
Record the decision before updating commitments
Confirm who can authorize the relevant change. The person who requests it may not be the person who can approve a fee or delivery-date adjustment.
Record one of the following states:
- Proposed: impact or authorization is still unresolved.
- Approved: the agreed revision and any conditions are recorded.
- Deferred: the request will be considered at a later point, with a next action if appropriate.
- Declined: the request will not be added to the current engagement, with a clear explanation.
If approval has conditions, identify them. “Approved once the client supplies the required assets” leaves a different next action from “ready to start today.” Preserve the decision reference so a teammate can understand what authorized the revised work.
Update the records and tell the people affected
After the appropriate decision, update the current brief or scope reference, tasks, dates, dependencies, and commercial records as needed. Tell the people whose responsibilities changed and identify the next action.
In ClientCee, project tasks can organize the delivery changes, while the relevant contract and invoice records provide commercial context. An approved operational change does not by itself prove that an invoice has been issued or paid. Review each handoff explicitly.
For creative teams, the creative agency workflow connects the brief, production responsibilities, and client review decisions. For the wider commercial process, see the project-to-invoice guide.
Review recurring causes at the end of the engagement
Look for repeated ambiguities in briefs, missing client inputs, and unclear review responsibilities. Use those observations to improve the next kickoff and proposal. A useful review describes what happened and what the team will change; it does not need invented savings or a headline productivity percentage.
If several requests came from the same missing brief decision, address that decision in your next project brief. If they came from a new business priority, consider how the agency should assess that priority before committing to the next service period.
Common questions
Is every client revision a scope change?
No. Compare it with the agreed deliverables, review conditions, and responsibilities. Feedback needed to meet an agreed requirement can be part of the original work. A new output or responsibility may require a separate decision.
Can we begin while the change is being assessed?
Follow your agreement and the authority given to the team. Make any limited exploratory work explicit rather than allowing an unassessed request to become an assumed production commitment.
Who should approve the change?
The person authorized for that decision under the engagement's agreed process. Identify both the agency owner responsible for the assessment and the client contact who can authorize the relevant revision.
Should the template replace our contract?
No. It helps the team record a request, its impact, and the decision. Use the agreement's process for changing commercial commitments and obtain appropriate professional advice when the contractual position needs clarification.
Published by ClientCee. See how these guides are prepared.
