Skip to main content

Reviewing Document History

Ensure every document’s history is transparent and traceable by using built-in tools to compare versions, view version history, and review the full audit trail.

Updated over a week ago

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.

  1. Open the document, then select the three-dots menu in the top bar.

  2. Click Compare.

  3. Choose the earlier version to compare against the current version.

  4. 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.


Step 2: Review the full Version History

See a chronological timeline of versions and what changed in each.

  1. From the three-dots menu, select See Full History.

  2. Review the timeline (most recent first).

  3. 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.


Step 3: Open and analyze the Audit Trail

Trace every action taken on the document for full accountability.

  1. From the three-dots menu, select Open Audit Trail.

  2. Sort by column headers or apply filters to focus on specific activity types.

  3. 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.


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.

What’s Next?

Did this answer your question?