One current version, reviewed on schedule.

Every save is a numbered version you can compare and restore. Set a review date and the editor is reminded before a policy goes stale.

30-day trialUnlimited free viewersNo credit card required

History you can trust

Your audience only ever sees the current approved version. Everything before it is kept, numbered and comparable.

Always know what changed, and when

Every save is a numbered version, marked minor or major. Numbers only go up.

Review a change in seconds

Compare any two versions: sections changed, and words added and removed.

Undo without skipping checks

Restoring an old version creates a new one, approved like any other.

Every policy stays current

Set a review date or a cycle, and the editor is reminded.

Retire a policy cleanly

An expired policy comes down for its audience, so everyone follows current rules. Editors and Admins keep it.

History when you need it

Version history is kept for 3 months on Startup and 3 years on Scale.

Major or minor, your call

Show how big a change is at a glance. Either way it gets the next number and goes for approval.

Reminded before it goes stale

Review dates look after themselves. When one is due, the editor is told in the app and by email.

Still accurate? Move the date.

A review that finds nothing to change takes seconds: set the next review date, with no new approval.

Changed? It goes for approval.

Every edit is checked before it reaches people. The policy goes back through approval, and your audience keeps the current version until then.

Expired policies leave the shelf.

When a policy expires, it is taken down for its whole audience, so everyone works from current rules. Editors and Admins keep it.

Bring it back by approving it again. Give each policy a review date or an expiry date, whichever fits.

Who can do what

AdminsSee every version of the documents they can open.
EditorsSave versions, compare and restore them, and set review or expiry dates.
ApproversCompare a version with the last one before approving.
ViewersAlways see the current approved version.

Restored and edited versions go through approval workflows.

Questions

How long is version history kept?

3 months on Startup and 3 years on Scale.

Does a review always need a new approval?

Only when something changed. If the policy is still accurate, move the review date. If you edited it, or it expired, it goes for approval.

Should I use a review date or an expiry date?

A review date when a policy should be checked and kept, an expiry date when it should come down on a set day.

Who is reminded when a review is due?

The editor, in the app and by email.

What happens when I restore an old version?

Its text comes back as a new version, which goes for approval before it goes live.

Try AllyMatter free for 30 days

  • No credit card needed
  • 30-day money-back guarantee
  • Free migration on yearly plans