Team Leave Transition Kit — Start Here
What Is This?
A structured process for managing any team member's planned absence — paternity/maternity leave, medical leave, sabbatical, extended vacation, or resignation notice period. Produces three documents that ensure zero client items fall through the cracks and the remaining team knows exactly who owns what.
When to Use
- Team member announces planned leave (2+ weeks)
- Team member gives resignation notice
- Owner/principal plans extended absence
- Any scenario where client-facing work needs temporary reassignment
Files in This Folder
| # | File | Purpose |
|---|---|---|
| 00 | start-here.md | You're reading it. Orientation and file inventory. |
| 01 | context.md | Why each document exists, design principles, methodology. |
| 02 | terminology.md | Locked vocabulary — statuses, roles, tiers, escalation levels. |
| 03 | golden-example.html | Anonymized real-world example (Kevin Garcia / Crulliance, April 2026). |
| 04 | quality.md | QC checklist — run before delivering to client. |
| 05 | output-skill.md | Production skill — full HTML templates with placeholders. |
What It Produces
Three documents, created together as a set:
- Handoff Document — The departing person completes this. Every open item, client promise, and recurring commitment documented with system-of-record verification.
- Coverage Plan — Plans A/B/C for escalating absence duration. Role assignments, decision authority, client triage tiers, check-in schedule.
- Client Communication — Templates the departing person sends to clients + an internal team notification.
How to Use
- Read 01 (context) to understand the methodology
- Read 02 (terminology) to lock vocabulary
- Reference 03 (golden example) for quality bar
- Run 05 (output skill) to generate the three documents
- QC against 04 before delivering
Key Principle
The leave transition is not about the person leaving — it's about the clients and team who stay. Every document answers one question: "Who owns this now, and where is the information?"