When three people can approve work, written alignment becomes non-negotiable.
11 min readWhy multiple stakeholders hurt VAs
- Marketing wants posts today.
- CEO wants inbox zero.
- Ops adds a "quick" spreadsheet.
You work nights. Nobody is wrong. Nobody aligned.
That is not a you problem. It is a process problem.
ANCHOR Protocol in plain terms
- Assign one lead contact.
- Note every new ask in one place.
- Compare to written scope.
- Hold approvals on one thread (email or ticket).
- Order priorities weekly.
- Record what was decided.
Kickoff questions to ask
- Who approves final deliverables?
- Who can assign new tasks?
- What happens if two leaders disagree?
- How do we handle urgent vs important?
Send answers in a recap email. Ask for "confirmed" reply.
Weekly priority email template
Week of [date] - priority plan
In scope this week (max [X] hours):
- [Task A]
- [Task B]
Waiting on client: [item] Out of scope noted: [item] - needs change order
Reply with changes by [day] or I will proceed as listed.
Copy this every Monday. See client status update templates for more.
When a new voice appears mid-project
Hi [name], welcome. To keep delivery smooth, I route tasks through [primary contact] against our scope doc dated [date]. Happy to include your asks in our next priority list.
Link: when client adds stakeholders.
Common mistakes
| Mistake | Result |
|---|---|
| Taking orders from everyone | Conflicting rework |
| No weekly priority | Fake urgencies pile up |
| Verbal "CEO said so" | No proof, no payment leverage |
| Absorbing conflict hours | Burnout, same rate |
How Salag helps
- Freelance Readiness Checker: flag missing approver before start.
- Scope Creep Detector: compare new asks from multiple people.
- Late Fee Calculator: if delays come from approval chaos.
Move safer. Not faster.
In short
Three people can assign work. Only one should approve it.
Get a primary contact, one approval thread, and weekly written priorities. Without that, you rework the same task for three different opinions.
Common questions
Three people can assign work. Only one should approve it. Get a primary contact, one approval thread, and weekly written priorities. Without that, you rework the same task for three different opinions.
Ask who has final say on scope, approvals, and payment. Get one primary contact in writing.
Route all requests through one thread. Summarize conflicts calmly. Do not let three bosses assign three urgent tasks without priority order.
Name the approver and process in your kickoff doc. Without it, you get rework from conflicting feedback.
Say multiple voices need one decision path so you can deliver on time. Offer a weekly priority call.
ANCHOR: Assign one lead, Note all asks, Compare to scope, Hold one approval thread, Order priorities weekly, Record decisions.
When conflicting directions block delivery or new people assign free work. Escalate to the primary contact in writing.
Yes. One email thread with confirmed priorities beats three Slack DMs.
Scope tools help you show what fits when everyone wants something different.
Shared doc, weekly recap email, scope creep detector, time ledger.
Ten minutes every Friday for a priority recap email.
Retainers need weekly priority lists. Projects need milestone sign-off from one approver.
Pause new tasks until priorities are confirmed. Protects you and the project.