An agency handoff plan should help another person act when the founder is not available. That sounds obvious, but many plans become archives: a long document full of process names, links, and background that nobody can use in the moment a decision arrives.
The difference is not the amount of documentation. It is whether the plan answers the operator’s next question at the right level of detail.
For a founder-led agency, the best first handoff is usually narrower than expected. It may cover delivery exceptions, client approvals, resourcing choices, or a recurring weekly rhythm. Start with the operating work that causes real pauses. Expand only after someone has used the first version.
Define the handoff in terms of situations
Avoid opening with “everything the founder does.” That phrase has no working edge. Instead, describe the situations that should move without the founder.
Examples include:
- A client asks to add a small item to an active project.
- A delivery date is at risk and the team needs to choose what changes.
- A team member is unavailable and work needs to be reassigned.
- A supplier or freelancer needs a decision before the next working day.
- An internal disagreement reaches the point where someone must choose a path.
Use examples from the agency’s actual week. A Singapore team may need to name the local working-day rhythm, the time zone used for client commitments, or how an overseas client reaches the on-call operator. Those details are operational context, not a reason to create a universal policy.
The goal is a bounded set of moments where an operator can act with enough context and a known escalation route.
Use a five-part handoff record
For each situation, capture five fields:
1. Trigger: What tells the operator this handoff applies? 2. Decision: What exactly must be chosen or communicated? 3. Context: What facts, preferences, or history are necessary? 4. Boundary: What is within the operator’s authority, and what must be escalated? 5. Record: Where should the decision or follow-up be written?
The trigger keeps the plan from becoming a general essay. The decision keeps it from becoming a list of tasks. The boundary prevents accidental over-delegation. The record creates continuity after the immediate moment is over.
Consider a delivery change. “Handle timeline issues” is not a handoff. “When a project is likely to miss its agreed date, the delivery lead proposes a revised sequence to the client and escalates only if scope, commercial terms, or a named senior relationship is affected” is closer. The agency still needs to define its own terms, but the operating shape is visible.
Record judgment, not just steps
A checklist is useful when the path is stable. Founder dependency often appears where the path is not stable: a client has an unusual priority, a team member has a different strength, or an old exception changes what “normal” means.
Document the judgment behind the choice in a sentence or two. What are you protecting? What trade-off is acceptable? Which signal matters more when two signals conflict?
Keep this explanation close to the decision. Do not bury it in a long founder story. An operator needs enough context to make the current call, not every detail of how the founder arrived there over several years.
Also say what is not part of the decision. Boundaries are often easier to trust when the out-of-scope cases are named. “This covers routine delivery sequencing; it does not cover a new commercial commitment” is more useful than “use your judgment.”
Name the operator and the backup
“The team” cannot own a handoff. Name a primary operator and a backup for the period the plan covers. Clarify how the operator can reach the backup and what happens if both are unavailable.
This is not a recommendation about job titles or employment structure. It is a practical ownership question: who is expected to notice the trigger, make the call, and communicate it?
The founder should also name the decision they are retaining, if any. Delegation is not the same as disappearing from every decision. A credible plan can say, “The operator handles the routine case; the founder remains the escalation point for this narrow boundary.” That is clearer than pretending the handoff is complete when it is not.
The delegation without passwords guide covers an adjacent trap: using shared credentials as a substitute for clear ownership. Access and authority need separate treatment in the plan.
Test it with a real scenario
Reading the plan aloud is not a test. Give the operator one representative scenario and ask them to work through it. Let them explain:
- What did they notice first?
- What information did they use?
- What decision did they believe they could make?
- What would they communicate, and to whom?
- Where would they record the outcome?
Do not grade the operator for matching the founder’s exact wording. Look for whether the plan creates a usable path. If the operator asks a question that the plan should answer, update the relevant field. If they escalate a routine case, the boundary may be too narrow or the context may be unclear. If they do not escalate a sensitive case, the boundary needs sharper language.
The operator readiness test provides a fuller structure for running this exercise without turning it into an exam.
Keep the operating ledger alive
A handoff plan is most useful when it records the decisions that made it better. Add a small change log: date, situation tested, ambiguity found, decision made, and owner for the follow-up. This turns the document from a static founder memo into an operating ledger.
Do not create a new system for every note. Use the place the agency already trusts, as long as the operator can find it and the access boundary is appropriate. The point is traceability, not tool complexity.
Review the plan after the first meaningful use. What did the operator need that was missing? Which parts were never consulted? Which instruction was interpreted in two different ways? Remove anything that adds noise without helping a decision.
Make the plan proportionate to the absence
For a two-day absence, you may need a short list of critical decisions and named contacts. For a longer planned break, you may need to cover recurring rhythms, client communications, internal approvals, and a return-to-founder process. The plan should match the time away and the work that can realistically occur during it.
The planned founder absence guide helps connect the handoff to a calendar rather than treating it as an endless documentation project. And if the plan is part of a larger effort to make the agency transferable, see preparing an agency for ownership transition for the wider operating picture.
A good handoff plan is not a monument to the founder’s knowledge. It is a small, tested agreement about what happens next when the founder is not the next person in the route.