Who Is This For?
Authors / Owners – validating edits before promoting state
Reviewers / Approvers – confirming changes and decision history
QA / Managers – investigating actions and ensuring compliance evidence
How to Do It?
Step 1: Compare versions to see what changed
Use Compare to identify differences between the current version and an earlier one.
Open the document, then select the three-dots menu in the top bar.
Click Compare.
Choose the earlier version to compare against the current version.
Review highlighted differences (e.g., content, state changes, role assignments).
❗ Compliance reminder: Always verify tracked changes and metadata before approvals to ensure the record reflects the intended edits.
📎 Reference: Navigating the Document Page
Step 2: Review the full Version History
See a chronological timeline of versions and what changed in each.
From the three-dots menu, select See Full History.
Review the timeline (most recent first).
Open a version’s details to check edits and property updates.
💡Tip: Use Version History first to pinpoint which earlier version you need to compare.
📎 Reference: Exploring the User Interface
Step 3: Open and analyze the Audit Trail
Trace every action taken on the document for full accountability.
From the three-dots menu, select Open Audit Trail.
Sort by column headers or apply filters to focus on specific activity types.
Use this view to see who did what, when, and what changed.
❗ Compliance reminder: The Audit Trail is a controlled quality record. Use filters to locate evidence for inspections and investigations; do not work from downloaded copies as your source of truth.
📎 Reference: Searching and Filtering Records
Tips
💡 Start with Version History to locate the right prior version, then use Compare for line-by-line differences.
💡 Capture screenshots or export views (where applicable) for audit packages to show exactly what was reviewed.
💡 If an action is missing from the Audit Trail, check your permissions and confirm you’re viewing the correct document.




