Overview

Most teams already have an approval process. It just lives in email threads, meeting notes and someone's memory. Somebody asks four people to review a page, three reply, one forgets, the page gets edited two weeks later, and nobody can say for certain whether the version people are reading now is the version anyone actually agreed to.

Capable Approval puts that process on the page itself, where the work already is.


#What you get


#Problems it solves

If this sounds familiar

Here is what to do

I never know who still owes me a review.

Ask everyone at once and watch the count go up under the page title. See Request an approval.

We need three of the five to sign off, not all five.

Set the number you need. The others still get notified. See Request an approval.

Someone edited the policy after it was approved.

Nothing to do. The approval resets itself on every edit. See How approvals work.

Our procedures are three years old and nobody noticed.

Set them to come back for review every six months. See Expiry and re-approval.

I am picking the same five reviewers every single time.

Make them a team and pick them in one click. See Teams and assignment.

The auditor wants evidence, not screenshots.

Export the full history. See What is recorded.


#Who it is for

Anyone who needs a page to be agreed before it counts. In practice that is quality and compliance teams working to a standard, HR and legal teams publishing policy, and engineering teams who want a design signed off before it gets built.

If you are working to SOC 2, ISO 9001, ISO 27001 or FDA 21 CFR Part 11, see Compliance for exactly which requirements Capable covers and which it does not.



Everything above, in about twenty minutes of setup.