Audit Trail in Simple Terms
If a control plan revision, an inspection result or a calibration date changes, someone will eventually ask who changed it, when and why. An audit trail answers that without relying on memory. Paper systems do this with signatures, dates and crossed-out entries. Software does it with an automatic change log that users cannot edit.
Key Elements
- Who: the user account that made the change.
- When: date and time.
- What: the old value and the new value.
- Why: a reason or change reference where required.
- Approval: who reviewed and released the change.
Standards such as ISO 9001 and IATF 16949 require controlled documented information, including protection from unintended changes. An audit trail is the practical evidence of that control.
Example
During a customer audit, the auditor asks why the torque specification on a work instruction changed from 25 to 22 Nm. The audit trail shows the engineer who made the edit, the date, the linked engineering change notice and the quality manager who approved it, so the question is closed in minutes.
Common Mistakes
- Shared logins, which make the who field meaningless.
- Spreadsheets where values can be overwritten with no history.
- Logging changes but never reviewing them.
OperaHive document control software keeps revision history, approval workflows and read acknowledgements for drawings, SOPs and work instructions.