How to Support a Tech Working Toward Their Own Licence

Why this matters

A tech who spends four years at your shop and cannot get licensed at the end of it was failed by your paperwork, not by their ability. The hours were worked. They were logged as "service", or logged to payroll categories that mean nothing to a licensing board, or attested by a supervisor who has since left with no record of what they supervised. The work happened and the evidence does not exist.

Your part in this is administrative, and it is three things: make the hours provable, make the exposure broad enough to satisfy the form, and make the schedule survivable. The tech owns the studying and the exam. See related: Getting Your License: The Path.

Step 1: Read the verification form before the first hour is logged

Get the actual document the authority will require at the end, not a summary of it, and read it before you design anything.

You are looking for four things. How hours are categorised, because almost every scheme wants a breakdown by type of work rather than a single total. Who may verify, which is usually a licence-holder with a specified relationship to the work. Whether hours are capped per year or per period, which changes how fast the clock can possibly run regardless of how hard anyone works. And what supervision means in that scheme, because "under the supervision of" has a specific definition and it is rarely "employed by the same company".

Requirements here are genuinely jurisdiction-specific: the number of hours, the categories, the ratios of unlicensed to licensed people permitted on a job, and whether classroom time substitutes for any of it all vary. Your authority's published rules are the only source of truth. Do not build a logging system from what another shop in another state does. See related: Apprentice Ratios + State Licensing.

Step 2: Make the log match the form, not your payroll

This is the single highest-value step and it costs an hour of setup.

Payroll categorises work by how it is billed. Licensing boards categorise it by what was learned. Those two taxonomies rarely overlap, and a shop that logs to payroll categories has to reconstruct the board's categories at the end from job descriptions, which is weeks of work producing an estimate rather than a record.

Log to the board's categories from day one, in the board's units, with the date, the job reference, the hours in each category, and the supervising licence-holder named. Signed off monthly rather than annually, because a month of recollection is recoverable and a year of it is not.

Give the tech a copy every month. Their hours are their property and their career; a log that lives only in your system is one hard drive failure away from four years being gone.

Step 3: Assign for breadth, not just throughput

Here is the real tension in the whole exercise. A tech who is good at one category gets sent to that category, because it is efficient and the customer gets a better outcome. Over two years that produces someone with excellent hours in one column and almost nothing in three others, which is a form problem and, more importantly, a competence problem the form is designed to catch.

Set an internal category floor as a proxy for whatever the board actually requires, and review it quarterly. A reasonable starting point, to tune: no category below 15% of the tech's cumulative logged hours, measured per tech per category against the running total, and evaluated only once the tech has at least 2 quarters of logged history so early noise does not trigger it. When a category sits under the floor, the correction is a standing routing rule sending every job of that category to that tech, released after the category has held above the floor on 2 consecutive quarterly reviews. Not a one-quarter push, for the reason the worked example below makes obvious.

Step 4: Protect the verifying licence-holder

The attestation is a personal legal statement by a named individual about work they actually supervised. It is not a company formality and it is not something an owner can sign on behalf of someone who did the supervising.

Two consequences. The verifier has to genuinely have supervised, in the sense the scheme defines, which means the assignment pattern has to be real and not reconstructed. And the relationship needs continuity planning: if your verifying licence-holder leaves, get their attestation for the hours to date before they go, signed and dated. Chasing a former employee for a signature two years later is a poor position and it is entirely avoidable with a five-minute exit-checklist item.

Supervision is also a safety obligation, not only a paperwork one, and the specifics matter at task level. An apprentice does not open an energized enclosure alone; the licence-holder verifies the circuit is dead with a tester proven on a known live source before and after the reading, and applies their own lock and tag to the energy-isolating device before anyone's hands go in. Where 29 CFR 1910.147 applies, that lock and tag by the person doing the servicing is the operative requirement, not an optional extra. Construction work has its own home in 29 CFR Part 1926, so establish which Part a given job falls under before quoting a requirement to a crew.

Step 5: Schedule the classroom load with everything else

Whatever classroom or related-instruction component the scheme requires competes with the same weeks as everyone else's continuing education and your peak season. Put it in the same annual budget rather than treating it as the tech's private problem, because it is your dispatch board it comes out of. See related: How to Budget Time for the Credential Year.

