CLIA
CLIA Competency Assessment: The Six Required Elements Explained
If your lab performs non-waived testing in the United States, CLIA requires you to assess each testing person’s competency against six specific elements — and to do it on a defined schedule. The six elements aren’t a suggestion or a best practice; they’re written into the regulation, and surveyors check them one by one.
This is a working explanation of each element: what it actually requires, how labs evidence it, who is allowed to perform the assessment, and the timing rules that trip people up. If you want the broader how to build the program picture across CAP, ISO 15189, and UKAS as well, start with building a competency assessment program — this post is the CLIA-specific deep dive on the elements themselves.
Where the six elements come from
CLIA’s competency requirements live in the regulation governing testing personnel (the relevant sections sit at 42 CFR §493.1451 and §493.1413, depending on complexity and role). The regulation lists six procedures a lab “must use” to assess competency, “as applicable to the test method”. That last phrase matters — not every element applies to every test, and a defensible program documents why an element was or wasn’t used for a given method.
CAP codifies the same six elements, which is why a program built to satisfy CLIA generally satisfies CAP’s competency requirements too. The reverse isn’t always true — CAP layers on its own cadence expectations — but the elements are shared vocabulary.
The six elements, one at a time
1. Direct observation of routine patient test performance
A qualified assessor watches the testing person actually perform a patient test, start to finish — specimen handling, processing, and analysis as applicable. This is the strongest single piece of evidence in the whole set, because it shows the person doing the real work under real conditions, not describing it.
Evidence: a dated observation record naming the assessor, the test system observed, and the outcome.
2. Monitoring the recording and reporting of test results
The assessor confirms the person records and reports results correctly — including, critically, critical-value reporting: does the technologist follow the call-back procedure, document it, and report within the required timeframe?
Evidence: review of the person’s actual result entries and critical-value call logs, or direct observation of a reportable event.
3. Review of intermediate test results, QC records, PT results, and maintenance records
This element checks the person’s sustained performance over time, through the paper trail they generate: are their quality-control records complete and in range? Are their proficiency-testing results acceptable? Are their maintenance and function-check logs being kept properly?
Evidence: documented review of that individual’s QC, PT, and maintenance records over the assessment period.
4. Direct observation of instrument maintenance and function checks
Distinct from element 1 (running the test), this watches the person perform the upkeep — the preventive maintenance and function checks the role requires. A technologist who runs assays flawlessly but skips or fumbles the daily maintenance is a real risk, and this element exists to catch it.
Evidence: a dated observation of maintenance/function-check performance — which, not coincidentally, is the same kind of record a good preventive maintenance program generates anyway.
5. Assessment of test performance through blind samples
The person tests a sample whose correct answer is known but not to them: a previously analysed patient specimen, an internal blind sample, or an external proficiency-testing sample. It’s the most objective measure of analytical accuracy in the set.
Evidence: the blind-sample result compared against the expected value, with the comparison documented.
6. Assessment of problem-solving skills
The person demonstrates they can handle the unexpected: a flagged result, an out-of-range control, an instrument error. Assessed through case studies, real problem reports they handled, or scenario-based questions.
Evidence: documented problem-solving assessment — a scenario worksheet, or a record of how they handled a real event.
The timing rules
CLIA’s competency cadence is specific, and it’s where labs most often slip:
| When | Requirement |
|---|---|
| Before testing patient samples | Initial training (and, for the role, qualifications met) |
| At 6 months | Competency assessed twice in the first year — the regulation requires semiannual assessment during the first year a person tests |
| Annually thereafter | Competency assessed at least once per year |
| After a change | Reassessment when a method, instrument, or the person’s duties change materially |
The first-year rule is the classic miss: a new hire is assessed at onboarding and then not again until the next annual cycle, skipping the required six-month assessment. A surveyor who finds a person hired in March with no assessment between onboarding and the following year’s review has found a citable gap.
Who is allowed to assess
This catches labs off guard. Under CLIA, competency assessment must be performed by someone qualified for the role — for high-complexity testing, the technical consultant (or a designee who themselves meets the qualifications) is responsible; the general supervisor may perform the assessments. An administrator clicking “acknowledge” on a checklist does not satisfy the requirement. The assessor must be competent in the procedure they’re judging.
A practical consequence: your program needs to record who assessed as well as what was assessed, because the surveyor will check the assessor’s qualifications against the test’s complexity.
Training is not competency
One distinction underlies all six elements: completing training does not establish competency. Training is teaching; competency is verified ability, demonstrated under defined conditions. A person can finish every training module and still owe a competency assessment — and until that assessment exists, they’re not cleared to test independently.
Treating these as two separate, independently-tracked states is what keeps a program honest. Someone can be current on training but pending assessment — and that distinction is exactly what surveyors probe when they pick a name and ask to see the full record.
Building a CLIA-defensible record
Pulling it together, a competency record that survives a CLIA survey shows, for each testing person and each test system:
- Initial training completed before unsupervised testing began.
- The first-year semiannual assessment performed on schedule.
- Annual reassessment thereafter, with dates that don’t have gaps.
- Each applicable element documented — and where an element wasn’t applicable, a note saying why.
- The assessment method captured (observation, blind sample, record review, scenario).
- A qualified assessor named for each assessment.
Every one of those is a field, not a science problem. The labs that struggle aren’t the ones that can’t assess competency — they’re the ones whose records can’t prove they did, when a surveyor picks a name and pulls the thread. Build the program so the proof is the byproduct of doing the work, and the survey stops being the event you dread.
Related reading:
