30-60-90 Day Onboarding Plan for a New Employee (With Example)

A new hire learns the booking software in a few shifts, but the owner still checks every unusual appointment. By the end of the first month, both may be unsure what “fully trained” means. A 30-60-90-day onboarding plan solves that by naming the work the employee should be able to do, the evidence a manager will inspect, and what support remains available.

Begin with three milestones: by day 30, the employee understands the job and can demonstrate the basics; by day 60, they handle agreed routine work with less prompting; by day 90, they contribute consistently within clearly defined authority. Treat those as planning checkpoints. A role, schedule, qualification requirement or employee’s support needs may require a different pace.

Download the 30/60/90-day plan and completed example (Word). The document includes an editable blank plan and a fictional service-coordinator example.

Start with the actual job, not a generic 90-day goals list

Start-day access, pay and hiring paperwork belong in the first-month onboarding checklist. This plan focuses on role-specific development milestones and evidence of learning.

Write down the work the employee is joining the business to do. A scheduling assistant might book routine service calls, confirm customer access, correct obvious contact errors and pass pricing exceptions to the owner. A shop supervisor will have very different milestones. The plan should match the job’s decisions, tools and risks.

For each responsibility, capture four things: the result you want, the circumstances in which the employee should perform it, how the result will be checked, and the person who can approve an exception. The words “learn the system” are too vague to review. “Create four sample bookings with the correct technician, time and job notes” gives the trainee something concrete to demonstrate.

Use the editable first-month onboarding checklist for first-day logistics, payroll setup and applicable hiring records. This 30-60-90 plan tracks role development after the initial setup. The two documents can share an owner and dates without storing confidential personnel information in a broadly accessible worksheet.

Build three milestones with proof, not wishful outcomes

DAY 30 | Understand and practice. What can the new employee show you with appropriate supervision? Examples: locate the current SOP, enter a normal test booking, explain the safety reporting route, and identify a request they must escalate. Evidence: observed practice, a sample record and answers to a realistic exception.

DAY 60 | Own routine cases. Which tasks are safe to transfer once the employee passes a practical check? Examples: confirm common appointments within approved slots, keep the customer and crew records consistent, and send clear handoffs when an item remains open. Evidence: a small sample of real work and an observed exception.

DAY 90 | Work consistently and improve. Can the employee maintain quality across a normal workload and recognize when the agreed rules don’t fit a request? Examples: handle routine cases reliably, escalate nonstandard terms before promising them, and flag a recurring booking issue for the manager. Evidence: documented work records and a manager conversation about next development goals.

Avoid treating these dates as automatic deadlines for independence. Someone working two shifts a week has fewer opportunities to practice than a full-time colleague. A role with required licensing, safety training or supervised practice cannot be accelerated to fit a generic template.

A filled 30-60-90 plan for a small service business

Consider a fictional appliance-repair company hiring Taylor as its first dedicated customer-service coordinator. Naomi, the owner, currently answers scheduling calls herself. Morgan, a more experienced coordinator, is the day-to-day buddy. Taylor’s authority is limited to approved appointment slots and documented booking rules.

DAY 30 | Goal: understand booking rules and manage simple requests under supervision. Practice: complete four test bookings covering an ordinary appointment, a reschedule, an incomplete customer-access note and an unavailable slot. Evidence: Morgan observes the test; Naomi compares the records with the agreed rules. Decision: if Taylor confirms an unavailable slot, keep that exception under supervision and schedule a retest.

DAY 60 | Goal: handle routine bookings and approved changes independently. Practice: make several real appointment confirmations and document each relevant customer promise. Evidence: Naomi reviews five recent routine job records for correct technician qualification, time and follow-up. Exception: pricing or changes to the agreed scope still go to Naomi, regardless of routine-case accuracy.

DAY 90 | Goal: maintain reliable scheduling through a typical week’s workload and transfer unfinished items without dropping commitments. Practice: prepare a handoff for a customer callback still waiting on a technician and get explicit receiver acknowledgment. Evidence: the agreed next action, responsible person and due time exist in the live job record. Decision: Naomi and Taylor identify the next skill to develop, such as handling more complex appointment constraints.

These are invented examples showing how a manager could assess work. They do not represent actual employee performance or a tested training program. A real manager would fill in dates and results after observing the employee.

Give the employee a fair chance to meet each milestone

A plan only works when the business supplies the tools and opportunities it assumes. Block time with a trainer. Make sure the employee can open the system and see a current instruction. If a test requires a booking exception the employee never encounters, create a safe simulated case. Agree on who will be available when questions arise.

At the start of each period, discuss expectations with the employee rather than presenting a finished scorecard. Ask what they already know, where they need help, and how their actual shifts affect training opportunities. Document reasonable adjustments through the appropriate process where applicable. A longer learning curve can reflect a training-design problem or missing permissions rather than employee performance.

Give feedback during the period, not only on day 30 or 60. If the booking form hides a key qualification, fix that interface or instruction. If the employee repeatedly offers appointments outside approved slots, revisit the decision rule and observe another practice case. Keep a record of what was changed and what the next check will be.

Help the new hire learn who does what

Competence also depends on knowing where a problem belongs. During the first 30 days, introduce the employee to the people who control their everyday work: the teammate who handles job handoffs, the person who resolves customer disputes, and whoever approves an exception. Keep introductions relevant to the role rather than booking meetings with everyone in the company.

In Taylor’s example, Morgan demonstrates scheduling; the field supervisor explains technician qualifications; Naomi confirms which promises require owner approval. At the 30-day check-in, Taylor should identify the right person for three ordinary problems and show a correctly handed-off unresolved request. By day 60, the manager can check the same judgment in actual work.

Use short check-ins to keep the plan alive

At the end of the first week, ask the buddy for one task the new hire can do with supervision and one exception that still needs work. The manager then agrees on the practice schedule.

At the 30-day conversation, look at actual examples rather than an impression of confidence. Confirm the tasks that passed, the ones still supervised and the next training opportunity. Record the owner and date for unresolved items.

At day 60, review whether the employee’s routine work is accurate across real cases and whether exceptions reach the right decision-maker. Expand responsibility only when the evidence supports it. If the job or staffing model changed, revise the goals with the employee.

At day 90, examine the employee’s contribution, current capacity, and what they should learn next. Any probation, employment-status or formal performance decision must follow the employer’s actual policies and applicable law. This article does not assign legal meaning to a 90-day milestone.

Mistakes that make 30-60-90 plans unhelpful

Too many goals: A small role may have three meaningful outcomes for its first month. Ten vaguely worded targets make the discussion harder and don’t improve learning.

Milestones without proof: “Comfortable with customers” cannot be checked consistently. Define a normal task, a difficult case and an observable result.

Manager-only expectations: If the employee doesn’t see the authority boundary, they may reasonably assume a price exception is theirs to approve. State the limit in the job aid and practice it.

Plans that ignore shifts: A restaurant employee with irregular shifts may need a manager check after a certain number of service periods rather than on an arbitrary calendar day. Record both the proposed date and the actual experience available.

No next step after a failed check: If someone isn’t ready to work independently on a case, retain supervision and schedule a specific retest. Don’t write “needs more training” without an assigned owner or practice task.

Copy the plan and adapt it for your next hire

The free Word template has an editable blank page for the employee, role, manager, start date, milestones, evidence and support needs. The document also includes Taylor’s fictional role with specific checks at days 30, 60 and 90. Download the editable Word plan.

Start with a role description and three attainable outcomes. Put real check-in dates on the calendar. For each milestone, name an actual record or demonstration that will tell you what has been learned. When the evidence is missing, leave the milestone open and agree on the next practice opportunity.