A CAP inspection is not an audit of your science — it is an audit of your documentation. The peer inspectors who walk through your laboratory are not questioning whether your Westgard rules are the right ones or whether your reagent choices are optimal. They are verifying that you have written evidence, consistently maintained, proving that your QC program is disciplined enough to protect patients. Labs that fail inspections almost always fail on documentation, not on analytical performance.

This guide covers exactly what CAP inspectors look for in QC documentation, the specific failures that generate the most citations, and a 15-item checklist every lab director should verify before inspection day. If your lab is accredited by CAP or preparing to seek accreditation, this is the practical preparation guide your Q-probe binder doesn't provide.

~2yr
CAP inspection cycle — peer-reviewed, every two years
12mo
QC records inspectors typically review in depth
Top 5
Recurring citation categories account for most deficiencies

What CAP Inspectors Actually Look For in QC Documentation

The College of American Pathologists uses specialty-specific checklists — Chemistry, Hematology, Microbiology, Molecular Pathology, and others — each developed and maintained by practicing laboratory professionals. Checklists are revised annually, and new checklist items often target the deficiencies that appeared most frequently in the previous inspection cycle. This is a peer review system that gets sharper every two years.

Across specialties, the QC documentation requirements converge on the same core areas:

Written QC Procedures That Specify the Rules Used

CAP requires that labs have a written quality management document — often called the QC plan or laboratory quality manual — that specifies the multi-rule statistical procedure used for each analyte, the control levels and frequency, and the corrective action procedure when rules fire. A QC plan that says "we evaluate controls daily" without specifying the evaluation criteria fails this requirement. See our guide to Westgard rules and multi-rule QC for a detailed explanation of what the written procedure must cover.

Control Results With Complete Traceability

Every QC result must be traceable — the specific control lot number, the expiration date of that lot, the open-vial stability period, the testing personnel who ran it, and the instrument or analyzer used. Inspectors will pick a QC result at random and trace the chain from that number to the control material it came from to the instrument that produced it to the person who reviewed it. If any link in that chain is missing, it is a finding.

Supervisor Review Performed Before Patient Result Release

This is the most commonly misunderstood requirement. CAP does not require that a supervisor physically sign a paper before every result is released — but it does require that the QC review and sign-off process is structured to occur before results are available to clinicians. Labs where the technologist reviews their own QC, or where QC is reviewed batch-style at end of shift after results are already out, have a systemic compliance gap that surveyors will identify.

Corrective Action Documentation for Every Out-of-Control Event

When a Westgard rule fires, the corrective action record must include: what rule triggered and on which analyte, what investigation was performed, what the identified root cause was (or "no assignable cause found"), what corrective action was taken, when corrective action was completed, and who verified that the issue was resolved before patient testing resumed. A corrective action record that says "repeated; passed" does not satisfy CAP's requirement — the investigation and resolution must be documented even when the repeat passes immediately.

Calibration Verification Within Required Intervals

CAP requires calibration verification for all quantitative tests at least every six months, and whenever a major event occurs: significant reagent lot change, instrument repair, or any time QC suggests a possible calibration shift. Inspectors ask to see the CalVer results and the date they were performed. Gaps — particularly after instrument service calls or lot changes — are among the most common CAP findings.

Annual Personnel Competency Assessments

Each testing personnel member must have a documented annual competency evaluation covering all six required elements: direct observation of test performance, monitoring of recording and reporting, review of intermediate test results, direct observation of performance of instrument maintenance, assessment of test performance through previously analyzed specimens, and problem-solving assessment. All six elements, per person, per testing specialty, every year after the first. Partial records — three elements documented, three missing — do not satisfy the requirement.

Common Documentation Failures That Cause CAP Citations

Based on patterns in CAP Q-probe data and deficiency trends reported in the literature, the following failures generate the largest share of QC-related citations. These are not edge cases — they are the predictable failure modes of labs that have good practices but inconsistent documentation discipline.

1. Corrective Action Records That Stop at "Repeated; Passed"

When a control flags, the technologist repeats it and it passes. That's the end of the paper trail in many labs. CAP treats this as an incomplete corrective action record. The inspection standard asks whether the lab investigated the initial failure — was it a pipetting error, a QC material issue, or a transient instrument condition? Even if the investigation concludes "no assignable cause found," that conclusion must be documented. The repeat result alone is not an investigation.

The "silent repeat" problem: Technologists who re-run controls until they pass without recording the initial failure are creating data integrity violations, not just documentation gaps. CLIA and CAP both treat the selective recording of QC results as a serious compliance breach — potentially as significant as the underlying QC failure itself.

2. QC Sign-Off Timestamps That Post-Date Patient Result Release

