Route every policy through the approvers you choose.

Build a workflow once and use it on any document. Approvers sign off in order, and what they approved is exactly what goes out.

30-day trialUnlimited free viewersNo credit card required

Every document is approved

Nothing reaches your audience until each step has signed off. The rules are simple and the same for every policy.

A sign-off that matches your org

Legal, then Finance, then the founder: mirror how decisions are really made. Up to four steps, six people in a step and twelve in all.

Move fast where one yes is enough

Let any one approver clear a routine step, and ask for everyone where it matters.

The right people, even outside

Bring in your lawyer, or a Viewer with the know-how. Approvers hold the document’s tags, so everyone who signs off can read what they approve.

Every policy signed off

Every document is approved before it reaches your staff. Working alone? You approve your own.

Clear next steps

A rejection always comes with a reason, so the editor knows exactly what to change.

Change course any time

Editors and Admins can pull a document out of approval. It goes back to Draft, and the withdrawal is logged.

Build a workflow once

Set up your sign-off once and reuse it on every policy, so nobody rebuilds the chain each time. Name it, add steps and pick the approvers.

Reminders keep it moving

Approvals keep moving. The approver on the current step is reminded every few days until they act, then the next step is reminded the same way.

Approval requests in SlackApprovers hear in Slack when it is their turn. Connect it under Admin › Integrations on the Scale plan.

Reject with a reason

Every rejection says what to fix. A rejection needs a reason, and when the document is sent again, approval starts at step one.

Compare before you approve

Approvers check only what changed instead of rereading the whole policy: sections changed, words added and words removed.

Locked while it is being approved.

What gets approved is exactly what goes out. The document stays exactly as submitted until every step has signed off, and your audience keeps the last approved version.

If an approver loses a tag the document carries, the approval is cancelled automatically, so every approval comes from someone who can see the document.

Who can do what

AdminsCreate saved workflows under Administrative Settings, and can withdraw any approval.
EditorsSend a document for approval, choose a saved workflow or build one, and withdraw it.
ApproversAnyone who holds the document’s tags. They approve, or reject with a reason.
ViewersCan be approvers, free of charge.

Once approved, the document is ready to distribute.

Questions

Is approval required for every document?

Yes. If you write alone, you set yourself as the approver.

Can someone outside the company approve?

Yes. Invite them to your workspace, for example your lawyer, and add them to a step.

What happens after a rejection?

The document goes back to Draft with the reason. When it is sent again, approval starts at step one.

What does my audience see during approval?

The last approved version. The new one appears once every step has approved.

How many steps can a workflow have?

Up to four, with up to six people in a step and twelve in all.

Try AllyMatter free for 30 days

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