A CLIA inspection doesn't announce itself with a warning — CMS surveyors can walk through your door on any working day, and a CAP inspection gives you only a narrow window of preparation. Yet every year, labs lose their certificates, incur civil money penalties, and scramble through corrective action plans over violations that a consistent internal QC discipline would have caught first. The failure is almost never scientific — it's documentation.

This checklist is built around the key CLIA quality control requirements for non-waived testing under 42 CFR Part 493, supplemented with CAP Q-track checklist priorities that correlate most strongly with deficiency citations. Use it to audit your own practices before an inspector does it for you.

What CLIA Actually Requires for QC

CLIA '88 — the Clinical Laboratory Improvement Amendments — establishes the federal quality standards all U.S. clinical labs must meet to receive Medicare and Medicaid reimbursement. CMS enforces CLIA; the Joint Commission and CAP operate as CMS-approved accreditation bodies whose standards are recognized as equivalent.

Under 42 CFR Part 493, Subpart K (Quality Control), the core QC requirements for moderate- and high-complexity testing are:

The regulations set a floor. Accreditation bodies and instrument manufacturers typically impose higher expectations — and inspectors use those higher expectations to drive citations even when the regulatory minimum is technically met.

Daily QC Compliance Checklist

Daily discipline is where most labs either build or destroy their compliance posture. These are the actions that must happen every day testing is performed.

Every Day Testing Is Performed

  • Run at least two levels of QC material per analyte before reporting patient results
  • Confirm QC results fall within established acceptable ranges (mean ± 2s minimum)
  • Apply Westgard multi-rule evaluation — not just a single 1-2s warning check
  • Document QC run time, operator, lot number, and expiration date
  • Review and sign off on QC records before the first patient report is released
  • Document any out-of-control event with a corresponding corrective action entry
  • Verify corrective action resolved the failure before resuming patient testing
  • Confirm QC materials are within their expiration and open-vial stability period
  • Check instrument flags, maintenance logs, and reagent lot status before first run
Common citation pattern: Labs run QC, record the result, but the supervisor review signature is absent or added hours after patient results were already released. Under CLIA, the review must precede the release — not follow it. Electronic systems that enforce a mandatory QC sign-off gate before the result queue unlocks are the only reliable fix.

Monthly QC Compliance Checklist

Monthly activities establish the statistical baseline that makes your daily QC meaningful. Without monthly review, you cannot demonstrate that your acceptability limits are grounded in current instrument performance rather than manufacturer claims from three years ago.

Monthly Tasks

  • Calculate cumulative mean and standard deviation for each control level from the current month's QC data
  • Compare calculated statistics against established ranges — flag any CV drift >10% from baseline
  • Review QC trend charts for systematic bias, progressive drift, or sudden shifts
  • Confirm Levey-Jennings charts are current and accessible for the current and prior 2 months
  • Audit corrective action log — verify every out-of-control event has a documented resolution
  • Review reagent and calibrator lot change log — verify QC was repeated after each lot change
  • Confirm all QC records are signed by a qualified supervisor, not just by the testing personnel
  • Verify proficiency testing (PT) sample handling: tested by routine testing personnel using routine methods, results submitted on time
  • Document any instrument maintenance performed and verify post-maintenance QC was run and passed

Monthly review is also the right time to assess whether your control ranges need updating. CLIA requires that you establish your own ranges — you cannot simply adopt manufacturer insert values as your acceptability criteria. If your lab has accumulated enough new data points to tighten or recalculate your mean and SD, do it now and document the change.

Annual and Semi-Annual QC Compliance Checklist

These are the scheduled activities that prove your QC program is a deliberate, documented system — not a set of habits that grew over time.

Every 6 Months

  • Perform calibration verification for all analytes using at least three levels spanning the reportable range
  • Document calibration verification results and the laboratory director's review sign-off
  • Repeat calibration verification after any major reagent lot change or instrument repair
  • Confirm reference intervals are appropriate for your patient population — review any age, sex, or demographic-specific sub-ranges

Annually

  • Review and re-approve the QC program — the lab director must formally document that the QC plan remains appropriate
  • Update the quality management plan and QC policy documents to reflect any procedural changes made during the year
  • Audit PT participation records — confirm enrollment, timely submission, passing scores, and corrective action for any failures
  • Conduct a method performance review: accuracy, precision, linearity, and reportable range still within original validation parameters
  • Review all personnel training and competency assessment records — verify all testing personnel have a current, documented annual competency evaluation
  • Confirm test procedure manuals are reviewed, dated, and signed by the current lab director (not an expired approval from a previous director)
  • Verify all instruments have current maintenance contracts or in-house maintenance documentation
  • Confirm the lab's CLIA certificate information (name, address, director) reflects current operations — update CMS if anything has changed

The Most Common CLIA and CAP Inspection Failures

CMS publishes condition-level and standard-level deficiency data from CLIA inspections. Year over year, the same five failure categories account for the majority of citations. Knowing them in advance is the most efficient inspection preparation a lab director can do.

1. Unacceptable QC — Running Out-of-Control Without Documentation

The most cited deficiency. An instrument drifts, a control flags, and the analyst repeats it until it passes — without recording that the first run ever happened. That's not just a documentation gap; it's a data integrity violation. CLIA requires that every QC event, including failures and repeats, is recorded with the corresponding corrective action.