Electronic LIS systems often time-stamp QC review actions. Inspectors compare the QC review timestamp to the timestamps of patient results released that same run. When patient results went out at 09:15 and the QC sign-off occurred at 14:30, the documentation trail directly contradicts the lab's stated QC-before-release policy. This is one of the cleaner deficiency findings — the data creates its own case.

3. Procedure Manuals With Expired Director Approval

CAP requires that test procedure manuals be reviewed and re-approved by the current laboratory director at least annually. Inspectors check two things: the date of the most recent director approval, and whether the signer is the current director of record. A manual approved by a director who left the organization 18 months ago is a straightforward citation. So is a manual approved last year — but by a medical director who signed as "acting director" and whose role was never formally recognized in the CLIA certificate.

4. Proficiency Testing Failures Without Documented Investigation

An unsatisfactory PT result requires a documented investigation and corrective action within 30 days. Labs that investigate informally — the director reviews the results in a team meeting, identifies the likely cause, decides no action is needed — but never write any of that down have a citation even if the investigation was sound. The requirement is not just that investigation occurs; it is that evidence of the investigation exists in writing.

5. Missing CalVer After Lot Changes or Service Events

Labs consistently fall behind on calibration verification after reagent lot changes and instrument service calls. The failure is systemic: there is no automated trigger that tells the next-shift technologist that this instrument had service yesterday and needs a CalVer before patients run. The QC program works; the event tracking doesn't. CAP inspectors know this and look for CalVer dates aligned with the lab's lot change and service logs.

6. Competency Records With Missing Elements or Incomplete Personnel Coverage

Labs that perform annual competency reviews but document only four of the six required elements, or that have complete records for full-time staff but missing records for part-time or per-diem personnel, have a documentation gap that surveyors will find. The coverage requirement is total — every person who performs testing must have a current annual record.

Stop Chasing Documentation — Automate It

AssayGuard timestamps every QC entry, flags every Westgard violation, and builds corrective action records automatically. Inspectors get exports, not binders.

See It in the Demo View Plans

The 15-Item CAP Inspection QC Documentation Checklist

Work through this checklist before any CAP inspection. Each item maps to a common finding category. Where your lab cannot answer "yes" with documentary evidence in hand, you have a gap to close.

Written QC Program Documentation

  • A written QC plan exists for each analyte, specifying multi-rule evaluation criteria (e.g., Westgard rules), control levels, frequency, and corrective action procedure
  • The QC plan has been reviewed and approved by the current laboratory director within the past 12 months
  • Test procedure manuals are current, complete, and signed by the current lab director — not a predecessor or acting director
  • Control target means and standard deviations are lab-established from your own instrument data — not copied from manufacturer inserts

Daily QC Records

  • QC records document the control lot number, expiration date, open-vial stability date, operator, instrument, and run time for every QC event
  • Supervisor QC review and sign-off timestamps precede patient result release timestamps — verifiable in the LIS audit trail
  • Every out-of-control event has a corrective action record that goes beyond "repeated; passed" — root cause investigation and resolution are documented
  • Levey-Jennings charts or equivalent trend displays are current, accessible by analyte and control level, and visually identify any violation points

Calibration and Verification Records

  • Calibration verification has been performed within the past 6 months for all quantitative analytes — records include at least three levels spanning the reportable range
  • CalVer was repeated after any significant reagent lot change, instrument service event, or instrument failure since the last scheduled verification
  • Reference intervals are validated for the lab's patient population and have been reviewed within the required interval

Personnel and Proficiency Records

  • All testing personnel have a current annual competency assessment covering all six required elements — including part-time and per-diem staff
  • Proficiency testing records are complete: enrollment documentation, results, and — for any unsatisfactory results — a written investigation and corrective action dated within 30 days
  • All PT samples were tested by routine personnel using routine methods — no evidence that PT samples received special handling differentiated from patient samples
  • Instrument maintenance logs are current; any corrective maintenance events are documented with post-maintenance QC verification
How to use this checklist: Run through it three months before a known inspection. Every "no" or "not sure" is an action item with an owner and a deadline. Three months gives you time to collect missing records, update outdated approvals, and close genuine practice gaps — not just assemble paperwork. If you find a practice gap (not a documentation gap), three months gives you enough QC cycles to demonstrate that the correction is sustained.

How Automated QC Systems Eliminate Documentation Gaps

The core insight behind every CAP documentation failure is that manual QC systems produce the documentation as a side effect of the analysis — and that side effect is easy to skip, defer, or do incompletely. A technologist running 40 QC results across 15 analytes per shift has limited bandwidth for the administrative layer on top of the analytical work. Documentation suffers not because of negligence but because of cognitive load.

