The ApprenticeRoute

When your manager or mentor leaves

At some point in a four-year programme, a calendar invitation appears with no agenda and a slightly odd guest list, and you learn that the person who has been explaining your entire working life to you is leaving.

I want to be careful in this article, because it's about other people and I've made a rule on this site not to write about colleagues. So this isn't anyone's story. It's the structural fact — that on a four-year apprenticeship you will almost certainly go through this two or three times — and what I'd do differently now.

It happens more than you expect, and it hits apprentices harder

Four years is a long time in a large organisation. People get promoted, move teams, go on parental leave, get poached, retire, or get reorganised into a different reporting line. Somewhere in the region of two to four line managers across a degree apprenticeship is completely normal, and there'll be reorganisations on top of that. Your programme is, quite often, longer than the average person's tenure in a specific role.

For most employees that's an inconvenience. For an apprentice it lands harder, for four reasons that took me a while to articulate.

Your manager is disproportionately your entire context. Someone joining at 35 brings a network: former colleagues, contacts across the industry, a sense of what normal looks like elsewhere. At 18 you have this building and these people, and one of them has been interpreting all of it for you.

They hold your record, and a lot of it is undocumented. They know what you were like in month two and how much you've improved since. That comparison exists almost entirely in their head. When they leave, your track record resets to whatever a new person can observe from next week onwards.

They may be your advocate in the room you're not in. Ratings and pay get decided in calibration meetings, as how pay reviews and bonuses work explains, and the person arguing for you there is your manager. Losing someone who knew your year, mid-cycle, has real consequences that nobody will ever say out loud to you.

There's an admin layer nobody mentions. Your manager is usually a party to the apprenticeship itself — attending tripartite reviews, signing off progress, agreeing your off-the-job training. That's a formal role, and it doesn't transfer automatically just because a reporting line changed in a system.

The fortnight before they go

This is the part I'd do completely differently, because the first time it happened I did nothing except feel a bit unmoored, and about four months later I realised what that had cost me.

There's usually a notice period. Use it. Everything below is a reasonable, professional ask that any decent person would be glad to be asked, and most of it takes them twenty minutes.

Ask for a handover conversation about you. Not about the work — about you. The sentence I'd use now: "Before you go, would you mind writing down what you'd say about me to whoever takes over?" Ask for it in an email so it exists in writing. It's the closest thing you'll get to a portable reference from someone who watched you learn the job, and it means the next manager starts from something better than a blank page.

Ask them to update your performance record before they leave. If a review cycle is in progress, or if there's a system where objectives and notes live, ask them to write their assessment now rather than leaving it for someone who wasn't there. This is normal practice and managers frequently forget.

Get names. "Who should I go to about X now? Who's the person who actually knows Y?" Half of what a good manager provides is routing, and routing is transferable if you ask for it explicitly. Write the list down.

Get the undocumented things documented. Where things live, why a process exists, the context behind the thing everyone treats as obvious. You'll be the one asked about it in a year, once you're on the other side of the experience gap.

Keep the relationship. Connect on LinkedIn, get a personal email if that's appropriate, and actually stay in touch — a message twice a year is enough. This is the one people skip and it's the most valuable of the lot. Someone who managed you for two years and rated you well is now a contact somewhere else in your industry, and at 20 you have very few of those. They left the company, not the planet.

Tell your training provider. If your manager is the one attending tripartite reviews and signing off your progress, your skills coach needs to know there's a change coming. Ten seconds of admin that prevents a confused review meeting three weeks later.

The first month with someone new

Assume nothing carries over. Not maliciously — systems are patchy, handovers are rushed, and your new manager has just inherited several people and a workload.

Send a short brief in your first week. Three or four bullets: what you're working on, what you've delivered recently, what's coming up, and one line on what you'd like to get better at. Nobody expects this from a junior person and it lands extremely well. It also means the first thing your new manager knows about you is something you wrote.

Explain the apprenticeship explicitly. This one genuinely matters. Your new manager may never have had an apprentice and may have no idea that they're required to release you for off-the-job training, that there's a tripartite review every couple of months, or that you have block weeks in the diary. Don't assume it was in the handover.

The framing that works is factual rather than demanding: "I'm on the degree apprenticeship — my study time is X, my university blocks are on these dates, and there's a review with my provider roughly every eight weeks that you'd be part of. Happy to walk you through it." The mechanics are in how work-based learning actually works if they want the detail, and the funding rules behind it mean this is a condition of the programme rather than a favour you're requesting.

Re-establish objectives early. Whatever you'd agreed with the previous manager may or may not have survived. Getting three lines written down in month one saves an awkward conversation in month nine, and your first performance review has more on why that matters.

Give it a real chance. A new manager will do things differently, and at 19 it's tempting to interpret different as worse — particularly if you liked the last one. Some of my most useful development came from someone whose approach I initially found irritating. And whatever you think, don't say the comparison out loud; it travels, and it makes you look like someone who's hard to manage rather than someone who was well managed.

When it's a mentor rather than a manager

Different loss, different fix.

The person I'd point to as most useful in my first two years wasn't my line manager at all. It was the sort of person I described in being the youngest person in the room — long-tenured, unremarkable job title, knew how the place actually worked and would explain it properly. There was no formal relationship there, so when that kind of person moves on there's no handover process to use.

Two things.

Keep it up anyway. An informal mentoring relationship doesn't require you to be in the same building. If anything, someone who's left is freer to be honest with you about your organisation than someone still in it.

Don't try to replace them with one person. This was my mistake — I looked around for the next version of the same relationship and didn't find one, because that's not how it works. What you actually end up with is three or four partial mentors: someone who's good on the technical bit, someone who's good on how to handle a difficult stakeholder, someone who'll tell you the truth about your career. Accumulating those deliberately is more robust than depending on one person, which is the whole lesson of this article really.

Reorgs, specifically

Somewhere in your four years, a diagram will be circulated with different boxes on it.

Honest guidance for a junior person: reorganisations are mostly noise at your level. Team names change, reporting lines move up a box, someone senior you'd never met is replaced by someone else you won't meet. The work usually stays the same. There's a strong instinct at 19 to read enormous significance into it, partly because everyone around you is talking about it constantly, and that instinct is mostly wrong.

What's actually worth watching:

Otherwise: keep doing the work. The people who came out of reorgs well were the ones who carried on being useful while everyone else was reading the diagram.

Build a network that isn't one person

The actual lesson, and I'd have benefited from hearing it in year one.

At 18 your entire professional world tends to be a single reporting line, and that feels safe until it isn't. What makes you resilient is having several relationships that don't depend on each other:

That last one compounds in a way that's invisible at 19 and obvious at 25. Over four years a surprising number of people will pass through your working life, and the difference between them being former colleagues and being contacts is roughly one message each.

The bit that's actually hard

It's destabilising, and at 19 it's more destabilising than it would be at 35, and there's no point pretending otherwise. When someone who's been your interpreter for eighteen months leaves, the building genuinely feels different for a while, and you may find yourself unreasonably upset about a colleague changing jobs.

That's a normal response to losing your main source of context in a place where you have less context than everyone else. It passes, usually within a month or so of the new person arriving.

And there's something worth taking from it. The first time it happened I understood a job as a place you sit in. By the third time I understood it as a set of relationships you maintain — which is both less comfortable and considerably more accurate, and learning it at 19 rather than 30 is genuinely useful.

Ask for the handover note. Get the names. Keep in touch. That's the whole method, and it takes about half an hour.