New Manager Onboarding Plan Template
Three documents and two sheets that flag which direct reports need your first two weeks, built from ratings, engagement and tenure nobody reads together.
Free download · No account needed
This pack builds a Team Register from three sources that never get compared to each other: the last two formal ratings, the last two engagement pulse scores, and months at the current level. The Early Signal Checklist flags anyone showing two or more of a real engagement drop, a stale rating, or years at level with a good rating and no promotion. That flag count sets the order for your first two weeks of 1:1s, then a Manager Ramp Plan and First 1:1 Guides carry the plan past week one.
A generic 30-60-90 template cannot do this, because a downloadable file has no access to your team's actual ratings, engagement scores or tenure. In the worked example, a seven-person team's average engagement moved from 75.1 to 68.3 between pulses, a 6.9 point dip that looks unremarkable on any dashboard. It conceals a 29-point drop on one report and a 15-point drop on another. Gallup's own analysis puts the manager at 70 percent of the variance in team engagement, which is why those two reports need the first meeting, not the third or fourth.
Written for anyone inheriting a team they did not build, whether a first-time manager or someone moving up to lead former peers. Three of seven reports in the worked example had gone 24 months or more at the same level on a Meets or better rating, a promotion-case finding unrelated to this quarter's numbers. If you are also picking up ownership from the outgoing manager, pair this with a role transition and knowledge capture plan. If a direct report is mid a 30-60-90 onboarding cycle, that pack covers the individual ramp this one does not.
What is in the pack
Team Register
One row per direct report joining tenure at level, the last two ratings and the last two engagement pulse scores, three systems that otherwise stay in three different tools.
Early Signal Checklist
Every report scored on three tests and flagged at two or more, sorted so the first two weeks of 1:1s follow the flags instead of the org chart.
Team Brief
The register's findings written out in full sentences, including what the team-wide average conceals and the flat-tenure pattern worth a note at the next promotion cycle.
Manager Ramp Plan
A 90-day plan ordered by what the priority 1:1s actually found, not a generic Learn-Contribute-Lead calendar with placeholder goals for a team that does not exist.
First 1:1 Guides
Three guides, one for an engagement-drop flag, one for a flat-tenure flag, and one standard meeting, each opening with the specific question that flag calls for.
How it works
- 1
Send what you have
The HRIS export with tenure and level history, the last two ratings, and the last two engagement pulse scores if your company runs them. A partial set is fine.
- 2
Get the flags
Every direct report scored against three tests and sorted by flag count, so you know before the first meeting who actually needs it most.
- 3
Run the priority 1:1s
Two or more flags means week one, with the specific opening question already written into the guide instead of a generic settling-in question.
- 4
Build the 90-day plan
The ramp plan drafts from what the priority meetings actually found, then hands days 31 to 60 a dated, specific action rather than a theme.
Frequently asked questions
Why not just use a 30-60-90 template?
Because a downloadable file has no access to your team's actual data. A generic plan schedules a 1:1 in week one for everyone equally. This pack tells you which specific report to meet first and why, from ratings, engagement and tenure your company already has on file.
What if my company doesn't run an engagement survey?
The register still works on two sources instead of three: tenure at level and formal ratings. A flag from two sources is still real, and the Team Brief states plainly which input is missing rather than treating a blank column as a score of zero.
Isn't a big engagement drop just noise from one pulse?
Sometimes. That is exactly why a flag is a reason to ask a specific, direct question in the first 1:1, not a verdict to act on before that conversation happens. A report who explains a rough quarter in two minutes costs you two minutes. A report you never ask can cost you the person.
What about the team's system access and tools?
Out of scope here, deliberately. If you also need to confirm what your inherited team can actually access, pair this with the access matrix built from the identity provider export. A register of people and a register of access answer different questions.
What if people have already left this team recently?
That is a related question this pack does not answer. Past departures and their themes belong in an exit interview programme that cross-tabs reasons by manager and team. This pack is about the people still on the team today.
Can I use this for someone I'm promoting from within their own team?
Yes, and it matters more there, not less. Managing former peers means the register gives you a reason for a hard conversation that is not because I said so, which is exactly the credibility problem an internally promoted manager runs into first.
Find out which of your new direct reports needs the first 1:1
Send tenure, ratings and engagement pulse data for your new team. The first thing back is who is flagged, why, and what to ask them in week one.
Build my team register