What "competency" actually means in a file
Competency verification is evidence that a specific person has been assessed and found capable of performing a specific task, under your practice’s supervision, before they perform it independently. It’s not a credential. It’s not a certificate from a weekend course three employers ago. It’s documentation created by your practice, showing your practice confirmed this person can do this job, here, under your protocols.
For most roles, a defensible competency record includes:
- Initial orientation to practice-specific protocols, not just general orientation to the job title
- A documented skills checklist or return demonstration for hands-on procedures, signed off by whoever supervised the assessment
- Evidence of any required certifications tied to specific procedures — not just that the certification exists, but that it’s current and applicable to what the person is actually doing
- A record of ongoing competency, particularly for skills that carry higher risk or that the person performs infrequently
- Documentation of any additional training required after a competency gap was identified, and confirmation it was completed
Where files typically fall apart
A few patterns show up across almost every practice type we review:
- A license is on file, but there’s nothing showing the person was ever assessed on the specific procedures they perform — injections, IV starts, particular equipment — under this practice’s protocols.
- Competency was verified at hire, two or three years ago, but nothing has been documented since, even for staff performing higher-risk procedures.
- A certificate from a training course is treated as sufficient, when the course covered general technique and never involved anyone from the practice observing the employee actually perform the task.
- Verification happened, but informally — a supervisor remembers watching someone do a procedure well — with nothing written down and no signature on file.
- New hires are cleared to work independently immediately, with competency verification scheduled for “sometime in the first month,” and the file shows no record it ever happened.
None of these usually reflect a practice that doesn’t care about training. They reflect training that happened, but wasn’t captured in a form that survives a records request. Verbal confidence in a team member is not the same thing as a documented competency record, and only one of those holds up when someone else is reviewing the file.
Building a file that actually holds up
The fix isn’t complicated, but it does require treating competency verification as a standing process rather than a one-time hiring step:
- Create a specific checklist for each role and task, listing exactly what needs to be observed and signed off before someone performs it independently
- Require a named supervisor to sign and date each competency assessment, tied to the specific skill
- Set a schedule for re-verification, especially for procedures that carry higher risk or that staff perform rarely
- Store this documentation in the personnel file itself, not in a separate training log that never gets cross-referenced during a review
- When a new certification or procedure is added to someone’s role, treat it as a new competency event requiring its own documentation, not an extension of what was verified before
The test worth applying to your own files
Pull a personnel file at random. Pick a procedure that person performs regularly. Can you point to a document showing this practice specifically confirmed, in writing, that this person is competent to perform that procedure? If the honest answer is “I’m sure they can do it,” that’s a training gap in your documentation, even if it isn’t a training gap in your team’s actual skill.