A job handover document can work as one page that answers seven questions: what the role is, who to contact, what repeats and when, where files and systems live, what is still open, which decisions need judgement, and who covers what. It cannot hand over years of expertise, so its job is narrower: keep the work moving and let the next person find things without phoning you.
The same page serves a last day and a long spell of leave. The emphasis differs, and so does what you need to test.
What a Handover Document Is For, and Its Limit
APQC defines a job handoff document as a record you create for someone who is taking over your job, either temporarily or permanently. It is clear about the limit too: a handoff document cannot transfer in-depth expertise from years in a position. Lauren Trees, formerly APQC's principal research lead for knowledge management, suggests positioning it as an insurance policy to avoid chaotic transitions, and names leave, unplanned absence and people leaving as the moments it covers.
That limit shapes the design. A page cannot carry what you know, so it should carry what the next person needs to find, do and decide in the first weeks, and point to a conversation for the rest. APQC notes that overstretched employees may see these documents as busywork, or even suspect the aim is to make it easier to fire or lay them off, and says trust must be earned. It calls continuous updating unrealistic and says most organisations gravitate towards an annual review cycle. Say at the top why the page exists, and date it.
The One-Page Structure: Seven Blocks
Use seven blocks, each short enough that the whole page fits on one side of paper. They adapt APQC's seven areas: the overview, contacts, routine activities and filing system stay, and job details fold into the recurring tasks. Open items, judgement calls and cover are added, drawing on Harrin's advice.
1. Role overview
Two or three lines: what the role exists to do, who it reports to, and what a good month looks like. APQC's equivalent is a basic job description covering objectives and key activities.
2. Key contacts
List each person with what they handle and when to call them. APQC frames contacts as the people someone might need to reach while doing the job, with guidance on when and why. Ask every named person first: Harrin advises checking that each one is happy to cover for you, and, if in doubt, putting your manager as the out-of-office contact.
3. Recurring tasks, with the schedule
Group tasks by rhythm: daily, weekly, month-end, annual. Give each a day or trigger, the steps in a line or two, and a link to the longer procedure. Harrin's advice for a manager handover is to include recurring and month-end processes, not only daily tasks, and APQC adds standing meetings, reviews and audits. A usable line reads: "Supplier invoices: Fridays, approve in the finance tool, query anything unusual with Priya."
4. Where files and systems live
Give paths, not descriptions. "Shared drive, Purchasing, Suppliers, Approved list" beats "in the usual folder." The test: could someone find the supplier list in under a minute using only the page? APQC's filing-system area covers where key work information is kept, such as folders, team sites and systems. An NHS trust's handover guide for leavers adds a question worth copying: is access to shared drives, Teams channels and systems up to date?
5. Open items and deadlines
One line per item: what it is, its status, the next action, the date, and what happens if nobody acts. Harrin's checklist asks for pending decisions, dependencies and the consequence of inaction, and her manager-handover advice lists each outstanding item with status, open actions, risks and issues.
6. Judgement calls and decisions due while away
This block holds the judgement that a list of facts leaves out. For each decision that could land on the cover person's desk, write the situation, your usual call and the reason. Harrin recommends explaining judgement calls as well as facts, and listing pending decisions with your recommendation. Example: "If a client asks for terms outside the agreed band, decline and ask the sales lead." Anything unpredictable goes in an escalation line: who decides, and how to reach them.
7. Who covers what
Name one person per area, not a committee. Harrin's profile of a good cover person: sufficient authority, an understanding of the work area, knowledge of where information is stored, spare capacity and knowing when to escalate. They should not be expected to do your whole job on top of theirs.
Keep the page to one side and link out for detail. Reed notes that the right length depends on the role, so a complex role can keep page one as the summary. If your employer has a template, follow it.
Leave or Exit: What Changes When You Cannot Be Reached
The difference is whether anyone can ask you a question afterwards. On leave you come back, so the page covers a window and the risks inside it. On exit you cannot count on being asked, so the page carries more reasoning and the files have to outlive your account.
For leave, Harrin starts by checking what will happen while you are away, then decides for each likely problem whether to prevent it, delegate it, escalate it or defer it. Set an out-of-office message with dates and a named contact, and do not become an emergency contact unless you have agreed to it. Plan a handback for your return. Start two to three weeks before you go.
For an exit, Harrin says to write a comprehensive report instead, and files need a second look. Microsoft's documentation for work accounts says the default retention period for a departed user's OneDrive is 30 days, a period administrators can change. The manager gets automatic access by default, but if delegation is off or no manager or secondary owner is set, no one has automatic access. Ask your IT team what happens at your organisation, and move files into shared team storage, or share them, before the last day.
| Part of the handover | Going on leave | Leaving the role | Who to ask |
|---|---|---|---|
| Depth | Short: the window you are away and its risks | Fuller: a comprehensive report with the reasoning | Your manager |
| Reachability | Out-of-office with dates and a named contact | You may not be reachable, so write the why as well as the what | Your manager |
| Files | Stay where they are, with access tested | Move work out of personal storage | Your IT team |
| Access | Delegate approvals and confirm permissions work | Access usually ends; the successor requests their own | IT or system admin |
| Return | Plan a handback, since things may have changed | No handback, so every open item needs an owner and a date | Your manager |
Test It Before You Go
Hand the page to the cover person and ask them to find three real things and do one real task using only the page. Every question they ask you is a gap. Harrin's checklist covers the access version in six words: test that delegated access actually works. Access can look granted and still fail when first needed.
Test days ahead, not on your last afternoon. Google's Gmail help says it can take up to 24 hours before a delegate can use an account, and that invitations expire after a week. Microsoft says Outlook delegate access needs a work or school account, and only your organisation's admin can set Send As permissions. Ask IT early.
- Ask the cover person to find the supplier list, the latest version of the main report and the person to call if the system is down.
- Ask them to approve a real request through the delegated access, not just see it listed.
- Ask them to say back what is due in week one and what they would do if the main risk hits.
- Fix each stumble in the page itself, not with a spoken answer that disappears when you leave.
Go1, a learning vendor, recommends at least one dedicated meeting between the person leaving and the successor or manager, and says even 30 minutes can surface key insights. For a structured handoff, one study comes from hospitals. A 2014 New England Journal of Medicine before-and-after study at nine paediatric residency programmes reported that medical errors fell 23% and preventable adverse events 30% after a handoff programme was introduced. Its verbal mnemonic ends with synthesis by the receiver. The setting is different, and the programme also bundled training and a campaign, so the study cannot show which part helped, or that an office handover would benefit.
Pace It Over the First 30 Days
Put week one on the page and everything else on a labelled later list. An eLearning Industry article on onboarding argues that new hires cannot turn a flood of information into usable knowledge, and that people learn best when information arrives as they are ready to use it. It proposes days 1 to 5 for what the first real task needs, weeks 2 to 3 for decision-making and weeks 3 to 4 for wider context. It covers onboarding in general, not handovers, so applying it here is a judgement call.
- Page one, days 1 to 5: tasks due soon, contacts, access and the costliest mistakes. The article's stage one names core workflows, essential systems and the mistakes that create the biggest risks.
- Second sheet, weeks 2 and 3: common exceptions and the reasoning behind decisions. The judgement-calls block grows here.
- Third sheet, weeks 3 and 4: cross-team processes, long-term plans and rare scenarios. APQC's learning-content and ideas areas fit here.
The article's filter is worth borrowing: "What does this person need before completing their first independent task?" If the answer is nothing, the item goes on the later list. A short leave handover may need only stage one.
Keep Credentials Out of the Document
Write where access is requested and who approves it, not the password itself. Template advice is split. BrightHR lists sensitive information such as passwords among job-handover content, and Whatfix lists credentials, logins and tokens as a must-have element without explaining how to share them securely. Reed includes login details and passwords but says to store them securely, naming a password manager.
The UK National Cyber Security Centre's password guidance for system owners is firmer. It says sharing work accounts, or even occasional use by anyone other than the account holder, introduces a number of risks, and that delegation should be used instead of sharing accounts wherever possible. If sharing is unavoidable, it says the password should be changed once someone is no longer allowed access.
Common mail tools build in delegation. Microsoft says a delegate can receive and respond to email and meeting requests on your behalf, at a permission level you choose. Google says a Gmail delegate can read, send and delete emails but cannot change your password, and keeps access after a password expires, so remove delegates when the leave ends. On the page, write the route: "Finance tool: request access from IT, approver is Dana." Your IT policy has the last word.
The Record-Yourself Shortcut
Talk through the page out loud and let a transcript capture it. Writing a task down can be slow, and explaining it to an imagined new starter can bring out exceptions you have stopped noticing. Linking out to media is normal: Harrin lists SOPs, screenshots and videos among the things a handover can point to.
- Pick one recurring task or exception per recording, so each is easy to find.
- Speak as if the new person is at your desk: the trigger, the steps, what goes wrong, who to ask.
- Read the transcript, cut it into the seven blocks and link the recording from the page.
- Leave passwords out of the audio as well as the page.
Two cautions. Record only yourself: the Reporters Committee for Freedom of the Press summarises each US state's laws on recording phone calls and in-person conversations, noting that many carry criminal penalties and some permit civil lawsuits. The guide covers US state law only, so check the law where you are. And ask your employer whether work content may sit in a personal app. The NCSC's guidance on personal devices says the organisation owns the corporate data on them, and lists compliance with company policies as a challenge.
Where MemX Helps With a Handover, and Where It Stops
The recording and the findability test are the two steps MemX (memx.app) can handle. It does not write the handover for you, and it does not share it with a team.
MemX Record is a recorder inside the phone app. Tap Record and talk through each recurring task and exception. MemX writes a live transcript in the language spoken, then gives you timestamped notes and a summary, searchable once processed. A photo of a whiteboard or a screenshot of the folder tree can be added through MemX Upload, which accepts photos, PDFs, text, Word documents and audio files up to 20 MB each. Write the paths into the page too, since the photo does not replace it.
For the test, ask MemX in plain words: "where do I keep the supplier list?" Chat With Documents answers from your own files and shows the memory it used, so a correct answer with the right source beside it suggests the handover is findable. A wrong or empty answer is a gap. To send the handover, share the transcript, the notes or the original audio file from the recording.
The honest limits: MemX is one account per person with no team sharing, so the cover person cannot open your library. The handover is exported and sent, not shared in the app. MemX does not arrange the transcript into the seven blocks, does not give anyone access to your systems, and cannot tell whether what you said is complete. Recording time is capped by plan: Free includes 15 minutes a month, Starter 200, Pro 1,000, and MAX is unlimited. Asking needs a connection.
Whether work content belongs in a personal MemX account is your employer's call, so ask before recording anything confidential. As for where the recordings live, MemX is private by architecture: encrypted at rest, with every read logged. That does not change what your employer's policy allows.
01What should a job handover document include?
A role overview, key contacts, recurring tasks with schedule, where files and systems live, open items and deadlines, judgement calls and decisions due while away, and who covers what. APQC's own template adds learning content and ideas for the role.
02How long should a handover document be?
It depends on the role. Reed says length and detail vary with the role and whether you are leaving or taking a break, and an NHS trust advises clear, simple bullet points. A one-page summary that links to detail can work for many roles, but a complex role may need more. Check whether your employer has its own template first.
03Should I put passwords in a handover document?
Safer not to. Write where access is requested and who approves it. The UK NCSC says delegation should be used instead of sharing accounts wherever possible. Some template guides still list passwords, and Reed says to store them securely. Your IT policy decides how access passes on.
04What is the difference between a leave handover and a resignation handover?
On leave you return, so the page covers the window you are away and its risks. On resignation you cannot count on being asked afterwards, so the page needs more reasoning, an owner for every open item, and files moved somewhere that outlasts your account.
05Can I record a voice handover instead of writing one?
Yes, as a supplement. Record yourself explaining each task, turn the transcript into the written page and link the audio. Record only yourself, since recording rules differ by place, and check your employer's policy. MemX Record gives a transcript and notes, but it has no team sharing, so you send the files.
