Locate the authoritative record
Identify the system and the intended use before reviewing a delivery event.

21 CFR Part 11 · Audit-trail review
A download record can show that a reviewer collected a file. To assess a regulated electronic record, trace its creation, changes and review in the system responsible for that record.
Identify the system and the intended use before reviewing a delivery event.
Ask how a reviewer can inspect the earlier entry and the event associated with the change.
Test whether the evidence explains the record history as well as the external delivery.
Use a sample record and its exported copy. Have quality assurance establish which events each system records and how reviewers connect them.
Identify the individual or system associated with the recorded event.
Determine whether the event describes a change to the source record or delivery of an exported copy.
Read the timestamp in context, including time zones where the systems differ.
Ask a reviewer to reconstruct a sample change from the information retained in the record system.
Use recipient and delivery activity to answer questions about the transfer.
Discuss the available MX exchange records, their scope and how your team would use them.
Assess the source system’s history against the record’s intended use and applicable requirements.
Evaluate these requirements within the system and procedures governing the electronic record.
Part 11 applicability depends on the records and underlying FDA requirements. Use the FDA scope guidance alongside the applicable predicate rules and your quality procedures.
Use a synthetic example to explain the source system, review process and intended recipients. We can explore where file exchange sits within that workflow.
Review your exchange requirementsNo. Determine applicability from the record, its use and the underlying FDA requirements. A company’s industry alone does not establish the scope.
Not by itself. A delivery log describes exchange events. The applicable record system may need to capture creation, modification and deletion with additional controls and reviewability.
No. Validation, audit trails, access controls and other requirements need to be evaluated in the context of the intended use and applicable rules.
No. The illustrative history is educational sample data. Electronic-signature functionality and associated requirements must be evaluated separately.