Free guide

30-60-90 Day Onboarding Plan Template: Free Example for Managers

The first three months decide a lot. New hires who get clear expectations, early wins and regular feedback ramp up faster and are more likely to stay. New hires left to "find their feet" often spend weeks confused, and some quietly start looking elsewhere. A 30-60-90 day plan is a simple, proven structure to prevent that. This guide explains how to build one, gives a free template with example goals, and shows how to run the check-ins that make it work.

What is a 30-60-90 day plan?

It's a short document that divides a new employee's first 90 days into three phases, each with a theme, specific goals and a review point:

• Days 1–30: Learn. Understand the company, the product, the team, the tools and how success is measured.
• Days 31–60: Contribute. Take ownership of real work with support, and deliver first results.
• Days 61–90: Own. Work independently, improve something, and set goals for the rest of the year.

The manager usually drafts it before day one and refines it together with the new hire in the first week. Some companies also ask candidates to draft one as part of the final interview — a useful test of how they think about the role.

Free mini 30-60-90 day plan template

Example: Customer Support Lead

Days 1–30

• Complete product training and handle 50 tickets personally to learn common issues.
• Meet each support agent one-to-one and the heads of product and sales.
• Review the last three months of support metrics and summarize the top five issues.

Days 31–60

• Run the weekly support team meeting.
• Rewrite the five most-used reply templates.
• Propose one process change to reduce first-response time.

Days 61–90

• Implement the process change and report the effect on response time.
• Publish ten help-center articles covering the top issues.
• Agree on quarterly goals and a development plan with the manager.

Example: Junior Software Developer

• Days 1–30: set up the development environment, ship a small bug fix in the first week, pair with a senior engineer on two features, learn the deployment process.
• Days 31–60: deliver a small feature end to end with code review, take a turn on support rotation with a buddy, document one part of the system that was confusing.
• Days 61–90: own a medium-sized feature, participate actively in planning, give useful code reviews to others.

How to write good goals

Every goal should be specific enough that both of you will agree whether it was achieved. "Learn the product" is not a goal. "Demo the three core workflows to the manager without notes" is. Use these rules:

• Start with a verb: complete, deliver, meet, publish, reduce, propose.
• Include a number or a clear deliverable where possible.
• Limit each phase to three to five goals.
• Include at least one relationship goal (who to meet) and one learning goal per phase.
• Make the 61–90 goals stretch a little — that's where ownership shows.

Check-ins that make the plan work

A plan that's written and forgotten is useless. Schedule these conversations on day one:

• Weekly 1:1s (30 minutes): progress, blockers, questions. The new hire brings the agenda.
• Day 30, 60 and 90 reviews (45–60 minutes): review each goal (done / partly / not), discuss what helped and what got in the way, and adjust the next phase.

Useful review questions

1. What's been clearer or less clear than you expected?
2. Which goal are you most proud of? Which was hardest?
3. What do you need from me or the team to succeed in the next 30 days?
4. Is there anything you'd change about how we onboard people?
5. (Manager) Here's what's going well, and here's one thing to focus on.

The 90-day review is also the natural point to confirm the end of probation and to record a quality-of-hire rating — a metric explained in our guide to recruitment funnel metrics.

Common mistakes

• Overloading month one. Learning takes time. Too many goals early leads to stress and shallow understanding.
• No early win. Plan something small and real to deliver in the first two weeks. It builds confidence on both sides.
• Skipping reviews when busy. The reviews are the point. Move them, don't cancel them.
• Vague success criteria. If you can't tell whether a goal was met, rewrite it.
• Treating it as a test. The plan is a shared tool. Adjust it when reality changes.

Adapting the plan for different roles and levels

The three-phase structure works for every role, but the content should change with seniority. For junior employees, weight the first month heavily toward learning and pair every goal with a named person who can help. For experienced hires, shorten the learning phase and expect a written assessment of the area by day 30 — what's working, what isn't, and what they'd change. For managers, add explicit people goals: one-to-ones with every direct report in the first two weeks, a team health check by day 45 and a first team plan by day 90. For sales and customer-facing roles, include pipeline or ticket targets that ramp up gradually rather than expecting full quota immediately. Whatever the role, keep the plan short enough to fit on one or two pages. A plan that is too long to read becomes a document nobody opens after the first week.

Frequently asked questions

Who writes the plan? The manager drafts it; the new hire reviews and adds to it during week one.

Does it work for remote employees? Yes — even more so, because remote hires have fewer informal chances to pick up context. Add explicit "meet" goals and a buddy.

What happens before day one? Equipment, accounts and a welcome message should be ready — see our new employee onboarding checklist.

The 30-60-90 Day Onboarding Kit gives you an editable plan with example goals, manager check-in agendas, a first-week checklist and a milestone review framework, ready to use for any role.

← More hiring guides