New hire onboarding checklist for a manager's first weeks
On this page
A new hire onboarding checklist, from a manager's side, covers what has to happen in someone's first two weeks beyond paperwork and equipment: who they meet, what context they get, what their first task is, and how the manager checks in. It is the manager's plan, separate from whatever HR sends for benefits and compliance.
This is not the same document as a contractor onboarding checklist, which covers staffing paperwork — I-9, tax forms, E-Verify — for a temp or contract worker before their first shift. This checklist is about a direct hire's first weeks as a person joining a team, not the compliance forms that get them legally onboarded. For the goals that follow this period, see the 30-60-90 day plan template.
Most of what determines whether a new hire feels settled by week two has little to do with the paperwork and everything to do with whether a manager showed up with a plan. A new hire left to self-onboard from a wiki and a calendar invite will eventually figure things out, but the weeks it takes to do that unassisted are the same weeks that shape whether they stay past the first year.
Before day one
- Confirm equipment, accounts and access are ordered with enough lead time to actually arrive.
- Send a short welcome note with start-day logistics: time, place or link, who to ask for, what to expect the first hour.
- Draft the skeleton of the 30-60-90 day plan so day one is not the first time the new hire hears how they'll be measured.
- Tell the team who is joining, their role, and their start date, so day one does not start with "who's that."
- Pick a buddy — someone other than the manager the new hire can ask small questions without feeling like they're bothering their boss.
- Block the first week's calendar: 1:1 meetings, team intros, and protected time with no meetings for reading and setup.
What to get from recruiting first
A manager starting from zero on day one is a common, avoidable gap. Ask recruiting or HR for three things before the new hire's start date: what stood out about them in the interview process that the resume does not show, any concerns raised and how they were resolved, and anything the candidate specifically asked about during the process that the manager should follow up on — a question about a career path, a stated interest in a particular project, a scheduling constraint they mentioned. If interviewers left structured notes or scorecards, read them again after the hire is made, not just before the decision; details that mattered for the yes/no call are often exactly the details worth building into the first two weeks.
Day one
- Meet personally, even briefly, before handing them to a buddy or a training schedule.
- Walk through the 30-60-90 day plan skeleton together and adjust it based on their questions.
- Introduce them to the team, in person or on a call, with one sentence on what each person does.
- Confirm equipment and access actually work — a laptop that cannot log into anything by lunch is a bad first impression that has nothing to do with the new hire.
- Give them one small, real task to start on, even something minor, rather than a full day of reading alone.
- End the day with a two-minute check-in: how did it go, anything confusing so far.
Week one
- Schedule 1:1 introductions with the people they will work with most, not the whole company.
- Assign a first real task with a deadline inside the week, reviewed together rather than silently.
- Explain the team's actual working norms: how decisions get made, how feedback is given, what "urgent" means here.
- Share context the job description could not: what's working well, what's a known problem, what changed recently.
- Hold a mid-week and end-of-week check-in, fifteen minutes each, specifically about how onboarding feels, not just work status.
Week two
- Move from shadowing toward doing: hand over a piece of real, ongoing work with support still close by.
- Revisit the 30-60-90 day plan and adjust the 30-day goals based on what's actually been learned.
- Ask directly whether anything from week one is still unclear — most new hires will not volunteer confusion unprompted.
- Confirm they know who to go to for what: technical questions, process questions, and anything they're unsure is even okay to ask.
- Check that the buddy relationship is actually being used, not just assigned and forgotten.
A filled example: two weeks for a new marketing hire
An invented new hire, written the way a usable manager's plan reads:
Priya Kapoor — Marketing Coordinator — starts Monday, October 5
Before day one: Laptop and software access confirmed with IT for Oct 2. Welcome email sent Oct 1 with start time, office details and a note that her buddy, Leo, will meet her at the door. Team told in Thursday's standup. First-week calendar blocked: intros Mon–Wed mornings, protected focus time each afternoon.
Day one: 30-minute 1:1 with manager to walk through the draft 30-60-90 plan. Team lunch. First task: review and give feedback on the draft Q4 campaign brief, due end of week — not urgent, but real.
Week one: 1:1s with the design lead, the two other coordinators, and the agency contact. Wednesday check-in: "the campaign calendar tool is still confusing" — Leo walks her through it Thursday. Friday check-in: campaign brief feedback submitted, on time.
Week two: Takes ownership of one live campaign's weekly reporting, with the outgoing owner still copied for two weeks. 30-60-90 plan's 30-day goals adjusted: she is ahead on tool fluency, behind on stakeholder names, so week three adds two more intro 1:1s.
What managers skip, and what it costs
| Skipped | What it costs |
|---|---|
| A real first task with a deadline | Days of reading with no sense of contribution, which quietly erodes early confidence in the decision to join |
| Daily or near-daily check-ins in week one | Small confusions compound into a new hire who feels lost by week two but hasn't said so |
| Explaining unwritten team norms | A new hire who reads every silence as disapproval, or misjudges what "urgent" means here |
| Introducing them to peers, not just the org chart | Weeks of not knowing who to actually ask for help with a specific problem |
| Revisiting the plan after week one | Goals set before the manager or hire had real information stay unchanged and eventually feel arbitrary |
The buddy system: making it real
A buddy assignment that is announced once and never followed up on rarely gets used. Tell the buddy explicitly what the role is — answer small questions, have lunch together once, check in midweek — rather than leaving it to them to figure out. Ask the new hire directly, in the week-one check-in, whether they have actually talked to their buddy. A buddy relationship that exists only on an onboarding spreadsheet does nothing for either person.
Adjusting the checklist
By seniority
A junior hire and a senior hire need different weight on the same checklist, not a different checklist. Junior hires generally need more structure: more explicit tasks, more frequent check-ins, and more explanation of unwritten norms they have no prior experience to compare against. Senior hires need less hand-holding on the work itself and more investment in relationships and context — who actually makes which decisions, what politics or history shaped the current state of the team, and where their judgment is trusted from day one versus where it needs to be earned first. A senior hire onboarded like a junior one will feel managed rather than welcomed; a junior hire onboarded like a senior one will quietly drown without saying so, since many new employees are reluctant to admit they need more structure than they were given.
Remote and hybrid
Everything above still applies remotely, with two changes worth being deliberate about. First, over-communicate what would be visible in an office automatically: who is in a meeting, who is heads-down, what the general mood of the week is. Second, make the first video call personal before it is functional — a few minutes of actual conversation before diving into the plan matters more when there is no walk to the coffee machine to build rapport informally. A remote new hire who only ever sees their manager in scheduled, agenda-driven calls takes noticeably longer to feel like part of the team than one who gets even a small amount of unstructured contact in the first two weeks.
Measuring whether onboarding is actually working
Ask two questions at the two-week mark and again at 90 days, directly rather than through a generic survey: what has been the most confusing part of joining, and is there anything you expected to have by now that you don't. The answers tell you more about your onboarding process than a satisfaction score, because they point at specific, fixable gaps rather than a general mood. If your team hires regularly, keep a running list of what new hires say was confusing — patterns that show up across several hires in a row are the checklist's weak points, and they are usually easier to fix than they are to notice without asking directly.
Questions people ask
How is this different from what HR sends a new hire?
HR's checklist is usually compliance and setup: tax forms, benefits enrollment, equipment. This checklist is what the manager personally owns: introductions, context, early work and the relationships that make someone feel like part of the team rather than processed by it.
How is this different from a contractor onboarding checklist?
A contractor or temp onboarding checklist is staffing paperwork — I-9, W-4 or W-9, E-Verify where it applies — completed before a worker's first shift. This checklist is a manager's plan for a direct hire's first two weeks: people, context and early work, not compliance forms.
Should the manager write this alone or with HR?
The manager owns it, but HR or a recruiting partner should hand over anything already known — the role's context from the search, what mattered in the interviews, any concerns raised and resolved — so the manager is not starting from zero on day one.
What's the single most common thing managers skip?
A clear first task with a deadline inside the first week. Without one, new hires spend days reading documentation with no sense of whether they are actually doing anything, which is a quiet but real driver of early doubt about the decision to join.