Turn a vague first quarter into a practical ramp plan with clear learning, contribution, and ownership milestones.
A 30-60-90 day plan template gives a new employee and manager one shared view of priorities during the first three months. It should make expectations visible without treating onboarding like a rigid performance test. The resource below is designed for managers, people teams, and operations leaders who want a plan they can copy, tailor, and review together.
Quick answer
A strong 30-60-90 day plan divides a new hire’s ramp into three phases: learn during days 1–30, contribute during days 31–60, and own defined outcomes during days 61–90. For each phase, record objectives, actions, support, success measures, owners, and a scheduled review. Customize the milestones to the role and revise them with the employee as real conditions become clear.
What is included in this resource?
- A reusable 30-60-90 day plan structure
- Phase-by-phase prompts for learning, relationships, delivery, and ownership
- A worked example for an operations coordinator
- A manager review checklist and common mistakes to avoid
The plan complements, but does not replace, required hiring and onboarding administration. U.S. employers should manage employment eligibility through the current USCIS Form I-9 process and handle payroll withholding through the current IRS Form W-4 guidance. Consult qualified HR or legal advisers for requirements that apply to your location and workforce.
How should a 30-60-90 day plan work?
Use the plan as a living agreement, not a one-time handout. Draft it before the employee starts, review it together in the first week, and adjust unrealistic assumptions. Keep administrative tasks in the onboarding checklist; reserve this plan for capability, relationships, contribution, and results.
The three phases should show a deliberate progression. Days 1–30 emphasize context and safe practice. Days 31–60 add independent contribution. Days 61–90 establish repeatable ownership. Asana’s new-hire guide similarly separates learning, practice, and increasing mastery, while Culture Amp recommends treating the plan as a collaborative, accessible document with goals and success indicators.
30-60-90 day plan template
| Field | What to enter |
|---|---|
| Employee and role | Name, job title, manager, start date, team, and primary role purpose |
| Business context | The problems this role supports and the outcomes it influences |
| Phase objective | One plain-language outcome for each 30-day phase |
| Actions | Specific learning, meetings, practice tasks, and deliverables |
| Support | Manager, buddy, training, documents, systems, and approvals required |
| Success measure | Observable evidence that the objective has been met |
| Review | Check-in date, owner, feedback, decisions, and plan changes |
Days 1–30: learn the system
- Objective: Understand the role, customers, team, tools, policies, and decision paths.
- Actions: Complete required training, meet key partners, observe core workflows, review examples of good work, and practice low-risk tasks.
- Success measures: Explain the workflow accurately, locate required information, complete access and training milestones, and deliver a supervised first output.
- Manager support: Provide context, introductions, documentation, permissions, and a weekly check-in.
Days 31–60: contribute with feedback
- Objective: Perform recurring work with limited supervision and learn from review.
- Actions: Own selected tasks, participate in team planning, resolve routine exceptions, and document questions or process gaps.
- Success measures: Complete agreed work to the required standard, meet a realistic service target, and close feedback loops on time.
- Manager support: Review quality, remove blockers, and clarify where independent judgment is expected.
Days 61–90: own a defined outcome
- Objective: Take repeatable ownership of a meaningful part of the role.
- Actions: Run an end-to-end workflow, handle standard escalations, recommend one improvement, and agree on next-quarter goals.
- Success measures: Deliver the agreed outcome consistently, communicate status without prompting, and identify risks before they become delays.
- Manager support: Confirm decision rights, calibrate performance expectations, and set the next development priorities.
Example for an operations coordinator
| Phase | Example objective | Evidence |
|---|---|---|
| 30 days | Map the service-request workflow and shadow five requests | Validated process map, completed system training, and supervised request |
| 60 days | Coordinate routine requests from intake through approval | Ten completed requests with accurate records and on-time handoffs |
| 90 days | Own the weekly request queue and propose one improvement | Reliable queue reporting, documented exceptions, and reviewed improvement proposal |
This example measures observable work rather than vague traits. The exact numbers should reflect volume, complexity, training time, and available support. A target that depends on another team should name that dependency instead of holding the new hire responsible for an outcome they cannot control.
Manager review checklist
- Confirm every milestone relates to the actual job description and business need.
- Separate learning goals from production goals so early exploration is not penalized.
- Assign an owner for access, training, approvals, and feedback.
- Use observable evidence instead of phrases such as “fit in” or “show initiative.”
- Schedule reviews before the start date: weekly at first, then at days 30, 60, and 90.
- Record changes when priorities, dependencies, or staffing conditions shift.
- Ask the employee what support or context is missing.
Common mistakes to avoid
- Overloading the first month: Information intake and relationship building are real work.
- Using identical plans for every role: Keep the framework consistent, but tailor outcomes and evidence.
- Listing tasks without purpose: Connect each action to the capability or result it develops.
- Ignoring dependencies: Access, data, approvals, and manager availability can determine whether a milestone is possible.
- Treating the plan as a surprise evaluation: Agree on goals and changes openly with the employee.
Turn the template into a live onboarding workflow
A document is useful, but it can become stale when tasks, owners, and approvals live elsewhere. Workhint can turn this plan into a role-based onboarding workflow with assigned training, access requests, milestones, manager reviews, reminders, and an auditable record of changes. Teams that need more than a static checklist can use employee onboarding workflow software to connect the first 90 days to the operational systems where work actually happens.
Frequently asked questions
Who should write a 30-60-90 day plan?
The manager should prepare the first draft using the role’s real priorities. The employee should then help refine goals, dependencies, support, and success measures during the first week.
How many goals should each phase include?
Use one primary objective and roughly three to five supporting actions per phase. More detail can live in task lists; the plan should remain readable at a glance.
Is a 30-60-90 day plan a performance improvement plan?
No. A new-hire ramp plan sets onboarding expectations and support. A performance improvement plan addresses documented performance concerns through a separate process.
Should remote employees use a different template?
The structure can stay the same, but remote plans should explicitly schedule introductions, communication norms, system access checks, shadowing, and informal support that might otherwise happen naturally in person.
Conclusion
A useful 30-60-90 day plan creates clarity without pretending the first quarter is predictable. Start with learning, increase responsibility in measured steps, define evidence, name the support required, and revise the plan together. The result is a practical ramp system that helps a new employee understand what good work looks like and how to reach it.
Leave a Reply