A 30-60-90 day onboarding plan is the structured roadmap a new hire and their manager agree on in week 1. It splits the first three months into three phases: learn (days 1-30), contribute (days 31-60), and lead (days 61-90). Done right, it turns "we hope they figure it out" into a measurable ramp with clear weekly milestones, defined success criteria, and a fixed check-in cadence. Done wrong, it sits in a template folder and never opens after week 1.
This guide gives you the full structure, a downloadable layout, role-specific variations, and the small details that determine whether the plan actually gets used.
What a 30-60-90 day plan actually does
Most onboarding is calendar-driven (orientation day, IT setup, manager intro lunch) but outcome-blind. The 30-60-90 plan reverses that: it starts with the outcomes you expect at days 30, 60, and 90, then works backward to what learning and projects need to happen each week. Three things change once the plan is in place:
- Both sides know what "good" looks like at each milestone. No vague "ramp up." Specific deliverables tied to specific dates.
- Weekly 1:1s become structured. The hire arrives to the 1:1 with progress against the plan. The manager arrives with adjustments. No more "how's it going" leading to "good" leading to nothing.
- The 90-day review is grounded. Either the hire hit the milestones or they did not. The decision to extend, level-up, or part ways is based on evidence, not gut feel.
The three phases
Days 1 to 30: learn
The "absorb" phase. The hire is consuming information, meeting people, understanding context. Output is low and that is correct. The bar for week 4 is "can describe how the business makes money, who the key people are, and what the team's current priorities mean."
Week-by-week structure:
- Week 1. Logistics + orientation + meet the team. Read the team's working docs. Set up the working environment. Shadow 1-2 stakeholder meetings.
- Week 2. Deep-dive sessions with peers and adjacent teams. Read the last quarter's review docs. Sit in on a customer or stakeholder call.
- Week 3. Start a small, low-risk task that produces a tangible artifact (a brief, a code review, a customer note, a data pull). The goal is to learn the team's review cycle, not to ship anything important.
- Week 4. Present back to the manager and peers: "what I've learned, what surprised me, what I'm still unclear about." This is the 30-day checkpoint.
Days 31 to 60: contribute
The hire is now expected to own pieces of work, not just learn. The 30-day "what I've learned" presentation becomes the entry into project ownership.
- Week 5. Take ownership of one defined project end-to-end. Manager scopes it down so it's achievable in 3-4 weeks.
- Week 6. First independent stakeholder call or customer interaction (with the manager in the room, but the hire leading).
- Week 7. Mid-project check-in. Course-correct if scope or approach is off.
- Week 8. Ship the project. Document the work. Present results at the 60-day checkpoint.
Days 61 to 90: lead
The hire is operating at full capacity, with the team treating them as a full team member. The plan now includes initiating things, not just executing them.
- Week 9. Pick up a second project, this time scoped by the hire (with manager input) rather than handed to them.
- Week 10. Mentor a smaller-stakes task for someone else (a peer, a contractor, an intern) if relevant. If not, take ownership of a recurring process.
- Week 11. Drive a meeting end-to-end (planning, agenda, follow-ups). The manager attends as a participant, not a host.
- Week 12. 90-day checkpoint. The hire presents what they own going forward, what they've learned about the team, and where they want to grow next. This conversation feeds the first formal performance check-in at month 6.
The plan template
The structure that works across roles:
| Section | What goes in |
|---|---|
| Role context | Title, team, manager, key stakeholders, primary OKRs the role contributes to. |
| 30-day goals | 3 to 5 specific outcomes. Mostly learning-shaped (e.g., "shadow 5 customer calls," "complete the engineering onboarding modules"). |
| 60-day goals | 3 to 4 outcomes. Project ownership starts (e.g., "ship the X workflow," "publish 3 blog posts"). |
| 90-day goals | 2 to 3 outcomes. Full ownership and one piece of initiative. |
| Weekly check-in cadence | 1:1 with the manager (weekly or every 2 weeks), 30/60/90 day formal checkpoint dates fixed in calendars on day 1. |
| Stakeholder map | Who the hire needs to meet by when (week 1: direct team. Week 2: adjacent teams. Week 4: leadership.). |
| Resources | Docs to read, courses to take, tools to learn. Linked, not just named. |
| Success criteria | The 1-sentence definition of "this is working" at each checkpoint. |
Run the plan, not just write it
The Employee Onboarding Form captures the hire's goals, stakeholder map, and checkpoint dates in one place. Pin it to your weekly 1:1.
Use the Employee Onboarding Form
Free forever plan • No credit card • Setup in 2 minutes
Role-specific adjustments
The structure is the same; the content shifts by role.
Sales (AE / SDR)
- 30 days: Product training, shadow 10 calls, learn the ICP, master the CRM and tooling.
- 60 days: First independent calls (with coach in the room), book first meetings, pipeline-building activities at 60-80% of ramped quota expectation.
- 90 days: First closed deals (if cycle allows). Pipeline at 100% of ramped expectation. Begin contributing to playbook updates.
Engineering
- 30 days: Local dev environment running. First small PR shipped (typo fix, doc update, simple bug). Read the architecture overview.
- 60 days: Own a small feature end-to-end. Participate in code reviews. On-call shadowing.
- 90 days: Lead a small project. Full on-call rotation. Identify and propose one technical improvement.
Marketing
- 30 days: Brand voice and positioning absorbed. Audit current channels. Shadow customer calls or read interview transcripts.
- 60 days: Ship the first campaign or content piece. Set up reporting for what they own.
- 90 days: Own one channel or content stream end-to-end. Propose one new bet for the next quarter.
Customer success / support
- 30 days: Product certification complete. Shadow 30+ customer interactions. Learn the support tool stack.
- 60 days: Solo on tier-1 tickets. First customer renewal conversation (CS specific) with manager listening.
- 90 days: Full ticket queue ownership at quality bar. Pattern-recognition reports flowing back to product.
Management / leadership
- 30 days: 1:1s with every direct report. Read the last 6 months of team output. Meet every peer leader.
- 60 days: Diagnosis written up: what's working, what's not, what they would change.
- 90 days: First strategic change implemented (or a clear plan for one). First quarterly plan owned.
The check-ins are the plan
A 30-60-90 plan without scheduled check-ins is a document, not a process. Three check-ins that must be on the calendar before day 1:
- Weekly 1:1 (45 min). Standing meeting. Agenda: progress against the plan, blockers, the question the hire most wants to ask. Both sides arrive prepared.
- 30-day, 60-day, 90-day checkpoints (60-90 min). Longer than the weekly 1:1. The hire presents what they've done and learned. The manager assesses against the milestones. Concrete changes to the plan come out of these.
- 90-day landing review. A formal review with skip-level if relevant. Outcomes: continue as planned, accelerate (more scope), course-correct (specific gaps and a 30-day plan to close them), or part ways. The decision is documented.
How this fits into the broader onboarding flow
The 30-60-90 plan covers months 1-3. The full onboarding lifecycle goes earlier and later. See the companion guide on the employee onboarding process for the 7-stage framework that spans pre-boarding through month 6. And if you're putting the plan into action without a manager's checklist, our breakdown of common onboarding mistakes covers the patterns that derail the plan in week 2.
One operational tip: use a standard employee records template so the plan, check-in notes, and 30/60/90 checkpoint summaries live in one place per hire, not scattered across docs, sheets, and Slack threads.
Common reasons 30-60-90 plans fail
Five patterns that explain why most plans get abandoned in week 3:
- Plan written, never opened. The hire never sees it referenced after day 1. Fix: pin it to the weekly 1:1 agenda.
- Goals are too vague. "Learn the product" is not a goal. "Demo the product unaided to a peer by end of week 3" is. Specific and verifiable.
- Manager doesn't track it. If the manager doesn't open the doc before the 1:1, the hire stops opening it too.
- No 30/60/90 checkpoints in the calendar. Without fixed dates, the milestones drift into "we'll catch up soon" and never happen.
- Plan never adjusted. Reality shifts. The first project gets cancelled. A new priority emerges. If the plan is treated as static, it becomes irrelevant. Fix: update it formally at each checkpoint.
The takeaway
A 30-60-90 day plan works because it forces both sides to align on outcomes at week 1, gives the weekly 1:1 a structure, and produces a defensible decision at day 90. The structure is consistent across roles; the content varies. Build the plan in the offer week (not day 1), put the weekly 1:1 and three checkpoints on the calendar before the hire starts, and treat the plan as a living document that gets updated at each checkpoint. Then it is a tool, not a folder artifact.
