The Most Commonly Misunderstood CLIA Requirements (And Why Labs Keep Getting Cited for Them)

If you've read our post on the 5 Most Common CLIA Citations, you already know which requirements trip labs up the most. What that post didn't get into is why. And in my seven years as a CLIA surveyor, "why" mattered more than "what" almost every time. Labs weren't cited because they didn't care about compliance. They were cited because a requirement got misread, half-implemented, or inherited from a policy nobody had updated in years. "That's how we have always done it" is the worst reason you can give.

Here are the four requirements I saw misunderstood most often — and what they actually mean.

1. Competency Assessment Isn't Just for "Testing Personnel"

This is one of the most common mix-ups I saw in the field, and it's not about whether competency assessment happens — it's about who it applies to. Labs tend to think of competency assessment as something that covers bench techs and stops there. But there are more positions in a lab than testing personnel. Clinical consultants, technical consultants, technical supervisors, and general supervisors all require competency assessments for the CLIA roles they fill. If they also perform testing, they will need a competency assessment for that in addition to the other.

I also saw a gap with smaller labs, where the "supervisor" is also the most experienced tech and regularly steps in at the bench. Their day-to-day skill was never in question — but their competency file often was, because everyone assumed their role put them above the requirement rather than squarely inside it.

The schedule itself doesn't change based on role: competency assessment happens twice in the first year for anyone new to a test method or position, then annually after that. Competencies for testing have to cover all six required elements — direct observation, monitoring of recording and reporting, review of QC and PT records, direct observation of instrument maintenance and function checks, review of test results (including proficiency testing and blind samples where applicable), and problem-solving assessment. Competencies for other roles need to be based on the position's responsibilities.

What to do: Ask a simple question for every person in your lab — what CLIA positions do they fill, and what testing do they perform? Has their competency been assessed for each duty they perform?

2. Passing Daily QC Isn't the Same as Being In Control

Most labs are diligent about running QC and confirming each result falls within range before reporting patient results. That daily pass/fail check is necessary, but it's not the whole picture, and it's the part that gets missed most often. A QC value can be technically "in range" every single day and still be quietly drifting toward the edge of that range — a shift or a trend that, left unreviewed, eventually turns into an out-of-control result that seems to come out of nowhere.

A shift is a sudden, sustained jump to a new level (often a reagent lot change or a calibration issue). A trend is a gradual, steady drift in one direction over days or weeks (often aging reagents, a slowly failing light source, or a temperature control issue). Both are visible if someone is looking at QC data over time — a run chart, a Levey-Jennings plot, even a simple month-over-month comparison. Neither is visible if QC review only ever asks "did today pass?"

What to do: Beyond your daily pass/fail check, build in a periodic review — weekly or monthly, depending on test volume — where someone actually looks at QC values over time, not just one day at a time. Most instrument software already generates this kind of chart; the gap is usually that nobody's assigned to look at it on a schedule. Assign it to someone specific, and put it on the calendar the same way you'd schedule competency or PT deadlines. And be sure the findings are documented — note the shift or trend and record the investigation into why it happened and what was done to correct it.

3. Corrective Action Isn't Finished Until You Know Who It Affected

When a QC result fails, most labs correctly stop, troubleshoot, and get the control back into range before reporting patient results. Where it goes sideways is documentation. A corrective action log that says "recalibrated, QC passed" tells a surveyor you fixed today's problem. It doesn't tell them you looked at why it happened or when it started.

If QC fails and you make a change to the test system to get it back into range — like recalibration or a new reagent pack — you need to determine when the issue began. You know it was okay the last time QC was tested, but did the issue affect patient results in between?

What to do: Rerun some patients since the last acceptable QC. Compare those results to the original results, using your lab's own established criteria for what counts as a clinically significant difference for that analyte — this will vary test to test, so don't rely on a single fixed percentage across the board. Be sure your lab's procedure for verifying these results is written and followed.

4. Personnel Requirements Are Role-Specific, Not Facility-Wide

Labs sometimes assume that if their testing personnel meet CLIA qualifications, they're covered across the board. But CLIA personnel requirements are role-specific — the qualifications for a technical consultant, a general supervisor, and testing personnel are all different, and moderate- and high-complexity testing have different thresholds for each role. A highly experienced tech who's excellent at the bench doesn't automatically meet the education or experience requirements to serve as a technical consultant, even informally.

What to do: Map every current staff member against the specific CLIA personnel category they're functioning in, not just the category they were hired into. Roles shift over time — someone who started as testing personnel two years ago may now be functioning as a technical consultant or general supervisor without the paperwork (or credentials) catching up.

Key Takeaways

• Competency assessment applies to every CLIA role someone fills, not just their title on the org chart

• Passing daily QC isn't the same as being in control — build in a periodic trend review

• Corrective action isn't complete until you've confirmed whether patient results were affected

• Personnel qualifications are role-specific and need to be reassessed as staff duties change

• None of these are obscure requirements — the gap is almost always between what the rule says and how a busy lab applies it day to day

Not sure where your lab stands on requirements like these?

Grab the free Top 10 CLIA Deficiencies Checklist — it's built around the exact patterns surveyors are trained to look for. [Download it here →]

That Lab Chic is an educational resource and does not constitute legal or regulatory advice.