Every regulated operation has the same piece of paper. It sits on a clipboard at the back of the training room: a name column, a date column, a signature column. At the end of the session it goes into a binder, and the binder goes onto a shelf, and the shelf is where the auditor eventually finds it.
That sheet answers one question well. Were you in the room?
It's the wrong question. Nobody gets hurt because a technician skipped a classroom session. People get hurt, and sites go dark, because someone was in the room and still couldn't do the work. The training checklist most teams rely on records attendance and calls it qualification.
What Regulators Actually Ask For
Read the rules, and attendance barely comes up. The OSHA standard for forklift operators is a good example of how specific they get. After training and an evaluation of the operator's performance, the employer certifies it, and "the certification shall include the name of the operator, the date of the training, the date of the evaluation, and the identity of the person(s) performing the training or evaluation" (29 CFR 1910.178(l)(6)). Operators are re-evaluated at least every three years.
ISO 9001 makes the same move in general terms. Clause 7.2 requires organizations to determine the competence people need, make sure they have it, and retain documented information as evidence of that competence. Evidence of competence, not evidence of a course.
The question underneath both is the same. Not "did training happen," but who evaluated whom, against what standard, and when.
Why Most Training Checklists Fail the Audit
Most teams already know a sign-in sheet isn't enough, so they add an on-the-job training checklist: a list of tasks a supervisor watches the new hire perform and initials. It's a real improvement. It usually still fails in four places.
Anyone could have ticked it
The checklist says a qualified person must observe the task. The record shows a set of initials. Was that person qualified to evaluate? Were two observers required? A paper or spreadsheet checklist can't enforce who is allowed to check an item. It can only hope.
The procedure changed underneath it
A technician was signed off on the generator transfer procedure in March. The procedure was revised in June. Which version did she demonstrate? If the checklist lives in a shared drive, nobody can say, and "the current one" is a guess.
The signature isn't a signature
Initials in a spreadsheet cell aren't tied to an identity. Anyone with edit access can type them, and anyone can change them later. In a dispute, that record proves nothing about who signed.
It lives nowhere near the role
The checklist is in a binder. The role's requirements are in the HRIS. The certifications are in a third system. When someone asks "is everyone on night shift qualified for this procedure," the answer is a week of reconciliation.
None of this is academic. Uptime Institute's 2025 outage analysis found that nearly 40% of organizations suffered a major outage caused by human error over the past three years, and that 85% of those incidents stemmed from staff failing to follow procedures or from flaws in the procedures themselves. The procedure was written down. What was missing was proof that the people running it could do it.
Checklists Work When Someone Owns the Check
None of this is an argument against checklists. The evidence for them is strong. When eight hospitals introduced the WHO Surgical Safety Checklist, the study published in the New England Journal of Medicine in 2009 found it was associated with deaths falling from 1.5% to 0.8% and major complications from 11% to 7%.
The checklist didn't work because it listed steps the surgical team didn't know. It worked because it assigned the check to specific people at specific moments, and made skipping it visible. That's the part most training checklists leave out. A list of tasks is a reminder. A list of tasks with named authority, a fixed version, and a real signature is a record.
The Five Fields Every Sign-Off Record Needs
Whether you keep a training record template in Excel or move to software, hold your current training sign off sheet against this list. If it can't answer all five, it's an attendance record.
- The person and what they're qualifying for. The role, career, or procedure the sign-off counts toward. Not just a name.
- The exact version checked against. The revision of the checklist or procedure in force when the work was demonstrated, so a later edit never rewrites history.
- Who checked, and why they were allowed to. The evaluator's identity, plus the rule that qualified them: a named trainer, the person's manager, or anyone holding a senior role, with a minimum count where two observers are required.
- When. The date and time of each check, and the date the sign-off is due again if it recurs.
- A signature that means something. Tied to an authenticated identity at the moment of signing, and impossible to edit afterward.
Most organizations can produce fields one and four today. Fields two, three, and five are where audits get uncomfortable, and they're the hardest to bolt onto a spreadsheet.
Where SkillsDB Comes In
We built Checklists in SkillsDB to record all five by default. Each item names who can check it: the person, their manager, named people, anyone in a career, or anyone with an access level, with "at least two" rules where a second observer matters. Published versions are locked, so every assignment stays on the version it started with. Sign-off can require an e-signature that asks the signer to confirm it's them with their password or company single sign-on, and for qualifications that need it, every step is signed on its own line and the record is sealed with a certificate of completion.
Because a competency checklist lives in the same system as your careers, skills, and certifications, it can also sit inside the process it supports. A checklist can repeat every year for recertification, or hold a promotion approval until it's complete.
Attendance was always the easy thing to record. Competence is the thing that matters, and it deserves a record that holds up.