Walk into most regulated facilities and ask to see the training program, and you will be shown a records system. Completion rates by department. Read-and-understood signatures. Classroom rosters. Curricula assigned and closed on time.

Every one of those records answers the same question: was the person there? None of them answers the question that matters on the floor and in the audit room: can the person do the work?

That gap - between proof of presence and proof of capability - has always been an operational problem. Deviations trace back to personnel who completed every assigned course. New hires with perfect training files take months to perform independently. Now it is also a regulatory problem, explicitly.

The regulatory floor has moved

FDA’s Quality Management System Regulation became effective February 2, 2026, incorporating ISO 13485:2016 into the requirements for medical device manufacturers. The shift that matters for training programs: manufacturers are expected to evaluate the effectiveness of training - to determine that personnel are competent, not merely that training occurred. ISO 9001 makes the same demand of its certified organizations through Clause 7.2: retain appropriate documented information as evidence of competence.

Read those requirements against a typical training file. A signature that says “read and understood” is not evidence of competence. A classroom roster is not evidence of competence. A completed e-learning module with an 80% quiz score is evidence that the person can pass a quiz.

Evidence of competence looks different: a record that a specific person performed a specific task to a defined standard, independently, observed and verified by someone qualified to judge it.

Why programs drift toward attendance

No one designs a training program to produce empty records. Programs drift there under real pressures. Completion metrics are easy to measure and report; capability is not. The LMS tracks assignments, not performance. Production needs people on the floor, so “training complete” becomes the release gate because it is the gate that exists. And qualification by shadowing - follow Maria for two weeks - produces a sign-off that reflects time served rather than competence demonstrated.

Each of these is rational locally. Together they produce a program that can show an investigator one hundred percent completion and still not be able to answer the follow-up question: how do you know this operator can perform this task?

What proof of competence requires

Closing the gap does not require more training. In most facilities it requires restructuring what already exists around four elements:

A defined standard. For each critical task, what does correct performance look like, in observable terms? If the standard lives only in the trainer’s head, every trainer qualifies to a different standard.

Structured practice. Between “watched a demonstration” and “performs alone” there is a stage where the person performs while being coached and corrected. Most programs skip it. It is where capability is actually built.

Independent verification. A discrete event: the person performs the task alone, measured against the standard, and the result is binary - qualified or not yet qualified. Not an impression. An outcome.

A record of the demonstration. The verification event, documented: who, what task, what standard, observed by whom, on what date. That record is what “evidence of competence” means. It is also what ends an investigator’s line of questioning instead of extending it.

The question to ask of your own program

Pick any operator and any critical task they perform. Can you produce, in five minutes, a record showing that this person demonstrated this task to a defined standard before performing it independently?

If yes, your program proves competence. If what you can produce is a list of completed courses, your program proves attendance - and the distance between those two is now measured in regulatory exposure, not just operational risk.

We build the systems that close that distance: defined standards, structured qualification, verified performance, and records that hold up. If your program can show completion but not competence, that is the work we do.