30-60-90 Day Onboarding Plan (Manager’s Guide)

This guide is for the hiring manager or HR person building an onboarding plan for a new team member. If you’re the new hire yourself, the main 30-60-90 day plan guide covers your perspective.

Up to 20% of employee turnover happens within the first 45 days. Research from Gallup shows that 70% of employees who had exceptional onboarding experiences say they have “the best possible job” — and they’re 2.6 times more likely to be extremely satisfied with their workplace. A structured 30-60-90 day onboarding plan is the single most reliable lever for turning a new hire into a confident, productive teammate by day 90.

The builder below walks you through five quick steps and produces a personalized onboarding plan for your new hire — name, role, company, and a clean structure with pre-built milestones and review schedule. Download as Word or PDF. No email required.

What a 30-60-90 day onboarding plan actually is

A 30-60-90 day onboarding plan is a document a manager builds for a new hire that outlines what the hire will learn, contribute, and deliver in their first three months on the team. Unlike an onboarding checklist (which is mostly administrative — equipment, paperwork, compliance training), the 30-60-90 plan is developmental. It answers three questions the new hire needs answered:

• What should I know? Foundations, training, key resources, who’s who.
• What should I do? Specific contributions, projects, deliverables — phased over 90 days.
• How will I be evaluated? The success metrics for each phase, the scheduled review dates, and what “fully ramped” means.

The framework: Welcome → Coach → Confirm. The first 30 days are about welcoming and integrating. Days 31–60 are about coaching toward independent contribution. Days 61–90 are about confirming full ramp and setting forward goals. Each phase has its own focus, its own measurement, and its own scheduled review.

Pre-boarding: what to do before day 1

The strongest onboarding plans begin before the new hire walks through the door (or logs in for the first day, for remote roles). The week before they start is when most preventable onboarding mistakes get baked in.

5 working days before start date

• Equipment, accounts, and access provisioned — laptop ordered, software licenses assigned, Slack/email/HR system access created
• Day-1 agenda drafted and shared — what time to arrive (or log in), who they’ll meet first, where to be at noon
• Onboarding buddy assigned and briefed — someone with at least 6 months of tenure, not someone who’s also new
• Welcome message sent from the manager — a short, warm email confirming start date and what to expect on day 1

2 working days before start date

• Final check that equipment has arrived and accounts work — log in once to verify
• Calendar holds placed for day 1, day 30, day 60, and day 90 reviews — this is the single most impactful preboarding step
• The 30-60-90 plan itself drafted and ready to share on day 1
• Team notified about the new hire — name, role, start date, what they’ll be working on

The reason to schedule the day-30, day-60, and day-90 reviews on the calendar before day 1 is that when reviews aren’t pre-scheduled, they get pushed. When they get pushed, the plan becomes decoration. Put them on the calendar first; everything else follows.

Days 1–30: Welcome and integrate

The first phase is about three things: making the new hire feel welcomed, getting them oriented on the basics, and starting relationship-building. Heavy ownership stays with the manager and the onboarding buddy in this phase.

Week 1: Foundation

• Day 1: Welcome 1:1 with the manager covering role, expectations, the 90-day plan, and the manager’s working style. End the day with a debrief and any open questions.
• Equipment, accounts, and access all working (verify, don’t assume)
• Required onboarding and compliance training initiated
• Onboarding buddy introduction — they own day-to-day “small question” support so the manager isn’t the only escalation path
• Team introductions: at least 5 1:1s with immediate teammates scheduled across the first two weeks

Weeks 2–3: Orientation

• Cross-functional introductions: 5–10 meetings with adjacent teams the new hire will work with
• Read the team’s key documents — strategy docs, last quarter’s OKRs, recent customer research, product roadmap (whichever apply to the role)
• Shadow current team members on representative tasks: a customer call, a sprint planning meeting, a typical workflow
• Manager 1:1 cadence established — weekly, with consistent agenda

Week 4: Synthesize

• New hire produces a “what I’m learning” memo for the manager — patterns they’re noticing, questions they have, things they want to dig into
• Day-30 review held (pre-scheduled): what’s going well, what’s harder than expected, adjustments to the 60-day plan
• First small independent contribution near the end of week 4 — a low-stakes task or workflow they own end-to-end

