The Competency Sign-Off SOP

Purpose

To define how this shop decides, records, and stands behind the statement that a person is competent to perform a specific task unsupervised. The sign-off is the point where training becomes a dispatch decision, and it is the only defensible answer to the question "why was this person sent alone on that call."

A sign-off is not a compliment, a milestone gift, or a pay trigger by itself. It is an assertion by a named person, on a named date, that they watched this individual do this task correctly, unaided, the required number of times, and would send them again tomorrow.

Scope

Applies to every field task on the shop's skills matrix, and to every person who performs field work, including experienced hires and long-tenured techs performing a task new to them.

Applies whether the person is an apprentice, a mid-level tech, or a journeyman. Tenure does not exempt anyone from sign-off on a task they have not been signed off on. This clause exists because the most common gap in any shop is a senior tech quietly performing a task nobody ever verified, on the strength of a job they held years ago.

Does not apply to, and does not substitute for, any license, card, or certification required by law or by a jurisdiction. Where a legal credential is required, that credential is a separate prerequisite and the sign-off cannot be issued until it is held and current. Competence and legal authorization are different things and this document never blurs them.

Roles and responsibilities

The assessor may be the person who taught the task. The alternative, requiring an independent assessor, is better in principle and unaffordable in a shop with two qualified people. The safeguard used here instead is the silent-observation rule in the procedure below, plus the second assessor on hazard-class tasks.

Definitions

Unaided. The learner performs the task with no prompting, no hints, no tool handed over unasked, and no question answered beyond what would be answered for any tech on the phone. The assessor may intervene only to stop an unsafe act or to prevent damage, and any intervention voids that instance.

Instance. One complete performance of the task on a real call, start to finish, including the documentation.

Hazard-class task. Any task involving gas, water in combination with electricity, stored energy, working at height, confined space, or energized work. These carry a higher instance count and a second assessor.

Sign-off. A dated record naming the task, the learner, the assessor, the instances observed, and the result.

Procedure

1. Confirm the prerequisites before scheduling an assessment

The assessor verifies, before the first assessment instance:

• Any required license, card, or certification is held and current.
• The learner has completed the training instances for this task and is not being assessed on something they have watched twice.
• For a hazard-class task, the learner has already been signed off on the relevant isolation and verification task. Nobody is assessed on work involving a hazard until they are signed off on making it safe first. A learner who cannot yet de-energize and verify dead with a known-good meter, or isolate and relieve stored pressure, is not assessed on anything downstream of that step.

Skipping this step is how a shop ends up assessing someone on a procedure they can perform and cannot make safe, which is the exact combination that produces an injury.

2. Tell the learner it is an assessment

Announce it. A hidden assessment produces a more natural performance and a worse outcome, because the learner does not get the chance to say "I have not done that variant" and instead improvises, and improvisation under observation is precisely the habit you do not want to reward.

State the task, the bar, and how many instances are required. If the learner says they are not ready, believe them and reschedule. A learner who self-declines has told you something true and should never be penalized for it.

3. Observe silently

The assessor's job during the instance is to say nothing. This is the hardest step and the one that gets violated constantly, because watching a slower person do a task you can do quickly is uncomfortable and the words come out on their own.

The rule: the assessor speaks only to stop an unsafe act or to prevent damage. Any other prompt, including a helpful one, converts the instance into a coached instance and it no longer counts.

Silence is what makes the sign-off worth anything. An assessment full of small hints measures the assessor's presence, not the learner's competence, and it is exactly the sign-off that fails in the field two weeks later when the assessor is not standing there.

4. Record the instance immediately

At the end of the call, before the next one, the assessor records: date, task, learner, pass or fail, and one line of specifics. "Passed. Predicted the reading before probing and was right on two of three, corrected himself on the third without prompting." That line is worth more than the pass or fail, because it is what makes the record readable to somebody else six months later.

Record failures with the same detail and no softening. A record that contains only passes is a record nobody believes.

5. Require consecutive unaided instances

The bar is three consecutive unaided instances for a routine task, five for a hazard-class task. Consecutive is load-bearing. A failed instance resets the counter to zero.

