How to Issue Tools to a New Tech

Why this matters

The first day sets what the tech believes about tools for the rest of his time with you. Hand him a bag somebody else left behind and you have told him that tools are whatever is lying around and nobody is counting. Walk him through a defined kit, verify the instruments in front of him, and say out loud what comes back at the end, and you have set an expectation that never needs to be enforced later. The issue conversation is also the only comfortable time to say what happens at separation, because nobody is leaving yet and nobody is offended.

Step 1: Define the kit by role, before the person shows up

A kit built on the day the tech arrives is a kit built out of whatever is on the shelf. Write it once per role and reuse it.

The sizing rule is the same one that decides truck stock: a tool belongs in the issued kit when the role needs it on 8 or more jobs per quarter. Below that it lives in the shared pool and gets staged for the job. Issue to the work the tech will actually do in his first 90 days, not the work you hope he grows into, because an unused tool in a new kit is a tool that will be missing at the first audit and nobody will remember whether he ever had it.

Write the kit as a numbered list with quantities. "Assorted drivers" is not a kit line and cannot be audited.

Step 2: Split the kit into three tiers and name them out loud

Ambiguity here is the source of every later argument.

  • Issued and tracked. Shop property, on his sheet, comes back. This is the kit.
  • Shared pool. Shop property, not on his sheet, checked out per job and returned to the shop. He needs to know this category exists on day one or he will assume anything he can find is his.
  • Personal. His own. The shop does not maintain it, does not replace it, and does not track it, and it goes home with him whenever he goes home.

Say which category each item is in as you hand it over. A tech who does not know whether the meter is his or the shop's will treat it as neither, and it will end up in a truck door pocket for two years.

Step 3: Verify every safety and measurement item before it leaves your hand

This is the step shops skip because the tools are coming out of shop stock and are assumed good. Shop stock is exactly where a bad instrument hides, because nobody has been personally responsible for it.

The instrument used to prove a circuit is dead. Verify it on a known live source in front of the tech, then have him do it himself. On his first live job he verifies on a known live source, tests the conductor, and verifies on the known live source again, which is the live-dead-live sequence NFPA 70E requires before a conductor is treated as safe to work on. Confirm the instrument's measurement category rating covers the circuits he will actually test, because a lower-rated instrument on a higher-energy circuit can fail as an arc rather than as a wrong reading. An instrument that fails either verification does not get issued, it gets tagged and pulled.

Ladders. Inspect the one you are about to issue: rails, rungs, feet, spreaders, rivets, labels. If it has a structural or other defect, tag it "Dangerous: Do Not Use" and remove it from service under 29 CFR 1910.23(b) (general industry; the construction equivalent is 1926.1053(b)(16), so use whichever Part governs the work) rather than issuing it with a note to be careful. Issuing a marginal ladder to the least experienced person on the crew is the specific version of this that gets somebody hurt.

Tight-fitting respirators. If the role requires one, the tech must be fit tested before he first wears it and at least annually after that under 29 CFR 1910.134(f)(2), and the fit test has to be on the same make, model, style, and size he will actually use. Do not issue a respirator on the assumption that a fit test will happen later that week.

Cordless and corded tools. Cords, plugs, ground pins, guards, and triggers get looked at. A guard that does not return under spring pressure is not issued.

Step 4: Issue against a record he can read and sign

Paper or a job-management record, it does not matter. What matters is that it exists, it is specific, and he signed it. Five fields is enough:

Field Why it is there
Item and quantity An auditable line, not a category
Identifier or marking So a found tool can be returned to the right sheet
Condition at issue Prevents the "it was already like that" argument in both directions
Date issued Anchors the replacement cycle and the audit
Signature Turns a handover into an acknowledgment

Condition at issue is the field shops leave off and the one that saves you later. A tool issued as used and marked as used cannot be charged to him as damage, and a tool issued as new and returned cracked has a documented change. Mark it honestly at issue and the whole category of arguments disappears.

Step 5: State the return rule on day one

Say it in the same breath as the handover, in plain terms: issued tools are shop property and come back at separation, and here is the list you are signing that says what they are.

Then say what the shop does not do, because that is the part that builds trust. Most shops of three to fifteen land here and it is a defensible position: damage during normal work is a shop cost and gets coached, not billed. What gets recovered is tools not returned, and that is a separate conversation with its own rules.