Manager’s checkpoint at day 30: new hire has completed onboarding training, met all immediate teammates plus 5+ cross-functional partners, has a basic working knowledge of the tools and processes, and has produced their first small piece of independent work.

Days 31–60: Coach toward independence

The middle phase is where the new hire transitions from “being onboarded” to “doing the work.” The manager’s role shifts from orientation to coaching — providing structured feedback on real deliverables.

• Assign the first real project — meaningful scope, clear success criteria, realistic timeline. Not a stretch project; a representative slice of the role.
• Coach on deliverables. Review the work, give specific feedback, model what “good” looks like for this team. The first 2–3 deliverables shape everything that follows — invest the coaching time.
• Continue weekly 1:1s with structured agenda: progress, blockers, feedback in both directions, development.
• Buddy stays active through day 60. Don’t retire the buddy relationship just because the new hire has been there a month — the buddy catches small questions that the new hire wouldn’t bring to the manager.
• Cross-functional relationships deepen — beyond the introduction meetings, the new hire starts collaborating on at least one cross-team workstream.
• Day-60 review held (pre-scheduled): performance against the 30-day plan, calibration on the 90-day goals, any role or scope adjustments.
• Skill gap identification. By day 45 or so, you’ll see where the new hire is naturally strong and where they need development. Build the training or coaching resource into the plan.

Manager’s checkpoint at day 60: first independent project shipped to standard, weekly 1:1 cadence running consistently, cross-functional relationships established, skill development plan in place if needed, day-60 review documented.

Days 61–90: Confirm full ramp

The final phase is about confirming the new hire is fully ramped on their core responsibilities and setting goals for the next quarter. The manager’s role shifts from coaching to confirming.

• Independent ownership. The new hire owns their core responsibilities without daily check-ins. The manager’s involvement scales back to weekly review rather than active oversight.
• Performance trajectory clear. By day 80 you should be able to answer: is this hire on track to meet expectations, exceed them, or are they struggling? Acting on the answer is the manager’s job in this phase.
• Day-90 review held (pre-scheduled): formal performance check, two-way feedback (the new hire reviews the onboarding too), next-quarter goal-setting.
• Set Q-next goals aligned with team OKRs. The new hire transitions from onboarding goals to ongoing performance goals.
• Onboarding retro. What worked in this onboarding? What would you change next time? Documenting this is how onboarding gets better over time — most teams skip it and stay at the same quality for years.
• Celebrate the milestone. Day 90 deserves recognition. A note from the manager, a team shoutout, mention in the next all-hands — choose what fits your team culture, but don’t let the moment pass without acknowledgment.

Manager’s checkpoint at day 90: new hire fully ramped on core responsibilities, day-90 review held with documented outcome, Q-next goals set and aligned, onboarding retro completed, milestone recognized.

The buddy system: how to actually make it work

Almost every onboarding guide mentions assigning an onboarding buddy. Very few explain how to make the buddy system actually work. Three things that distinguish effective buddy programs:

1. Choose the buddy deliberately

Not the most senior person on the team. Not the person with the lightest workload. The right buddy has these characteristics: 6+ months of tenure, a positive attitude toward the company, patient communication style, and bandwidth to spend 2–3 hours a week on buddy duties for 60 days. Skipping any of these criteria undermines the program.

2. Brief the buddy before day 1

The buddy needs to know: what they’re supposed to do (catch small questions, model the team’s norms, introduce the new hire to people, share unwritten rules), what they’re not supposed to do (replace the manager, perform formal evaluation, take on the new hire’s actual work), and how long the relationship lasts (typically 60 days). Without the brief, “be an onboarding buddy” defaults to “say hi on day 1 then disappear.”

3. Build a buddy rhythm

Daily 10-minute check-in for the first week. Twice-weekly for weeks 2–4. Weekly thereafter through day 60. The rhythm matters more than the content — most useful conversations happen because both people are sitting down at the same time, not because either had a specific topic in mind.

When onboarding is going wrong: the rescue

