How to Train Your Replacement at Work (Without Burning Out)

Being asked to train your replacement is one of the strangest parts of leaving a job. You're on your way out, and the company wants you to invest your last weeks in the person taking your seat. Done well, it ends your tenure on a high note. Done badly, it burns you out and leaves your successor stranded. Here is how to do it well, without giving away more than the situation deserves.

Why training your replacement feels uncomfortable

Training a replacement asks you to do something that runs against instinct: spend energy on a future you won't be part of. It is normal to feel a mix of generosity, resentment, and detachment in the same week. None of that is a problem unless you let it leak into how you show up.

The reframe that helps most: you are not training them for the company. You are training them so the work you spent years on doesn't quietly fall apart after you leave. The artefact you produce, and the way you hand it off, is the last public thing your name is attached to.

Agree the scope before you start

Before the first training session, get clear with your manager on what "training your replacement" actually means. It is rarely the same thing in their head as in yours. Ask three direct questions:

• How many hours per week are you expected to spend on training, on top of finishing your own work?
• What does "trained" look like? Are they expected to run the role solo on day one, or is there a transition period with someone else as a safety net?
• What is the priority order if training conflicts with your other deliverables?

Without those answers, you'll end up doing both jobs at full intensity and resenting both. With them, you have a defensible structure for your remaining weeks.

Build a short training plan, not a long one

Resist the urge to teach them everything you know. You can't, and they wouldn't retain it anyway. Instead, build a plan around what they need in their first 30 days. Everything else can be written down for them to find later.

A workable plan has three layers:

Most of your time should go to Layer 1 and Layer 2. The handover document carries Layer 3, which means the better the document, the less you have to explain twice.

How to run the training sessions

Keep sessions short and frequent rather than long and rare. Sixty to ninety minutes is the sweet spot. Anything longer and retention drops. Anything shorter and you spend the whole time context-switching.

A simple format that works:

1. Set the topic at the start. One thing per session, not five.
2. Show, then explain. Open the actual system, the actual file, the actual email thread. Abstract explanations don't stick.
3. Let them try it while you watch. The fastest way to find gaps is to see them get stuck.
4. End with three questions: What's still unclear? What would you do tomorrow if I weren't here? What do you want to cover next session?

What not to do

A few mistakes are common enough to flag:

• Don't dump everything in one marathon session. A six-hour download is for your sake, not theirs. They will forget 80% of it by the next morning.
• Don't badmouth the company, your manager, or the role in front of your replacement. Whatever you say will reach the people you said it about, usually within a week.
• Don't oversell how hard the job is to make yourself feel important. Your replacement is already nervous. Adding to it doesn't help them or you.
• Don't accept extensions to your notice just to keep training. If the company hired late, that is a planning failure on their side, not a debt you owe.
• Don't hand over your personal contacts, passwords, or files casually. Anything sensitive should go through the proper channels, not a shared Google Doc.

Protect your own work and your last weeks

Training someone is genuinely tiring. It will eat into the time you need to finish your own deliverables, close out your projects, and write the handover document itself. Block out training time on your calendar and treat it as fixed: not a thing that expands to fill whatever space your replacement needs.

If your manager keeps adding to the scope, push back early and in writing. A short email saying "to make sure we hit the training goals and finish the X project, I'll be spending Tuesday and Thursday afternoons with [name] and protecting the rest for project work" sets the expectation cleanly. It is much easier than renegotiating in week three when you're behind on both.

The handover document does the work you can't

However well you train your replacement in person, they will forget things. They will want to check something at 9pm a month after you've left, and you won't be there. The handover document is what they reach for then.

A good document covers the things you can't easily teach in a meeting: the list of active projects, key contacts, recurring commitments, tools, and critical knowledge. The training sessions are for the parts that only make sense with you in the room. The document is for everything else.

If you're handing over to someone with little prior experience of the role, the document changes shape: there is a separate guide on handing over to someone who has never done the job, and it is worth reading before your first session.

If you work in Google Workspace, OneLast.Day reads your Gmail, Calendar, and Drive and drafts the handover document for you, so the written layer of training your replacement is already 70% done before you walk into the first session.

The last session: hand over cleanly

In your final training session, do three things. Walk through the handover document one last time, so they know exactly where every section lives. Give them the names of two or three people they can ask if something comes up after you leave. And tell them, plainly, what is and isn't reasonable to contact you about once you've gone.

That last part matters. "Feel free to ping me anytime" sounds generous and almost always becomes a problem. "I'm happy to answer one or two short questions in the first month, please send them by email" is kinder to both of you. You're not abandoning them. You're handing them a role, with a document, with a few names, and with a clear edge to the relationship.