Do not promise a payroll deduction for unreturned tools as a deterrent unless you have checked whether you can actually do it. Under the FLSA, a deduction cannot cut an employee's pay below the federal minimum wage for the hours worked in that workweek or reduce overtime premium pay, because wages must be paid free and clear under 29 CFR 531.35, and many states go further by prohibiting the deduction outright or requiring prior written authorization. A threat you cannot execute is worse than no threat, because the first tech who calls it teaches the rest that the tool sheet is theater.

Step 6: Walk the kit, do not hand over a bag

Twenty minutes, item by item, with the tech holding each one. Three things happen in that twenty minutes that will not happen any other way.

  • You find out what he does not know. A tech who has never used a particular instrument will say so while it is in his hand and he has an excuse to ask. He will not say so in front of a customer three weeks later.
  • He learns where things live. Which pouch, which case, which side of the truck. This is what makes the kit stay organized, because an organized kit is one that started organized.
  • You cover the care that is specific to these items. Not a lecture on tool care in general, which belongs in its own conversation and is better delivered by the crew than by you. Just the two or three items in this kit that have a real maintenance requirement, said while he is holding them.

Worked example: apprentice versus journeyman kit

The defined kits. The shop's journeyman kit is 34 tracked items. The apprentice kit is a subset: 19 of those 34 items, which is 56 percent of the full kit. The remaining 15 are released as the apprentice is signed off on the tasks that need them.

Why not issue all 34 on day one. Two reasons and both are practical. The 15 held back are the items used on work he is not yet doing, so under the 8-jobs-per-quarter rule they do not belong in his kit at all yet. And every item issued and unused is an item that goes missing without anybody noticing, which shows up at the annual audit as a loss with no story.

How releases work. Each release is a dated line on the same sheet, signed the same way. Across his first 90 days he gets 6 of the 15 released, so he ends the quarter at 25 of the 34 items, which is about 74 percent of the journeyman kit. The sheet now doubles as a training record: what he has been signed off on is visible from what he has been issued.

The cost of the alternative, in hours. Under-issuing is not free. Suppose the apprentice has to borrow a tool three times a week because it was held back too long. Each borrow costs the lender roughly 0.1 hours of interruption and the apprentice roughly 0.2 hours of finding and waiting, so about 0.3 crew hours per borrow. Three a week is 0.9 crew hours a week, and across a 48 week working year that is about 43 crew hours. That is the number that should decide whether an item is held back, not a feeling about whether he is ready to own it. Hold back tools he cannot yet use safely or correctly. Do not hold back tools he simply has not needed yet this month.

Run the sizing rule against the case. One of the 15 held-back items turns out to be needed on 11 jobs in his first quarter, which is above the 8 jobs per quarter gate. Under the rule it should have been in the initial kit, and the 90 day review is where that gets corrected in the written kit definition so the next apprentice starts with 20 items instead of 19. The kit definition is supposed to move. A kit list that has not changed in three years is a list nobody is checking against reality.

Step 7: Check at 30 days and again at 90

Ten minutes each, and they answer different questions.

At 30 days, check completeness and organization. Is everything on the sheet still present, and does the kit look like a kit or like a pile. Losses in the first month are almost always storage problems, not people problems, and they are trivial to fix at 30 days and entrenched at 300.

At 90 days, check fit. What has he not touched, and what has he had to borrow. The first list comes out of the kit. The second list goes into it, and into the written kit definition for the role so the next hire gets a better starting kit than he did.

How to verify you got this right

Pick a tech hired within the last year and ask him three questions cold: which of the tools you use are shop property, what happens to them if you leave, and what do you do if one of them is damaged. If he can answer all three without hedging, the issue process worked. If he cannot answer the first one, the three-tier split in step 2 was never said out loud, and everything downstream, including the audit and the recovery at separation, is going to be an argument.

Then pull his signed sheet and count against his actual kit. A new tech's sheet should reconcile exactly. If it does not reconcile at 90 days, it will not reconcile at three years, and the annual audit will inherit the discrepancy with no way to date it.

References

  • 29 CFR 1910.23, OSHA ladder requirements including defective-ladder tagging and removal from service
  • 29 CFR 1910.134(f), OSHA respiratory protection fit testing requirements before first use and at least annually
  • 29 CFR 531.35, FLSA free and clear requirement governing deductions from wages
  • NFPA 70E, Standard for Electrical Safety in the Workplace, verification of test instruments before and after absence-of-voltage testing
  • See related: How to Standardize Tools Across a Crew, The Annual Tool Audit SOP, How to Recover Tools When Someone Leaves