Onboarding New Hires: A 30-60-90 Day Plan That Actually Works

Most companies spend six weeks and a small fortune getting someone to sign an offer, then hand them a laptop, a wiki link and a calendar full of “intro chats”. The new hire spends the first month guessing what good looks like. By day 90 they have either worked it out on their own or started quietly browsing open roles on HireWise again.

A 30-60-90 day plan fixes most of that, but only if it is specific. “Learn the codebase” is not a goal. “Ship one change to the billing service with a reviewer from another team” is. This guide walks through the plan we have seen work at companies from 12 to 1,200 people, along with the checklist, the metrics and the mistakes to avoid.

Why the first 90 days decide so much

Early attrition is expensive and surprisingly common. In the 2026 HireWise employer survey, 17.4% of people who left a job within the first year said they had made up their minds before the end of month two. The reasons were rarely about pay. They were about unclear expectations, a manager who was never available and the feeling of being “parked” while everyone else was busy.

Replacing a mid-level hire is not cheap either. Using a conservative estimate of 30% of base salary, losing a $128,000 engineer in month four costs roughly $38,400 in recruiting fees, interview hours and lost output. For a £58,000 account manager in London, the same calculation lands near £17,400. Compared with that, a structured plan that takes a manager four hours to prepare is the cheapest retention tool you have.

Before day one: the pre-boarding week

The plan starts before the start date. Send the welcome email at least five working days in advance, ideally on a Tuesday or Wednesday so it does not get buried under weekend mail. It should include the first-day schedule with times in the new hire’s own time zone (for example, “09:30–10:00 CET: coffee with your buddy, Lisa”) and a named person to message if the laptop does not arrive.

Hardware and access are where most first days go wrong. Ask IT to confirm, in writing, that accounts for email, chat, the code host and the HR system will be live by 08:00 local time on day one. If you work with contractors in other countries, confirm payroll details and equipment shipping two weeks early, since customs alone can add five working days.

Days 1–30: learn the terrain

The first month is about context, relationships and one small win. Resist the urge to schedule a full slate of meetings. Two or three a day is plenty.

Goals for month one

1. Understand how the team makes money or saves money
   1. Sit in on two customer calls or support shifts
   2. Read the last two quarterly reviews or board updates
2. Meet the people who will make or break the role
   • The direct manager, weekly, 45 minutes
   • A buddy outside the reporting line, twice a week for 15 minutes
   • Two or three peers in adjacent teams
3. Deliver one small, visible piece of work
   • Something that ships or gets used by day 21
   • Reviewed by someone who is not the manager

The small win matters more than it looks. It proves to the new hire that they can get something done here, and it shows the rest of the team that the newcomer is contributing. At one product studio we spoke with, engineers were asked to fix a real but low-risk bug in their first week. Median time to first merged pull request dropped from 11 days to 3.5 days after they introduced the rule.

Days 31–60: contribute and connect

By the second month the new hire should be taking on work that would otherwise land on someone else’s desk. This is also when the manager shifts from teaching to coaching. The weekly one-to-one stays, but the agenda moves from “what don’t you know yet” to “what is getting in your way”.

What a good month two looks like

• Owns at least one recurring responsibility, such as a weekly report, a support rotation or a standing customer account
• Has presented something to the wider team, even a 10-minute demo
• Can explain the top three priorities for the quarter without looking at a slide
• Has given feedback on a process, which the manager writes down and acts on

Around day 45 is a good time for the first formal check-in. Keep it short and two-way. Ask what surprised them, what they expected that did not happen and what they would change about their first month. You will get better answers if you ask on a Thursday afternoon at 3:30 p.m. than at 9 a.m. on a Monday.

“We used to treat onboarding as an HR project. Now the hiring manager owns the plan and HR owns the logistics. Our 90-day retention went from 86% to 97% in two hiring cycles, and nobody had to buy new software.”

Priya Nandakumar, Head of People at Halden Logistics

Days 61–90: own outcomes

