The onboarding program at most shops is a person. The new hire shadows the senior tech for a week, then calls him, then texts him, for the first ninety days. It works, mostly. It also means your best producer is running a one-student school between jobs, and everything he knows rides around in his truck.
What the shadow week actually costs
The visible cost is the week itself: two people on every call, one of them billing nothing, the other billing slower because he is narrating. The larger cost comes after, and it is invisible because it arrives ninety seconds at a time. Where is the torque spec for that lug. Which supplier do we use for igniters. Does the company card cover lunch on an out-of-town job. What do I do with a recovered refrigerant cylinder. Each interruption is short; the cost is the senior dropping what he was doing, every time, all season.
And the arrangement does not scale or pause gracefully. Hire two people in the same quarter and the senior does little else. Send him on vacation and onboarding simply stops for a week, because the curriculum is him.
An assistant grounded in your procedures, not the internet
The alternative is an assistant that answers from the company's own documents and nothing else: the SOPs, the safety policies, the truck-stock list, the purchase-order threshold, the warranty-callback procedure, the vehicle policy. A question comes in, the relevant sections are retrieved, and the answer is composed from those sections.
The restriction to your documents is the entire point, because general trade knowledge is precisely wrong about your rules. The internet has plenty to say about refrigerant recovery. Your SOP names the recovery machine in your shop, the tag your company puts on the cylinder, and the vendor who takes it. When the new hire asks what to do with recovered refrigerant, the useful answer is yours — the machine, the tag, the vendor — not a correct-in-general paragraph that leaves him standing in the shop holding a cylinder.
Every answer says where it lives
Each answer carries its source: "Purchases over $200 need a PO first — Purchasing SOP, section 3." That citation does two jobs. The immediate one is verification; the hire can open the section and confirm. The slower one is more valuable: after a few dozen answers, the hire has absorbed the map — which manual governs what, where the safety policies end and the operations procedures begin. That map is half of what shadowing was actually teaching. A senior gives you the answer. The citation gives you the answer and the address, and the address is what makes a hire independent by month two instead of month six.
The rule that keeps this honest: no source, no answer. When a question has no written procedure behind it, the assistant says so plainly and flags it, rather than improvising a policy. An invented answer about, say, ladder-inspection intervals is worse than none — the hire cannot tell it from a real one, and it carries the same confident tone.
The question log is a documentation to-do list
Every question gets logged, and the unanswered ones are the interesting ones. When three consecutive hires ask how overtime gets approved and the assistant comes up empty three times, you have learned something specific: that procedure either does not exist or exists without saying the one thing people need from it.
This converts "we should really document more" — a guilt that never becomes a task — into a ranked list. Sort the unanswered questions by how often they were asked, take the top ten, and that is the documentation plan for the quarter. It is short, it is ordered by demand rather than by anyone's guess, and each item comes pre-validated: a real person already needed it. Most companies write SOPs top-down and wonder why nobody reads them. This is the bottom-up version — you write the answers to the questions that were actually asked.
A day-one checklist built from your policies, not a template
Onboarding checklists usually come from the internet and say things like "set up email." A checklist generated from your actual documents says what your documents actually require: the uniform policy's rule about what must be issued before the first ride-along, the vehicle policy's insurance form, the safety orientation the handbook says gets signed before anyone touches a lift.
Because the checklist is derived from the documents rather than copied from a template, it moves when they move. Change the vehicle policy in March and the day-one checklist changes with it. The failure mode of the laminated sheet by the front desk is drift — the sheet says one thing, the current policy says another, and the new hire learns on day one that the paperwork here cannot be trusted. A derived checklist cannot drift, because it has no life of its own to drift into.
What this does not replace
Hands-on skill. Nobody learns to braze a joint or diagnose a short-cycling compressor from an answer box. Ride-alongs stay, and so does the scrutiny of a senior watching a hire's hands.
Judgment and culture. How this company treats a customer whose complaint is half their own fault is not in any SOP, and the conversations where that gets passed on are the ones worth protecting. The goal is fewer interruptions for lookups — not fewer conversations.
And there is a hard prerequisite: written procedures have to exist in some form. If nothing is written down, the first project is capture, not software — often literally recording the senior explaining a procedure on a slow afternoon and turning the transcript into a draft. An assistant sitting on an empty filing cabinet answers nothing, correctly.
Where to start
Ask whoever you hired most recently to list every question they asked in their first two weeks. Or ask the senior which questions he answers over and over — he knows them by heart and resents most of them. Twenty minutes of listing, and the result does double duty: it measures how ready your documentation actually is, and it becomes the test you run any assistant against before you trust it with the next hire.