Onboarding a Technician in the First Ninety Days

A technician who leaves in the first year is the most expensive kind of departure: recruitment cost, months of reduced productivity, senior technician time, and nothing produced.

Early exits are also the most preventable, because the causes are consistent and they are visible within weeks.

What people leave over in the first months

The job was not what was described. More routine work, less variety, different equipment, a different pay reality once the flat-rate arithmetic became clear. This is a recruitment failure that presents as a retention failure.

No clarity about expectations. What good looks like, how long they have to get there, what happens if they are slower at first.

Nobody assigned to them. A new technician who has to work out who to ask is a new technician not asking.

Tooling. In markets where technicians supply their own, the early investment is substantial and it is a real barrier for someone who has just started.

Being measured immediately on numbers they cannot yet meet, particularly productivity, which depends on the workshop rather than on them. See the three ratios.

And the first mistake. How a workshop responds to a new technician's first comeback determines a great deal about whether they stay.

The first week

Somebody meets them. This sounds obvious and it is the most common failure — a start date nobody was told about produces a first morning standing in a workshop.

Safety, access, systems, tools. Practical, and it should take a morning rather than a week.

Introduced to everyone, by name and by what they do.

A named buddy — not necessarily the mentor, someone to ask the small questions.

Their first job on day one or two, something achievable. A new technician who spends three days observing has learned nothing and has started to doubt the decision.

And a conversation about the pay structure, in detail, with the arithmetic. If flat rate, what that means in practice while they are learning. Surprises here cause departures.

The first month

A named mentor, with time allocated and paid. Under flat-rate pay, mentoring costs the mentor income and everything depends on this being addressed. See training the trainer.

Work matched to capability, and deliberately varied. A new technician given only the routine work for a month is being sorted into it.

A weekly conversation, brief, with someone who is not the mentor.

Explicit expectations about ramp-up. "We expect efficiency below the workshop average for the first three months, and that is normal" removes a large amount of anxiety and it is rarely said.

Do not report their numbers alongside everyone else's in the first weeks. They will be lower, everyone can see it, and it teaches nothing.

Days thirty to ninety

Increasing independence, deliberately managed rather than emergent.

A progression plan, written, with what they will be able to do at ninety days and at six months. See a career ladder for a workshop.

Training scheduled, not promised. Product induction, systems, and whatever certification the role requires.

First formal review at ninety days, with the criteria known in advance.

And a conversation about what is not working, initiated by you. A new technician will not raise a problem in month two.

Handling the first mistake

It will happen, and the response is disproportionately formative.

Treat it as a case, not as a failure. What happened, what would have caught it, what to do next time. The same approach as any comeback review. See comeback rate.

Do not make it public.

And check whether the work was appropriate. A new technician given a job beyond them made a supervision error rather than a technical one.

What to measure

Time to first independent job.

Time to competence on a defined set of operations, which is the number that determines whether hiring feels affordable and which almost nobody tracks.

Efficiency trajectory, as a trend rather than as a level.

Ninety-day and twelve-month retention, separately. These have different causes.

And ask them at ninety days what would have made the first month better. They still remember, and by month six they will have normalised it.

For a manufacturer's training function

Product induction available immediately, not scheduled for the next cohort. A technician who joins in March and receives induction in September has spent six months guessing.

Short, accessible, on the device they have. See mobile learning.

And design for reducing time to competence, because that is the number that makes hiring affordable for the dealer and it is the part of the problem the training function actually controls. See the technician shortage.

The short version

Early departures are onboarding failures, and the causes are visible within weeks.

Somebody meets them, somebody is assigned to them, and they do real work in the first two days.

Say the ramp-up expectation out loud — that efficiency will be below average for months, and that this is normal.

Do not measure them against the workshop in the first weeks, particularly on productivity.

And ask at ninety days what would have made the first month better, while they still remember.

For official guidance relevant to worker orientation and safe systems of work, see OSHA recommended safety-management practices.