Ask a clinical department whether its staff are competent and you will usually be shown a file. The file is complete. Orientation was documented, the checklist was signed, the annual attestation was collected, the education hours were logged. Everything an auditor would ask for is present.
Now ask a narrower question: if a new hire and a fifteen-year veteran performed the same study, the same procedure, the same assessment this afternoon, would the department know whether the results were equivalent? Would it know before something went wrong?
For a great many departments, the honest answer is no. And the gap between those two answers is not an administrative gap. It is a clinical one.
What the checklist actually documents
A competency checklist records that on a particular date, an observer watched a task and judged it acceptable. That is genuinely useful information. It is also narrower than it appears in three ways.
It is a point in time. Skill acquired during orientation is not the same as skill maintained three years later, particularly for tasks performed rarely. A signature from 2023 tells you about 2023.
It is one observer’s threshold. Two preceptors of good faith and different standards will pass different work. Without a shared, written definition of what adequate looks like, a checklist measures the observer as much as the observed.
It is task-shaped, and clinical work is not. Checklists decompose work into steps that can be watched. Much of what distinguishes safe practice is not a step: recognizing that a finding does not fit the picture, knowing when to escalate, knowing what to document so the next clinician is not guessing. These are the parts of competency that checklists are worst at capturing and that matter most.
None of this is an argument against checklists. It is an argument against mistaking a completed one for an answer.
Competency as a system
Treating competency as a system means asking a different question. Not “was this person trained?” but “how would this organization know, and how soon, if capability had drifted?”
That question produces a different structure, with a few recognizable components.
A written standard of what adequate looks like. Specific enough that two experienced people applying it independently would reach the same judgment. This is harder than it sounds and it is the foundation; without it, everything downstream measures opinion.
Assessment that reflects how the work is actually distributed. High-volume routine work and low-volume high-consequence work need different treatment. The rare, difficult task is the one most likely to be signed off once and never revisited, and it is the one where drift is most dangerous. Frequency of assessment should follow consequence, not convenience.
Evidence drawn from the work itself. Structured review of real output — images, documentation, decisions, the actual artifacts of practice — is a more honest signal than an annual observed encounter, because it reflects ordinary conditions rather than observed ones. It also generates specific, teachable feedback instead of a pass.
A defined response to a gap. A system that identifies a capability gap and has no predetermined path — targeted education, supervised practice, scope adjustment, reassessment — will stop identifying gaps. People do not surface problems into a vacuum, and a program that punishes disclosure will be told nothing.
Education tied to the specific gap. Generic annual education is efficient to deliver and weakly connected to capability. Education that responds to what assessment actually found is harder to administer and is the only kind that changes practice.
Where this shows up first
Competency systems tend to be tested at the seams rather than in the center of a department’s work.
They are tested when a service extends its scope, and the new scope arrives before the standard defining adequate performance of it. They are tested when volume grows faster than the structure for onboarding, and orientation compresses into shadowing. They are tested when experienced staff leave and the informal transmission of judgment — the correction offered across a workstation, the second look asked for at the right moment — leaves with them, invisibly, because it was never part of the documented system.
Departments may discover that the structure holding quality together was not the competency program itself, but a small number of experienced people providing informal oversight and judgment. That arrangement becomes vulnerable when those individuals leave.
The reframe
The purpose of a competency system is not to satisfy a regulator, though a sound one will. It is to give an organization an accurate, current answer to a question it should be able to answer at any moment: are the people doing this work today able to do it well, and how do we know?
An organization that can answer that has a competency system. An organization that can only produce the file has documentation. Both matter, but they are not the same asset—and documentation alone cannot establish current capability.
Clinical Integrity Group works with healthcare organizations and academic institutions on competency frameworks, clinical education, onboarding structure, and workforce development. Workforce Development & Clinical Education · Partner with CIG