Most onboarding plans assume things go well. They don’t, sometimes. Here’s how to recognize and address the three most common failure modes.

If the new hire seems lost at day 30

Common symptoms: not asking many questions, missing small expectations, looking overwhelmed in meetings. Common cause: information overload combined with a culture they can’t read yet. The fix is to slow down: cancel any optional meetings on their calendar, reduce the next 30-day plan to 2–3 concrete goals (not 8), increase 1:1 frequency to twice a week temporarily, and ask the buddy to spend more time on day-to-day questions. Most “lost at day 30” cases resolve by day 50 with this intervention.

If the new hire is overconfident and pushing for change too fast

Common symptoms: proposing significant process changes in the first 30 days, sharing strong opinions about the team’s work before they’ve seen the context, downplaying input from teammates. The fix is direct conversation: “I appreciate the energy, and I want to channel it well. The first 30 days are for understanding the system before changing it. Your ideas matter — let’s revisit them at day 60 when you have full context.” Most of the time this lands. If it doesn’t, you have a culture-fit problem to address in phase 2, not phase 3.

If the new hire isn’t delivering on basic tasks by day 60

This is the hardest situation. By day 60 a new hire should be shipping work to standard on representative tasks. If they’re not, the cause is usually one of three: a skill gap that wasn’t caught in hiring (fixable with training), a fundamental misalignment between the role and the person (rarely fixable), or a context the new hire can’t navigate yet (often resolves with more time). Diagnose directly in your next 1:1: “I want to be honest — I expected we’d be further along on X by now. Help me understand what’s making it hard.” Their answer tells you what to do next.

Whatever you do, don’t avoid the conversation. The worst outcome for both you and the new hire is reaching the 90-day mark with unresolved concerns. They deserve a chance to course-correct; you owe them clarity.

By role: what changes

The framework is the same; the content shifts by role:

• Sales hires need a heavier ramp on product mastery in days 1–30, pipeline activity by week 3, first deals closing in days 60–90. See the 30-60-90 day sales plan for the rep-level framework.
• Engineers need a tech-stack onboarding plan, first code contribution by week 2 (ideally a small bug fix to validate the dev environment), feature ownership by day 60.
• New managers being onboarded need a hybrid plan — the onboarding framework for the company plus the manager-specific framework for leading the team. See the 30-60-90 day plan for new managers.
• Designers, marketers, and other functional specialists follow the standard framework with role-specific deliverables — first design review by day 45, first campaign by day 60, etc.
• Executives being onboarded need a very different plan with stakeholder mapping and a 30-day memo to the CEO. See the 30-60-90 day plan for executives.

Common mistakes managers make in onboarding plans

• Treating the plan as a document, not a process. The plan is only useful if the day-30, day-60, and day-90 reviews actually happen. Schedule them before day 1.
• Vague goals. “Get up to speed on the team” is not a goal. “Shadow 3 customer calls and write a one-page summary of patterns observed” is.
• No buddy or a bad buddy. Assigning a buddy who doesn’t have time or isn’t briefed is worse than not having one — the new hire learns that the team’s commitments don’t get kept.
• Information overload in week 1. Pacing matters. Too much in week 1 leads to retention loss by week 3. Spread the introductions and training across the full 30 days.
• Skipping the day-90 review. By day 90 onboarding feels “done” and busy managers move on. The day-90 conversation is the highest-leverage moment in the entire onboarding — don’t skip it.
• Not adjusting the plan as you learn. The plan you wrote on day 0 is wrong in some ways. By day 30 you’ll know which parts. Update accordingly.
• One-way feedback. The day-90 review should include the new hire’s feedback on the onboarding itself. Most managers skip this; the ones who don’t have better onboarding next time.

Example: 30-60-90 day onboarding plan for a new marketing manager

Filled-in structure. The interactive builder generates a much more detailed personalized version.

Pre-boarding (week before start):

• Laptop, software licenses, Slack/email access provisioned and tested
• Day 1 agenda shared by email
• Onboarding buddy assigned (Sarah, marketing manager with 18 months tenure)
• Day-30, day-60, day-90 review calendar invites sent
• Team notified in #marketing Slack channel