One scheduling rule specific to apprenticeship: instruction that is a prerequisite for an hours category should be scheduled early in the year, not late, because hours logged before the prerequisite instruction sometimes do not count in that category. Confirm whether that applies in your scheme before ordering the sequence.

Step 6: Settle who pays, in writing, before the first course

Whatever you decide, decide it before rather than after, and write it down. The common arrangements are the shop paying fees and the tech giving the time, the shop paying both, or a split. Any of them works. What does not work is leaving it unstated, because the ambiguity gets resolved at the worst moment, usually when someone resigns.

If you use a repayment agreement tied to the tech leaving within a period, know that the enforceability of those varies by jurisdiction and that a badly drafted one is worth less than no agreement while costing you goodwill. Keep the term short, make the amount decline over the term, and have it reviewed locally.

Worked example: the breadth audit that showed the correction is slow

A tech had 18 months of logged hours, 2,600 in total. The quarterly review broke them out by category:

Running the rule. The tech has 6 quarters of history, so the 2-quarter minimum is met and the rule is live. Two of the four categories sit under the 15% floor: rough-in at 9% and controls at 5%. Standing routing rule triggers for both.

What the shop expected. A hard push for two quarters and the problem is fixed.

What the arithmetic said. Over the next 6 months the tech would log roughly 900 more hours. Suppose the shop routed aggressively and 200 of those 900 were controls work, which is a lot of deliberate scheduling against customer demand. Controls then stands at 130 plus 200, so 330 hours, against a new cumulative total of 2,600 plus 900, so 3,500. That is 9.4%.

Six months of aggressive redirection moved controls from 5% to about 9%, and it is still under the 15% floor. The denominator grew alongside the numerator, which is exactly why category share moves slowly on a cumulative total and why a one-quarter push is not a correction, it is a gesture.

What that changes. Three things follow, and they are the actual payload of the exercise.

Start the breadth review early. At 6 months of logged hours the total is small enough that redirection moves the share fast. At 3 years it barely moves at all, which is why breadth problems discovered late are usually not fixable within the remaining time.

Set the routing rule as standing, not as a sprint. The rule above releases after 2 consecutive quarters above the floor precisely because a single quarter above the floor on a growing denominator is likely to be noise.

And check whether your authority scores on cumulative share at all. Some ask for a minimum in each category, some ask for a total with categories reported for information only. If it is the latter, the floor is your internal competence standard rather than a compliance gate, and it is still worth keeping, just with different consequences for missing it.

The honest caveat on the middle two categories. Installation at 24% is above the floor and the shop counted it as fine. It is worth watching anyway, because 624 of those hours came almost entirely from one seasonal stretch. A category that is above the floor because of a single burst is more fragile than the percentage suggests, and it will drift down as the denominator grows unless work keeps flowing to it. Above the floor is a pass under the rule as written, and this one is a pass with a caution.

Step 7: Plan for both endings

They leave. The hours go with them. Give them the signed log and be gracious about it, because the shop that hands over a clean record is the shop that gets recommended and sometimes gets them back. Fighting over a log you are obligated to provide anyway buys nothing.

They pass. Something structural changes in your shop the day they do, and it is worth planning for rather than discovering. You gain a second person who can supervise, which changes your crew composition options. Your qualifying-individual bench gets deeper, which reduces the single-point risk on your company licence. And their expectations change immediately: a newly licensed tech who stays on the same pay and the same work for another year usually does not stay a second one.

How to verify you got this right

Two checks, once a quarter.

Take the tech's log and try to fill in the authority's actual verification form from it, without asking anyone anything. Any field you cannot fill is a logging defect, and finding it in quarter two costs nothing while finding it in year four costs the hours.

Then ask the tech to name their weakest category. If their answer and your table disagree, one of the two is wrong and it is worth knowing which before the board finds out.

References

• Your state or local licensing authority, for hour requirements, category definitions, supervision rules, annual caps and the verification form itself
• U.S. Department of Labor, Office of Apprenticeship, for registered apprenticeship program structure where one applies
• Occupational Safety and Health Administration, 29 CFR 1910.147 (control of hazardous energy, general industry; construction work falls under 29 CFR Part 1926)
• See related: Getting Your License: The Path; Apprentice Ratios + State Licensing; How to Budget Time for the Credential Year