How to Hand Over Your Job When There Is No Replacement

Handing over your job is hard enough when there's a name on the org chart to hand it to. When there isn't — no replacement hired, no internal transfer lined up, no clear plan — it's a different problem. You're not transferring knowledge to a person. You're leaving it somewhere it can be found later, by someone who doesn't exist yet.

Accept what you can and can't fix

First, set expectations honestly with yourself. You cannot prevent the gap. If your employer hasn't hired someone in time, that is a staffing decision, not your problem to solve in two weeks. What you can do is make sure that when the gap is filled — whether next week or next quarter — the person walking in has what they need.

This reframe matters. People in this situation often spiral into trying to do the impossible: train a successor who doesn't exist, finish every project, hold the line indefinitely. You can't. Your job is to leave a clean, findable trail. That's it.

Decide who the document is actually for

Without a named successor, your handover has up to three different audiences, and you should write with all of them in mind:

• Your manager — who will absorb the urgent stuff in the short term and use your document to brief whoever comes next.
• Colleagues picking up pieces — peers, adjacent teams, or junior staff who will inherit specific projects or relationships in the interim.
• The future hire — someone who may join in three weeks or three months, who will read this document on day one with no context whatsoever.

That third audience is the one most people forget. They write for the manager who already knows half of it. Write for the stranger who knows none of it.

Split the handover into two layers

A standard handover assumes one reader doing one continuous job. Yours has to work in pieces. Structure it in two layers:

Layer 1: The interim plan

A short, action-oriented document for your manager and colleagues, covering the next 4–8 weeks. What needs to happen, by when, and who you suggest picks it up. Keep this tight — one page if possible. The goal is to make it easy for your manager to redistribute work without having to read your whole brain.

Layer 2: The full handover document

The complete reference document for the eventual successor. This is the standard handover — role overview, projects, contacts, recurring commitments, tools, critical knowledge. The difference is that you're writing it for someone who isn't reading it yet, so it has to stand entirely on its own without verbal context.

Redistribute the urgent work deliberately

Without a successor, your active work has to land somewhere in the interim. Don't leave this to chance. Go through every active project and recurring commitment and propose a specific home for each one. Your manager may overrule you, but starting with a draft makes the conversation ten times faster.

For each item, decide one of four things:

• Pause it — if it can wait until a successor is hired, say so and explain the cost of pausing.
• Hand it to a colleague — name the person and the rationale. Confirm with them first.
• Escalate to your manager — for things only a manager-level person can hold.
• Hand it to a vendor or external party — sometimes the cleanest option for specialised work.

Item: [Project / meeting / responsibility]
Urgency: [This week / This month / Can pause]
Proposed owner: [Name, or "needs decision"]
What they need to know: [One sentence]
Cost of dropping it: [What breaks if no one picks it up]

Write the full document for a stranger

With no successor in the room, you lose the safety net of being able to say "I'll explain in person." Anything ambiguous in your document will stay ambiguous forever. A few rules:

• Spell out acronyms once. Internal jargon ages badly and the future reader may not have your team context.
• Name the person and their role. "Talk to Priya" is useless in six months. "Priya Shah, Senior Legal Counsel — handles vendor contracts" still works.
• Link to source-of-truth files. Don't paraphrase what's already documented elsewhere; link to it and confirm the link works.
• Date everything. Status notes like "waiting on legal review" need a date so the future reader knows whether that's still relevant.
• Capture the unwritten rules. The workaround, the client preference, the meeting that always runs late — this is the stuff no one else can write.

Brief your manager properly

Your manager is the bridge to whoever comes next. Schedule at least one substantial handover meeting with them — not a standup, an actual sit-down. Walk them through both documents. Make sure they know:

• Where the full handover document lives.
• Which colleagues have agreed to absorb which pieces.
• Which decisions are pending and need owners.
• Which external contacts have been told you're leaving, and which haven't.
• Which risks you see in the next 60 days.

End that meeting by asking: "Is there anything you'd want documented that I haven't covered?" The answers will surprise you.

Tell external contacts who to talk to

Without a successor, "reach out to my replacement" doesn't work. For every external contact who matters — clients, vendors, partners — send a transition email naming a specific interim contact. Even if that contact is just your manager, name them. A vague "the team will be in touch" gets ignored.

Protect yourself after the last day

When there's no replacement, the temptation for former employers to ping you afterwards is high. Set the boundary before you leave, not after. Remove your work email and Slack from your phone. Decide in advance whether you're willing to answer questions after your last day, and if so, in what form.

A reasonable position: "Happy to answer one or two short questions by email in the first two weeks. After that, the document covers it." Then stick to it. The cleaner your handover document, the less anyone will need to ask.

If you're working in Google Workspace, OneLast.Day reads your emails, calendar, and files and builds the handover document from your actual work data — which matters even more when there's no successor to fill in the gaps verbally. The document has to stand alone, and starting from a structured draft of your real work is faster than building one from memory.