What a training record has to show, not just track

Competence is the requirement; training is one way to get there

Clause 6.2 doesn't require training as an end in itself. It requires personnel performing work that affects conformity to product requirements to be competent, on the basis of appropriate education, training, skills, and experience — and it requires the organization to determine the competence necessary for each role before deciding how to close any gap. Training is the most common way to close that gap, but the clause names it as one action among others, which matters for roles where the actual gap-closer is supervised experience or a documented skills assessment rather than a course. A record built only around course completions has no place to put the competence path that doesn't run through a classroom.

The step a roster alone can't satisfy

Clause 6.2 requires the organization to evaluate the effectiveness of the actions taken to achieve competence — not simply to confirm the actions took place. A completion date shows a person sat through a training session or read a document and signed for it; it says nothing about whether they can now do the work correctly. A working competency record needs a field a roster doesn't have: what evaluation was performed after the training — an observed task, a written check, a supervised run — and what it found, filled in after the fact and not assumed in advance.

Effectiveness checking is supposed to scale with risk, not run on one setting

The standard doesn't leave the rigor of that evaluation to guesswork. Its guidance on Clause 6.2 ties the effectiveness-checking method to the risk associated with the work the training supports — a role with a direct line to product safety needs a more rigorous check than a role several steps removed from it. A single evaluation method applied uniformly across every role, quiz or otherwise, is either doing too little for the highest-risk positions or more than the standard requires everywhere else. A training record that can show which method was used for which role, and why that method fits the role's risk, is answering a question a flat completion grid never asks.

Where this record is supposed to close a loop CAPA opens

“Operator retrained” is one of the most common entries in a corrective action's action-taken field, and it isn't a root cause by itself — it's a corrective action that only closes the loop if the training record can then show the retraining actually worked, under Clause 6.2's own effectiveness step, not just that it happened. A CAPA marked closed on the strength of a training completion date, with no linked competency evaluation, has satisfied the CAPA tracker's paperwork and skipped the training record's actual requirement. It's the same failure an internal audit program keeps reopening as the same finding year after year: the retraining gets logged, the underlying competence never gets checked, and the mistake recurs on schedule.

Awareness is a separate line item, and an easy one to forget

Clause 6.2 also requires the organization to ensure personnel are aware of the relevance and importance of their activities and how they contribute to achieving quality objectives. That's a distinct requirement from technical skill — a fully competent operator can still be unaware of why a step matters to the finished device's safety, and a training record that only tracks technical sign-offs has no field for this awareness element at all. It's a small, checkable gap: does the record show awareness was addressed, separately from competence, or does it only ever ask whether the technical box got signed.

A training and competency record built around these distinctions — competence determined before training is assigned, effectiveness evaluated and scaled to risk, and awareness tracked as its own element — is previewed in the launch catalog. If your program checks effectiveness differently, the shelf takes that correction directly.