Team Leave Transition Kit — Context

Purpose

This kit solves three problems that surface every time a key team member takes planned leave:

1. Knowledge trapped in one person's head — Open items, client promises, and context that only the departing person knows. If it's not documented in the system of record, it's invisible to the team.
2. Unclear ownership during absence — Team members don't know what they can decide independently vs. what needs escalation. This creates either paralysis (nothing moves) or chaos (wrong decisions made).
3. Client anxiety — Clients don't know who to contact or whether their work is covered. Silence breeds distrust.

Document-by-Document Methodology

Document 1: Handoff Document

What it is: A fill-in template the departing person completes before their last day. Not a narrative — a structured inventory.

Why each section exists:

• Open Client Items — Forces the departing person to enumerate every active item with a system-of-record reference. The critical design choice: every row must link to the practice management system (Financial Cents, Karbon, Canopy, etc.), not personal notes, Slack messages, or memory. If it's not in the system, it gets entered before the handoff is accepted.

• Client Status by Service Line — For tax/accounting firms: tax return status by client. For other firms: project status by client. The column "Who Handles During Leave" forces an explicit assignment, not a vague "the team will cover it."

• Advisory / Escalation Items — Items requiring professional judgment (not routine execution). These are the items most likely to be dropped because they require context the covering person doesn't have. The "Ruben Briefed?" column (or equivalent) creates accountability — the departing person must confirm the covering person has been verbally briefed, not just assigned.

• Recurring Commitments — Scheduled obligations that will come due during the absence. Easy to forget because they're not "open items" — they're future items.

• Personal Notes Transfer — The most important section for firms where team members keep workarounds outside the system. This section directly names the problem: "You've been keeping notes outside [system]. Transfer them now." The spot-check step exists because people will say "it's all in there" without actually doing it.

• Communication & Access — Logistics checklist. Exists because these always get forgotten on the last day.

Design principle: The handoff document is adversarial by design. It assumes the departing person will underestimate what's in their head. Every section is structured to surface what they'd otherwise forget.

Document 2: Coverage Plan

What it is: Three escalating contingency plans (A/B/C) based on absence duration, plus an immediate action checklist and check-in schedule.

Why Plans A/B/C:

Most leave transitions plan for the best case and panic when reality differs. The three-plan structure forces the owner/manager to think through escalation before it's needed:

• Plan A (best case) — Short absence, smooth return. Standard coverage assignments. Low complexity.
• Plan B (realistic) — Extended absence, limited availability. Additional coverage needed. Manager absorbs more. Requires a second client communication.
• Plan C (worst case) — Prolonged or indefinite absence. Full client reassignment. Triage required. May trigger hiring decisions.

Why the decision authority matrix matters:

The single biggest source of friction during a teammate's absence is the covering person not knowing their authority boundaries. The matrix explicitly states:

• What they CAN do independently (routine execution)
• What they MUST escalate (judgment calls, relationship decisions, scope/fee changes)

Without this, covering team members either over-escalate (bothering the manager with routine items) or under-escalate (making decisions they shouldn't).

Why the check-in schedule:

Prevents two failure modes:

1. Contacting the person on leave too early (disrespectful, creates guilt)
2. Waiting too long to assess which plan you're in (delays contingency activation)

The checkpoint question ("Are you coming back this week, next week, or do you need more time?") is deliberately simple — one question, three answers, each maps to a plan.

Design principle: The coverage plan is a decision tree, not a wish list. Every scenario has a pre-decided response.

Document 3: Client Communication

What it is: Pre-written templates the departing person sends to clients, plus an internal team notification.

Why two template options:

• Standard — Professional, thorough, appropriate for advisory/high-touch clients who expect detail.
• Casual — Warm, brief, appropriate for clients with strong personal relationships or lower-touch engagements.

The departing person (or manager) picks the right tone for each client. Neither template is "better" — they serve different relationship dynamics.

Why individual sends, not mass communication:

Each client message must include their specific status (return filed, extension filed, project in progress, etc.). A mass message that says "everything is covered" without specifics reads as generic and erodes trust. The execution notes section exists to prevent this shortcut.

Why the internal notification is separate:

The team needs different information than clients. The internal message:

• Names specific coverage assignments (not vague "we'll figure it out")
• Sets the escalation protocol (who to contact, who NOT to contact)
• References the handoff document location in the system of record
• Sets tone (support the person's leave, don't guilt them)

Design principle: Communication is not optional logistics — it's the mechanism that makes the coverage plan work. Without it, the plan exists on paper but fails in practice.

Sequencing

The three documents are created and executed in order:

1. Handoff Document — Created first. The departing person fills it in. Manager reviews and spot-checks.
2. Coverage Plan — Created second (can be parallel with #1). Manager drafts, reviews with team.
3. Client Communication — Sent last, after handoff is verified complete. Never send the communication before the handoff is done — you're making promises you can't keep.

Timing

Adaptation Notes

This kit was developed for a CPA/accounting firm (Crulliance) during a CPA advisor's paternity leave. The concepts are universal but the specifics adapt:

• Tax return status table → becomes project status table for non-tax firms
• Financial Cents → becomes whatever practice management system the firm uses
• Liscio → becomes whatever client communication platform the firm uses
• CPA advisor / tax preparer roles → become whatever role hierarchy exists
• April 15 deadline → becomes whatever external deadline applies (or remove if none)

The structure holds. The vocabulary changes.