Is a second round of stakeholder review in scope?
Ambiguous — a new stakeholder reviewing already-approved work usually introduces new feedback that exceeds the original scope, but the review itself isn't the billable activity. The new revisions are.
Why this answer
Stakeholder review is one of the most misunderstood scope boundaries. A review itself — someone looking at work and giving an opinion — isn't a billable unit. What creates scope impact is what comes out of the review: new feedback, new revision rounds, new direction changes. If a new stakeholder (a CEO, a legal reviewer, a new marketing director) joins and rubber-stamps the existing work, no scope issue. If they want substantive changes, those changes are what matters, not the review itself. The scope analysis should focus on the revision rounds the new feedback triggers, not on 'can we add a reviewer.'
When the answer flips
Clearly In Scope: the new stakeholder reviews and has no substantive changes, or the new feedback is minor enough to fold into your remaining included revision rounds. Clearly Out of Scope: the new stakeholder rejects the current direction and wants to restart, effectively invalidating the work done so far. Most common: somewhere in the middle — the new stakeholder has meaningful but not direction-changing feedback, which pushes you past the revision rounds originally budgeted. Treat this exactly like any other 'one extra revision round' situation: acknowledge, quote the clause, offer a change order.
What to do next
Clarify the stakeholder's role before accepting the feedback. 'I want to make sure I understand their authority — is this a sign-off review or a consultative review?' If it's consultative (they're giving input but not blocking), you have more room to incorporate the most useful feedback without a scope fight. If it's sign-off (they can block the project), the dynamics shift: their feedback is effectively a new approval gate, which likely wasn't in the original scope. Document the clarification, then treat their feedback as any other revision round — within the included rounds if possible, as paid work if not.
Frequently asked questions
What if the client says the new stakeholder 'was always going to review'?
Check your original project brief. If stakeholder reviewers weren't listed, a new one is genuinely new — regardless of whether the client planned to include them internally. 'We always meant to' doesn't put it in the scope you signed.
Can I refuse to incorporate a new stakeholder's feedback?
You can, but rarely should. If they have sign-off authority, refusing means the project stalls. Better: accept the feedback, quote the additional work as a change order, and let the client decide whether to pay for the revisions or push back on the stakeholder internally. Your job is to deliver work and manage scope, not manage the client's internal politics.
How do I handle a stakeholder who joins late and wants to change everything?
Treat it as a pause-and-renegotiate moment. Stop incremental work, write a new project brief based on the new direction, quote it, and get explicit agreement. Proceeding as if this is still the original project will burn hours and eventually force a harder conversation.
Should stakeholder lists be in the contract?
Yes, or at least in the project brief. Name the primary approver(s), and add a clause that new stakeholders introduced mid-project trigger a scope review. This doesn't prevent new stakeholders — it makes their arrival a structured event rather than an ambiguous one.
What if the new stakeholder is actually my main point of contact's boss?
Their feedback has authority weight even if it introduces scope change. Handle it respectfully: 'I want to make sure [name] is happy with the direction — incorporating this feedback is about one additional revision round of work. I'll send a short change order to cover that.' Don't pretend the scope impact isn't real just because the request comes from a senior person.
Related reading
- The full guide
The scope creep guide for freelancers
How to spot scope creep, why clients do it, what it costs you, and how to respond professionally.
- Scenario
Is one extra revision round in scope?
Ambiguous — one extra round is one of the most context-dependent scope questions. If your contract lists a specific number of rounds, anyth…
- Scenario
Is a full logo redesign out of scope mid-project?
Yes — in nearly every freelance design contract, a logo redesign introduced after the original logo has been approved is a separate engagem…
- Clause guide
What a revisions clause should include in freelance contracts
A strong revisions clause defines three things: how many rounds are included, what counts as a round (consolidated feedback from a named ap…
- Scenario
Is a rush deadline out of scope?
Yes — a mid-project deadline acceleration is out of scope unless your contract explicitly accommodated shifting timelines. The work itself…
- Email template
Copywriter scope creep email template
A professional email template for copywriters responding to out-of-scope client requests.
Answer scope creep from your actual contract — not a template.
Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.