Version History & Reverting

CrownSync Playbooks maintains a complete version history for every section of every playbook. Each time content is published, a new version is created with a timestamp, the name of the person who made the change, and the change note they provided. This gives your team a full audit trail of how playbook content has evolved over time.

Accessing Version History

To view the version history for a section, open the playbook and locate the section card. Click the clock icon or the Version History button on the section card. This opens the version history panel, which lists all versions in reverse chronological order (most recent first).

Each version entry shows:

• Version number — An incrementing number starting from v1 (the original baseline)
• Author — The name of the user who published the change
• Timestamp — When the version was published
• Change note — The description provided at publish time
• Badge — A “Baseline” badge on v1 and a “Current” badge on the latest version

Viewing Diffs

To see exactly what changed between two versions, select any two versions from the history list and click Compare. The diff view displays the content side by side with additions highlighted in green and deletions highlighted in red.

The diff view is particularly useful for:

• Understanding what a colleague changed in a section you are responsible for
• Reviewing changes made by external collaborators before incorporating them
• Identifying what was altered during an incident response that should be kept or reverted
• Preparing audit evidence showing the evolution of a specific procedure

You can also compare any version against the current baseline by selecting the version and clicking Compare with Baseline. This is helpful when CrownSync releases updated baseline content and you want to understand the differences between your customised version and the new baseline.

Reverting to a Previous Version

If a change needs to be undone, you can revert a section to any previous version. To revert:

1. Open the version history for the section
2. Find the version you want to restore
3. Click Revert to This Version
4. Enter a change note explaining why you are reverting (e.g., “Reverting to v3 as v4 changes were made in error”)
5. Confirm the revert

Reverting does not delete any version history. Instead, it creates a new version whose content matches the version you selected. The full history remains intact, preserving the complete audit trail. This means you can always see that a revert happened, who performed it, and what the content looked like at every stage.

Comparing with the Baseline

The baseline is the original CrownSync-authored content for each section. It represents the expert-written guidance before any organisation-specific customisation. CrownSync periodically updates baseline content to reflect new threats, regulatory changes, and improved practices.

When a baseline update is available, a notification badge appears on affected sections in the playbook viewer. You can then:

• View the updated baseline content to understand what changed
• Compare it against your current customised version using the diff view
• Choose to incorporate the baseline changes into your content manually
• Or reset to the new baseline if you want to start fresh with the updated content

Baseline updates never automatically overwrite your customised content. You are always in control of when and how updates are incorporated into your playbooks.

Audit Trail Integration

Every version action — publishing, reverting, and resetting to baseline — is recorded in the organisation's audit log. This provides an immutable record that can be presented to auditors, regulators, or insurers to demonstrate that your incident response procedures are actively maintained and governed.

For organisations pursuing ISO 27001 certification or Cyber Essentials Plus, the version history provides evidence that incident management procedures are regularly reviewed and updated, supporting compliance with document control requirements.