What a document-control SOP actually controls

Clause 4.2.4 covers control of documents: instructions, procedures, forms in their blank state — anything meant to be revised as the organization's practice changes. A separate clause, 4.2.5, covers control of records: the filled-in, dated evidence that something happened, which by design is not revised once created. A document-control SOP that treats these as one undifferentiated pile — one retention schedule, one review cycle, one set of rules — is misapplying half its own procedures to things that were never meant to be edited.

A document and a record are not interchangeable

The distinction sounds academic until you watch a completed inspection form get treated like the blank template that generated it: someone "revises" a filled-in nonconformance report to fix a typo, overwriting what should have been permanent evidence of what was actually observed on that date. The blank form lives under 4.2.4 and gets versioned. The completed one lives under 4.2.5 and gets preserved, legible and retrievable, exactly as it was written. A working SOP states, for every document type it governs, which side of that line it falls on — not as a philosophical aside, but as an operating rule for what "correcting an error" is allowed to mean.

The clause people skip: obsolete documents

Approval and versioning are the easy half of 4.2.4. The harder requirement is preventing the unintended use of obsolete documents — and if an obsolete version is retained for any purpose, applying suitable identification so it can't be mistaken for current. A SOP that describes how a document gets approved but never describes how a superseded version gets pulled, flagged, or locked isn't controlling the failure mode the clause exists for: someone on the floor building today's device against yesterday's work instruction, because nobody's job was to go get the old copy.

Retention has a floor, not just a policy statement

Clause 4.2.5 sets a specific default: records are retained for at least the lifetime of the medical device as the organization defines it, or as applicable regulatory requirements specify, but not less than two years from the device's release. “Per applicable regulations” in a retention table is the records equivalent of a checklist item that asks for agreement instead of evidence — it names no number and commits to nothing checkable. A working SOP states the actual retention period per record type, and the reasoning behind it, on the page.

In an electronic system, distribution control is a permissions problem

Most quality systems now live on a shared drive or a QMS platform rather than in redlined paper binders, which changes what “prevent unintended use of obsolete documents” means in practice. It stops being about collecting old copies and becomes about whether the system itself enforces version control — locking prior revisions, surfacing only the current approved copy, logging who accessed what and when. A folder of files named _FINAL, _FINAL2, and _FINAL_use_this_one is not document control with a light electronic wrapper; it's the exact failure Clause 4.2.4 was written against, just moved onto a server.

A document-control SOP built around these distinctions — document/record separation, obsolescence handling, stated retention periods — is previewed in the launch catalog. It sits next to the shelf's other structural pieces, including the checklist rules that make the same evidence-over-agreement argument at the row level; if your version handles a case ours doesn't, the shelf takes that correction.