The part of your job that rarely makes it into a handover is the part you do without thinking. Here's how to get it out of your head and onto the page, with AI doing the asking.
Don’t ask AI to write your handover from your files. Ask it to interview you, one responsibility at a time, so the unwritten habits and exceptions come out. Turn the answers into one card per responsibility, mark anything the AI inferred, and have the person covering say the card back to you before you leave.
Say you run accounts payable at a mid-sized company and you’re starting twelve weeks of leave on Friday. On Thursday afternoon you write the handover document: a link to the payment tracker, the bank portal steps, a list of the fifteen suppliers with their terms. It looks thorough. The colleague who’s covering says thanks and clearly means it.
Then the payment run comes round in week two. Two of those suppliers, freight and cleaning, get paid a week early because they charge late fees, and nobody ever wrote that down. It’s just what you do. The bank portal token also expires on the 24th, and the only reminder for that was you. You left both out because they’re so ordinary to you that they didn’t register as information.
That gap is where AI is genuinely useful, and it isn’t where people usually put it. The usual move is to paste your files into a chat and ask for a handover document. You get a tidy summary of what’s already written down, which your colleague could have found without you. The more useful move is to have AI interview you, so the questions pull out what you wouldn’t think to write.
This guide covers what a handover has to carry, the interview method with a prompt you can paste, how to split the work between AI and you, and a read-back test to run before you go. It’s written for someone stepping away for a stretch or leaving a role, and it works for individual contributors and managers, with a few differences I’ll point out along the way.
A handover has four kinds of content. Where things live: links, folders, systems. How things run: the steps. Who’s involved: people, roles, suppliers. Files and a good template can carry those three. The fourth is judgment: the habits, thresholds, exceptions and reasons that you apply without noticing. That’s the part that sits in your head, and it’s the part a cold copy-and-paste from your inbox won’t recover.
The fix is to write handovers in units small enough to fill in properly. One card per recurring responsibility, not one document per project. Here’s what a filled-in card looks like for the payment run above.
| Field | Filled in |
|---|---|
| Responsibility | Monthly supplier payment run |
| What good looks like | Every approved invoice paid by the 25th, and no supplier chasing us. |
| When and where | Prep starts on the 15th. The approved list is on the “Run” tab of the payment tracker. The bank portal needs two approvers. |
| The unwritten habit | Freight and cleaning suppliers get paid a week early because they charge late fees. There’s no rule for this. It’s a habit, so keep doing it. |
| You can decide alone | Holding a payment under $5,000 while a query is open. |
| Escalate first | Any change to a supplier’s bank details. Any payment over the approval limit. Ask the Controller, by phone, not email. |
| What can go wrong | The portal token expires on the 24th. Renew it on the 22nd, through IT. |
| Who to ask | The AP clerk for supplier questions, the Controller for anything over the limit. |
The amounts, dates and roles are placeholders, and the layout is the point.
In my judgment the bottom four rows do the most work, and they’re also the ones you’re least likely to fill in from memory. The unwritten habit and the escalate-first line are the two that a good handover exists to carry. “Change to a supplier’s bank details” is on that card because a convincing email asking for new bank details is a risk worth deciding in advance, and a rule written beforehand is easier to follow than a judgment made under pressure.
A handover is finished when a capable stranger could run the work from it, not when everything has been listed.
Write each card for someone smart who hasn’t seen your inbox. That single test removes most of the shorthand: “the usual folder,” “as agreed with Priya,” “you know the one.” The person covering for you may well know the folder. They won’t know which of the four similar folders you mean at 4:45 on the 24th.
The method has three steps, and the order matters more than the tool. It works in ChatGPT, Claude, Gemini or Copilot, as long as your organization allows the tool for this kind of material.
| I’m going on leave for 12 weeks, starting Friday 2 October. A colleague will cover my work. I want you to interview me about one responsibility so we can build a handover card for it. The responsibility: monthly supplier payment run. Below are last month’s emails and the tracker tab, with names and credentials removed. Before you ask anything, quote the three details in them you think a newcomer would most likely get wrong. Then interview me. Ask one question at a time. Focus on: what I do from habit without a written rule, what I check before I act, what goes wrong and how I notice, when I’d ask someone else first, and what a newcomer should leave alone. If my answer is vague, ask a follow-up. Don’t fill gaps with guesses. When I say “done,” write the card with these fields: what good looks like, when and where, the unwritten habit, what they can decide alone, escalate first, what can go wrong, who to ask. Put “(inferred)” after any line that came from the files and not from my answers. |
Swap in your own responsibility, dates and material. The “(inferred)” instruction is the line that makes the draft checkable.
Here’s roughly how it goes. Say you coordinate recruiting and you’re handing over the interview scheduling process. Somewhere in the interview the AI asks: “What happens when a hiring manager hasn’t submitted feedback 48 hours after an interview?” You start to answer “I chase them,” and then realize what you actually do. You message the manager, then their assistant, and if the candidate is a strong one you flag it to the recruiting lead, because feedback delays lose candidates. None of that was written anywhere. It’s now three lines on a card.
Two things make this work. You’re answering a specific question instead of facing a blank page, which is far easier than remembering what to write. And the AI has no stake in what’s “obvious,” so it asks about the things you’d skip. It’s also worth having it quote first. Anthropic’s documentation for Claude advises that, for long document tasks, you ask the model to quote the relevant parts before doing the task.[1] That’s vendor guidance, not independent research, but it fits the job: quoting first is what keeps a summary from smoothing away the odd detail that mattered.
Ask AI to interview you before you ask it to write anything.
There’s a limit worth knowing. AI can only ask about what it can imagine, and it will happily produce fluent filler for anything it can’t. That’s why the prompt says not to guess, and why the “(inferred)” tag exists. If the repeatable part of a responsibility is really a procedure, our guide to writing standard operating procedures with AI covers the step-by-step version, and the card sits on top of it. And if you’re unsure what you can paste into a tool at all, read how to use AI at work without leaking confidential company data first.
Handing this to AI doesn’t hand over the responsibility. The decisions on the card, especially “you can decide alone” and “escalate first,” are yours, because they carry your authority and your organization’s risk. A clear split keeps the document honest.
| What AI does | What you still own | How it gets checked |
|---|---|---|
| Turns your interview answers into one card per responsibility, in a fixed layout | What the covering person may decide alone, and what they must escalate | The covering person reads each card back to you; you fix any line they’d have to guess |
| Lists every deadline mentioned in your emails and calendar for the next twelve weeks | Which deadlines are real and which have already lapsed | You compare the list against your calendar before the last day |
| Flags the questions it couldn’t answer and marks inferred lines | Answering them, or writing “unknown, ask Sam” with a name | Nothing tagged “(inferred)” goes into the final version |
| Drafts the short note to suppliers or clients about who to contact | The relationship, the tone, and what stays confidential | You send it yourself, from your own account |
The same split works for any handover. Only the cards change.
Who’s handing over changes how you use this. Honestly, “employees” is too blunt a category here, so it helps to name the cases.
Hospitals have studied handovers closely, because a bad one shows up in patient outcomes. In one widely cited evaluation, nine pediatric residency programs adopted a structured handoff called I-PASS: illness severity, a patient summary, an action list, situation awareness and contingency plans, and a last step called synthesis by receiver, where the person taking over says the plan back. Medical errors fell from 24.5 to 18.8 per 100 admissions, and preventable adverse events from 4.7 to 3.3.[2]
Two things stand out for an office handover. The read-back is built into the method, and it’s the step most handover documents don’t have. And it wasn’t only a template. The programs also ran a workshop, simulations and observation feedback, and three of the nine sites didn’t reach a significant reduction.[2] A format helps. Practice with the format is what seems to change behavior. A payment run and a hospital ward carry different risks, so treat this as a design idea for your handover, not a forecast of your results.
Your handover isn’t finished until the person covering has said it back to you.
Here’s a quick way to score where you are, with the accounts payable example filled in. One point per yes.
| Question | AP manager’s answer | Point |
|---|---|---|
| Can the person covering say, without looking, what runs in the first week? | Yes, said back on Tuesday | 1 |
| Does every recurring task have a date and a place it lives? | Yes | 1 |
| Does every “escalate first” line name a person, not a team? | No, one says “Finance” | 0 |
| Has every habit become a rule with a reason? | Yes, the early-payment habit now has its late-fee reason | 1 |
| Did they ask at least three questions in a walk-through of one card? | Yes, five | 1 |
| Does the card say what to leave alone? | No | 0 |
Score 6: ready. Score 4 or 5: fix the gaps this week, starting with the zeros (this example scores 4). Score 3 or less: it’s a list of links, not a handover yet.
You can rehearse before the human read-back. Open a fresh chat, paste in the finished cards, and ask the AI to play the person covering. Say the accounts payable manager does this on Wednesday. It comes back with five first-week actions and two guesses it had to make, and one guess is which supplier gets paid early. That’s a missing line on a card, found while there’s still time to fix it.
| You’re a capable colleague covering for me for 12 weeks. You haven’t done this work before. Read the handover cards below and answer three things. 1. The first five things you’d do in week one, in order. 2. Every place you’d have to guess. List each guess separately and don’t resolve any of them yourself. 3. The three questions you’d want to ask me before I go. Then point out any “escalate first” line that doesn’t name a specific person. |
The instruction not to resolve guesses matters. Left alone, a model tends to fill gaps with reasonable-sounding assumptions, which is the failure you’re testing for.
Treat the dry run as a cheap rehearsal, not a replacement. The AI can find gaps a careful reader would find, but it can’t tell you whether your colleague actually understood which supplier matters. Only the person covering can say that, out loud, to you.
A handover done in one afternoon tends to look like Thursday’s document from the start of this guide. Spread over two weeks, the same work takes a few short sessions.
List every recurring responsibility for the next twelve weeks. Run the interview prompt on each and produce one card per responsibility. Start with the one that would hurt most if it lapsed.
The person covering reads the cards. Walk through the top two together. Run the dry-run prompt on all of them and fix the guesses it lists.
Date and freeze the document. Send the note to suppliers or clients. Agree the reach-out rule. Hold a 30-minute read-back, and score the six questions above.
The person covering owns the document now. When they hit a gap, they fix the card. You stay out of it unless the reach-out rule applies.
Read what changed. Keep the cards current, since they’re the start of the next person’s onboarding, and of any procedure you later write up.
Shorten the schedule if you need to, but keep the read-back and the freeze.
To know whether it worked, look past whether the document exists. Use, persistence and impact are a better lens than a checkbox.
If you want this to be how a whole team hands work over, not one careful person’s habit, it’s a different job from the steps above. Training builds the skill of interviewing with AI and writing a card someone else can run. Workflow design gives it somewhere to live, for example a completed card set as part of approving any leave request. Reinforcement is a manager who asks for the read-back. Adoption is what you see when that happens without being asked. A team can start with this guide on its own, and structured training shortens the path to a shared standard. If that’s what you’re after, our corporate workshops are built for it, and the cards also feed into onboarding a new hire with AI.
For today, pick the one responsibility that would hurt most if it lapsed while you’re away. Run the interview prompt on it, produce the card, and put the read-back in the calendar before you do anything else.
It depends on what your organization allows, so check the policy first, or ask IT. Even where a tool is approved, remove passwords, security tokens and customer personal data before pasting, and describe the sensitive parts in your own words instead. People matters such as performance concerns, pay and health don’t belong in an AI tool for a handover at all. Our guide to using AI without leaking company data covers the wider rules.
Use one cover page plus one card per recurring responsibility. As a working rule of thumb, a card that runs past a page is really two responsibilities and should be split. A typical role might end up with a handful of cards. That’s my judgment rather than a measured figure, and the useful test is the read-back, not the page count.
Write down the three things that would break first in the next thirty days, and run the interview on those alone. Put “unknown, ask Priya” with a real name on anything you can’t answer, and leave your personal contact details if the company agrees. In my view, a rough card for the riskiest responsibility is worth more than polished cards for the safe ones.
Yes, and it can work well, because they know what they don’t know. If you record or transcribe the conversation with a meeting-notes tool, get consent and check your organization’s policy first. Then have them, or the AI, turn the transcript into cards, and score them with the same six questions. The read-back is still the last step.
Name an owner and a next-review date on the cover page, and let the person covering edit the cards whenever they hit a gap. Read them again in your first week back. A card that gets used during your absence stays accurate, and one that nobody opens is the sign that it didn’t help.
The structured handoff figures come from Starmer and colleagues’ evaluation of the I-PASS program in nine pediatric residency programs, published in the New England Journal of Medicine in 2014. The journal page and the PubMed abstract could not be read directly when this article was written, so the figures were read from the AHRQ’s Making Healthcare Safer IV review on NCBI Bookshelf, which quotes them. The advice about asking a model to quote long documents first comes from Anthropic’s own prompting documentation, so it’s vendor guidance, not independent research. The example handover cards and dialogue are illustrative, not real cases. A widely reported government trial comparing AI and human summaries was left out because its primary submission could not be opened.
Weekly tips. Real examples. Practical help for busy professionals.
We care about your data, check out our privacy policy.