Table of contents
At a glance
What are predicate rules, and how do they determine Part 11 scope?
Predicate rules are requirements outside Part 11 that require records or submissions. Examples include drug CGMP requirements in 21 CFR 211 and medical device requirements in Part 820 (QMSR). Part 11 addresses electronic implementation and certain electronic submissions to FDA. It does not impose blanket retention on every company file. Section 11.1(b) excludes paper records merely transmitted electronically. There are also express exceptions for certain food and animal feed records or related signatures. Determine the source requirement, extent of the record and actual use for each case.
- From activity and record type to the specific responsible position.
- Consider both paper designation and actual electronic usage jointly.
- Treat an unexplained mandatory source as an open decision, not as an automatic exception.
1. Describe the regulated activity first.
A laboratory result, a batch protocol, and a travel expense reconciliation may reside within the same IT environment without fulfilling the same regulatory function. Therefore, identify the product area, activity, responsible operation, and affected decision upfront. The presence of a US customer or a server location does not substitute for this classification.
The examples in this article assume an appropriate Drug-CGMP scope for human medicinal products. 211 is not automatically applicable to every research or medical device application. For other FDA areas, the relevant basis must be determined; the method remains applicable, but the example paragraphs do not necessarily apply.
2. Look for the required content, not the filename
The predicate rule may require certain information without specifying a particular software report. §211.194 addresses laboratory records, including sample receipt, methods, data, calculations, and review. §211.188 specifies information required for batch manufacturing and control. The filename "Analysis Report" does not yet indicate whether all required contents are fully included.
Therefore, initially define the professional record type. Then assign the actual components: database entries, paper sheets, files, or required supplementary information. A record type may be distributed across multiple technical objects. Conversely, a report may consolidate several mandatory contents.
3. Combine mandatory source and technical storage locations
The following internal work aid presents an example of a record inventory. It is not a complete list of all medicinal product obligations. The activities and applicability are explicitly assumed for the three regulated lines; for the fourth line, the assessment remains open.
| Record-Art | Mandatory source and required content | Actual use | Scope decision |
|---|---|---|---|
| Sample testing: Probe L-17 | §211.194(a): complete test validation evidence | Electronic data are evaluated; a signed report complements them. | Electronic record scope including all necessary components to be captured. |
| Batch documentation Batch B-8 | §211.188: Manufacturing/Testing Information | Electronic recordkeeping supports the process validation. | Use this as the basis for the Part 11 assessment. |
| Standard solution S-4 | §211.194(c): Complete records of testing and standardization | Database record is used for laboratory work. | Assign required content and electronic usage. |
| Technical Import Log I-9 | Mandatory source initially unresolved | Possible only evidence of a failed data import. | Assess significance; not solely exclude based on log file entries. |
4. Verify actual usage in addition to storage placement
The FDA Scope Guidance distinguishes between a sufficient paper record that actually supports the regulated activity and electronic records that are used for that purpose. Therefore, the deletion of a record does not automatically satisfy Part 11 requirements. Conversely, not every additional file stored is, by itself, a Part 11 record.
Query the department regarding the actual decision pathway: Is the decision filtered, recalculated, or an electronic status verified within the system? What information does the decision-maker view exclusively there? Document such usages. A SOP that designates paper as the primary evidence must align with actual practice and the required content.
5. Submissions and work files are distinguished
§11.1 also encompasses certain electronic submissions to the FDA under the aforementioned laws, even if individual records are not explicitly referenced in FDA regulations. Therefore, a consideration limited exclusively to retention-required internal records would be incomplete. Additionally, the applicable assumptions and conditions relevant to the specific submission must be clearly defined.
The Guidance distinguishes a file prepared solely for the purpose of submission preparation from the actual submission documentation. Such a working file may still be relevant if it is required for retention independently, based on a predicate rule. The article does not specify current formats or transfer methods for a particular submission.
6. Investigate the directory using targeted questions
Example: A team has assigned three record types as relevant and initially left the import log open. During process walkthrough, it is observed that the log only documents which of the twelve intended inspection results were actually imported. The results report contains eleven values. This finding must be reflected in the content and scope assessment.
A value is therefore missing. This does not yet prove whether data were lost, a valid exclusion exists, or the original required quantity was incorrect. The missing relationship will be investigated before the assignment is considered complete.
| Follow-up question | Observation in this example | Consequence |
|---|---|---|
| Is the required content fully assigned? | Eleven out of twelve expected values reported in the report. | Investigate missing value and associated import process. |
| Is a purportedly technical record functionally necessary? | Import log explains success or failure for each result. | Include necessary log content in the record, if necessary. |
| Does the paper definition align with practice? | The auditor additionally verifies electronic import statuses. | Reflect the actual electronic use in the scope determination decision. |
| Is the decision permanently traceable? | Source available, responsible party and rationale missing. | Complete the decision with the responsible role and rationale. |
7. Record retention, storage, and enforcement to be handled separately
The obligation to keep a record and its retention period are coherent but different questions. §211.180 contains, for example, requirements for storage and availability for its scope. Part 11 does not provide a universal deadline for all company data. Therefore, a comprehensible link to the appropriate time limit decision should exist in the directory.
The FDA Enforcement Discretion of 2003 does not waive the predicate rules. An explicit limitation regarding Part 11 controls is not equivalent to required documentation. Similarly, a narrow interpretation of Part 11 applicability should not be construed as a general statement authorizing the FDA to review any particular documentation during an inspection.
8. Keep the register useful for decisions
For a small and medium-sized enterprise (SME), a concise inventory with clear sources and defined responsible roles is generally more helpful than an unannotated compilation of regulatory references. The technical department outlines the purpose of the data; IT details storage arrangements and dependencies; and the responsible quality or regulatory function evaluates the regulatory alignment.
Add new insights related to process changes, other data formats, or new uses. Open items require a specific clarification task. A formally completed field containing the word "unknown" does not protect the record and does not constitute a decision regarding its further use.
- State the activities and product/regulatory scope.
- Determine the Record-Art and fully compliant mandatory content.
- Document a specific primary location with a section.
- Check electronic usage, paper components, and submission reference.
- Essential data components and record retention requirements are linked.
- Assign storage and access through appropriate sources.
- Record unresolved questions, the responsible owner and what would trigger a reassessment.
Project experience and collaboration
Start with the record and the rule that requires it
With process and regulatory owners, we start with one type of record, such as a laboratory or batch record. Which information is required, and where is it actually held? A clear data path may need only more precise mapping. Where several systems contribute, we connect the components and open questions in a records inventory. Your designated experts make the binding assessment. We help translate it into testable requirements for electronic use.
Frequently asked questions about Predicate Rules
What does Predicate Rule mean in the context of Part 11?
These are the requirements outside of Part 11, governing the retention of records or the provision of information. This includes, for example, 21 CFR 211 for pharmaceutical cGMP and Part 820 (QMSR) for medical devices. Part 11 addresses the electronic implementation. Therefore, the evaluation begins with the required record and its intended use, not with the functional name of a software system.
Is a US customer justification sufficient?
No. A customer- or market-related trigger may justify an investigation, but it does not establish a specific record retention obligation. Assign activities, relevant FDA regulatory areas, and documentation requirements. Only thereafter can the electronic use be appropriately evaluated.
Must the regulation require our specific report to be referenced by name?
No. It can describe the required content while your organization maintains it across various reports or system objects. Section 211.194 serves as an example. What is decisive is whether the necessary information is fully and reliably represented.
Sources: [3]
Is a directory of deployed applications provided?
An application registry is helpful but does not define every record obligation. Within an application, different purposes may exist. Supplement with record types, responsible parties, and actual usage. This enables identification of which functions and data are relevant to the considered audit evidence.
Are technical logs generally exempt?
Does a signed printout make all electronic data optional?
No. Verify that the record scope fully encompasses the required content and that the activity actually relies on it. If electronic data are additionally used for regulated decisions, the electronic record scope cannot be eliminated solely by the printout.
Sources: [6]
Are all files required for preparing an FDA submission automatically considered Part 11 records?
Does Part 11 specify the retention period?
Does the absence of Part 11 applicability mean that the FDA may not review the record?
How do we deal with an unknown source of duty?
Document the open question, the relevant usage, and the responsible clarification task. Review available primary sources and actual data pathways. An empty source field neither confirms applicability nor establishes an exception; the significance for the process must not be overlooked until clarification is completed.
Sources and review date
Source date: 7 October 2026. eCFR notice period until 5 October 2026; separate consideration of binding regulatory text and non-binding FDA Guidance. Examples and tables are internal work aids and do not represent completed product testing.
- 21 CFR §211.1 – ScopeeCFR notice until 05.10.2026; Scope: Drug-CGMP.
- 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
- 21 CFR §211.194 – Laboratory recordseCFR notice until 05.10.2026; paragraphs (a)(1)–(8), (b)–(e).
- 21 CFR §211.188 – Batch production and control recordseCFR notice until 05.10.2026; paragraphs (a), (b).
- 21 CFR §211.180 – General requirementseCFR availability up to 05.10.2026; specifically (c), (d) regarding availability and copies.
- FDA: Part 11 – Scope and ApplicationFinal guidance. The PDF is dated August 2003 and the status page September 2003. See sections I and III.A–C.
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and AnswersFinal Guidance December 2018; in particular Questions 1–3, 9–12, 14 and 17.
Sources checked: .
Jointly develop the specific evidence process
We support you in aligning documentation obligations and actual data usage for your process, resulting in a clear scope and targeted validation responsibilities for your team.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

