Training vs. Competency — What's the Difference?

If you've spent any time in a laboratory quality manual, you've seen these two words used almost interchangeably. Training and competency get paired together so often that it's easy to assume they're just two ways of saying the same thing.

They're not. And mixing them up is one of the most common (and most citable) mistakes a lab makes.

Let's clear it up.

Training Teaches. Competency Confirms.

Here's the simplest way to think about it:

Training is the process of teaching someone how to perform a task. It's the instruction, the demonstration, the practice runs, and the SOP walkthrough. Training answers the question: Does this person know what to do and how to do it?

Competency is the process of confirming that someone can perform the task correctly, consistently, and independently. Competency answers a different question: Can this person actually do it, on their own, and do it right?

Training is the "teach." Competency is the "prove it."

You can train someone thoroughly and still find out during competency assessment that they haven't fully grasped it. That's not a failure of the system. That's the system working exactly as intended, catching the gap before it becomes a patient safety issue.

What This Looks Like in Real Life

Training example: A new hire shadows a senior tech on the chemistry bench for two weeks. They watch specimen processing, learn the LIS workflow, review the SOP for troubleshooting QC flags, and run practice samples under supervision.

Competency example: Ninety days later, that same tech is observed independently performing a full testing cycle, correctly identifies and documents a QC failure without being prompted, passes a blind sample challenge, and answers problem-solving questions correctly on an unknown or unusual result.

See the difference? One is "I showed you." The other is "you showed me."

Training can happen in a classroom, over the shoulder, or through an online module. Competency has to be demonstrated by the person actually doing the work, observed or measured by someone qualified to judge whether they did it right.

When Should Competency Be Assessed?

CLIA and most accrediting bodies (CAP, TJC, COLA) expect competency assessment at predictable checkpoints, not just whenever there's time:

• At the end of initial training, before the person tests patient samples independently
• At 6 months for new testing personnel in their first year
• Annually thereafter for each test the person performs
• Whenever something changes — new instrumentation, a major method change, a procedure revision, or an extended leave of absence
• When performance issues arise, a competency reassessment is one of the most useful (and most underused) tools for addressing a quality concern before it becomes a bigger problem

If you'd feel nervous defending a tech's ability to perform a test to an inspector, it's probably time for a competency check.

Why Both Need Documentation (Yes, Both)

This is the part that trips people up. Labs are usually pretty good about documenting training. Sign-in sheets, checklists, and module completion certificates. But competency documentation tends to be less complete, or worse, it gets combined with training records as if they're the same thing.

They need to stand on their own for a reason: an inspector isn't just asking "did this person get trained?" They're asking, "How do you know this person can do the job?" Training records answer the first question. Competency records answer the second. If you have only one, you've only told half the story.

Solid competency documentation should include:

• The six required elements per test (direct observation, monitoring QC/PT/EQA, review of records, blind sample testing, problem-solving assessment, instrument maintenance/function checks, as applicable)
• Date of assessment and due date for the next one
• Who performed the assessment and their qualifications
• Any corrective action taken and the follow-up plan

Without this paper trail, even a technically competent staff member looks, on paper, like an unassessed risk. And "looks like a risk on paper" is exactly what keeps lab directors up the night before a CAP inspection.

The Bottom Line

Training gets someone ready, butcompetency proves they're ready. One teaches the skill, while the other confirms it can be performed correctly and independently. A lab that only trains is hoping for the best. A lab that trains and verifies competency knows where it stands.

Next time someone says "they're trained, so they're good," you'll know exactly what follow-up question to ask.

This article builds on concepts introduced in New Employee Onboarding in the Lab: A Step-by-Step Guide, where we explore how effective onboarding sets the stage for successful training and long-term competency.

Want a head start on structured competency assessments for your team? Explore Compass and CompassPlus to see how labs are bridging competency, compliance, and clinical judgement.