A handover document has one job: let someone else carry the role without calling you every day. There are two kinds, and they are written for different readers. Below is one of each, for the same role, with a note under every section on why it is there and where its content comes from.
Both examples describe the fictional company in our live demo: Alex Rivera, a delivery lead at a retailer, running an S/4HANA migration, a vendor renewal, and four other workstreams. They are written in the exact format Understudy produces from a role record.
What is the difference between a temporary and a permanent handover?
A temporary handover tells a stand-in what will happen while you are away and how far their authority goes. A permanent handover gives a successor the whole role, including its history.
| Temporary handover | Permanent handover | |
|---|---|---|
| Situation | Parental leave, sick leave, vacation, sabbatical | Retirement, resignation, promotion, succession |
| Reader | A colleague covering on top of their own job | The person taking the role over |
| Horizon | The cover window: weeks to months | The role's past and its next year |
| Leads with | The three risks most likely to bite | Why the role exists |
| Must include | What the stand-in may decide alone, and what can wait | History, the people outside the team, a first-30-days plan |
Example 1: a temporary handover
Covering for Alex — temporary handover
If you read nothing else — the three things most likely to go wrong
- Atlas go/no-go slips sideways. Lena Petrova's pricing-table variance report lands Thursday — it decides the late-July cutover. If it's not clean, the position is slip-the-date, not patch-the-data. Keep Priya ahead of it the same day.
- The Apex negotiation stalls on you. Daniel Cho is blocked until he gets the liability-cap decision (current thinking: hold at 12 months, carve-out if pressed). Give it to him tomorrow or the redlines sit for your whole cover.
- The DPIA clock quietly eats the CDP schedule. Marcus Bell can't sign until the data-flow diagram reaches him this week; every day late pushes the pipeline build.
The role in one paragraph
Alex is Delivery Lead for Enterprise Applications at Meridian Retail: they run the S/4HANA migration (Atlas), own the Apex Logistics contract renewal, govern the Customer Data Platform build, and carry support capacity planning and the PCI remediation. Your job for the next few weeks: keep Atlas moving toward its go/no-go, don't let the Apex negotiation stall, and keep the two compliance clocks (DPIA, PCI) ticking.
What's live right now
- Project Atlas — S/4HANA migration (cutover prep). Checklist ~80%. The one thing to watch: the custom pricing-table load variance — Lena Petrova (Northwind) owes the dry-load variance report Thursday. If it's clean, the late-July cutover holds. Next event: the runbook + rollback walkthrough Priya asked for.
- Apex Logistics renewal. Redlines are back; the sticking point is the liability cap (12 vs 24 months). Daniel Cho is blocked on our position. Apex opened at a 9% uplift — the counter is flat-to-low-single-digit.
- Customer Data Platform. Build is gated on the DPIA; Marcus Bell needs the data-flow diagram before he can sign the consent model. Rachel Adeyemi's pipeline work waits on it.
- Support backlog & headcount. Three-week backlog going into peak. Decision pending: seasonal hire vs. absorbing tier-1 volume. Nadia Hassan has the req; approval is slow.
- PCI-DSS remediation. Four medium findings, owners assigned; Tom Becker owes the segmentation + logging evidence. Steady state — monitor, don't drive.
Deadlines & meetings in the cover window
- Tomorrow — give Daniel the liability-cap decision so the redlines go back. Done = Daniel has a written position he can paste into the doc.
- +2 days — runbook + rollback walkthrough with Priya. Done = Priya confirms the rollback story is board-ready.
- +2 days — ticket-type breakdown + a staffing plan to Priya.
- +3 days — data-flow diagram to Marcus (unblocks the DPIA).
- Weekly — Atlas cutover sync (Tom, Lena, Sofia); the town hall is on the calendar.
Who will come to you
- Priya Nair (sponsor) — wants cutover confidence and no surprises. Short, direct updates; bad news early.
- Tom Becker — checklist decisions and PCI evidence questions; he'll self-serve if you're explicit about priorities.
- Lena Petrova (Northwind) — the real technical counterpart; her variance report decides the cutover date. Responsive on direct questions.
- Daniel Cho — negotiation mechanics; he needs decisions, not analysis.
- Carlos Mendes (Apex) — will push for a quick close; don't concede the cap casually.
- Hannah Weiss — queue escalations; ask for data (ticket types), not anecdotes.
- Nadia Hassan (HR) — the seasonal req; chase politely, weekly.
Waiting on others
- Lena → pricing-table variance report (due Thu; chase Friday morning if silent).
- Sofia → finance reconciliation sign-off (gates cutover; chase after the variance is in).
- Daniel → final redlines package (returns once you give the cap decision).
- Marcus → DPIA sign-off (after the diagram lands).
- Nadia → seasonal req approval.
Decisions you may need to make
- Go/no-go posture: if the variance is NOT clean, the position is slip-the-date, not patch-the-data — the board prefers a late clean cutover to an on-time messy one.
- Liability cap: current thinking is hold at 12 months with a carve-out for data-breach claims; trade the uplift down before conceding the cap.
- Seasonal hire: if the ticket breakdown shows >40% repetitive tier-1, argue measurement first, hire second.
What can wait
- CDP pipeline build (hard-gated on DPIA anyway) · POS phase-2 ideas · anything Northwind commercial (James O'Connor will try; park it for Alex).
Escalation
Decide yourself: sequencing, meeting cadence, chasing. Pull in Priya: anything that moves the cutover date, concedes >0 on the Apex cap, or spends money.
Example 2: a permanent handover (knowledge transfer)
Delivery Lead, Enterprise Applications — knowledge transfer
The role's actual mission
Own the delivery of Meridian Retail's enterprise application landscape through its current transformation: migrate the ERP core to S/4HANA without breaking finance or supply chain, keep the vendor and contract base (Northwind, Apex) commercially sound, stand up the customer data platform lawfully, and keep support capacity and PCI compliance from becoming board problems.
Workstreams
Project Atlas — S/4HANA migration (the one the board watches)
Blueprint and build are done; cutover prep at ~80%. The entire live risk is the custom pricing tables — non-standard keys that didn't survive a clean dry load. History that matters: the risk was flagged in week one and has been managed openly with the sponsor since; the pattern that works is keeping Priya ahead of every wobble. Tribal knowledge: Northwind's paper says "on track" by default — the truth lives in Lena's variance numbers, not James's status slides. Go/no-go discipline: a late clean cutover beats an on-time messy one.
Apex Logistics — contract renewal
Three-year renewal; Apex opened at +9%. Position: flat-to-low-single-digit, hold the liability cap at 12 months (carve-out for data-breach if pressed), kill termination-for-convenience asymmetry. Daniel Cho runs the mechanics; he needs crisp decisions. Carlos Mendes is friendly and professional — and negotiates everything.
Customer Data Platform
Unified customer schema drafted (Rachel Adeyemi); build is deliberately gated on the DPIA (Marcus Bell) after the privacy review — that gate was accepted, not fought, and it bought credibility with compliance. Consent-flag model is the open design question.
Support backlog & headcount
A 3-week backlog going into peak. The real insight: a large share is repetitive, structured tier-1 — measure before hiring. Nadia Hassan (HR) owns the req path; approvals are slower than peak, so decisions can't wait for them.
PCI-DSS remediation
Four medium findings, owners assigned, evidence trickling in. Tom Becker owns the technical two. Low drama if chased weekly; a board topic if ignored.
POS rollout (closed)
Done and stable — the reference story for "we can execute": Tom ran the technical rollout, Hannah's floor training measurably cut support load.
The people
Inside the team: Tom Becker (integration + checklist; give him priorities, he executes), Rachel Adeyemi (data engineering; schema owner), Hannah Weiss (support lead; brings the queue truth).
Outside the immediate team — the contacts a handover usually loses:
- Lena Petrova — Northwind solution architect (vendor). The single most important external relationship. Owns the migration tech and the data loads; her numbers decide the cutover.
- James O'Connor — Northwind account exec (vendor). Commercial counterpart; escalation path for slips; treat status decks with healthy skepticism.
- Carlos Mendes — Apex Logistics account manager (counterparty). The renewal lives here.
- Sofia Marchetti — Finance. Reconciliation sign-off gates the cutover; bring her in early, never surprise finance.
- Marcus Bell — Security & compliance. Gates CDP (DPIA) and runs PCI; an ally if treated as a gate, an obstacle if treated as an afterthought.
- Nadia Hassan — HR business partner. Headcount reqs and approvals.
- Priya Nair — VP / executive sponsor. Sponsor of Atlas, approver on Apex and Support spend. Operating rule: bad news early, options attached.
Systems owned
- Workday → S/4 HR integration (SAP Integration Suite, package WorkdayToS4): 8 iFlows, currently 8/8 started, no failures. Per-iFlow source and a generated design document are in the role record (Systems, on Atlas).
- S/4 HR inbound data model (transport MRDK900412): 27 objects — tables, CDS/RAP, behavior classes; released; object-level source pulled. The V2 OData binding was retired; only the V4 binding is live.
Rhythms
Weekly Atlas cutover sync (Tom, Lena, Sofia) · sponsor 1:1 with Priya · company town hall · weekly PCI evidence chase (Tom, Marcus).
Open commitments & waits
Runbook walkthrough to Priya (this week) · liability-cap decision to Daniel (now) · data-flow diagram to Marcus (this week) · ticket breakdown + plan to Priya (this week). Waiting on: Lena's variance report, Sofia's reconciliation, Daniel's redlines, Marcus's DPIA, Nadia's req.
First 30 days for the successor
- Week 1: sit in the cutover sync; read the Atlas runbook; meet Priya with your read of the variance report. 2. Call Lena and Carlos personally — the two external relationships that decide the quarter. 3. Close the liability-cap position with Daniel. 4. Walk the CDP data flow with Marcus and Rachel. 5. Decide the seasonal-hire question off Hannah's ticket data.
- Only then look at anything new — the record above is the job.
What should a handover document include?
The people the role depends on, open commitments and their deadlines, recurring work, the systems and their workarounds, the decisions in flight with the reasoning behind them, and clear rules on what the stand-in or successor may decide alone. The 100 handover questions checklist covers each of these in detail.
How were these produced?
Understudy reconstructs a role from the work itself, the mail threads, calendar and systems of record, into a living role record. The handover documents are generated from that record, so the outside contacts, the open promises and the deadlines come from evidence rather than from what the person remembers under pressure. The record belongs to the person whose role it is, and it maps the work, not the worker. Open the live demo to see the record behind these two documents. The same record also produces the job description for hiring the next person.
How the record behind all of this is built: knowledge transfer from the work itself.