Days 1–30 — Welcome and integrate:

• Complete onboarding training and product certification by day 20
• 1:1s with all 5 immediate teammates and 8 cross-functional partners
• Shadow 3 customer calls and 2 sales-marketing alignment meetings
• Read last 4 quarters of campaign performance and competitive research
• Produce “what I’m learning” memo by day 28
• Day-30 review with manager

Days 31–60 — Coach toward independence:

• Own the next email campaign (briefing through send) with weekly coaching
• Propose one improvement to the campaign briefing process
• Establish weekly 1:1 with cross-functional partner in product marketing
• Day-60 review: campaign retrospective + 90-day goals refinement

Days 61–90 — Confirm full ramp:

• Own and ship 2 campaigns end-to-end with measurable results
• Document new campaign briefing process if the proposal landed
• Set Q-next OKRs with manager — campaign volume, KPIs, growth goals
• Day-90 review: performance summary, two-way feedback, onboarding retro
• Onboarding milestone acknowledged in marketing team standup

Download an onboarding template

If you’d rather start from a blank Word doc or PDF, the 30-60-90 day plan templates page includes an onboarding-specific version with the Welcome → Coach → Confirm structure built in. Word and PDF, both free, no email required.

Frequently asked questions

Who creates the 30-60-90 day onboarding plan — the manager, HR, or the new hire?

The hiring manager creates the plan, ideally with HR providing the template and ensuring consistency across departments. The new hire reviews and discusses it on day 1, then uses it as a working document. HR’s role is structural — making sure plans exist and the reviews happen. The manager’s role is substantive — making sure the goals and milestones are right for the role.

When should the plan be created — before or after the new hire’s first day?

Before. Ideally a draft is ready 5 working days before start date, with calendar invites for day 1, day 30, day 60, and day 90 placed at the same time. Creating the plan after the new hire arrives signals that their onboarding wasn’t planned, which is exactly the impression you want to avoid.

How specific should the day-30 / day-60 / day-90 goals be?

Specific enough that you can answer “did we hit it or not?” at the review. Vague: “get up to speed on the product.” Specific: “shadow 5 customer calls, complete product certification, write a one-page summary of the top 3 customer pain points you’ve heard.” Both you and the new hire need to know what success looks like.

What’s the difference between an onboarding checklist and a 30-60-90 day onboarding plan?

An onboarding checklist is administrative — equipment, paperwork, compliance training, account access. It’s mostly HR-driven and the same for every hire. A 30-60-90 day plan is developmental — what the new hire will learn, contribute, and deliver. It’s manager-driven and unique to the role. Both are needed; they complement each other.

How long should the plan be?

1–2 pages total. If it’s longer than that, the new hire won’t read it carefully and you won’t keep it updated. Concise plans get used; long ones become decoration.

What if the new hire is struggling at day 30?

Most “struggling at day 30” cases are information overload, not a hire mismatch. The fix is usually to slow down: reduce the next 30-day plan to 2–3 concrete goals, increase 1:1 frequency temporarily, and have the buddy spend more time on day-to-day questions. Most resolve by day 50 with this intervention.

Should I share the plan with the new hire on day 1 or earlier?

Day 1 in person works best. Sharing earlier (via email before start) can be overwhelming and creates the impression you’ve already decided what they should think. Walking through it together on day 1 lets the new hire ask questions and feel ownership.

How is this different for remote hires?

Same framework, more intentional execution. Build in video calls where you’d have casual hallway interactions in person. Schedule social time deliberately (a 30-minute “get to know you” with the team in week 1, virtual lunch in week 2). Buddy involvement is even more important for remote hires because there’s no informal context to pick up. And calendar everything — including the “small” check-ins that happen organically in person.

Build your plan now

The builder at the top of this page walks through five quick steps and produces a personalized 30-60-90 day onboarding plan with the Welcome → Coach → Confirm structure, scheduled reviews, and downloadable Word and PDF versions you can hand to the new hire on day 1.

For other situations: the main 30-60-90 day plan guide (new hire’s perspective), the downloadable templates, the manager spoke, sales spoke, executive spoke, and interview spoke. Related: goal setting and SMART goals.