How to Onboard a Tech Who Holds Credentials From Elsewhere

Why this matters

A tech who worked ten years two states over walks in holding a folder of certificates, and the natural instinct is to treat that folder as a green light. It is not. Some of what is in there follows the person anywhere, some of it belonged to their last employer and stopped being valid the day they left, and some of it is worth nothing in your jurisdiction until an authority here says so. Get that sorting wrong and you either park a capable tech on ride-alongs for six weeks you did not need to lose, or you send them out on work they are not covered to perform, which is the version that costs you a licence and not just a payroll week.

The instrument here is an assignment envelope that starts narrow, widens on documented evidence, and carries a date every time it widens.

Step 1: Sort every credential into one of four portability classes

Do this on paper before you promise the hire anything about their schedule. Every item in that folder falls into one of four classes, and the class determines what you do with it, not how impressive the certificate looks.

Federally issued and portable. These attach to the person, travel across state lines, and in some cases never expire. Technician certification for refrigerant handling under 40 CFR Part 82 Subpart F is the cleanest example: anyone who maintains, services, repairs or disposes of appliances containing a regulated refrigerant must hold the applicable certification type, it is issued to the individual, and it does not carry an expiration date. Verify the card is genuine, record the type, and move on.

Vendor or manufacturer certifications. These travel with the person too, but many lapse quietly. The common pattern is an annual affirmation, a purchase requirement, or a network membership tied to the previous employer's account rather than to the tech. Treat these as unverified until the issuing program confirms current standing for that individual.

Jurisdiction-bound licences and registrations. A state or local licence to perform trade work does not travel. Reciprocity is the only bridge, it is partial almost everywhere, and it is administered by the authority here, not by the one that issued the original. See related: How Reciprocity Usually Works and Where It Does Not.

Employer-attached items. These look like credentials and are not. They are your compliance records, they were the last employer's compliance records, and they do not transfer. The respirator program is the sharpest example: where your employees use respirators, you must ensure a medical evaluation before fit testing and use under 29 CFR 1910.134(e), and a fit test before initial use and at least annually thereafter under 1910.134(f)(2). A fit test card from another shop is not your record. Same shape for a driver qualification file, which under 49 CFR 391.51 is maintained by the motor carrier for drivers operating vehicles subject to FMCSA, and for enrollment in a drug and alcohol testing program.

Step 2: Set the day-one assignment envelope before you set anything else

The envelope is a written list of what this person may be assigned starting Monday, given only what you have verified so far. Write it before the first shift, share it with dispatch, and put it where the schedule lives rather than in a folder nobody opens.

The default envelope for a hire whose jurisdiction-bound licence has not cleared is: work performed under the direct supervision of a licensed holder, no independent permit-drawing work, no solo dispatch on anything that requires the licence to be pulled. That is not a comment on their skill. It is a statement about whose licence the work runs under while the paperwork moves.

Two things make this envelope work rather than annoy everyone. First, it is specific by job type, not by vague category, so dispatch can apply it without calling you. Second, it names the person whose licence covers the supervised work, because "under supervision" with nobody named is how a shop ends up with nobody supervising.

Step 3: File the jurisdiction application on day one, not after orientation

Authority processing time is the longest pole in this tent and it is entirely outside your control, so it starts first. Check the authority's published turnaround before you set expectations with the hire, and check whether they issue a temporary or provisional permit while an application is pending, because that permit is what widens the envelope early.

What the application needs is usually a verification of licensure sent authority to authority, not a photocopy from the applicant, plus proof of experience hours or an exam. The verification request is the item that quietly adds weeks, because it depends on a second agency's queue. File it the same day.

Step 4: Redo the employer-attached items regardless of what the last shop did

This is where good shops lose time arguing and bad shops lose coverage. The rule is simple: if the obligation runs to you as the employer, you generate the record, and the previous employer's paperwork is at best useful background.

Redo the medical evaluation and fit test before the tech uses a respirator on your work, per 29 CFR 1910.134(e) and (f)(2). Build the driver qualification file if they will drive a vehicle subject to FMCSA, and confirm the medical examiner's certificate is current, since 49 CFR 391.45 requires a physical examination at least every 24 months for drivers subject to the rule and a certificate expiring next month is not a certificate you can rely on. Enroll them in your testing program under your program's rules.

The competency question - can this person actually do the work at the standard we hold - is a separate track that runs in parallel. It is not a credential question and it does not belong in this envelope. See related: The Skills Gap Audit SOP.

