Your New Manager Doesn't Know What You Did Last Year

When your reporting line changes, almost none of your track record travels with it. Here's what actually transfers, what quietly disappears, and the one-page briefing that fixes most of it before your first 1:1.

By JobPost Team · Sep 23, 2026 · 4 min read

A reorg lands on a Tuesday. By Friday you report to someone who has never watched you work. The migration you rescued in March, the launch you gave up to do it, the conversation where your old manager said "next cycle" — none of that arrives with the new org chart.

What Actually Transfers

The list is shorter than people assume. When a reporting line changes, your new manager typically inherits:

Your title and salary band, from HR's system
Your last written review, if the company stores completed forms centrally
A rating or level, stripped of the reasoning behind it
Whatever your old manager says in a fifteen-minute handover call, if there is one

Here is what does not transfer. The reason your rating was a 3 and not a 4 — that you volunteered for the unglamorous infrastructure work and it doesn't demo well. The verbal commitment about a promotion packet in the spring. The fact that two other teams route their hardest questions through you. The peer feedback that was glowing in tone but bland on paper because your colleague writes like a lawyer.

If your old manager left the company, the written form is all that survives. If they stayed, they are busy onboarding their own new boss.

The Reset Nobody Announces

No one tells you that your record has been cleared. It just happens. Your new manager reads the file in ten minutes, then forms a real impression over the next six weeks from what is directly in front of them: what you're shipping now, how you show up in meetings, whether you speak in the ones where they're watching.

That's not malice. It's the only data they have. But it means your standing is now built almost entirely on recent, visible work — and recent, visible is not the same as valuable.

The people who lose most in a manager change are the ones holding things together rather than launching them. Migrations. On-call. The onboarding doc everyone uses. The client who only stays because you answer on Fridays. That work generates gratitude from peers and almost no paper trail for someone who arrived last month.

Then calibration comes. Your manager sits in a room and has to argue for your rating against other managers arguing for theirs. Everyone else's manager has eighteen months of stories. Yours has six weeks and a form.

Write The Briefing Nobody Asked For

One page. Send it before your first 1:1 or bring it with you. Not a defence, not a complaint — a briefing, written for someone who has just inherited a team and is drowning.

What goes in it:

What you own. Systems, accounts, processes, relationships. Name the things that break if you stop.
The last twelve months. Four to six items, each with a date, an outcome, and a named person who can confirm it. "Led the billing migration, Feb–May, cut failed transactions by about half, Priya ran QA."
Anything you were told. Promotion timing, a comp adjustment, a scope change. Write it neutrally: "Dev and I agreed I'd be put up for senior in the spring cycle."
Current commitments. What you've promised other teams, and by when.
What you want next. One line. It gives the new manager something to manage toward.

Most people feel awkward sending this. Managers inheriting a team almost never do. You are handing them the context they were supposed to get and didn't.

The First Conversation

Four questions, in your first or second 1:1:

"What did you inherit about me?" This is the one that matters. It is the only chance you get to see the file and correct it. Ask it plainly and then be quiet.

"How do you evaluate people, and when is the next cycle?" Calibration dates move when orgs restructure. Assuming the old calendar still applies is how people miss a cycle entirely.

"What do you need from me in the next sixty days?" Their answer tells you what they'll actually remember.

"Can we keep the commitments from before?" Verbal promises die with the manager who made them. Name the specific one, then follow up by email with a sentence confirming what you agreed. That email is the only version that exists now.

If the answer is that the promise can't carry over, you've learned something worth knowing in month one instead of month nine.

Keep The File Between Reorgs

In a scale-up that has restructured twice since you joined — which describes a lot of Toronto, Montreal and Vancouver tech right now — this will happen again. Treat the record as maintenance, not crisis response.

Once a month, three lines in a personal document: what shipped, what it changed, who saw it. Save the Slack message where someone thanked you. Note the date a client renewed after you fixed their integration.

Keep it at a level of detail you could say out loud in a coffee shop. No client data, no confidential numbers, no exported internal documents — that's a separate problem you don't want. Dates, outcomes, names of people who'd vouch.

The next time the org chart changes, you won't be reconstructing a year from memory on a Sunday night. You'll have a page ready by Tuesday.