Automated QC software restructures the workflow so that documentation is the system's job, not the technologist's job. The difference is not cosmetic.

Automatic Corrective Action Record Creation

When AssayGuard detects a Westgard violation, it immediately creates a corrective action record linked to that specific QC event — timestamped, rule-annotated, and surfaced in the violations queue. The technologist adds the investigation note and resolution; the system handles the record structure, the timestamp, and the linkage to the control result. There is no path to a silent repeat. Every violation that fires has a corresponding record.

Enforced QC-Before-Release Workflow

Software that gates patient result release on QC sign-off makes the CAP requirement structural rather than policy-dependent. It is not possible for results to be released before QC is reviewed because the system will not permit it. The LIS timestamp problem — QC reviewed hours after results released — does not occur because the sequence is enforced, not recommended.

Real-Time Levey-Jennings Charts

Every QC result updates the Levey-Jennings chart immediately. Violation points are highlighted. The chart is filterable by analyte, control level, and date range — producing exactly the format a CAP inspector wants to see, without any manual chart maintenance. Labs that maintain paper Levey-Jennings charts are spending staff time on an administrative task that software eliminates entirely. See how this compares to the broader CLIA QC compliance requirements that frame the documentation obligation.

Calibration Verification Tracking

Automated systems can track the due date for calibration verification per analyte and alert the lab when a CalVer is approaching, overdue, or triggered by a lot change event. This closes the gap that generates most CalVer citations — the absence of a trigger that fires when a lot change or service event should require a verification run before the next patient batch.

Inspection-Ready Exports at Any Time

AssayGuard can generate QC summary reports for any analyte, any date range, and any control level on demand. The report includes control statistics, violation log, corrective action status, and trend charts — exactly the documentation package a CAP inspector will request, available in seconds rather than the hours of pre-inspection binder assembly that manual systems require. AssayGuard plans include compliance reporting at every tier.

Preparing for Your Next CAP Inspection: A Timeline

CAP inspections are peer-reviewed — teams of laboratory professionals from other accredited labs, familiar with the daily realities of clinical lab work. They are not adversarial, but they are thorough. The inspection team will work through the specialty checklists methodically, and they will find documentation gaps that casual self-review misses.

Three Months Before

Run through the 15-item checklist above and document every gap. Pull the CAP checklist for your specialty from the CAP website and work through it systematically — not at a summary level, but at the individual checklist item level. Each finding you identify now is a finding you can close before the inspection team arrives. Assign each gap an owner, a corrective action, and a deadline.

Six Weeks Before

Verify that all corrective actions from the three-month review are complete. Confirm that QC records from the past 12 months are organized, complete, and accessible. Check that all personnel competency records are current and that any personnel who joined the lab in the past year have their initial and (if applicable) annual assessments on file. Confirm procedure manuals have been reviewed and director approvals are dated within the past year.

Two Weeks Before

Confirm CalVer is current across all quantitative analytes. Run a PT record audit — confirm all programs are enrolled, all submissions were timely, and any unsatisfactory results have closed corrective action records. Brief testing personnel on the inspection process: inspectors may ask them directly about QC procedures, corrective action steps, and how they would respond to specific out-of-control scenarios.

The Day Of

Have your QC documentation accessible in a format that allows inspectors to navigate by analyte and date range. If your QC is in software, ensure the inspector-accessible report function is ready. If your QC is in binders, organize by analyte with current month on top. Prepare to walk inspectors through a recent out-of-control event and its corrective action record — this is a common inspection exercise, and a clean walk-through demonstrates documentation discipline better than any binder can.

The most inspection-ready labs share one trait: they are not doing anything different for the inspection. Their QC is documented completely every day, every shift. Corrective actions are closed the day they happen. Procedure manuals are reviewed on their anniversary date. The inspection is a review, not a scramble. That posture is what automated QC systems are designed to enable — not by making labs more compliant in theory, but by making compliance the default outcome of normal workflow.

Summary: Documentation Is the Inspection

CAP accreditation is a rigorous, peer-reviewed process that sets the highest standard for clinical laboratory quality. The QC documentation requirements exist because documented consistency is the only form of quality a peer inspector can verify. They cannot observe your QC program across two years of shifts — they can only read its record.

The 15-item checklist in this guide covers the documentation areas that generate the majority of QC-related citations. A lab that can answer "yes" — with evidence — to each item is a lab that will pass its inspection. The challenge is not the inspection itself; it is building the operational systems that produce complete, accurate, traceable documentation as the normal output of every shift, not as the product of a pre-inspection scramble.

Automated QC software is the most direct path to that operational posture. Try the AssayGuard demo to see what inspection-ready documentation looks like when the system builds it automatically — not because an inspection is coming, but because it does it every time.