Plumbworks / Review Cycle / Confluence Cloud
An auditor will ask who approved this page and when. Have an answer.
Review Cycle turns Confluence pages into controlled documents: a named owner, a review date, an approval that expires, and a signature trail that survives the person who left. For teams holding ISO 9001, ISO 27001, SOC 2 or medical device certification.
How a controlled page works
You mark a space or a set of pages as controlled. From then on each page carries its own review state, visible at the top of the page to every reader.
- ownerSomeone is responsible. Every controlled page has a named owner and a named approver. Ownership can be reassigned in bulk when people move on, which they will.
- scheduleReview dates that recur. Set an interval — annual, six-monthly, whatever your standard demands — and the page enters review automatically when it comes due.
- approvalSign-off with a reason. Approvers record a decision and a comment against a specific page version. Editing an approved page moves it back to draft rather than silently changing a signed document.
- expiryApprovals lapse. A page past its review date is visibly marked as expired to readers, so nobody follows a procedure that stopped being current in 2024.
- remindersNagging, scheduled. Owners are emailed before a review falls due and again after. Space administrators get a weekly digest of what is slipping.
- registerOne index for the auditor. A live table of every controlled page: version, owner, approver, approval date, next review, current state. Exports to CSV and PDF.
- historyNothing is overwritten. Every approval, rejection, reassignment and expiry is retained against the page version it applied to.
What it deliberately does not do
Review Cycle is not a workflow engine. There are no branching approval paths, no conditional routing, no scripting layer. If your process needs seven conditional stages with parallel approvers, buy something larger.
Most teams chasing a certification need one thing: proof that documents are reviewed on a schedule by named people, and evidence of it. That is the whole app, which is why it takes an afternoon to roll out rather than a quarter.
Pricing
Billed by Atlassian at your Confluence user tier. Free for instances of 10 users or fewer.
| Users | Per user / month | Monthly |
|---|---|---|
| 1 – 10 | free | $0 |
| 11 – 100 | $1.10 | $110 at 100 |
| 101 – 500 | $0.65 | $325 at 500 |
| 501 – 1,000 | $0.40 | $400 at 1,000 |
| 1,001 + | $0.25 | $500 at 2,000 |
Questions
Is an approval here a valid electronic signature?
It records the approver's Atlassian identity, the exact page version, a timestamp and an optional comment, retained immutably. Whether that satisfies your standard depends on the standard and your auditor — teams working to 21 CFR Part 11 in particular should check before relying on it.
Can readers still see a page while it is in review?
Yes. Confluence permissions are untouched. What changes is the banner at the top of the page, which states the current review state and the last approved version.
What happens to approvals if we uninstall?
Export the register first. Approval records live in Forge app storage inside your tenant, and Atlassian removes that storage on uninstall.
Can we apply this to an existing space with hundreds of pages?
Yes. Bulk-assign owners, approvers and review intervals by label, by page tree, or by CSV import.