The final stretch is where the new hire moves from contributor to owner. They should have a project with a clear outcome, a deadline and their name on it. For a designer that might be a redesigned onboarding flow. For a sales hire it might be a quota for the first full month, often set at 50% of the standard target.

The day-90 review should be a real conversation, not a form. Both sides should be able to say whether the role matches what was described in the original job posting and whether the plan for months four to six is clear.

A simple onboarding plan, at a glance

Here is the structure we recommend to hiring managers who use the HireWise employer plans. Adjust the details to your team, but keep the cadence.

Phase	Dates (start June 1, 2026)	Main goal	Manager time per week	Success signal
Pre-boarding	May 25 – May 29	Access and logistics ready	1 hour	Laptop and accounts work by 08:00
Days 1–30	June 1 – June 30	Context and first win	4 hours	First shipped task by day 21
Days 31–60	July 1 – July 30	Recurring ownership	2.5 hours	Runs one process without help
Days 61–90	July 31 – August 29	Own an outcome	1.5 hours	Project delivered, review held
Day 90 review	2026-08-31	Plan months 4–6	1 hour	Mutual “yes, this works”

The checklist managers actually use

A plan only helps if someone follows it. We suggest keeping the checklist in the same tool your team already uses for tasks, so it shows up next to real work instead of in a forgotten document. This is the Markdown template we share with customers:

# Onboarding: [Name], [Role]
Start date: 2026-06-01 | Manager: [Name] | Buddy: [Name]

## Pre-boarding (week before)
- [ ] Welcome email sent with day-one schedule
- [ ] Laptop shipped, tracking number shared
- [ ] Accounts created: email, chat, code host, HRIS

## Days 1–30
- [ ] Two customer calls attended
- [ ] Buddy coffee x 8
- [ ] First small task shipped (target: day 21)
- [ ] 30-day check-in held

## Days 31–60
- [ ] Owns one recurring responsibility
- [ ] 10-minute demo to the wider team
- [ ] Day-45 feedback conversation

## Days 61–90
- [ ] Project with named outcome delivered
- [ ] Day-90 review, plan for months 4–6 agreed

Measuring whether it works

You do not need a dashboard to know if onboarding is working, but a few numbers help you spot problems early. Track them for every hire, then look at them each quarter.

• Time to first shipped task. A median under 14 days is healthy for most knowledge roles.
• 90-day retention. Anything below 90% deserves a closer look at the hiring process, not just onboarding.
• New-hire confidence score. A two-question survey on day 30 and day 90, scored 1 to 5:
  • “I know what is expected of me this quarter.”
  • “I know who to ask when I am stuck.”
• Manager follow-through. The share of planned one-to-ones that actually happened.

One B2B software company with 140 staff shared its numbers with us after rolling out the plan in Q1 2026. The day-30 confidence score rose from 3.1 to 4.2, and the share of new hires who said they knew “who to ask” went from 58% to 91%. Their total spend on the change was €2,400 for a half-day manager workshop.

Common mistakes to avoid

The most common failure is not a bad plan but an abandoned one. Managers start strong, then a launch or a quarter-end hits and the weekly one-to-one gets cancelled three times in a row. Protect those meetings the way you would protect a customer call.

Other patterns to watch for:

1. Front-loading every training session into week one, so nothing sticks
2. Assigning a buddy who is about to go on leave or is already overloaded
3. Setting goals that depend on access the new hire does not have yet
4. Skipping the day-90 review because “it is going fine”

Remote and hybrid hires need a little more structure, not less. Schedule the buddy chats with fixed times (for example, 16:00–16:15 GMT on Tuesdays and Thursdays) and make sure at least one of the month-one meetings happens on video with cameras on. If you are hiring across time zones, the remote-work articles on our blog cover overlap hours in more depth.

Where to start

If you are hiring this quarter, pick one upcoming start date and write the plan for that person before their offer is even signed. Share it with them in the welcome email. People notice when a company has thought about their first month, and it often comes up later when they talk about why they stayed.

Want to see how other teams describe onboarding in their listings? Browse roles that mention onboarding or read how Supabase presents its hiring process on its company page.