New voices need alignment against written scope, not new free work.
11 min readWelcome script
Hi [new name], great to meet you. I support [client] on [scope summary]. I route tasks through [primary] so nothing slips. Share your priorities with [primary] or on our Monday list and I will slot them in.
If they assign directly
Thanks [new name]. Logging this for [primary] to prioritize against our [X]h cap this week. [Primary], please confirm order.
Copy primary on email.
When new stakeholder = new work
New person wants new function (e.g. ads when you do inbox):
[New area] is outside our current scope dated [date]. I can send a change order for [hours/rate] or we adjust retainer tier.
See managing multiple stakeholders.
ROUTE steps
Refer to lead One thread Update scope if needed Teach process Escalate free work
Common mistakes
| Mistake | Fix |
|---|---|
| Yes to new VP to look helpful | Route and cap |
| Separate Slack DMs per person | One channel or email |
| No primary named at kickoff | Fix in recap email |
| Absorbing conflict hours | Change order |
How Salag helps
- Agreement Builder: approver field in scope.
- Freelance Readiness Checker: before multi-voice clients.
- Scope Creep Detector: new assigner language.
Move safer. Not faster.
In short
New boss, new marketing lead, new "helper" from client side = new scope risk.
Welcome them. Send them to your primary contact and written scope. Extra roles may need a rate or cap talk.
Common questions
New boss, new marketing lead, new "helper" from client side = new scope risk. Welcome them. Send them to your primary contact and written scope. Extra roles may need a rate or cap talk.
Welcome them politely. Route tasks through primary contact and written scope. Do not take orders from everyone.
One approval thread. Weekly priority email copied to primary contact.
Kickoff should name approver. Add note when roster changes.
Explain one path prevents conflicting rework. Offer intro call to align.
Refer to lead, One thread, Update scope if role grows, Tell new voice the process, Escalate if free work demanded.
New exec assigns daily urgent tasks outside cap. Change order or cap talk.
Yes. "Please route through [name]" emails set norm.
Scope creep detector on new assigners.
Priority email, scope doc, change log.
Five minute welcome and route reply.
Retainers absorb noise faster. Still need one approver.
Do not multiply free stakeholders work without cap change.