21 CFR 211.160 needs specification and method authority
21 CFR 211.160 requires written laboratory controls with scientifically sound specifications, standards, sampling plans and test procedures, including quality-control-unit review and approval. A laboratory should resolve the governing approved version before sampling or testing begins and preserve any later deviation or change separately.
Editorial figure by Lab Systems Index. Source context: 21 CFR 211.160 General requirements.
Resolve the governing laboratory control before work starts
| Control record | Evidence to retain | What it does not establish |
|---|---|---|
| Material and sample scope | Product or component, lot or batch, sample ID, purpose, stage, specification family and regulatory context | That a familiar test applies to this sample |
| Approved authority | Specification, sampling plan and method identifiers, versions, effective dates, approvals and supersession links | That the newest document was effective at execution |
| Execution readiness | Instrument and system, analyst qualification, standards and reagents, environmental conditions and prechecks | That document approval proves readiness |
| Performed work | Actual steps, times, data, calculation version, observations, audit trail and contemporaneous documentation | That a passing result proves procedure adherence |
| Deviation or change | Departure, impact, investigation, temporary instruction or change control, approval and disposition | That a deviation may be erased by updating the method |
Bind the sample to the approved control set
The direct answer is to resolve the exact approved specification, standard, sampling plan and test procedure before the sample is taken or the test begins. Section 211.160 requires written laboratory controls and quality-control-unit review and approval. Record the material or product, lot or batch, manufacturing stage, sample ID, purpose, applicable requirement, each document identifier and version, approval, effective date and any superseded version. [1]
A laboratory information system can suggest documents, but it should not infer authority solely from the newest revision number or a method name. Product, market, compendial commitment, filing, protocol, specification status and effective date can produce a different governing set. Preserve the qualified decision and unresolved conflict. This article does not select a method or specification for a reader’s material.
Prove approval and effective status at execution
Store quality-control-unit approval and the change history for each control, including who approved, when the approval became effective, the population affected, training or implementation prerequisites, and retirement of the prior version. Freeze the execution packet to the version effective when work occurred. Later changes should remain linked without rewriting historical authority. [1]
Approval is distinct from readiness. Verify the analyst’s qualification, equipment status, software or calculation version, reference standard and reagent status, sample condition, environmental requirements and required prechecks. Section 211.160 establishes general laboratory-control requirements, but it does not prove local method suitability, validation, instrument fitness or sample identity. [1]
Document performance as it occurs
The regulation says laboratory controls must be followed and documented at the time of performance. Preserve the actual sampling and testing steps, times, analyst, instrument, raw data, observations, integrations, calculations, transfers, audit trail, review and result relationship. A final result copied into a summary cannot substitute for contemporaneous execution evidence. [1]
Distinguish the approved instruction from what happened. When the analyst departs from a step, an instrument interrupts, a sample changes, or a calculation is corrected, preserve the original evidence and route the event through the applicable deviation, investigation or change process. Do not update the method version on the completed record to make execution appear aligned. [1]
Control changes without losing historical traceability
A change should state the reason, affected specification, sampling plan or procedure, scientific and regulatory assessment, approval, effective date, training, migrated population and relationship to work already in progress. Define which samples remain under the old version and who may authorize a transition. Retain superseded records for reconstruction.
Lab Systems Index freshly reviewed the exact eCFR section on October 7, 2026. No post-October 6 amendment was relied on, so this is durable compliance analysis. Unknowns include product scope, approved local controls, scientific suitability, sample identity, validation, execution, deviation impact, data integrity, batch disposition, compliance and FDA conclusion; the actual records and quality unit must resolve them. [1]
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Lab Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.