The Training Record SOP

Purpose

To keep one durable, retrievable record of what every person on the crew has been trained on, proven on, and is restricted from, so that dispatch, an insurer, a licensing board, a warranty adjuster, and the next owner of the shop all get the same answer from the same place.

The test this SOP is built around: a stranger, two years from now, with the trainer no longer employed here, has to be able to answer four questions about any task any employee performed. Who was trained. On exactly what. To what standard, proven how. By whom, on what date. A record that cannot answer all four is a note, not a record.

Scope

Covers every field employee, office employee, apprentice, and any subcontractor whose competency your shop vouches for in front of a customer or a general contractor.

Covers four record classes, which behave differently and must not be blended into one column:

• Attendance - training was delivered to this person on this date. Proves exposure, not skill.
• Competency - this person performed the task unaided to a stated standard, observed by a named assessor. Proves skill.
• Credential - an external card, license, certification, or medical clearance issued by somebody other than you, with an issue date and an expiry date.
• Restriction - what this person may not do at all, or may not do unsupervised, and until when.

Does not cover performance reviews, discipline, or pay. Those carry different access rules and different retention obligations, and mixing them into the training file is what turns a routine records request into a legal problem.

Roles and responsibilities

Definitions

System of record. The one place that wins when two sources disagree. Every other copy is a convenience copy and is treated as wrong by default.

Standard. The observable bar that was met, written as something a third party could re-check. "Torqued to the value on the label and verified with a calibrated wrench" is a standard. "Did a good job" is not.

Lead time. The number of days before a credential expires at which you start the renewal, chosen so that a class seat or a testing appointment can still be found.

Procedure

1. Fix the four fields before you build anything

Every entry, regardless of class, carries: person, task or credential name (from a controlled list, not free text), date, and evidence. Evidence differs by class - a sign-in sheet for attendance, an assessor name plus the standard met for competency, a card number and expiry for a credential.

Skip the controlled list and within a year you will have "Brazing," "brazing joints," and "braze cert" as three separate rows describing one skill, and your coverage count for that task will read three names when it is really one.

2. Keep one system of record and forbid the second

Pick the place: the shop management system, a shared spreadsheet, or a physical binder, in that order of preference. Announce it. Then actively kill the shadow copies - the mentor's notebook, the safety guy's separate class list, the folder on somebody's desktop.

The reason is not tidiness. Two systems do not stay in sync, and the moment they disagree you cannot prove either one. If a mentor keeps notes, that is fine, but the notes are an input that gets transcribed within a day, never a parallel record.

3. Write the record at the moment of the event

Same day, ideally within the hour. Not at week end, not at review time.

A record written from memory a week later is systematically wrong in one specific direction: it records what was covered, because that is what you remember, rather than what was proven, which is the detail you have already forgotten. That is exactly the error that makes the record useless in a dispute.

4. Record what was proven, not what was covered

For a competency entry, write the standard and the instance count in the entry itself:

Recovery and evacuation, unaided, third consecutive instance, held vacuum through the standing test with no rise, observed by J. Ruiz, no prompting required.

Compare that with "trained on recovery." The first survives a warranty argument. The second does not survive a follow-up question.

If the person needed prompting, that is a coaching note, not a competency entry. Log it as attendance, name the gap, schedule the next instance.

5. Stamp every credential with an expiry and a lead time

Credentials are the only record class with a built-in failure date, and the only one that can silently make a job illegal. Every credential row carries issue date, expiry date, issuing body, and a lead time.

Set lead times by how hard the renewal is to schedule, not by a single blanket number. A commonly workable pattern: 30 days for anything you can renew online the same week, 90 days for anything requiring a proctored exam or a seat in a scheduled class, 120 days for anything with a medical or physical component that might come back needing follow-up. Run the report monthly.

6. Record restrictions as explicitly as competencies

A restriction is an active safety control, not an absence of a record. "Not cleared to work on energized equipment, review in Q3" belongs in the file as its own row with its own review date. So does a medical restriction on the weight or the height a person can work at, recorded as the restriction only, never the underlying medical detail - that stays in a separate confidential medical file.

The absence-of-a-record approach fails predictably: a dispatcher who sees no entry assumes the gap is administrative and sends the person anyway.

7. Set retention and never delete early