2. Competency Assessment Not Performed or Not Documented

CLIA requires six competency assessment elements for each testing personnel member, annually after the first year. Labs routinely perform competency evaluations but fail to document them in a format that surveyors can verify. A verbal review doesn't count. A training check-off from three years ago doesn't count. Dated, signed records for each of the six elements, per person, per year — nothing less satisfies the requirement.

3. Procedure Manuals Outdated or Unsigned

CLIA requires that test procedure manuals be reviewed and re-approved by the current lab director at least annually. Inspectors check the signature date and the signer's name against the current CLIA certificate. A manual approved by a lab director who left the organization two years ago is a citation waiting to happen.

4. Proficiency Testing Failures — Handling and Communication

PT failures become citations not because labs score poorly — it's how they respond. CLIA requires that PT samples are tested by routine personnel using routine methods, and that unsatisfactory results trigger a documented investigation and corrective action within 30 days. Labs that investigate informally but never write it down are as exposed as labs that don't investigate at all.

5. Calibration Verification Gaps

Semi-annual calibration verification is required, but labs frequently miss it after instrument repairs, reagent lot changes, or during equipment transitions. The failure is usually not deliberate — it's a gap in the triggering system. If your lab has no automated alert that fires when a lot change occurs and demands a CalVer before the next patient run, you are relying entirely on human memory.

How to Prepare for a CAP or CLIA Inspection

CAP inspections are peer-reviewed and scheduled roughly every two years. CLIA-only labs receive CMS or state agency surveys on a similar cycle, but without advance notice in most states. Either way, inspection readiness should be a continuous state, not a six-week sprint before the scheduled date.

60–90 Days Before a Known Inspection

Pull the most recent CAP checklist for your specialty (Chemistry, Hematology, Microbiology — each has its own). Work through it item by item and document any gap you find. Every gap needs a corrective action owner and a closure date. The inspection team will ask whether you found any deficiencies in your self-inspection — and "we didn't find any" is a harder answer to defend than "we found three and corrected them."

30 Days Before

Organize your QC records. Inspectors typically want 12 months of QC documentation accessible. If your QC is in binders, confirm they are complete, in date order, and include supervisor sign-offs. If your QC is in software, confirm that the auditor role can generate a clean export. Verify that your PT records, competency files, and procedure manual review dates are current.

Ongoing — The Only Reliable Strategy

Labs that consistently pass inspections are not doing more work in the weeks before the inspector arrives — they are doing the same disciplined work every week. That means QC review is never deferred, corrective actions are documented the day they happen, and procedure manuals are reviewed on their anniversary date rather than whenever someone remembers. The paperwork burden of inspection readiness is entirely a function of how consistently you document in real time.

AssayGuard automates the documentation burden.

Every QC run, Westgard violation, corrective action, and trend alert is logged automatically with timestamps, operator IDs, and audit trails — ready to export for any inspection. No manual chart maintenance, no end-of-month data entry sprint.

See It in the Demo

How AssayGuard Supports CLIA Compliance

The compliance burden in clinical lab QC is not analytical — it's administrative. The Westgard rules are well understood; it's the documentation of every run, every failure, every corrective action, and every supervisor review that consumes time and creates citation exposure. AssayGuard addresses that directly.

Automated Rule Evaluation

AssayGuard applies all six Westgard rules to every QC result in real time. When a violation fires, it is immediately logged with the rule triggered, the result value, the control level, and the time — forming the beginning of a compliant corrective action record. There is no manual chart review step, no analyst judgment call on whether a trend has crossed a threshold. See the full guide to Westgard rules and how they work for a deeper look at each rule.

Timestamped Audit Trails

Every action in AssayGuard — result entry, QC review, corrective action note, supervisor approval — carries a timestamp and the authenticated identity of the user who took the action. When an inspector asks for documentation of your QC program, the answer is an export, not a stack of binders.

Trend Analysis and Predictive Alerts

CLIA requires you to detect control failures before patient results are released. AssayGuard's trend engine detects progressive drift and systematic shifts before they cross a hard violation threshold, giving you time to investigate and correct before a formal out-of-control event occurs. That distinction — catching a trend versus documenting a failure — is the difference between proactive QC and reactive damage control.

Compliance Reporting

AssayGuard generates QC summary reports that map directly to CLIA documentation requirements: date range, analyte, control level, mean, SD, CV, violation count, corrective action status. These can be exported for internal review, lab director sign-off, or direct presentation to inspectors. There is no "preparing for inspection" mode — the reports are always current. Explore AssayGuard plans to see which reporting features are available at each tier.

Summary: What Separates Compliant Labs from Cited Ones

CLIA compliance is not a function of how good your science is — it is a function of how consistently you document that your science is good. The labs that get cited are not running bad QC; they are running QC without complete, real-time records that prove it.

The practical checklist is short: run two levels of QC daily before releasing patients, apply multi-rule evaluation, document every result and every failure, review before releasing, perform calibration verification on schedule, maintain competency records per person per year, and keep procedure manuals signed and current. Do those things consistently and the inspection is a review, not a discovery.

The hard part is not knowing the rules — it is building the operational habits and systems that execute them without fail, shift after shift, analyst after analyst. That is exactly the problem AssayGuard was built to solve. Try the free demo to see how automated QC monitoring changes what compliance looks like in practice.

<\!-- Article footer nav -->