Audit trails: test correction, identity and context
Test whether an MES reviewer can explain a correction, identity, time and record context. Assess retrieval, export and privileged change procedures.
Evaluate an MES audit trail by testing whether an authorized reviewer can explain a meaningful change: who acted, what changed, when it happened and why, under the requirements established for that record. A long technical log is not automatically a usable review history.
Define the events worth reviewing
Start with the records and decisions the organization relies on. Identify changes to quantities, material relationships, instructions, approvals, dispositions and relevant configuration. Determine required controls with quality, security and regulatory personnel. Do not assume every diagnostic event needs the same retention or review process.
Distinguish business history from application diagnostics. A server log may show a request but not explain the production meaning or authorized reason for a correction. Conversely, an operator-facing history may omit details needed for incident investigation. The system may need both, with appropriate access and ownership. Define the purpose before judging whether a log is complete.
Test one correction end to end
Create a fictional production completion with an intentionally incorrect quantity. Correct it through the approved application workflow. Have a reviewer who did not perform the action reconstruct the original event, the correction and its effect on related records. Check the interface destination as well as the MES screen.
| Review question | Evidence to inspect |
|---|---|
| Actor | Account and relevant role or authority |
| Object | The record and stable identifier affected |
| Change | Previous and resulting state where required |
| Time | Interpretable timestamp and context |
| Reason | The explanation or approved workflow context |
| Effect | Related postings and current production state |
The exact evidence depends on the assessed record requirements. Use the table to expose gaps, not to claim a universal compliance checklist.
Examine identity and permissions
Test separate roles for requesting, approving and administering changes where the organization requires that separation. Shared terminals should not silently erase individual accountability. Identify how service accounts appear when an interface creates or changes a record, and how the initiating business context is preserved if needed.
Ask who can alter configuration, delete data, change permissions or manage retention. Have qualified personnel assess privileged access and monitoring. Do not assume an administrator’s technical ability is an authorized business action. A correction method should be documented and approved, with appropriate evidence. Informal direct database editing can undermine the very history the plant expects to rely on.
Make timestamps and sequence interpretable
Identify the time source and how the application represents time zones, event time, receipt time and later corrections. Distributed systems can receive events after they happened. A reviewer needs enough context to understand the sequence without guessing which clock a displayed value uses.
Test a delayed event and a shift spanning a clock change if relevant to the site. Do not invent a universal timestamp precision requirement; establish the need for the process. Ensure exports preserve enough time context to interpret records outside the application. A formatted local time without an offset or documented convention can be ambiguous when records from several sites are combined.
Review retrieval and export usability
Ask an authorized reviewer to find a selected change, filter relevant events and explain the record without help from a developer. Include an older record and an attachment or linked event where relevant. A history that can only be accessed through a bespoke database query may not support the intended review process.
Test export relationships and readability. Confirm that a printed or exported representation does not omit information the organization requires for interpretation. Discuss retention, access and review responsibilities with qualified owners. Storage capacity alone does not establish that history will remain accessible or meaningful after an upgrade, archive or supplier transition.
Connect findings to procedures and change control
Document what the configured application captures automatically and what depends on user action or procedure. Train the roles that create, approve and review corrections. Define how suspected unauthorized or unexplained changes are escalated. A log that nobody is responsible for reviewing may not achieve the intended control.
Retest the relevant behavior after workflow, interface or retention changes. Keep test results linked to the record requirements and configuration version. Avoid a blanket claim that audit trails establish compliance. They are one part of a broader record and operating process whose suitability must be assessed for the actual use. Unresolved gaps should remain visible before production approval.
Take this to the working meeting
Choose one order that has a correction and ask a reviewer to explain it using only the retained application records and approved procedure. Note every external explanation they need. If the reviewer cannot distinguish an original event from a later correction, record the missing context as a requirement. Repeat the exercise after export so the archive is evaluated as well as the live interface.
FAQ
Is every application log an audit trail?
No. Determine whether the information supports the required record review and preserves meaningful business context.
Can a reason field prove a correction is appropriate?
No. It records an explanation. Authorization, evidence and review may still be needed under the organization’s requirements.
Does this establish Part 11 compliance?
No. Applicability and controls need qualified assessment of records, use, configuration and procedures.
Continue your decision
- MES risk review: test the failures before launch
- MES and OT security: define the trust boundaries
- Electronic records: establish Part 11 applicability
- Lot genealogy: prove the trace in both directions
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.
