The 30-60-90 Day Onboarding Plan for a New Technician
Why this matters
Most shops that "have an onboarding plan" actually have a pile of activities with no gates attached: shadow this week, solo that week, review sometime. Activities without gates let a struggling hire drift for months before anyone admits it is not working, and they let a strong hire sit underused because nobody checked whether they had already outgrown the plan. A 30-60-90 structure fixes this by attaching a pass or fail question to each milestone. This card is the checkpoint spine: what must be demonstrably true at each gate before you move the new hire forward, not the day-by-day activity list itself. See related: New Hire Week One: Set Up to Succeed and Ride-Along Training for the activities that fill the time between gates.
The three gates at a glance
| Gate | Core question | What "pass" looks like |
|---|---|---|
| Day 30 | Are the basics automatic? | Comfortable with dispatch/billing systems, safety reflexes present, customer conduct solid, no red flags |
| Day 60 | Are they producing at an acceptable rate? | Handling most routine work with light supervision, callback rate close to the crew norm, revenue or output trending toward expectation |
| Day 90 | Are they a full, standing member of the crew? | Working the bulk of standard jobs solo, escalating the right things, ready for a formal status and pay conversation |
Treat each gate as a real decision point, not a rubber stamp. A hire who is not clearly passing a gate does not automatically fail either; the gate's job is to force an honest look and a specific plan, which is the whole value of having gates at all.
Day 30: are the basics automatic
By day 30 the question is not "are they good yet," it is "have the fundamentals stopped requiring conscious effort." A new hire who is still hunting for buttons in the dispatch system or still needs reminding about PPE at day 30 is not behind on skill, they are behind on repetition, and that is a coaching problem you catch now instead of at day 90.
Check specifically:
- Can they operate the job system, log time, and read a work order without help.
- Do safety habits happen without a reminder: PPE, lockout steps where they apply, vehicle safety.
- Is customer-facing conduct solid: greeting, respecting the space, basic communication.
- Has anything already surfaced that worries you: attendance, attitude, safety shortcuts. Small red flags at day 30 are cheap to address and expensive to ignore.
If the basics are not automatic yet, do not push more responsibility onto a shaky foundation. Extend the supervised period and name exactly which basic is the gap.
Day 60: are they producing at an acceptable rate
Day 60 shifts the question from "can they do it" to "are they doing it fast enough and well enough." This is the productivity gate, and it is where a lot of shops go soft because the person is likeable and trying hard. Likeable and trying is not the same as producing.
Check specifically:
- Output or revenue trend: are they closing in on what a competent tech at this stage should be producing, even if not yet at full-tenure levels.
- Callback rate compared to the crew average, not compared to zero. Some early callbacks are normal; a rate that is not narrowing is the signal.
- How much oversight they still need on routine work versus how much they needed at day 30. The trend line matters more than the absolute number.
- Customer feedback, if you collect it, on this specific hire's jobs.
A hire who is behind on the trend but improving fast is a different case than one who has plateaued below the bar. Plateaued is the one that needs a direct conversation now, not at day 90 when the cost of a wrong hire has compounded for two more months.
Day 90: are they a full, standing member of the crew
Day 90 is the formal decision point. By now you are not asking whether they can do the job, you are confirming it and deciding what comes next: full status, a pay adjustment if your structure includes one, and the start of a real development conversation about where they go from here.
Check specifically:
- Are they running the bulk of standard jobs solo, with escalation reserved for the genuinely complex or unusual.
- Do they know what to escalate and when, rather than either escalating everything or nothing.
- Is attendance, attitude, and safety conduct consistent, not just present on a good week.
- What is the next stretch goal: a harder skill, a certification, a step toward mentoring someone newer themselves.
If day 90 arrives and the honest answer is still "not quite," that is not automatically a failed hire. It means you extend the plan with a specific, written list of what remains and a new date, rather than letting an ambiguous "still ramping up" drag on indefinitely with no checkpoint at all.
Where this plan can bend
The 30-60-90 rhythm is a default, not a law. A technically simple role can compress the gates; a highly regulated or highly technical trade may need to stretch day 90 into day 120 for licensing or certification reasons. What should not bend is the discipline of the gates themselves: a specific question asked and answered on a specific date, in writing, every time. The shops that skip the gates are the ones surprised, six months in, that a hire everyone assumed was "coming along" never actually got there.
References
- Society for Human Resource Management (SHRM), 30-60-90 day onboarding framework
- U.S. Department of Labor, registered apprenticeship progression standards
- See related: New Hire Week One: Set Up to Succeed, The First Solo Job Go/No-Go Checklist, Early Feedback Cadence That Catches Problems Before Day 90