Three is the minimum that distinguishes competence from a good day: one is a demonstration, two can be short-term memory, three across different equipment or conditions is the first honest evidence that the skill transfers. Five on hazard-class tasks reflects that the consequence of a wrong call there is not a callback.

Where possible, the instances should differ. Three instances on the same equipment in the same configuration is close to one instance repeated.

6. Sign, decline, or defer

Sign when the instance count is met at the stated bar. The record names the assessor, not the shop.

Defer when the learner is close and specific work remains. Deferral must name the gap and the next step. "Not yet" without a named gap is a demoralizing non-answer and it is how good people start looking around.

Decline when the learner is not close, and say so directly and privately. Then rebuild the training plan for that task rather than repeating the assessment.

7. Publish the change

The sign-off is worthless if the board does not know. Within one business day, the records holder updates the skills matrix and tells whoever assigns work. The whole reason for the process is to change dispatch behavior, and a sign-off that has not reached dispatch has changed nothing.

8. Revoke when the evidence says to

The shop lead revokes a sign-off when: a callback or incident traces to that task and reveals a gap; the person has not performed the task in roughly six months and the skill has plausibly decayed; the task itself has changed materially, such as new equipment or a new procedure.

Revocation is not discipline and must be stated that way, or nobody will report the callback that triggers it. It restores the task to supervised status until re-signed.

Records

Keep for each sign-off: task, learner, assessor, dates of each instance, the one-line note per instance, result, and any later revocation with its reason. Keep hazard-class sign-off records for as long as you keep other safety and training documentation, and check your jurisdiction's retention requirement, since training-record retention periods are set by regulation and vary by the type of training and the jurisdiction.

A worked example: five instances to reach a three-instance bar

An apprentice requests sign-off on a routine diagnostic task. Bar: three consecutive unaided instances.

Instance 1. Clean pass. Stated the expected reading before measuring, was right, documented well. Assessor stayed silent throughout and noted that staying silent took visible effort during a two-minute stretch where the apprentice was looking in the wrong place. Counter: 1.

Instance 2. The apprentice reached toward an energized component without verifying dead first. The assessor stopped the act. That is an intervention, so the instance is void, and because the intervention was a safety stop it is recorded as a fail rather than a no-count. Counter resets to 0.

This is the moment the process earns its keep. The temptation is to treat it as a slip on an otherwise good day and carry the earlier pass forward. Do not. The reset is what makes the sign-off mean something, and more importantly the reset is a signal about a prerequisite: the learner was signed off on verification as an isolated task and did not apply it under time pressure on a real call. Verification training gets repeated, not just the diagnostic.

Instances 3, 4, and 5. Three consecutive unaided passes on three different equipment configurations across eleven days. Verification performed correctly and unprompted on all three. Counter: 3. Signed.

Total instances observed: 5 against a bar of 3, roughly 67% more assessment time than the ideal case. That overhead is the cost of a bar that is real, and it is the cheapest version of this lesson available. The alternative price is the same mistake made alone.

Failure modes and how to catch them

• The pencil-whipped sign-off. Everything passes, every note is one word. Catch it by comparing sign-off dates against the completed-call history: if the instances do not correspond to real calls of that type, the record is fiction.
• The coached assessment. Ask a learner what the assessor said during the assessment. If they can recall helpful guidance, the instance was coached and the sign-off is soft.
• Sign-off drift. Two assessors applying visibly different bars. Catch it by having the shop lead sit in on one assessment per assessor per quarter, observing the assessor rather than the learner.
• The sign-off that never reaches dispatch. Check that the last three sign-offs actually changed how those people were scheduled. If not, step 7 is being skipped and the whole process is ceremony.

Review

Review this SOP annually, and immediately after any incident, callback, or near miss that traces to a task someone was signed off on. The most useful revision is almost always to the instance count or the bar on one specific task, not to the process itself.

References

• See related: The Ride-Along Debrief SOP, How to Check Whether Training Actually Stuck
• See related: How to Build a Skills Matrix for a Small Shop, The Apprentice-to-Journeyman Path as a System
• OSHA requirements to train and verify employee qualification before assignment to hazardous tasks, including retraining when performance indicates a gap
• State or local licensing rules, where a credential is a legal prerequisite to performing the task