Agency team handoffs: where work breaks (and how to fix it)
Why most agency mistakes happen in the handoffs between roles - and the short, structured note that prevents them. The four-part handoff template every team should use.
Part of the systemise your agency guide
The cracks between roles are where work goes wrong
Most agency mistakes don't happen inside a role - they happen between roles. Sales promises something delivery can't quite deliver. Account hands a brief to creative that's missing the constraints. The founder makes a verbal promise in a meeting that never reaches the project tracker. Every one of these is a handoff gone wrong, and they compound: a vague handoff produces a vague kickoff, which produces a vague brief, which produces scope creep, rework and a slipped deadline.
Fix the handoffs and you fix most of the operational problems the team complains about - without changing the people, the tools or the work itself.
What a clean handoff contains
A handoff isn't a status update or a meeting summary. It's a transfer of ownership. Four parts:
- Context. Why this work, what the client really cares about, the decisions already made (and why).
- Scope. What's in, what's out, the SOW reference, any constraints (budget, brand, deadline).
- Ownership transfer. Who's now responsible, by when, who they escalate to if something doesn't fit.
- Definition of done. How we'll all know it's finished - not "good," done.
Make it a habit to write all four every time, even when it feels obvious. The handoffs that feel obvious are the ones that break.
A handoff note template
HANDOFF - [Project / piece of work]
From: [name + role] To: [name + role] Date:
1. Context (3-5 lines)
What this is, why it matters to the client,
the key decisions already made.
2. Scope
In: [specific deliverables]
Out: [explicit boundaries]
Constraints: [budget / deadline / brand / etc.]
Reference: [SOW / brief / Slack thread]
3. Ownership
Owner: [single person]
Due: [date]
Escalate to: [person] if [trigger]
4. Definition of done
- [Concrete criteria 1]
- [Concrete criteria 2]Five lines, every time, no exceptions. Send it in writing (project tool, shared doc, ticket) - not a Slack DM that disappears in a scroll.
The handoffs that matter most
Some handoffs are higher-stakes than others. Prioritise these:
- Sales → delivery. What was sold vs. what can actually be delivered. The single biggest source of scope creep in most agencies.
- Account → creative / production. The brief is the handoff. Vague brief = vague work.
- Founder → team. Verbal commitments in client calls that never reach the project tracker. Either write them down immediately or stop making them.
- Team → client. Delivery handoffs to the client (especially for sign-off) - what they're approving, by when, and what happens if they don't.
Each of these has a textbook failure mode. A short structured handoff prevents all of them.
Handoffs are a leading indicator
The clever thing about tracking handoffs is that they predict trouble downstream. If your delivery team is constantly clarifying what they were given, the upstream handoff is broken - not delivery. Fix the breakdown there and the downstream problems disappear. Handoffs are also one of the highest-leverage things to systemise: a single template, used consistently, pays back across every project you run.
For where handoffs fit alongside SOPs, RACI and the rest of the operations layer, see the systemise your agency guide.
Frequently asked questions
What is a team handoff in an agency?
The transfer of ownership of a piece of work from one person or team to another - sales to delivery, account to creative, team to client. Done well, it sets the next person up to succeed; done badly, it's where most agency mistakes start.
What should a handoff note include?
Four things: context (why this work, the decisions behind it), scope (what's in, what's out, the SOW reference, constraints), ownership transfer (single owner, due date, escalation), and a definition of done (the concrete criteria for "finished").
Where do most agency handoffs break?
Sales-to-delivery (what was sold vs. what can be delivered), account-to-creative (vague briefs), founder-to-team (verbal commitments that never reach the tracker), and team-to-client (unclear sign-off criteria). Each has a predictable failure mode a structured handoff prevents.
Why use a written handoff instead of a meeting?
A meeting is a conversation; a written handoff is a record. Memory is unreliable and people leave roles. A short written note is the artefact that survives, and the act of writing it forces the gaps to surface before the next person hits them.