30-60-90 day plan template for new hires
On this page
- Plans by role
- What makes a 30-60-90 plan useful instead of decorative
- The 30-60-90 day plan template
- A filled example: a mid-level customer support hire
- Writing goals a manager can actually check
- Building the plan before day one
- Running the check-ins
- Mistakes and what this plan is not
- Adapting the plan by role type
- Questions people ask
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.
Plans by role
| Role | First 30 days | Day-90 bar |
|---|---|---|
| Sales reps | Product and objection-handling certification, shadowed calls, a scored target account list, no live quota yet | Carry 75% of full quota with pipeline coverage of at least 3x that number, and a deal closed or in final signature |
| New managers | A first one-on-one with every direct report and a written team diagnosis, with no structural changes | Propose the team's next-quarter priorities and make one staffing or workload call independently |
| Software engineers | A working dev environment by day two and 3-5 small, reviewed pull requests merged | Join the on-call rotation as secondary responder and own a project with real ambiguity |
| Nurses | Hospital orientation, EHR competency, and core skills validated with the preceptor present at a reduced patient ratio | Carry the standard unit patient assignment independently with a fully signed competency record |
| Recruiters | A reduced req load of 1-3 requisitions, with every submittal and rejection reason logged in the ATS | Carry the desk's standard req load with a placement closed or in final offer stage |
| Customer success managers | Reading the full book's account history before taking ownership of any account | Carry the full book independently with one renewal run and closed solo |
| Marketing managers | An audit of every active channel, campaign and spend line, with no new spend authorized yet | Full budget ownership and a next-quarter campaign calendar defended with the audit and campaign evidence |
| Executives | A structured listening tour across reports, peers and stakeholders, with no structural changes announced | A forward plan for the next two to four quarters, plus one independent decision within agreed decision rights |
| Product managers | 8-15 customer conversations, a written product teardown and the area's key metrics reproduced without help | Present a next-quarter roadmap the eng lead will defend, with the day-60 change measured against its baseline |
| Project managers | A status reassessment memo with a refreshed RAID log and an honest forecast finish date | A milestone delivered on the rebaselined date and a forecast the sponsor and workstream leads believe |
| Account managers | A tiered book with a risk note per account and an intro meeting with every top-tier contact | Carry the full book with an accurate quarter forecast and one expansion opportunity taken to proposal |
| HR managers | A risk memo covering every open case, the compliance calendar and HRIS-to-payroll gaps | The first phase of an agreed people priority live, plus a quarterly people review leadership acted on |
| Operations managers | A full shift on every shift pattern and a 13-week KPI baseline with causes found on the floor | One process improvement measured against the baseline and held for at least two weeks |
| Engineering managers | A one-on-one with every engineer and a delivery, on-call and technical-debt baseline | A quarterly plan agreed with product, a written staffing plan and one hard people issue handled directly |
| Data analysts | Key metrics reproduced from source tables and reconciled to the dashboards, with SQL reviewed | An analysis that informed a decision and a dashboard with documented definitions used weekly |
| Customer service reps | Training and nesting on simple contact types, with passing QA scores and handle time tracked but not targeted | Team-standard quality, resolution and efficiency for two consecutive weeks, including tier-two contacts |
| Finance managers | Shadow the first month-end close and write a close and controls assessment | Run the third close alone, faster or cleaner than the first, with a forecast used in the board pack |
| Sales managers | A call review and one-on-one with every rep, a scrub of every open deal and the forecast call shadowed | The quarter's commit lands within the agreed range, with a next-quarter pipeline plan and one people decision made |
| Nurse managers | Time on nights and weekends with every staff member met, and a labor, quality and turnover baseline with trends | One quality focus moving on its process measure, stay conversations held and a 6-month unit plan agreed |
| IT managers | Privileged access transferred, a systems and contract inventory, and a ranked risk register | A timed backup restore done, a roadmap tied to the risk register and one measured service desk fix |
| UX designers | A heuristic audit backed by evidence and one small change shipped through critique | A feature tested with target users, shipped and reported against a measure agreed before the build |
| Data scientists | An existing model's training and evaluation reproduced, with every gap documented | A model or experiment taken to a launch, iterate or stop decision, compared against a simple baseline |
| Executive assistants | A preferences guide the executive has corrected, written delegated-access rules and a calendar audit | Calendar and travel run without approval, plus a board meeting or offsite run end to end |
| Retail store managers | Every shift pattern worked, cash and key procedures signed off and a 13-week scorecard baseline | Two agreed scorecard metrics at plan, a passed district walk and a season plan |
| HR business partners | A listening tour of the client group's leaders and a people data baseline with exit themes | A people plan the client leader presents as their own, with first actions underway |
| Supply chain managers | A network map, a service and inventory baseline with written definitions, and a stockout root-cause list | One recurring cause fixed and measured, and a 12-month plan agreed with finance |
| Teachers | Classroom routines in place, every IEP and 504 plan read and every family contacted | A formal observation that shows growth from informal visits, with grades and IEP progress reports on time |
| Accountants | A first batch of handed-over accounts reconciled on deadline, with every review note logged by type | A full set of owned accounts reconciled for the third straight close, with written procedures and audit requests ready |
| Recruiting coordinators | A map of every interview loop and a baseline of time to schedule, reschedules and on-time feedback | Interview days run solo and one recurring scheduling problem measurably reduced |
| Chiefs of staff | A written mandate the principal signed off, a one-to-one with every leader and a time audit | A planning cycle or board meeting delivered and one cross-team priority moved to a decision |
| Warehouse managers | A blind sample count against the system, forklift operator records checked and a dock-to-ship baseline | One measured flow improvement held for two weeks and a peak plan agreed |
| Restaurant managers | A shift on every station and daypart, required food safety certification in hand and a cost baseline | Prime cost at target for four weeks and a clean self-inspection or health inspection |
| Construction project managers | A contract summary with every notice deadline, a cleaned change order log and a job review memo | A cost-to-complete forecast that holds month to month, with pending change orders falling |
| Social media managers | An account access audit, a 90-day channel baseline and a signed-off escalation guide | A quarterly plan tied to one tracked business goal, plus a written playbook |
| Business analysts | A current-state process map built by watching the work and corrected by the people in it | One change through user acceptance with its downstream defect and clarification measures reviewed |
| Office managers | An inventory of every vendor and contract with notice dates, and 12 months of office spend | One recurring request problem fixed with numbers, a vendor improved and a forward office calendar |
| QA engineers | The suite running locally, critical user journeys mapped with coverage and a flaky test inventory | A release signed off with a written risk summary and an escaped-defect analysis that led to a change |
| DevOps engineers | An infrastructure inventory and drift list, a delivery metrics baseline and a full on-call shadow week | Primary on-call, with one pipeline or reliability improvement shipped and measured against the baseline |
| Account executives | Every inherited deal re-qualified, demo certification passed and every active buyer contacted | A closed or signature-stage deal and weekly commit calls that track what actually closed |
| Sales development reps | Messaging certification passed and reviewed outreach live on researched accounts, with activity tracked but not targeted | Accepted meetings at the ramp target for three straight weeks and one message test shared with the team |
| Controllers | The first close observed, a written balance sheet review and a controls map with segregation-of-duties gaps | A third close tracked and improving, a named preparer and reviewer on every account and a controls roadmap |
| Paralegals | Docketing and e-filing sign-off, written client contact rules and a status note on every assigned matter | A named list of matters run reliably and one major binder, production or closing set delivered on time |
| Plant managers | A safety walk in week one, a full shift on every crew and a plant scorecard baseline with definitions | One loss fixed and held for weeks, with a 12-month plant plan agreed |
| School principals | Safety, special education and staffing checks done, every classroom visited and a data baseline by student group | One instructional priority with early walkthrough evidence and a year plan shared with staff and families |
| Nurse practitioners | Credentialing, prescribing and any required collaboration in place, with supervised visits on a reduced schedule | The standard schedule with chart review at a reduced sample and a first panel quality report |
| Product marketing managers | Customer and win-loss conversations summarized and an audit of the messaging and sales materials | A launch delivered against measures agreed in advance, with positioning and materials sales actually use |
| Talent acquisition managers | An audit of every open req with recruiters and a funnel baseline with written definitions | A two-quarter hiring forecast and one funnel stage measurably improved |
| Pharmacists | License verified, controlled substance procedures signed off and overlapped shifts with a near-miss log | The full shift rotation, including peaks, with counts reconciled and one recurring task owned |
| Physical therapists | License and payer setup, a reviewed documentation sample and outcome measures on a reduced schedule | The standard schedule with plans of care certified on time and a caseload review using outcome data |
| Social workers | Mandated reporting and safety training, shadowed cases and a starter caseload of lower-risk cases | The standard caseload, including higher-risk cases, with documentation on time and supervision logged |
| Field service managers | A ride-along with every technician, a day with dispatch and a service metrics baseline with definitions | One cause of repeat visits fixed and held against the baseline, with a two-quarter service plan |
| IT support specialists | Identity verification signed off before any reset, shadowed tickets and reviewed device builds | An owned queue at team standards and one recurring ticket type fixed or proposed |
| Cybersecurity analysts | An environment map with log coverage gaps, a runbook review and shadowed triage | An owned detection area, a tabletop exercise run and a log coverage gap closed or scheduled |
| Financial analysts | Last month's results reproduced from the ledger with every difference explained | An analysis a business partner used for a decision and a forecast review against actuals |
| Procurement managers | A spend analysis from AP and card data and a contract calendar with notice dates | A sourcing event awarded on documented criteria and savings reported on a definition finance agreed |
| Facilities managers | Every building walked, a compliance calendar and a work order baseline with risks ranked | Nothing overdue on the calendar, backlog improving against baseline and a capital plan reviewed with finance |
| Content marketers | A content audit with numbers and decisions, customer and sales interviews and agreed measures | Publishing on cadence with a first report on agreed measures and next quarter planned |
| Mechanical engineers | Drawing standards learned, time on the floor and small changes released through the full change process | A part released with first articles reviewed, a design review led and a part family owned |
| Maintenance managers | Lockout/tagout and forklift records checked, a shift with every crew and a downtime and PM baseline | One worst asset improved and held against the baseline, with a 12-month maintenance plan |
| Property managers | Every building walked, a lease and rent roll audit and fair housing practices reviewed | Turn time and delinquency improving against baseline and a budget the owner accepts |
| Insurance agents | License and appointments confirmed, shadowed calls and practice quotes reviewed | An owned book of renewals and service with coverage decisions documented on every file |
| Real estate agents | License active under the broker, brokerage training done and a tagged contact database | An active client with a complete file and a lead plan built from what produced appointments |
| IT directors | A business listening tour, an evidence-based risk check and a spend and contract map | A roadmap and budget tied to business priorities that leadership approves |
| HR generalists | I-9 and new hire reporting deadlines met, a question log and a sample file audit | An owned employee group supported solo and one HR process improved against baseline |
| Payroll managers | Tax deposit schedule confirmed, every pay group shadowed and last quarter's 941 reconciled | A clean quarter-end filed and reconciled, with a written payroll controls plan |
| Medical assistants | HIPAA and bloodborne pathogens training before patient contact and skills checked off with a preceptor | A full provider schedule worked alone with one recurring clinic task owned |
| Dental office managers | HIPAA and OSHA records checked and a schedule and insurance AR baseline agreed with the owner | Old AR and unfilled time falling against baseline, with a monthly owner report running |
| Civil engineers | Redlines and takeoffs through QA/QC, a site visit and the PE in responsible charge named | A submittal owned through first agency review with hours tracked against the task budget |
| Electrical engineers | Electrical safety training and qualified status settled, drawings checked against the field and small corrections released | A design installed or commissioned with punch items closed and a scope owned |
| Data engineers | Two critical tables traced from source to dashboard and small fixes merged through review | A data domain owned with freshness, failures and cost reported and one recurring failure fixed |
| Technical writers | The product used hands on, a docs audit backed by support and search data and small fixes published | A doc set owned with a ranked backlog and one audit theme fixed and checked against support data |
| Account coordinators | Every client's scope, budget and open items summarized, with meeting notes drafted for review | One client's routine work run with light review and budget reconciled to billing |
| Office administrators | A written list of every recurring task, a request log and OSHA postings and exit routes checked | Daily operations run alone, one repeat problem fixed and a 12-month office calendar |
| Store managers | Every shift worked, minor labor rules and exit routes checked and a baseline agreed with the owner | Written cash and receiving controls in use, measures improving and a quarter plan agreed |
| Hotel managers | A shift in every department, accessible reservations and pool safety checked and an operating baseline | Guest and operating measures improving against baseline with a next-quarter plan agreed |
| School counselors | Reporting and crisis procedures learned and every high-priority student on the caseload contacted | Lessons and groups running, referrals tracked and program goals set from school data |
| Clinic managers | HIPAA, OSHA and CLIA records checked and an access, flow and denial baseline agreed | Denials and no-shows falling against baseline with a monthly report and staffing plan |
| Dental hygienists | License, permits and bloodborne pathogens training done, with charts reviewed on a reduced schedule | A recall column owned at the standard appointment length with same-day notes |
| Occupational therapists | License and payer setup, functional goals in reviewed notes and a reduced schedule | The standard caseload with plans certified on time and a caseload review using outcome data |
| Respiratory therapists | Credentials verified, fit test done and core competencies signed off with a preceptor | The full assignment, including critical care and nights where required, with all competencies signed |
| Logistics managers | A 12-month freight spend baseline, written delivery definitions and DOT records checked | One lane or cost problem fixed and held against the baseline, with a two-quarter plan |
| Compliance officers | Every open case owned, an obligations calendar and the policy gaps listed | A refreshed risk assessment and a compliance work plan the board or committee approved |
| Underwriters | Guidelines and filed rules learned, with files reviewed before binding at reduced authority | A clean file audit and an authority letter widened one step |
| Loan officers | NMLS status confirmed, the disclosure workflow learned and first applications reviewed | An owned pipeline with Loan Estimates on time on every file and a referral plan |
| Claims adjusters | License and state claim rules learned, with a reduced desk under file review | The standard desk within an authority letter with no missed state deadlines |
| Quality managers | Audit, corrective action and complaint records reviewed and every shift walked | Overdue corrective actions closed with verified causes and a management review held |
| Safety managers | Five years of OSHA logs audited, every shift walked and hazards ranked | Top hazards controlled and a funded 12-month safety plan with agreed measures |
Each row links to a full plan with copy-ready goals, a filled example and the mistakes that most often stall that specific role, current as of October 2026.
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:
Jordan Ellis — Customer Support Specialist — 30-60-90 Day Plan
Manager: Nadia Farris | Start date: Monday, September 28
First 30 days: Learning
- Complete the support platform and macros training
- Shadow 15 live tickets and 5 calls across senior teammates
- Handle 10 low-complexity tickets solo, reviewed before sending
Success looks like: comfortable navigating the ticketing system unassisted, and the 10 reviewed tickets need only minor edits, not rewrites.
Check-in: October 27, with Nadia
Days 31-60: Contributing
- Own a full queue shift independently, no pre-send review
- Reach first-response time within team average
- Complete the escalation-handling module and shadow 2 escalations
Success looks like: a full shift handled solo with normal escalation to a lead only when genuinely needed.
Check-in: November 26
Days 61-90: Owning
- Hit team-average CSAT and resolution-time targets for two consecutive weeks
- Identify and write up one recurring ticket pattern worth a macro or FAQ update
- Begin cross-training a newer hire on one workflow
Success looks like: performing at team baseline on core metrics with no unusual escalation rate.
Check-in: December 27 — full 90-day review
Writing goals a manager can actually check
| Vague | Checkable |
|---|---|
| "Get comfortable with the tools" | "Complete the platform certification and handle 10 solo tickets, reviewed" |
| "Build relationships with the team" | "Meet 1:1 with each of the 5 cross-functional partners listed by day 20" |
| "Start contributing" | "Ship one feature/fix/deliverable reviewed by a peer by day 45" |
| "Understand our metrics" | "Present the team's current dashboard back to the manager, explaining what drives each number, by day 30" |
| "Be fully ramped by 90 days" | "Independently own [specific area] and hit [specific target] for two consecutive weeks" |
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 and what this plan is not
Mistakes that make the plan pointless
| Mistake | Why it fails | Fix |
|---|---|---|
| Goals copied from a generic template, unchanged | Reads as a formality, not a real expectation for this role | Write at least half the goals specific to this team's actual work |
| No one revisits it after day one | The plan becomes a document nobody references, including the manager | Calendar the three check-ins before the new hire even starts |
| Every goal is equally vague | Neither party can tell whether the phase went well | Rewrite each goal until it names something a manager could actually check |
| The plan is used only to justify a bad outcome | New hire feels it was a trap rather than a support tool | Use check-ins to surface and fix problems early, not just to document them at 90 days |
| 90-day goals are set with no input from the new hire | Goals feel imposed and disconnected from what they've actually learned by day 30 | Revisit and adjust days 61-90 goals at the 60-day check-in based on real progress |
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.
Questions people ask
Who writes the 30-60-90 day plan, the manager or the new hire?
The manager drafts the skeleton before day one so the new hire is not starting from a blank page, then the new hire fills in specifics and adjusts it in the first week once they have real context. A plan the new hire had no hand in tends to feel imposed rather than owned.
Should the plan be shared with the new hire before they start?
Share at least the shape of it — what the three phases are about — during the offer or pre-start period, so the first day is not the first time they hear what success looks like. The specific milestones can be finalized in week one.
What if the new hire is behind by day 60?
Say so directly at the 30-day check-in if it is already visible, rather than waiting for day 60 to deliver news that should not be a surprise. A 30-60-90 plan only works as an early-warning tool if the manager actually uses the checkpoints to have the hard conversation early.
Does every role need a full 90-day plan?
Roles with a short ramp — highly structured, high-volume roles with clear daily output — can use a lighter version focused on the first 30 days. The fuller three-phase plan earns its complexity for roles where judgment and relationships take longer to build than task competence.