Confluence page review reminders: a cadence that sticks

Why Confluence content goes stale, and what a page review reminder has to do

Nobody decides to let a page go stale. Writing a page is a project with an end; keeping it true is a chore with no end. The usual causes:

• The author moved on. The person who wrote the runbook changed teams, and nobody else feels it is theirs to fix.
• The world changed around the page. A tool was replaced or a process gained a step. The page still describes last year.
• Nothing marks a page as checked. A page edited two years ago may be accurate or badly wrong, and from the outside the two look the same.

A Confluence page review reminder only helps inside a routine that answers four questions for every page that matters: who is responsible, when it is next due, how anyone finds out it is due, and how you show later that the review happened. The rest of this article builds that routine with features Confluence Cloud already has.

First, find the stale Confluence pages you already have

You don't need to review every page in the site. Start with the spaces where wrong information costs something: support procedures, onboarding, policies and runbooks.

• Search by last modified. Confluence's advanced search can filter by space and by a Last modified date range, so you can list the pages in a space that nobody has touched in a year or more. Old isn't always wrong, but it is where to start.
• Check who still reads it. On Standard, Premium and Enterprise, content insights show how many people have viewed a page. Premium and Enterprise add full analytics, including who viewed it and when. A page nobody has opened in a year is a candidate for archiving rather than review.
• Use the content manager if you have it. On Premium and Enterprise, space admins get a content manager that filters a space by when pages were last updated or last active, and by owner, status and label, and can archive many items at once.

Sort what you find into pages to keep, pages to merge and pages to archive. Only the first pile needs a review date.

How to set up Confluence content review dates by hand

The approach below uses standard Confluence Cloud features and needs no apps. For a space of a few dozen pages, it is an afternoon's work.

1. Give every page one owner

Confluence Cloud already records an owner for each page, shown in the byline under the title. It starts as the creator, and the current owner or a space admin can change it to anyone who can edit the page. Make it the person who will actually do the review. Reviews belong to a person, not a team.

2. Add a review block to each page

At the top or bottom of each page you want reviewed, insert a content properties macro (previously called the page properties macro) holding a small two-column table:

Then add the same label to every page that carries the block, for example needs-review. Use the same property names on every page, exactly, because they become column headings in the report.

3. Build a "what's due" register

On a register page in the same space, insert a content properties report macro and point it at your label. It collects the review block from every labeled page into one table. You can narrow it to one space or one part of the page tree, and sort it by a column such as Next review.

4. Put the reminder where people already look

The register only helps if someone opens it. Pick one of these and make it someone's job:

• A recurring calendar event on the first working day of each month: open the register, find everything due in the next 30 days, and nudge each owner. Five minutes in an existing monthly meeting works just as well.
• An action item per review. In Confluence, type [] to add an action item, @mention the owner to assign it and add a date. The owner is notified, the item appears in their task list, and it shows as past due once the date passes. A task report macro on the register page can list the open review tasks by assignee or due date.

Confluence automation also has a Scheduled trigger if your team already builds rules; its runs count toward your plan's automation allowance.

5. Show the state on the page itself

Content status, the small label at the top of a page, can be set by anyone who can edit it. The suggested defaults are Rough draft, In progress and Ready for review, and space admins can set up to five suggested statuses of their own, such as "Needs review" for the owner to set while a review is under way.

6. Archive what's obsolete

Archiving is available on every Confluence Cloud plan; bulk archiving is Premium and Enterprise. An archived page leaves the content tree and quick search, keeps its permissions and links, can't be edited, and can be restored later. That suits pages that are no longer true but that someone may need to look up.

A sensible review cadence by content type

One cadence for everything means either reviewing stable pages too often or volatile pages too rarely. These are examples to adapt, not rules:

Count the next review from the date of the last real review, not from the last edit. A typo fix is not a review, and it shouldn't reset the clock.

What to do at review time: confirm, update or retire

A review ends in one of three outcomes. Make the owner choose one explicitly:

1. Confirm. The page is still accurate. Check the links, the names, the tools and the steps. Ideally, ask someone who uses the page whether it matches reality.
2. Update. Something is wrong or missing. Fix it, and if the change affects what people must do, tell them: for a policy that may mean asking people to read and accept it again.
3. Retire. The page no longer applies. Archive it, or merge it into the page that replaced it and archive the old one. Don't just delete it, because its history may still be needed.

In every case, set the next review date before you close the page. Otherwise this review is the last one the page gets.

How to record a review when nothing changed

The hardest review to prove is the one that found nothing to fix. If nobody edits the page, its history shows no trace of the review. With the review block from step 2, the record is simple:

• Update the dates. Change Last reviewed to today and move Next review forward by the cadence.
• Publish with a version comment such as "Annual review: no content changes". The page history then shows who reviewed it, when and what they concluded.
• Optionally show the history on the page. The change history macro lists each version's number, author, date and comment inline.

Policy review dates with Compliance in a Box

For most Confluence content, the manual routine above is enough. Policies are different: an audit needs each review to be an approval tied to a version, and the dates need to be right without anyone typing them. Compliance in a Box does this for the policy pages it manages in your compliance space (the SOC 2 policies it creates, plus any custom policies you add). The full detail is in Periodic reviews.

Review dates worked out from approvals

Each SOC 2 policy has a 12-month review cadence, and custom policies are reviewed yearly too. The next review date is the date of the latest approval plus the cadence. Every approval counts as a review, so approving a changed version also resets the clock.

Review due, then Overdue

From 30 days before the date a policy is flagged Review due, and once the date passes it is flagged Overdue. The flags show in the Next review column and the Review due filter on the Policies tab, on the policy's page in the app, in the byline on the Confluence page, and in the owner's My Tasks. A due review doesn't change the policy's status: it stays approved until someone edits it. The app also records each due and overdue review in its audit log, once per review cycle.

Mark as reviewed for a no-changes review

When the page is identical to the approved version, the owner sees Mark as reviewed instead of Submit for approval, on the policy's page in the app or in the byline. The note is optional and defaults to "Reviewed: no changes.". The review still goes to the policy's approvers like any other submission. Once they approve, it counts as the review, the next review date moves forward, and the approval is labeled Review only in the policy's record. The page itself isn't edited.

My Tasks, the Dashboard and reminders

In My Tasks, owners see each policy whose review is due within 30 days or overdue, with the review date, and approvers see the review under Approvals waiting for you. Compliance Admins see Reviews due in 30 days on the Dashboard, overdue reviews in the Overdue figure, and upcoming review dates in the Upcoming list. Owners are also reminded through Confluence tasks: 30 days before the review date, on the date, then every 2 weeks after it (up to 6 times). See My Tasks and when reminders are sent.

For the yearly check across the whole policy set, the SOC 2 content also includes an Annual Policy Review activity whose evidence page starts with a list of your policies and their approval dates. For how reviews fit with the rest of a policy's life, see Confluence policy management, and for the full program, the SOC 2 compliance calendar.

FAQ

How do I get a reminder to review a Confluence page?

Give the page an owner and a next review date, then put the reminder somewhere it will be seen: an action item assigned to the owner with a due date, a recurring calendar event to check a register of due pages, or, if your team uses it, a scheduled Confluence automation rule.

Should stale Confluence pages be deleted or archived?

Usually archived. An archived page keeps its permissions and links and can be restored, but it leaves the content tree and quick search, so it stops misleading people.

Does a review with no changes need a new page version?

In a manual setup, yes: updating the review dates and publishing with a version comment is what puts the review in the page history. In Compliance in a Box, a Mark as reviewed approval records the review without editing the page.

← All articles