Step 5: Widen the envelope on evidence, and log the date it widened

Each time a piece of evidence lands, you make one change to the envelope and you write the date next to it. Evidence means a verification returned by the issuing authority, a permit number, or your own completed record. It does not mean a phone call, a screenshot, or the tech saying it came through.

The log matters more than it looks. Six months later, when someone asks what work this tech was doing in week three, you have a dated line instead of a memory. That is also the artifact that shows an auditor the gap was managed rather than ignored.

Worked example: one hire, a 30-day clock, three envelope changes

A four-truck shop hires a tech relocating from another state. The folder holds five items: refrigerant handling certification, a manufacturer certification, a state trade licence from the prior jurisdiction, a fit test card dated seven months ago, and a driver medical certificate dated 19 months ago.

Sorting on day zero: item one is federal and portable, item two is vendor, item three is jurisdiction-bound, items four and five are employer-attached. That is 1 portable, 1 vendor, 1 jurisdiction-bound, 2 employer-attached.

Day 1 envelope. Refrigerant work permitted, since that certification is verified from the card and does not expire. All licence-gated work supervised, with a named holder on each ticket. No solo dispatch on permit-drawing work. No respirator use at all until the medical evaluation and fit test are done here, so one job type on the board that week is off the list for them. The reciprocity application and the authority-to-authority verification request both go out on day 1. The medical certificate at 19 months has 5 months left against the 24-month interval, so driving is permitted now and the renewal goes on the register with a date.

Day 9, first change. The fit test and medical evaluation are completed in-house. Respirator work opens. Envelope change logged with the date and the record number. Nothing else moved.

Day 16, second change. The vendor program confirms the manufacturer certification is current in the tech's own name, not the prior employer's account. Warranty-network work opens. Logged.

Day 24, third change. The authority issues a provisional permit while the full reciprocity application sits pending, on the strength of the returned verification. Solo dispatch opens for the job types the permit names, which is most but not all of them. Two job types stay supervised because the permit does not cover them. Logged with the permit number and its own expiry date, which goes straight onto the credential register as a stop-work row.

Count the outcome honestly: of the five items in the folder, 1 was usable on day 1 as it stood, 1 was usable after vendor confirmation, 2 had to be regenerated by us, and 1 never transferred at all and was replaced by a different instrument issued here. At day 30 the tech is dispatching solo on most work and still supervised on two job types. Three envelope changes in 30 days, each with a date and a document behind it.

The thing that would have gone wrong: treating the prior state licence as covering anything, or treating the seven-month-old fit test as satisfying an obligation that is ours. The first exposes the licence the work is running under. The second leaves a hole exactly where an inspector looks first, because the fit test record is one of the easiest things in a shop to ask for.

What changes the answer

The authority issues no provisional instrument. Then there is no day-24 change and the supervised envelope runs until the full licence lands. Plan the hire's first two months around supervised work rather than assuming a bridge exists, and say so at offer stage.

The hire is coming in as your licence holder. Everything inverts. You cannot widen anything on evidence because the whole point is that their credential covers the work, so the reciprocity clock is a go or no-go on the hire itself rather than a schedule constraint. Do not let them start on the assumption it will clear.

The prior credential was in the same jurisdiction, from a different employer. Then only the employer-attached class is in play. That is a one-week onboarding, not a thirty-day one, and treating it like this example wastes a capable tech.

How to verify you got this right

Pick the hire's third week at random and answer three questions from records alone, without asking anyone. What was the envelope that week? What evidence widened it last? Who was the named supervising holder on the licence-gated tickets?

If any of the three needs a phone call, the log is not doing its job. Then check the reverse direction: pull every ticket the hire was assigned in the first 30 days and confirm each job type sat inside the envelope that was in force on that date. A ticket outside the envelope is not a paperwork problem, it is work performed under a credential that did not cover it, and it is worth finding now rather than at a renewal review.

References

• U.S. EPA, 40 CFR Part 82 Subpart F, technician certification for refrigerant handling
• OSHA, 29 CFR 1910.134(e) and (f)(2), respirator medical evaluation and fit testing
• FMCSA, 49 CFR 391.45 and 391.51, driver medical examination interval and driver qualification file
• See related: How Reciprocity Usually Works and Where It Does Not, The New Hire Credential Verification SOP, How to Build a Credential Register for a Small Shop