Source: frameworks/kit-team-leave-transition/04-team-leave-transition-quality.md

Team Leave Transition Kit — Quality Checklist

Run this checklist before delivering any of the three documents to the client.

Before Creating

[ ] Leave dates confirmed with departing person
[ ] Team roster and role assignments available (reference data)
[ ] Practice management system identified (Financial Cents, Karbon, Canopy, etc.)
[ ] Client communication platform identified (Liscio, email, portal, etc.)
[ ] Client list for departing person available
[ ] Any external deadlines known (tax deadlines, audit dates, filing dates)

[ ] Every section has content (no blank sections — if N/A, mark explicitly)
[ ] Every open item row references the system of record (not "see my notes")
[ ] Client status table covers ALL clients, not just "the ones I remember"
[ ] Advisory/escalation items include context sufficient for the covering person to act
[ ] Personal notes transfer section is present and names the specific workaround (e.g., "your personal notes file," "your spreadsheet," "your notebook")
[ ] Sign-off section has both departing person AND manager lines
[ ] Communication & access checklist is complete

[ ] All three plans (A/B/C) are present with realistic scenarios
[ ] Every function in the coverage table has a named person (not "TBD" or "team")
[ ] Decision authority matrix clearly separates "can do independently" from "must escalate"
[ ] Immediate actions checklist has owners AND due dates for every item
[ ] Check-in schedule includes specific dates and specific actions
[ ] Plan activation checkpoint has a clear trigger question and mapped responses
[ ] Emergency protocol defines who can contact the departing person and under what conditions

[ ] At least one template option provided (standard or casual)
[ ] Template includes per-client customization points (name, specific status)
[ ] Execution notes specify individual sends, not mass blast
[ ] Clients with open advisory items get an additional line about briefed coverage
[ ] Internal team notification is separate from client communication
[ ] Internal notification names specific people and specific coverage assignments
[ ] Tone is supportive of the departing person (not framing leave as a burden)

[ ] HTML renders correctly in browser (open file, visual check)
[ ] Tables copy cleanly into Google Docs (select all in browser, paste)
[ ] All placeholders are marked with visible styling (highlight, brackets, or bold)
[ ] No hardcoded client names from golden example left in templates
[ ] Firm name, system names, and role titles match the actual client's firm

Do not deliver until:

All three documents pass their section checklists above
Advisor has reviewed all three documents for accuracy
Client-specific details (team names, system names, role titles) are correct
Documents have been tested: open HTML in browser, select all, paste into Google Doc