Team Leave Transition Kit — Golden Example

Source

Client: Ruben Cruz / Crulliance (CPA firm, ~60 clients, veterinary accounting) Departing person: Kevin Garcia, CPA Advisor (Pod 2 lead) Leave type: Paternity leave Leave start: April 8, 2026 Complicating factors: Tax season deadline April 15 (7 days into leave), Kevin keeping personal notes outside Financial Cents, no CPA backup (Ashwin is tax prep only, not advisory)

Why This Is a Good Example

• High stakes: Key revenue-generating team member leaving during the firm's busiest week of the year
• System trust issue: Departing person had been keeping notes outside the system of record — the handoff forced that into the open
• Cascading constraints: Leave intersected with an active systemization project (Accounting Manager OS), an overdue approval gate (Build 3), and the owner's personal capacity limits
• Three-plan structure tested: The Plans A/B/C framework was directly useful because the C-section date and tax deadline created real uncertainty about timeline

Documents Produced

All three documents were created in a single pre-session prep block (45 minutes) and reviewed with the client on the next call.

1. Handoff Document

Sections used:

• Open Client Items (with FC column for system-of-record verification)
• Tax Returns — Status by Client (Ready / Extension / Waiting on Info buckets)
• Advisory / Escalation Items (with "Ruben Briefed? Y/N" column)
• Recurring Commitments During Leave Period
• Personal Notes Transfer (directly named Kevin's workaround: "keeping an old file of notes outside FC")
• Communication & Access checklist
• Sign-Off (Kevin + Ruben)

What made it effective:

• The Personal Notes Transfer section named the specific problem — not a generic "make sure everything is documented" but "go through your personal notes file and for each item, create it in FC." The spot-check step (Ruben verifies 3-5 items) prevented the departing person from saying "it's all done" without actually doing it.
• The tax return table forced a per-client status with explicit assignment ("Ashwin" or "Ruben" for each client), not a vague "the team handles it."

2. Coverage Plan

Plans used:

• Plan A (1 week off, then remote): Standard coverage. Ashwin handles tax prep. Ruben handles advisory. Sariah routes Liscio threads.
• Plan B (2 weeks, minimal availability): Added month-end close oversight and advisory client check-ins to Ruben's plate. Flagged capacity risk.
• Plan C (3-4 weeks unavailable): Full client reassignment with A/B/C triage tiers. Triggered accelerated third CPA advisor hiring.

What made it effective:

• The Decision Authority matrix was the most referenced section. Ashwin needed to know exactly what he could do independently (file returns, answer routine questions) vs. what required Ruben (advisory conversations, fee discussions). Without this, he would have escalated everything or decided things he shouldn't.
• The check-in schedule with specific dates prevented both "bothering Kevin too early" and "waiting too long to assess which plan we're in."
• The single checkpoint question ("Are you coming back this week, next week, or do you need more time?") mapped cleanly to plan activation.

3. Client Communication

Templates used:

• Option A (Standard) for advisory/high-touch clients
• Option B (Casual) for routine/strong-relationship clients
• Internal Slack notification for the Crulliance team

What made it effective:

• Per-client customization was critical: each message included the specific tax return status (filed / extension / in progress with Ashwin). A generic "your work is covered" would have generated follow-up questions from every client.
• The internal notification set the escalation protocol clearly: "Come to me. Do not contact Kevin unless I tell you to." This protected Kevin's leave.

Adaptation Notes

If reusing this example as a reference:

• Replace tax-specific language with the client's service lines
• Replace Financial Cents with the client's practice management system
• Replace Liscio with the client's client communication platform
• The three-plan structure and decision authority matrix are universal — don't change the framework, just the role names and functions