Guided example: revising COAG-SOP-014

A bench technologist is asked to add a new anticoagulant lot-verification step to "Coag Analyzer Daily Startup and Verification," document ID COAG-SOP-014, version 6, effective 2025-11-01. The reagent manufacturer sends an updated package insert on 2026-07-02 changing the acceptable lot-to-lot correlation range for the level 2 coagulation control from "within manufacturer-stated range" to "within plus or minus 10 percent of the assigned target on the new lot's certificate of analysis."

The document owner, the technical supervisor, opens a change request against COAG-SOP-014 version 6, citing the package-insert revision as the trigger. Because a manufacturer instruction was incorporated by reference into the laboratory's own controlled procedure, the change belongs in the controlled document, not only in a loose copy of the insert kept in a binder.

The draft, version 7, adds one measurable step: verify the level 2 control mean falls within plus or minus 10 percent of the lot's assigned target from the certificate of analysis before releasing patient results on a new lot; if outside range, do not release results, notify the technical supervisor, and quarantine the lot. That single sentence carries a numeric criterion, a named consequence, and a named responsible role, which is what turns a vague instruction into a corrective-action step a reader can actually execute and a reviewer can actually audit.

The laboratory director reviews and approves version 7, signs and dates the approval on 2026-07-10. The effective date is set for 2026-07-14, four days later, specifically to allow staff notification before the new criterion governs live testing. Version 6 is marked discontinued effective 2026-07-13, one day before version 7 takes effect, with that discontinuance date recorded. Version 6 is archived, not deleted, and pulled from the active bench binder and electronic point-of-use location so no one can act on the superseded acceptance range by habit.

The technical supervisor then works through a change-impact question: does this change how the task is physically performed? No; the pipetting and loading steps are unchanged. Does it change an acceptance criterion staff must apply? Yes; the numeric range changed.

Because the CLIA competency-assessment requirement is a distinct standard from the procedure-manual requirement itself, and because this revision is a criterion update rather than a new skill, the supervisor determines that a read-and-understand acknowledgment of version 7 is the appropriate personnel action for staff already competent on the base procedure. A full re-competency assessment is not automatically triggered by every revision. Each affected technologist reads version 7 and signs a document acknowledgment tied to that specific document ID and version number, not a blanket annual form.

The revision-history entry for COAG-SOP-014 records version 7, its effective date, the reason for the change, the approving director, and the version 6 discontinuance date, satisfying the retention requirement that a copy of each procedure show its dates of initial use and discontinuance.

When a manufacturer changes an acceptance criterion, write the new numeric criterion and its consequence directly into the controlled step, get director approval before the effective date, and confirm the superseded version is out of the technologists' hands, not just out of date on paper.