Electronic records: establish Part 11 applicability
Establish electronic-record scope and intended use before assessing MES Part 11 controls. Prepare questions for qualified quality and regulatory staff.
Establish which electronic records are in scope before evaluating Part 11 features. FDA’s scope guidance connects applicability to underlying record requirements and how electronic records are used; buying an MES does not by itself answer that question. Involve qualified quality and regulatory personnel.
Start with the record and intended use
Inventory the records the proposed workflow creates, changes, reviews and retains. Identify the applicable underlying requirement and how the organization relies on each record. Distinguish operational convenience data from records used for regulated activities. Do not decide applicability from a software brochure or from whether a screen contains a signature button.
Have responsible specialists document the determination and its basis. This guide cannot decide it for a particular manufacturer or product. Where uncertainty remains, preserve the question and obtain appropriate advice. Avoid the opposite blanket claim that all electronic manufacturing information is automatically within the same regulatory scope. The actual record, obligation and use matter.
Build a record-use matrix
| Matrix field | What to document |
|---|---|
| Record type | The specific production or quality record |
| Underlying basis | Requirement assessed by qualified personnel |
| Intended use | How decisions rely on the electronic information |
| System boundary | Where the record is created, changed and retained |
| Responsible owner | Who approves the scope and controls |
| Evidence plan | What tests and procedures are needed |
Include interfaces and attachments where they form part of the record. A record can be distributed across applications even if users experience one workflow. The matrix should expose that boundary so the organization can assess completeness, access and retention rather than focusing only on the MES user interface.
Translate scope into tested workflows
Once applicability and requirements are established, define how the configured workflow will meet them. Test identity, authority, record creation, correction, review and retrieval as appropriate to the assessed use. Connect requirements to test cases and operating procedures. The appropriate evidence and assurance approach must come from the responsible organization and qualified advisers.
Use representative records with exceptions. A completed standard order may not reveal how a correction is approved or how an attachment remains associated with the right revision. Preserve configuration and version context. A supplier capability can support the process, but the buyer still needs to evaluate the actual implementation and the procedures people will follow.
Examine signatures without assuming a generic meaning
If electronic signatures are part of the intended use, have specialists define what is being signed, by whom, for what purpose and under which requirements. Distinguish a simple acknowledgement, a supervisor approval and a signature with a particular regulated meaning. Their appearance on a screen does not settle their status.
Test how the signed record is identified and retrieved and what happens after a correction or revision. Ensure the organization’s approved process addresses role authority and training. Do not invent legal equivalence from a button label or a supplier claim. Ask for documented behavior and have qualified personnel determine whether it is suitable for the actual use.
Plan changes, retention and retrieval
The record boundary can change when an interface, report, attachment type or workflow is modified. Include record impact in change assessment. Determine whether existing tests remain relevant and what additional evidence is needed. Preserve the prior configuration context when necessary to interpret historical records.
Retention is not established by selecting a convenient default period. Have the responsible specialists determine applicable obligations and retrieval expectations. Test a historical record with its relationships, attachments and correction context. Assess export and archive behavior as well as normal application access. A system that can store data is not automatically proven to preserve an interpretable record for the required purpose.
Keep procurement claims bounded
Ask suppliers to identify the capabilities, documentation and services they provide for the proposed use. Require them to distinguish standard functionality, configuration, custom development and buyer procedures. Avoid accepting a blanket Part 11 compliant statement as the entire evaluation. The claim needs a defined scope and evidence.
Record unresolved questions before contract award and pilot approval. Quality and regulatory personnel should review the final record-use matrix and evidence plan. This site offers no legal determination, certification or professional validation service. Its purpose is to help buyers ask precise questions and find the official guidance, not to replace the accountable assessment required for their products and operations.
Take this to the working meeting
Prepare a short scope workshop using three fictional record types: an informal production note, an operation result used for disposition, and an approval attached to a controlled record. Ask the responsible specialists to explain their different uses and the basis for any applicability determination. Do not assign the same controls automatically to all three. Record unresolved questions and the evidence needed to answer them.
FAQ
Does every MES need Part 11 controls?
Applicability depends on the records, underlying requirements and use. Qualified personnel should make and document the determination.
Can a vendor guarantee our compliance?
A supplier can provide capabilities and services. Your organization must assess its configured workflow, procedures and applicable obligations.
Is an electronic acknowledgement a regulated signature?
Not automatically. Determine its intended meaning and applicable requirements with qualified quality and regulatory advice.
Continue your decision
- MES risk review: test the failures before launch
- MES and OT security: define the trust boundaries
- Lot genealogy: prove the trace in both directions
- MES outage recovery: rehearse the return to service
Use the pilot readiness to document your own inputs. Compare operating models on the comparison page.
Sources and scope
- FDA Part 11 scope and application guidance — Official scope guidance for electronic records and signatures. Applicability depends on records and use; the worksheet is not legal advice.
Examples are hypothetical and are not measured customer results, supplier quotations, or evidence of professional review. Prepared on October 30, 2026; confirm current requirements with the relevant official body and your responsible specialists.
