Building a Lab Competency Assessment Program That Passes Inspection

Every accredited lab has a competency program. Many of them are spreadsheets that drift out of date the week after the last inspection. This is a guide to building a program that doesn’t — one where the matrix is current the day before the next inspection because that’s the normal state, not because someone went on a marathon update sprint.

The audience is lab managers, quality officers, and training coordinators in clinical labs under CAP, CLIA, ISO 15189, or UKAS accreditation. The principles are the same across the four; the cadence and the specific assessment methods differ in detail.

What “competency assessment” actually means

There’s a tendency to use training and competency interchangeably. They are not the same thing.

• Training is the act of teaching: an instructor-led course, a self-study packet, on-the-job shadowing, an e-learning module.
• Competency is the verified state of being able to perform a procedure correctly, demonstrated under defined conditions.

Training without competency assessment proves nothing. Competency without training is sometimes possible — an experienced hire might be competent on day one — but most labs run training first, then assess.

Both states have expirations. ISO 15189 and CAP both expect recurring assessment because skills decay, equipment changes, procedures evolve. The interval depends on the procedure: a high-complexity test might warrant semi-annual reassessment in the first year and annual thereafter; a low-risk routine test might be assessed annually from the start.

The six elements of competency assessment

CAP, in particular, codifies competency assessment around six elements. Most of these map cleanly onto the other standards too. For every test system and every testing person:

1. Direct observation of routine patient test performance — someone watches the technologist run a real test from start to finish.
2. Monitoring of the recording and reporting of test results, including critical-value reporting.
3. Review of intermediate results such as quality control records, proficiency testing results, and patient test results.
4. Direct observation of performance of instrument maintenance and function checks — including preventive maintenance the technologist is expected to perform.
5. Assessment of test performance through blind samples — testing previously analysed specimens, internal blind samples, or external proficiency samples.
6. Assessment of problem-solving skills — through case studies, real problem reports, or scenario-based questions.

Frequency: how often is “often enough”?

The default cadence many labs use:

• New testing personnel: initial competency assessment before they begin testing unsupervised. Then a second assessment six months later. Then annually thereafter.
• Established personnel: annually, ongoing.
• After a significant change — new instrument, new test, new SOP, significant deficiency — a triggered reassessment outside the normal cycle.

ISO 15189 and UKAS expect “appropriate” cadence with documented rationale. CLIA names initial and ongoing competency. CAP’s six-month-then-annual cadence for new personnel is the strictest of the common ones — running to that schedule keeps you defensible everywhere.

Methods: what counts as evidence

Each of the six elements above can be evidenced multiple ways. The matrix should record both what was assessed and how. The “how” matters because not all methods are equal in regulatory weight.

• Direct observation is the strongest evidence — and the most labour-intensive.
• Blind-sample retesting is excellent for technical accuracy but says nothing about the broader workflow.
• Review of records (controls, PT, patient results) is good for sustained performance but weak for one-time skills.
• Case studies and scenario tests are appropriate for problem-solving elements but should not substitute for direct observation of routine performance.

A well-rounded annual assessment uses several methods. A program that relies entirely on “review of records” is one finding away from a problem.

The matrix: where the program lives

The single most important artefact of a competency program is the matrix: a grid of topics (or tests, or procedures) by staff members, with each cell showing the current competency status.

A useful matrix has at least five states per cell:

• Compliant — current assessment on record, not expired
• Expiring soon — currently compliant, but the assessment will expire within a defined window (usually 30 days)
• Non-compliant — expired or never assessed; this person should not be performing this test
• Pending assessment — training is complete but the assessment hasn’t been performed yet
• Not started — no training and no assessment; not assigned

The matrix tells you, at one glance, the readiness of your lab to perform every procedure with every staff member. It’s the single most useful object an inspector can be shown — and it’s also the single most useful object you can look at every Monday morning.

The five gaps that recur

From competency-related deficiencies we see most often:

1. Quietly expired training. The 30-day reminder went to an inbox that nobody monitors. The technologist kept running the test. The cell turned red and stayed red.
2. Training without subsequent competency assessment. The course was completed, the record is filed, and that’s where it stopped. No formal assessment was ever performed, so technically the person is still pending — but they’ve been running the test for eight months.
3. Assessment by an unqualified assessor. Whoever signs off on the competency needs to themselves be qualified to perform and judge the procedure. An admin acknowledging a check-the-box record doesn’t satisfy this.
4. Documentation method missing. The record shows “competent” but doesn’t specify which of the six elements was assessed, or how. The auditor can’t reconstruct what happened.
5. No triggered reassessment. A significant deficiency or process change should trigger reassessment, and often doesn’t.

Every one of these is a tracking problem, not a skill problem. A system that tracks expirations, requires method capture, and ties assessor qualification to procedure makes most of these structurally hard to do wrong.

Tying it together

A good competency program looks like this on a normal Tuesday:

• New hires move from “not started” to “pending assessment” to “compliant” via a documented training pathway with timed expirations.
• Expiring assessments fire reminders 30, 14, and 7 days out, to both the technologist and the supervisor.
• Each assessment captures method, assessor, and which of the six elements were observed.
• The matrix on the wall (or on the dashboard) is always current, because the system rebuilds it every time an event is logged.
• The lab-wide readiness score sits next to the readiness scores for calibration, EQA, maintenance, and documents — one number, one glance, you know where you are.

The reward for building the program this way is straightforward: the inspection itself stops being a special event. It becomes a Wednesday where you happen to also have a visitor.

---

Related reading:

• Training & Competency management software for clinical labs — the matrix in software
• How to prepare for a CAP inspection — the broader inspection-readiness checklist
• Why spreadsheets fail lab compliance — why the spreadsheet competency matrix always drifts