30-60-90 day plan template for new hires

A 30-60-90 day plan is a written set of goals for a new hire's first three months, broken into three phases: learning the role in the first 30 days, contributing independently by 60, and owning real outcomes by 90. It gives both the new hire and the manager a shared, checkable definition of what "going well" means at each point, instead of a vague sense that things seem fine.

This is a goals document, not a task checklist. For the operational first-week checklist — equipment, access, introductions — see new hire onboarding checklist. The two work together: the checklist gets someone set up to work, the plan defines what they are working toward.

What makes a 30-60-90 plan useful instead of decorative

A plan that says "get up to speed" by day 30 cannot be checked against reality. A plan that says "complete the onboarding curriculum, shadow three customer calls, and submit one ticket with review" can be. The difference is specificity: each phase needs goals a manager can look at on the actual day and say yes or no, not goals that require interpretation.

• 30 days: learning. Understand the systems, people, and current state of the work. Low-risk output, heavily reviewed.
• 60 days: contributing. Independent work on real tasks, still checked but with less hand-holding. First visible output the team can evaluate.
• 90 days: owning. A defined piece of the role run with real autonomy, and early signal on the metrics or outcomes the role exists to move.

The 30-60-90 day plan template

[Employee name] — [Role] — 30-60-90 Day Plan
Manager: [Name] | Start date: [Date]

FIRST 30 DAYS: Learning
Goals:
- [Goal — e.g. complete onboarding/training on X systems]
- [Goal — e.g. meet with these X stakeholders]
- [Goal — e.g. shadow/observe X process]
Success looks like: [What a manager can check by day 30]
Check-in: [Date], with [manager/buddy]

DAYS 31-60: Contributing
Goals:
- [Goal — e.g. independently complete X task type]
- [Goal — e.g. deliver first version of X]
- [Goal — e.g. take ownership of X recurring responsibility]
Success looks like: [What a manager can check by day 60]
Check-in: [Date]

DAYS 61-90: Owning
Goals:
- [Goal — e.g. own X area/metric independently]
- [Goal — e.g. propose an improvement to X process]
- [Goal — e.g. hit X specific target]
Success looks like: [What a manager can check by day 90]
Check-in: [Date] — full 90-day review

Notes: [Anything role-specific — a project this role inherits,
a person they'll partner closely with, a known gap to close]

A filled example: a mid-level customer support hire

An invented new hire and role, written the way a usable plan reads:

Writing goals a manager can actually check

Building the plan before day one

Draft the skeleton — the phase goals, not every detail — before the new hire starts, using the job description and what the role actually needs to be doing by 90 days. Share the shape of it during the pre-start period so the first day is not the first time they hear how they will be measured. In the first week, sit down together and adjust: the new hire may have context from their own onboarding conversations that changes a goal, and having a hand in shaping the plan makes it something they own rather than something handed to them.

Running the check-ins

Each phase ends with a real conversation, not just a box checked on a form. Ask three questions at every check-in: what did you actually get done against the plan, what got in the way, and what needs to change in the next phase because of what you learned. If the new hire is behind at the 30-day mark, say so plainly rather than waiting to see if 60 days fixes it on its own — a plan that never surfaces a real problem until day 90 has failed at the one thing it exists to do, which is catch a struggling ramp early enough to help.

Mistakes that make the plan pointless

Not a performance improvement plan

A 30-60-90 day plan and a performance improvement plan look superficially similar — both have phases, both have checkpoints — and treating the first like the second is a common way to sour a new hire's start. A 30-60-90 plan is a shared onboarding tool built with the new hire before or during their first week, aimed at ramping someone who is presumed to be a good hire. A performance improvement plan is a corrective document, usually introduced later and often after specific problems have already surfaced, aimed at giving a struggling employee a defined chance to improve or documenting that the company did so. If a new hire is genuinely underperforming during their first 90 days, that is a direct conversation and, if it continues, likely a separate process — not something to fold into the onboarding plan's language, which will read as a bait-and-switch to the new hire and undermine the plan for the next person who receives one.

Adapting the plan by role type

• Individual contributor, technical: weight 30 days toward codebase or systems literacy, 60 toward a first shipped contribution reviewed by a senior peer, 90 toward independent ownership of a defined area.
• Sales: 30 days on product and process training with no live quota, 60 days on a reduced quota or pipeline-building target, 90 days on a full or near-full quota.
• Manager hires: 30 days on 1:1s with every direct report and stakeholder, 60 days on a first team process change, 90 days on a defined goal the team is accountable to under the new manager.
• High-volume operational roles: a lighter 30-day version is often enough — structured tasks with a short ramp do not need a full 90-day arc to show whether the hire is working out.

Whatever the role, keep the phase boundaries loosely tied to the calendar rather than rigid. A new hire who starts the week before a major holiday, or joins a team mid-launch, will not have a clean 30-day mark the way the template implies. Move the check-in by a few days rather than forcing a review onto a date that will not reflect real progress either way.

Comparing plans across a team or cohort

If your team hires often enough to bring on several people a quarter, keep the completed 90-day reviews on file and read them together once or twice a year. Patterns that are invisible in a single hire's plan — the same goal consistently missed across several new hires, or a check-in date that always slips because the real workload does not match what the plan assumed — show up clearly once you have four or five plans side by side. That comparison is usually more useful for improving the template itself than anything a single 90-day review can tell you on its own.