Know the shape of the obligations before you pick a number. Some OSHA standards require a training record only until it is superseded by the next one, with respirator fit testing the usual example. Employee exposure and medical records under the access-to-records standard (29 CFR 1910.1020) run far longer and the numbers are specific: medical records for the duration of employment plus 30 years, exposure records for 30 years, where the standard covers your exposures. Confirm which standards actually apply to your trade and your headcount rather than adopting one blanket rule, but do not leave the number vague once you know it applies.

For competency records, the pressure is different and comes from the work, not the regulator: statutes of repose on installed construction work cluster around 6 to 10 years from substantial completion, with an outer range of roughly 4 to 15 depending on the state, so look up the number where you work rather than assuming the cluster covers you. A workable shop default is separation plus the longest repose period you are exposed to, so that when a claim lands on an install from six years ago you can still name who did it and prove they were qualified. Write your number down in this SOP and stop re-deciding it.

8. Control who writes and who reads

Write access: the training owner and the owner. Read access to a person's own record: that person, always, on request. Read access to another person's record: supervisors with a work reason.

Uncontrolled write access is how competency entries appear for instances that never happened, usually with good intent, to unblock a dispatch decision on a busy morning.

9. Reconcile against the dispatch board monthly

Pull the tasks actually dispatched last month. For each one, check that whoever ran it has a competency record for it. Every mismatch is one of two things: a person doing work they are not signed off on, or a sign-off that happened in the field and never got written down. The first is a live exposure to fix this week. The second is your record decaying, and it decays fastest exactly when the shop is busiest.

10. Export the record on separation

When someone leaves, export their full record to a static file before their access is closed, and store it under your retention rule. Hand them a copy of their own competency and credential list. This costs about fifteen minutes and it is the cheapest protection you have against a claim on work they performed.

Records and retention

A worked example: reconstructing a record two years later

A general contractor sends a claim on a commercial install your shop completed 26 months ago. The question is straightforward: was the person who performed the connection qualified at the time.

You pull the job. It names two techs. One is still on the crew, one left 14 months ago.

For the tech still employed, the competency file shows the task with three instances recorded, the third dated 5 months before the install, assessor named, standard written out. That answers the question in about two minutes.

For the departed tech, the file exists only because step 10 was followed. The static export shows the same task, two instances, both recorded, plus a restriction row that was lifted 8 months before the install with a named approver. Also two minutes.

Now run the same claim against a shop that skipped this SOP. The competency evidence is a sign-in sheet from a manufacturer class that both techs attended 31 months ago. That sheet proves attendance and nothing else - it proves both men sat in a room. It cannot say either one ever performed the task unaided, so the shop's position collapses from "here is the proof" to "we are sure they knew how." Reconstructing anything better means calling a former employee and a former lead, both of whom will reasonably say they do not recall a specific connection from over two years ago.

The cost difference is not the four minutes. It is that one shop enters the claim with documentary evidence and the other enters it with an assertion, and those two positions settle very differently.

Failure modes and how to catch them

Attendance recorded as competency. The most common defect by a wide margin. Catch it by auditing ten random competency rows a quarter and asking whether each names an assessor and a standard. Any row that names only a class title is an attendance row filed in the wrong column.

The record that only grows. Nothing is ever revoked, so the sheet shows coverage the shop does not actually have. Techs lose perishable skills. If a competency has not been exercised within your refresh interval for that task, it needs a refresher instance before it counts toward coverage, and the row needs a last-performed date for that check to be possible.

Credential tracked in a person's head. It works right up until that person is on vacation the week a card lapses, and then a job stops or, worse, does not stop. The monthly report is the control.

Retention decided per incident. Somebody purges old files to clean up, and the purge is deepest on exactly the departed employees whose records you most need. Write the number in this SOP, make deletion a scheduled annual action against that number, and require the owner to approve it.

Review

Review this SOP annually, and immediately after any of the following: a records request from a regulator or insurer, a warranty claim where the record was needed, a change in scope of work that adds a credential, or a change in the software or binder that holds the records.

References

• OSHA 29 CFR 1910.1020, access to employee exposure and medical records, for the retention shape on exposure and medical records
• OSHA 29 CFR 1910.134 for the fit-test record pattern where a record is retained until superseded
• See related: The Competency Sign-Off SOP, for how an instance is assessed before it is recorded
• See related: The Annual Skills Review SOP, for the periodic reconciliation this record feeds
• Trade-standard recordkeeping practice for licensed contracting work; confirm your state's statute of repose before setting a retention number