Last Two Weeks Handoff Skill
Your last two weeks are the trailer for how you'll be remembered — and the handoff doc is the only work artifact colleagues will use after forming their final opinion of you. The goal is specific: no one should need to call you in month two, and everyone should slightly resent that you're gone. This skill inventories what actually needs transferring (it's less than it feels, and different than it looks), writes the doc future-someone can actually navigate, and handles the mechanics — access, ownership transfers, goodbyes — that get forgotten until 4pm on the last day.
What This Skill Produces
- The handoff inventory — everything owned, triaged: transfer / finish / document-and-drop
- The transition doc — per item: state, next step, who-now-owns, where-things-live, the landmines
- The KT session plan — 2–4 sessions with agendas, because docs transfer facts and sessions transfer judgment
- The last-day checklist — access, ownership flips, personal-file hygiene, the goodbye message
Required Inputs
Ask for these if not provided:
- Role and the notice window — 2 weeks plans differently than 4
- The ownership list — projects, systems, recurring duties, relationships (internal and external), and the invisible things (the cron job only they know about, the vendor contact only they have)
- Who's inheriting — named successors, an interim manager, or nobody-yet (changes the doc from "handoff to a person" to "message in a bottle" — write for the bottle)
- The exit temperature — a happy exit and a bitter one produce the same professional handoff; only the goodbye note differs
Framework: The Triage Rules
- Triage before documenting: Transfer (ongoing things a named person continues), Finish (closeable in the window — close them, a done thing beats a documented thing), Document-and-drop (things with no owner: state them, flag the risk, and explicitly don't pretend someone will do them). The undocumented fourth category — things that should die with your tenure — gets listed too, as "recommend discontinuing."
- Write for month two, not day one: day-one questions get asked in KT sessions; the doc's job is the month-two question at 6pm with you unreachable. Per item: current state, immediate next step + date, the owner now, where everything lives (links, not descriptions), and the landmine — the non-obvious thing that will bite ("the deploy fails if run before the nightly sync; nobody knows why; run it after 9am").
- Sessions transfer judgment, docs transfer facts: schedule 2–4 KT sessions early in the window (people postpone them; late ones get cancelled). Agenda per session, successor drives the tool while you watch — watching them do it finds the gaps your doc missed.
- Relationships are handoffs too: every external contact and internal stakeholder gets a warm intro to their new counterpart before you leave — "after I go, Priya owns this; she's cc'd" — because an unintroduced successor starts from cold email.
- The last day is mechanics, not memories: ownership transfers verified (calendars, on-call, docs, admin rights, recurring meetings re-owned), personal files separated per policy days earlier, expenses filed, equipment logistics, and a short goodbye note — gratitude, contact info, zero speeches.
Output Format
Handoff Plan: [role] — last day [date]
Inventory & Triage
| Item |
Type |
Triage |
Inheritor |
Status |
Transition Doc (the artifact)
[Per transferred item: State · Next step + date · Owner now · Where things live (links) · ⚠ Landmine]
[Plus: document-and-drop section with risks stated · recommend-discontinuing list]
KT Sessions
[Session 1 (day 2–3): … · Session 2: … — agendas, successor drives]
Last-Day Checklist
[Ownership flips verified · access/equipment · personal-vs-company file hygiene (per policy, done early) · warm intros sent · expenses · the goodbye note draft]
Quality Checks
Anti-Patterns
1---2name: last-two-weeks-handoff3description: Turn your notice period into a handoff that makes you missed for the right reasons — the transition doc nobody has to call you about, the knowledge-transfer sessions, and the graceful goodbye mechanics. Use when asked I just resigned how do I hand off my work, write my transition document, plan my last two weeks, or what do I do before I leave my job. Produces the handoff inventory, the transition doc template filled with your reality, the KT session plan, and the last-day checklist.4---5
6# Last Two Weeks Handoff Skill
7
8Your last two weeks are the trailer for how you'll be remembered — and the handoff doc is the only work artifact colleagues will use *after* forming their final opinion of you. The goal is specific: no one should need to call you in month two, and everyone should slightly resent that you're gone. This skill inventories what actually needs transferring (it's less than it feels, and different than it looks), writes the doc future-someone can actually navigate, and handles the mechanics — access, ownership transfers, goodbyes — that get forgotten until 4pm on the last day.
9
10## What This Skill Produces
11
12- **The handoff inventory** — everything owned, triaged: transfer / finish / document-and-drop
13- **The transition doc** — per item: state, next step, who-now-owns, where-things-live, the landmines
14- **The KT session plan** — 2–4 sessions with agendas, because docs transfer facts and sessions transfer judgment
15- **The last-day checklist** — access, ownership flips, personal-file hygiene, the goodbye message
16
17## Required Inputs
18
19Ask for these if not provided:
20- **Role and the notice window** — 2 weeks plans differently than 4
21- **The ownership list** — projects, systems, recurring duties, relationships (internal and external), and the invisible things (the cron job only they know about, the vendor contact only they have)
22- **Who's inheriting** — named successors, an interim manager, or nobody-yet (changes the doc from "handoff to a person" to "message in a bottle" — write for the bottle)
23- **The exit temperature** — a happy exit and a bitter one produce the same professional handoff; only the goodbye note differs
24
25## Framework: The Triage Rules
26
271. **Triage before documenting:** *Transfer* (ongoing things a named person continues), *Finish* (closeable in the window — close them, a done thing beats a documented thing), *Document-and-drop* (things with no owner: state them, flag the risk, and explicitly don't pretend someone will do them). The undocumented fourth category — things that should die with your tenure — gets listed too, as "recommend discontinuing."
282. **Write for month two, not day one:** day-one questions get asked in KT sessions; the doc's job is the month-two question at 6pm with you unreachable. Per item: current state, immediate next step + date, the owner now, where everything lives (links, not descriptions), and *the landmine* — the non-obvious thing that will bite ("the deploy fails if run before the nightly sync; nobody knows why; run it after 9am").
293. **Sessions transfer judgment, docs transfer facts:** schedule 2–4 KT sessions early in the window (people postpone them; late ones get cancelled). Agenda per session, successor drives the tool while you watch — watching them do it finds the gaps your doc missed.
304. **Relationships are handoffs too:** every external contact and internal stakeholder gets a warm intro to their new counterpart *before* you leave — "after I go, Priya owns this; she's cc'd" — because an unintroduced successor starts from cold email.
315. **The last day is mechanics, not memories:** ownership transfers verified (calendars, on-call, docs, admin rights, recurring meetings re-owned), personal files separated per policy days earlier, expenses filed, equipment logistics, and a short goodbye note — gratitude, contact info, zero speeches.
32
33## Output Format
34
35# Handoff Plan: [role] — last day [date]
36
37## Inventory & Triage
38| Item | Type | Triage | Inheritor | Status |
39|---|---|---|---|---|
40
41## Transition Doc (the artifact)
42[Per transferred item: **State** · **Next step + date** · **Owner now** · **Where things live** (links) · **⚠ Landmine**]
43[Plus: document-and-drop section with risks stated · recommend-discontinuing list]
44
45## KT Sessions
46[Session 1 (day 2–3): … · Session 2: … — agendas, successor drives]
47
48## Last-Day Checklist
49[Ownership flips verified · access/equipment · personal-vs-company file hygiene (per policy, done early) · warm intros sent · expenses · the goodbye note draft]
50
51## Quality Checks
52
53- [ ] Every inventory item has a triage decision — nothing implicitly abandoned
54- [ ] Doc entries answer the month-two question: state, next step, owner, links, landmine
55- [ ] KT sessions scheduled in the first half of the notice window
56- [ ] Every external relationship has a warm intro before the last day
57- [ ] Personal-file separation follows company policy and happens early, not at 4pm
58
59## Anti-Patterns
60
61- [ ] Do not write a memoir — the doc is navigation, not narrative; links beat descriptions
62- [ ] Do not start new work in the window — finishing and transferring are the whole job now
63- [ ] Do not hand off to "the team" — every item gets a name or an honest "unowned, here's the risk"
64- [ ] Do not skip the landmines to seem tidy — the non-obvious gotchas are the doc's highest-value lines
65- [ ] Do not take anything that isn't yours — code, docs, contact lists per policy; the clean exit includes the laptop
Mohit Aggarwal