Most SOP failures during a CAP inspection are not about accuracy. The procedure is usually technically correct. The failure is about format, accessibility, and evidence of use. An inspector who cannot find the current version of a procedure, or who finds a procedure that has not been reviewed in three years, will cite it — regardless of whether the procedure itself is accurate.
What CAP requires in an SOP
CAP does not prescribe a specific SOP format, but it does require that procedures include certain elements: the principle of the test, specimen requirements, reagents and equipment, step-by-step instructions, quality control requirements, reference ranges, and the procedure for reporting results. The procedure must be approved by the laboratory director, dated, and reviewed at least annually.
The annual review requirement is where most labs fall short. A procedure that was written five years ago and has been technically accurate ever since still needs to be reviewed and re-approved every year. The review does not need to result in changes — it needs to result in documented evidence that a qualified person looked at the procedure and confirmed it was still current.
Format matters more than you think
An SOP that is technically complete but difficult to use is a compliance risk. If a bench technician cannot find the step they need in the middle of a run, they will not use the SOP — they will rely on memory. An inspector who asks a technician to show them the procedure for a specific step and watches them struggle to find it will note the observation.
The best SOPs are written for the person performing the test, not for the person writing the procedure. They use numbered steps, not paragraphs. They include decision points explicitly — "if the QC result is outside range, do X before proceeding." They are formatted consistently across the entire procedure library so that any technician can navigate any procedure without training on the format itself.
Version control is a system, not a folder
Version control means more than keeping old versions in a folder labeled "archived." It means that every copy of every procedure in the laboratory is the current version, that superseded versions are not accessible at the bench, and that there is a documented record of what changed between versions and when.
The most common version control failure we see is the existence of multiple versions of the same procedure in different locations — one in the binder at the bench, one in the shared drive, one in the director's files. When an inspector asks which version is current and gets three different answers, that is a deficiency.
The sign-off requirement
Every testing personnel member must sign off on every procedure they are authorized to perform, at least annually. This is not a training record — it is a competency attestation. The sign-off must be dated, must identify the specific procedure, and must be retained for the period required by CAP and CLIA.
If you are building a new SOP library or overhauling an existing one, the SOP Development service is designed to do exactly this — from validated templates through version control setup through staff sign-off tracking.
