21 CFR 820: FDA Quality Management System Regulation (QMSR)
Understand the current FDA device quality framework and connect its requirements to practical records, manufacturing controls and authorised decisions.

On this page · 12 sections
- 121 CFR 820: FDA Quality Management System Regulation (QMSR)
- 2Navigate current Part 820 and its incorporated framework
- 3FDA-specific requirements that sit alongside ISO 13485
- 4Check applicability by product, activity and US regulatory context
- 5QMSR, former QSR and ISO: distinguish the neighbouring terms
- 6Connect design changes, risk decisions and lifecycle evidence
- 7Connect production instructions, actual results and lot disposition
- 8Map legacy record labels into a navigable evidence model
- 9Link complaints, investigations, actions and supplier evidence
- 10Reconcile interfaces and recover exceptions without losing provenance
- 11Prepare for FDA's current inspection approach and retrieval questions
- 12Review scope, references, record links and decision ownership
How does 21 CFR 820 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
0121 CFR 820: FDA Quality Management System Regulation (QMSR)
What 21 CFR 820 means today: the current QMSR
21 CFR 820 is FDA's Quality Management System Regulation (QMSR), the current good manufacturing practice regulation for medical devices. The QMSR became effective on February 2, 2026, as stated in FDA's QMSR introduction. From this article's October 2026 perspective, it is the rule currently in effect—not an approaching transition.
This reference focuses on navigating current Part 820 and organising operational records: finding the relevant provision, connecting it to manufacturing evidence, and identifying who owns the resulting decisions. For the broader regulatory context, see the FDA QMSR overview.
Four categories remain distinct throughout:
- Binding regulatory requirements: statements of legal duties, linked to the relevant provisions.
- FDA explanatory material: the agency's explanations of the rule and its administration, identified separately from regulatory text.
- Recommended industry practice: suggested ways to organise evidence, reconcile records and assign review responsibility—not prescribed forms.
- Illustrative software support: examples of how records might be organised digitally, kept separate from legal requirements and authorised people's approval decisions.
Read the practical examples as implementation choices rather than regulatory wording. A useful record model connects the applicable requirement, the activity performed, the supporting evidence and the responsible reviewer without treating a preferred folder layout or file name as law.
02Navigate current Part 820 and its incorporated framework
Current Part 820 is short. In the current eCFR text, Subpart A contains §820.1 (Scope), §820.3 (Definitions), §820.7 (Incorporation by reference) and §820.10 (Requirements for a quality management system); Subpart B, Supplemental Provisions, contains §820.35 (Control of records) and §820.45 (Device labeling and packaging controls), with §§820.20–820.30 and §820.40 reserved. The detailed quality-system clauses come from ISO 13485, which §820.7(b) lists as "IBR approved for §§ 820.1 , 820.3 , 820.10 , 820.35 , and 820.45 ."
| Section | Role in the current rule | Key point |
|---|---|---|
| §820.1 Scope | Who is covered and how Part 820 relates to other rules | Where Part 820 conflicts with a requirement specifically applicable to the device elsewhere in the chapter, the specific requirement supersedes. |
| §820.3 Definitions | Vocabulary | ISO 13485 and Clause 3 of ISO 9000 definitions apply, except where §820.3(b) specifies otherwise. |
| §820.7 Incorporation by reference | Names the two standards | ISO 9000:2015 Clause 3 and ISO 13485:2016. |
| §820.10 QMS requirements | The core duty | Document a QMS that complies with ISO 13485 and Part 820, plus listed FDA-specific links, design-and-development scope and life-supporting device traceability. |
| §820.35 Control of records | FDA additions to record control | Specific content for complaint and servicing records, UDI recording and confidentiality marking. |
| §820.45 Labeling and packaging | FDA additions to production control | Documented procedures for labeling and packaging integrity, inspection, storage and operations. |
FDA’s incorporation-by-reference explanation states that QMSR incorporates ISO 13485:2016 and clause 3 of ISO 9000:2015. FDA describes ISO 13485 as the foundational quality management system framework for medical device manufacturers; clause 3 of ISO 9000 supplies terms and definitions supporting a common understanding of quality management system fundamentals. These references therefore have different roles: the quality-system framework and its supporting vocabulary.
FDA also states that when an ISO 13485 clause conflicts with the FD&C Act or its implementing regulations, the Act and/or those regulations control. Incorporation does not put the standard above US law. Keep this hierarchy in view when using the separate QMSR vs ISO 13485 comparison.
When reading the final rule, distinguish its codified regulatory text from its explanatory preamble: use the former for the rule’s provisions and the latter for explanation. Here, §820.3’s cross-reference to §820.7 serves only as a navigation point. For broader context, use the FDA QMSR overview entry; for implementation planning, use the ISO 13485 readiness guide.
03FDA-specific requirements that sit alongside ISO 13485
§820.10(a) states the central duty directly: a manufacturer must "Document a quality management system that complies with the applicable requirements of ISO 13485 (incorporated by reference, see § 820.7 ) and other applicable requirements of this part". §820.10(b) then ties specific ISO 13485 clauses to other FDA rules. For identification, "the manufacturer must document a system to assign unique device identification to the medical device in accordance with the requirements of part 830 of this chapter". For traceability, the manufacturer "must document procedures for traceability in accordance with the requirements of part 821 of this chapter , if applicable." Reportable complaints link to part 803, and advisory notices to part 806.
§820.10(d) adds a condition-based duty. Manufacturers of devices that support or sustain life, where failure to perform when properly used "can be reasonably expected to result in a significant injury, must comply with the requirements in Traceability for Implantable Devices, Clause 7.5.9.2 in ISO 13485". Whether a product falls into this group is a classification judgement the manufacturer should document, not something to assume from the product family name.
§820.35 adds content to specific records. Complaint records for complaints that are reported, investigated or that the manufacturer chooses to investigate must include items such as the name of the device, the date received, any UDI or UPC, complainant details, the nature of the complaint, corrective action and any reply. Servicing records must capture, at a minimum, the device, any UDI or UPC, the date, who serviced it, the service performed and test data. §820.35(c) states that "the UDI must be recorded for each medical device or batch of medical devices."
§820.45 requires each manufacturer to "document and maintain procedures that provide a detailed description of the activities to ensure the integrity, inspection, storage, and operations for labeling and packaging". Under §820.45(a), labeling and packaging must be examined for accuracy before release or storage where applicable, including the correct UDI, UPC or other device identification. In practice, these are the duties most likely to need explicit procedures and record fields even in a site already certified to ISO 13485.
04Check applicability by product, activity and US regulatory context
FDA's applicability explanation states that QMSR applies to finished-device manufacturers intending to commercially distribute medical devices. FDA describes a finished device under 21 CFR 820.3(a) as a device or accessory suitable for use or capable of functioning, whether or not packaged, labelled or sterilised. Those processing steps therefore do not determine finished-device status.
The FDA-described positions below explain regulatory applicability; the suggested scope records are implementation practice, not additional legal requirements.
| Product or situation | FDA-described position | Practical scope record |
|---|---|---|
| Finished devices | Manufacturers intending commercial distribution are within QMSR's stated applicability. | Product identity, intended use, distribution intent and manufacturing activities. |
| Accessories | FDA identifies accessory manufacturers as subject to QMSR. | Accessory determination and supporting rationale; assess component suppliers separately rather than extending this statement to all suppliers. |
| CGMP-exempt finished devices | Exemption does not remove complaint-file or general-records obligations: see FDA's explanation of 21 CFR 820.35. | Exemption basis, retained record responsibilities and accountable owner. |
| IDE devices | Not exempt from design and development requirements: see FDA's explanation of 21 CFR 820.10(c). | Investigational status and the design-and-development scope boundary. |
| Mixed-product manufacturing site | Apply FDA's device applicability explanation to the device products, rather than treating the site name as the scope decision. | Separate product-and-market entries for device and non-device operations. |
For mixed device, pharma, supplement, food or chemical operations, maintain a product-and-market scope register. As a practical method, record each product family, destination market, site activity, applicability rationale, exemption basis where relevant, responsible reviewer and review date. Identify shared processes without assuming that one product's regulatory status governs another.
Have authorised regulatory and quality personnel review uncertain classifications before using the register to set procedures or record responsibilities. Keep non-US market assessments separate; this US scope decision is not an equivalence finding. For the broader framework, see the FDA QMSR overview.
05QMSR, former QSR and ISO: distinguish the neighbouring terms
These terms identify different things: a regulatory citation, its current or historical title, and standards used within the framework. Keep those roles distinct when updating procedures and requirements indexes.
| Term | Meaning in this article | Boundary |
|---|---|---|
| 21 CFR Part 820 | The regulatory citation | Identifies the US regulation, not an ISO standard. |
| QMSR | Part 820’s current title | Use for the current regulatory framework. |
| Former QSR | Historical Quality System Regulation terminology | Use only for historical orientation. |
| ISO 13485:2016 | The incorporated framework | Read alongside Part 820’s other applicable requirements under § 820.10(a). |
| ISO 9000:2015, clause 3 | The referenced terminology source | Terms and definitions; see § 820.7. |
For the broader comparison, see QMSR versus ISO 13485. The practical document-control task here is narrower: move the current requirements index away from a former-QSR-only structure.
As recommended document-navigation practice, maintain separate fields for:
- Current regulatory reference: the applicable current provision or incorporated requirement.
- Historical reference: the former QSR reference, explicitly marked historical.
- Internal procedure reference: the controlled procedure that addresses the current requirement.
Keep former section numbers out of the current-reference field. A historical cross-reference helps people locate familiar material; it does not substitute for a current applicability decision. Review each mapping against the activity covered by the procedure rather than assuming that an old heading establishes a one-to-one match. This preserves useful navigation without making the legacy index the basis for current decisions.
06Connect design changes, risk decisions and lifecycle evidence
FDA's QMSR explanation describes the incorporated framework as promoting consistency in design, production and lifecycle controls across global markets, and specifically requiring risk management. That explanation provides context; the record-handling workflow below is recommended engineering practice, not a reconstruction of ISO design clauses.
Recommended linked-record workflow
Use this diagram as a recommended record-handling sequence, not a mandated regulatory process or a software capability. Decisions can occur at several points; the arrows show evidence connections, not permission to proceed.
Product scope → design revision → related risk assessment → supporting results → production instructions → subsequent quality events → authorised decisions.
Assign a stable design-change identifier and use it to connect both revised records and records reviewed but left unchanged. For each connection, retain the relevant revision, review outcome, reviewer and decision rationale. An unchanged instruction then has a visible assessment history rather than appearing to have been overlooked.
This supports requirements traceability: a reviewer can follow the change from its purpose through risk reasoning and supporting results to the instructions used in production. Link later quality events back to that identifier where relevant, so an investigation can recover the earlier assumptions and decisions without relying on matching document titles.
Worked case: eight linked records
Assume one design change affects eight linked records. The counting unit is a record—not a test or a device unit. Assume the revised and unchanged groups have completed their documented review paths:
- Five records are revised and reviewed.
- Two records are reviewed and unchanged, with reasons recorded.
- One record remains unresolved.
Completed review paths: 5 + 2 = 7 records. Reconciliation: 7 completed + 1 open = 8 linked records. Keep the unresolved record visible with its owner and outstanding question. This count describes review status only; it does not establish design acceptability. Authorised people assess the evidence and document the decision, including how the unresolved issue affects any proposed next step.
- Set scopeRecord the product, intended market and responsible owner.
- Link DesignConnect the current revision to risk and design evidence.
- Control productionUse approved instructions for the identified build.
- Record outcomesAssociate results and exceptions with the device or lot.
- Assess exceptionsDocument the investigation, affected records and proposed action.
- Review dispositionAn authorised person records the decision and its basis.
- Retrieve HistoryFollow identifiers across revisions, complaints and completed actions.
07Connect production instructions, actual results and lot disposition
As recommended manufacturing-record practice, organise production evidence around an identifiable build or lot. The chain below is an operational model, not a prescribed Part 820 record schema. Its purpose is to let a reviewer connect intended work, actual execution and the resulting disposition without reconstructing events from disconnected documents.
Keep instructions and execution evidence distinct
- Identify the product revision and build or lot identifier; use consistent production context tagging across related records.
- Link the applicable instructions and the specific revision used for that build. A link that always opens the latest document cannot establish which instructions governed earlier work.
- Connect input lots and equipment references to recorded process results, including the units and execution context needed to interpret those results.
- Link exceptions to affected units or identifiable groups, and connect their resolution to the recorded disposition.
Instructions describe expected work; execution records show what actually happened. Preserve that distinction through document control. Supporting process evidence can include relevant equipment records or process studies, linked with enough context to explain their relevance. This operational category does not specify validation methods, thresholds or frequencies.
Worked case: reconcile quantities before considering release
Assume a lot contains 240 individual devices and three mutually exclusive count categories: 216 conforming units, 18 held units and six rejected units. The check is 216 + 18 + 6 = 240 devices. This demonstrates quantity reconciliation, not a release decision. In-process reconciliation helps expose missing or duplicated counts.
Authorised people decide disposition and release; record completeness and software status do not make those decisions.
| Production failure | Concrete control |
|---|---|
| Overwritten instruction reference | Preserve a revision-specific link and its accessible content. |
| Unexplained quantity difference | Reconcile counts against the lot total; document and resolve discrepancies. |
| Hold detached from affected units | Link the hold to unit identifiers or a clearly bounded group and its disposition record. |
08Map legacy record labels into a navigable evidence model
Current Part 820 has no separate sections for the design history file (DHF), device master record (DMR) or device history record (DHR); those requirements belonged to the former Quality System Regulation. Record expectations now flow from ISO 13485 clauses through §820.10 and the FDA additions in §820.35. The final rule's discussion refers to the ISO 13485 "medical device file" concept rather than redefining it, so the practical task is to show where the content an inspector would previously have found in a DHF, DMR or DHR now lives.
Use DHF, DMR and DHR as legacy retrieval labels in an internal index. The mapping below is an implementation convention, not an official one-to-one legal equivalence, a quotation from ISO 13485 or a list of ISO-mandated replacement names. Renaming folders is not evidence of conformity; this approach does not call for deleting historical files.
| Legacy label | Practical retrieval question | Proposed linked evidence | Mapping caution |
|---|---|---|---|
| DHF | How did this design develop? | Design plans, reviews, supporting studies and change decisions; see design history file. | Preserve revision context, not just a folder alias. |
| DMR | What defined the product and manufacturing instructions? | Product specifications, approved methods and electronic work instructions. | Distinguish today's revision from the revision used. |
| DHR | What happened during this particular build? | Lot execution records, actual results, exceptions and disposition decisions. | Link actual execution to its governing instructions. |
Keep historical references separate from current requirements
Create a crosswalk containing legacy_record_id, current_record_id, product_id, record_revision, current_requirement_ref, historical_reference and owner_id. A historical_reference explains the citation under which a record was originally organised; current_requirement_ref identifies the current basis against which its relevance is assessed. Do not copy an old citation into the current-reference field merely because the record remains useful. Assign owner_id to the person responsible for reviewing the mapping, and allow multiple linked records where a single legacy file covers several subjects.
Connect records through identifiers
An illustrative model has five entities: product definition, evidence record, production lot, quality event and decision. Give each a stable identifier. Link a lot to its product-definition revision and execution evidence; link a quality event to affected lots and supporting evidence; link a decision to the records considered and the authorised person making it. These relationships can span applications and controlled paper records rather than assuming one repository. An electronic release record can be one retrieval destination within that model.
Add source_system and source_record_id to preserve origin, created_at for creation time, effective_revision for the applicable version, review_status for review state and superseded_by for the successor record. Keep the original identifier resolvable after migration or revision.
Test retrieval with one question: which product revision and instruction revision governed this lot, which supporting records were considered, and where is the resulting decision? The answer should traverse identifiers to readable records, not depend on someone's memory of folder names.
Product Definition
Identifies the product and applicable revision.
- product_id
- product_revision
- market_scope
- owner_id
Evidence Record
Connects evidence to its source.
- record_id
- record_type
- source_record_id
- record_revision
Production Lot
Connects execution to product definition.
- lot_id
- product_id
- product_revision
- instruction_revision
Quality Event
Connects an issue to affected production.
- event_id
- lot_id
- event_type
- investigation_status
Decision
Identifies the decision and accountable reviewer.
- decision_id
- subject_record_id
- reviewer_id
- decision_status
09Link complaints, investigations, actions and supplier evidence
With the complaint-file scope point covered above in mind, use the following as a recommended operational workflow, not regulatory definitions or a prescribed sequence. Keep the originating event visible as evidence develops; do not treat every complaint as requiring the same action.
- Complaint: retain the incoming report and its context without treating an allegation as a confirmed defect.
- Nonconformance: separately identify a departure from an applicable specification or process requirement when supported by the evaluation.
- Investigation: track the questions, evidence, findings and unresolved issues used to assess the event.
- Corrective action: link a cause-directed response through the manufacturer’s CAPA workflow when the evaluation supports that route.
For each incoming quality event, connect the device or lot identity, relevant device revision, available production evidence, investigation status, supplier involvement, proposed action and subsequent review. Record uncertainty explicitly when identity or revision is not yet established. Preserve links to any resulting design, supplier or production change, including the decision owner and rationale. Where appropriate, connect the action to an effectiveness check rather than equating implementation with a successful outcome.
Keep supplier-supplied evidence separate from the manufacturer’s evaluation and decision. Give each external attachment a source identifier and an identified local reviewer; retain the reviewer’s assessment alongside, rather than inside, the supplier’s statement.
Three closure traps
- Event closed, action untracked: retain a linked action owner, status and review route even when event handling is complete.
- Wrong revision linked: check the evidence against the affected device configuration, not merely the latest revision.
- Supplier attachment received, review assumed complete: distinguish receipt from local evaluation and an authorised decision.
10Reconcile interfaces and recover exceptions without losing provenance
ERP, MES, laboratory, document-control and quality-system connections are possible architecture choices, not prescribed applications. The following is a vendor-neutral practice pattern, not a statement of Part 820 requirements or any product’s capabilities. Choose connections around the records people need to reconcile, rather than assuming every system must exchange every record.
Preserve identity and context
Map source_system, source_record_id, source_event_id, product_revision, lot_id, event_time, received_at and reconciliation_status across interfaces. Distinguish when an event occurred from when it arrived. Define identifier namespaces and reference checks so matching text does not silently link unrelated records. Use production context tagging to keep revision and lot associations explicit.
Worked case: messages are not devices
Assume 60 incoming messages include four duplicate replays. Deduplication leaves 56 unique events. Two unique events lack a valid lot reference, leaving 54 linked events and two unresolved events. The reconciliation is 54 + 2 + 4 = 60 incoming messages: linked events, unresolved events and duplicate replays respectively. These units are messages and events, not devices.
A successful import establishes receipt or processing, not that the referenced revision or lot is correct; semantic reference checks remain necessary within this pattern. Release authority remains with authorised people, as covered in the production section.
11Prepare for FDA's current inspection approach and retrieval questions
On February 2, 2026, FDA stopped using the Quality System Inspection Technique (QSIT) for device inspections and began using the inspection process described in Compliance Program 7382.850, Inspection of Medical Device Manufacturers. See FDA's QMSR inspections explanation. This is FDA's description of its inspection approach; the exercise below is recommended internal preparation, not a reproduction of that program or a prediction of inspection outcomes.
Rehearse a connected retrieval
Choose one device or lot identifier. Ask someone other than the record's author to follow its links, rather than relying on the author's memory or a prepared folder:
- Find the applicable product revision and instructions used for that build.
- Retrieve execution evidence, such as the linked batch record, and associated exceptions.
- Follow relevant quality events to their investigations, decisions and authorised decision-makers.
- Compare source records with exported copies; use an audit trail review workflow where needed to explain differences.
Use the earlier design-change case as a prompt: can the reviewer connect the affected build to the change decision? For the reconciliation case, can the reviewer trace the exception through recovery to the reconciled record? Retrieve the supporting links rather than repeat the calculations.
Fix navigation failures
- Historical-citation-only index: add product, process and current-reference routes so old section numbers are not the only entry point.
- Unlinked records: resolve records that exist but cannot be connected to the device or lot selected for the exercise.
- Unexplained export differences: document why source and exported records differ and preserve their relationship.
Record each retrieval gap as a named action with an owner and review date. These are internal management choices, not FDA-mandated intervals or forms. Check the repaired link at review; use the separate ISO 13485 readiness guide for broader preparation.
12Review scope, references, record links and decision ownership
Use this recommended-practice checklist to close an internal review. It is not an exhaustive compliance determination or certification test. Record gaps as assigned actions rather than treating a completed checklist as proof of compliance.
- Scope recorded: identify the products, markets, sites and activities covered, with a rationale for exclusions.
- References separated: distinguish current governing references from historical citations retained in legacy procedures or records.
- Crosswalk owned: assign owners to record mappings, including ambiguous legacy labels and broken links.
- Build traceable: sample one completed build and follow its instructions, actual results, exceptions and disposition decision.
- Interface exceptions visible: identify failed, duplicate or unmatched transfers and who owns their resolution.
- Quality events identifiable: locate unresolved complaints, investigations and actions linked to the sampled product or build.
- Decision authority documented: identify who may approve changes, resolve quality issues and authorise release.
For each gap, retain the affected record, responsible owner and next review point. Use the ISO 13485 readiness guide for a broader implementation assessment; use the FDA QMSR overview when the review raises questions about the surrounding framework.
Frequently asked questions
Q.How should a site making both devices and non-device products organise its Part 820 records index?+
As a records-management practice, organise the index by product family and activity, with an explicit applicability field rather than a single site-wide “Part 820” label. Identify the record owner, governing procedure, repository and relevant product identifiers. Index shared records, such as equipment maintenance, once and link them to affected product families. Keep the rationale for each scope decision separately reviewable. A shared QMS can support this arrangement without treating every product as subject to the same requirements.
Q.What changes in the scope assessment when the product is an accessory rather than the primary device?+
FDA explains in the final rule’s accessory discussion that accessories are finished devices and therefore subject to QMSR. The scope assessment should consequently address the accessory itself, rather than assuming the primary device’s records cover it. As a practical indexing approach, identify the accessory’s product identifier, configurations, manufacturing activities and interfaces with the primary device. Use requirements traceability to distinguish shared evidence from accessory-specific evidence and record the rationale for that allocation.
Q.Can older records retain DHF, DMR and DHR names within a current QMSR records map?+
As a document-management approach, preserve older DHF, DMR and DHR titles and identifiers, and add a cross-reference to the current record categories used by the site. Avoid treating a renamed folder as evidence that its contents satisfy current requirements. Map records by purpose and content, including their product coverage, versions and relationships to other evidence. The DHF overview provides terminology context; the working map should make each legacy record discoverable without rewriting its historical identity.
Q.How should records spanning February 2, 2026 be indexed without obscuring their original context?+
For a record set spanning February 2, 2026, use separate index fields for the activity date, record creation date, applicable procedure revision and any later mapping date. Preserve the original identifier and approval history. If work crosses that date, link the relevant procedure versions and document how the site handled the transition rather than assigning the whole file a new historical context. This is a practical document-control approach, not a rule that every existing record must be reissued.
Q.How can a US-facing team adapt a global ISO-based procedure when an FDA requirement differs?+
Use a controlled US supplement or an explicitly identified US branch within the global procedure. As an implementation practice, record the requirement assessed, affected activities, operational difference, responsible owner and resulting records. Have authorised reviewers resolve conflicts before issuing the revised instructions; avoid leaving operators to choose between inconsistent documents. Route the adaptation through change control, including an assessment of related forms and training. This describes procedure design, not a conclusion that a particular global procedure meets FDA requirements.
Q.What should a linked record set show when a complaint investigation is still open?+
As a review practice, make the open status unmistakable and connect the complaint to the affected product identifiers, investigation owner, available evidence, outstanding questions and next review action. Separate confirmed findings from hypotheses, and distinguish completed actions from proposed actions. Record interim decisions with their authors and dates so reviewers can understand what was known at each stage. If a CAPA is linked, show its separate status rather than allowing that link to imply the complaint investigation is complete.
Q.How should supplier records held in an external system be referenced and reviewed locally?+
A practical local index should identify the external repository, supplier record identifier, version or date, record owner and access route. Record what the local reviewer examined, when it was reviewed and which purchasing or quality decision it supported. If the external record can change, identify the reviewed version or retain a controlled snapshot where appropriate. Plan for broken links and lost access. These supplier-management practices make the basis of local decisions retrievable without assuming that an external link alone is sufficient.
Q.How can a reviewer distinguish approval of an instruction from disposition of a particular lot?+
Use separate approval objects and labels. As a records-design practice, instruction approval should identify the authorised document version and its intended use; lot disposition should identify the specific lot, evidence reviewed, unresolved issues and the authorised person’s decision. Link the lot record to the instruction version actually used, not simply the latest version. An electronic release record should make that distinction visible: an approved instruction is not itself a decision to release the lot produced using it.
Primary sources
Further reading
Explore this topic
21 CFR 820 sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Master and executed records that prove a batch or device was made to spec.
Device-specific rules, submissions and the standards that bind them.
Want to see how 21 CFR 820 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
