Training records are where a lot of otherwise solid quality systems quietly fail an audit. Not because the training didn’t happen — but because the system can’t prove that the people using a procedure are trained on the current version of it. That single gap, between your documents and your training records, is one of the most reliable findings an auditor knows how to produce. Here’s the link they always check, why it breaks in most systems, and how to close it for good.

The question auditors always ask

Pick any released procedure in your quality system. An auditor points at it and asks: “Show me that the people who do this work are trained on this revision.” It sounds simple. It ends more audits than almost any other question, because answering it requires two things to be true at once:

• Your document control knows which revision is current.
• Your training records tie a named person to that specific revision — not to “the procedure” in the abstract.

This isn’t a nice-to-have. ISO 9001 requires both competence (Clause 7.2) and control of documented information (Clause 7.5); ISO 13485 and the FDA’s QMSR carry the same expectation for training and records. The standards treat training and document control as two halves of one control. Most software treats them as two separate modules — and the seam between them is exactly where findings live.

Why the training–document link breaks in most systems

In a typical setup, documents live in one place and training lives in another — a spreadsheet, an LMS, a folder of signed sheets. Everything looks fine until a document is revised. Then the question no one owns surfaces: who reassigns training to the people who use it?

If the answer is “someone remembers to,” you have a gap. Revisions ship, and the training records still point at last year’s version. People keep working from a revision they were trained on but that’s no longer current. A shared drive or a folder can’t tell you who has read the current revision — and a training log maintained by hand can’t keep up with every release. The bigger your system gets, the wider the gap grows.

Do the math on a real library. Two hundred controlled documents across a hundred and fifty people isn’t unusual — and that’s thousands of read-and-understand assignments to build, and then rebuild every time a document is revised or someone changes roles. No team maintains that by hand without gaps. The manual link is the failure mode.

What your training records actually have to prove

A training record that survives an audit isn’t “Jane took the SOP training.” It has to answer, on demand:

• Who — the specific person.
• What document — and, critically, which revision.
• When — the date they acknowledged it.
• Proof of understanding — an acknowledgment, and where the risk warrants it, a passed quiz.

The revision is the part that trips people up. “Trained on the procedure” is not the same as “trained on Rev C, the one that’s released today.” When Rev C supersedes Rev B, every training record for that document should, in effect, reset — and the right people should be reassigned automatically. If that reassignment depends on a human remembering, it will eventually be missed.

The fix: tie training to the document release

The durable answer is to stop treating training as a separate activity and make it a consequence of releasing a document. When a procedure is released under control, the people who use it are automatically assigned to read and acknowledge that revision. No spreadsheet, no memory, no seam to fall through.

The part that separates a real system from a checkbox is how those people get assigned. The strongest approach doesn’t make you hand-pick names for every document. It assigns training from the relationships you already maintain:

• By department — everyone in Manufacturing gets the manufacturing procedures.
• By job title or role — every inspector gets the inspection work instructions.
• By category or document type — release a document of a given type and the right audience is already defined.

Set those relationships up once, and every future release — and every role change — reassigns training correctly on its own. That’s the difference between a system that records training and one that guarantees the link the auditor is going to test.

Why this matters beyond passing an audit

Passing the audit is the visible payoff, but it’s not the real one. The real one is that your people are demonstrably working from current instructions — which is the entire point of a quality system. A controlled document nobody has been trained on is just a file. Training tied to release is what turns your controlled library into competence on the floor.

It’s also, quietly, one of the features buyers most often forget to test for. When you’re evaluating QMS software, it’s easy to check the boxes for version control and approvals and never ask, “when I release a revision, does the right training reassign itself?” Ask it. The answer separates the tools that close the loop from the ones that leave you holding a spreadsheet.

How TLM makes the link automatic

TLM was built so training and document control are one system, not two. When a document is released, the people who use it are assigned to read and acknowledge that specific revision — assigned automatically from department, job title, or category and document-type relationships you define once. Where understanding needs to be proven, a quiz can gate the sign-off. And every acknowledgment is captured, revision-specific, in the same audit trail as the version control and approvals behind it.

The result is the answer to the auditor’s favorite question, ready before they ask it: here is the current revision, here are the people who use it, and here is each one’s dated acknowledgment of this version. Not reconstructed from a spreadsheet — just there, because the link was never manual to begin with. (See how TLM handles it in training management.)

See training tied to document release on your own process → Book a 20-minute walkthrough.

Frequently asked questions

What is a training record in a QMS?
A training record is documented proof that a specific person has been trained on a specific document at a specific revision, on a specific date — typically with an acknowledgment and, where risk warrants, a passed quiz. In a quality system it’s the evidence that the people doing the work are competent on the current instructions.

What does ISO 9001 require for training records?
ISO 9001 requires you to determine necessary competence, ensure people are competent, and retain documented information as evidence (Clause 7.2) — alongside control of documented information (Clause 7.5). Together they mean your training records must show people are trained on the current, controlled version of the documents they use. ISO 13485 and the FDA QMSR carry the same expectation.

Why do training records need to be tied to a document revision?
Because being trained on an old revision isn’t the same as being trained on the current one. When a procedure is revised, the previous training no longer proves competence on what people are actually supposed to follow. A record tied to a specific revision is the only thing that answers an auditor’s question: are these people trained on this version?

How can training be assigned automatically?
By assigning it from relationships you define once — department, job title or role, and document category or type. Then every time a document is released or a person changes roles, the right training reassigns itself to the right people, tied to the released revision, with no manual list to maintain.

What’s the difference between an LMS and QMS training records?
A general LMS manages courses and completions but usually has no live link to your controlled documents, so it can’t guarantee training reflects the current revision. QMS training records are tied to document control: releasing a revision drives the training, and the record proves competence on that specific version — which is what audits require.