Confluence Governance Checklist: Owners, Reviews and Cleanup
A useful Confluence governance review ends with an owner, a decision, and a next review date for each important page. Start with one space and its essential guides, check who can use them, and assign the work needed to keep them reliable.
This checklist is for Confluence Cloud space owners and administrators. It covers a periodic review of ownership, access, and content lifecycle. For the everyday workspace, meeting notes, and weekly routine, use the companion practical Confluence guide for remote teams.
1. Prepare a manageable review
Choose one space and a small first set of pages: onboarding instructions, operating procedures, current project decisions, and frequently shared reference pages. Add pages reported as confusing or outdated. Record what you reviewed so the sample is not mistaken for a complete space audit.
- Choose a review coordinator: the person who collects decisions and follows up on unfinished work.
- Involve a space administrator: a business owner may know the content without having access-management permissions.
- Create a review page: use the audit record below and link it from your space overview. Keep its audience appropriate for the information it contains.
You need permission to edit the review page and any content you change. Custom permissions and restrictions are unavailable on the Free plan; existing restrictions can remain after a downgrade. Check Atlassian's Free-plan permission guidance if your controls differ. The individual-page archive steps below assume Standard or higher, which includes content archiving.
2. Assign space and page owners
On the space overview, name a business owner, a backup contact, the space's purpose, and the next governance review date. These are team responsibilities you document; they do not automatically grant administrator rights.
For each important page, agree who can confirm its accuracy and arrange updates. If the original author has moved teams, transfer native content ownership:
- Open the page in a desktop browser and select its owner's name or avatar beneath the title.
- Select Change owner, find the agreed person, and confirm the change.
- Record a backup contact in the page or review record so an absence does not leave the review unassigned.
The new owner needs access to the space and permission to edit the page. The current owner, a space administrator, or a Confluence product administrator can make the transfer. Native ownership transfer does not cover space overview pages or blog posts; document their responsible contact in the content instead. See Atlassian's ownership-transfer instructions.
3. Set review dates and check accuracy
Add a small maintenance section to important pages: Owner, Last reviewed, Next review, and Review outcome. These can be ordinary text or table cells. They are a team convention, so assign someone to check due dates; writing a date does not create a reminder.
Use a cadence that reflects how quickly the subject changes. As a starting example, review active project instructions monthly, stable team processes quarterly, and update affected pages whenever the underlying process changes. Agree the schedule with each owner.
- Follow the instructions or ask the responsible subject expert to check them against the current process.
- Check linked resources, named contacts, screenshots, and prerequisites. Record the specific issue when something cannot be verified.
- Write the review outcome and reviewer. Set the next review date, or assign an update with a due date.
A recent edit may only fix a spelling mistake; an old page may still be correct. Keep the accuracy review separate from the last-modified date. Do not mark an unresolved page as reviewed and current.
4. Check the intended audience and permissions
Write down who should read, edit, and administer the space before changing access. Include external collaborators where relevant. Ask the space administrator to compare that intended audience with the actual settings.
- On sites using roles, open Space settings → Users. Use More actions → View role permissions, or a person's More actions → Manage access, to inspect what their role permits. Sites still using legacy permissions show individual permissions instead. Follow the space-access guide for roles and Atlassian's explanation of the two access models.
- Open a representative page's Share window. Review General access and any people or groups with specific access. Check a restricted parent as well as the page itself.
- Record any mismatch, who will correct it, and when. After changes, have an intended reader confirm they can open the relevant pages and links.
Parent view restrictions flow down to child content; parent edit restrictions do not. Page restrictions also depend on space access. See how Confluence content restrictions work. Changing page access requires the appropriate edit and restriction-management permissions, as described in Atlassian's content-permission guidance.
If someone cannot open a page, check their space access and restricted parents before assuming the page is missing. If the control you need is unavailable, give the administrator the page link and intended audience so the follow-up is actionable.
5. Decide what to update, merge, link, or archive
Make the decision with the page owner. Use one current reference for a process, and preserve useful context when retiring older material.
| What you find | Decision | Concrete next step |
|---|---|---|
| The page is accurate and still needed | Keep | Record the reviewer and next review date. |
| The task is current, but instructions are wrong or incomplete | Update | List the corrections, assign an owner, and set a due date. |
| Two pages answer the same question | Merge | Choose the main reference, move useful unique details into it, and update known incoming links. |
| A page repeats instructions owned elsewhere | Link | Replace repeated details with a descriptive link to the maintained reference. |
| The work has ended, but its history is useful | Archive | Record the reason and any replacement page, then check access before archiving. |
For example, two onboarding pages may share setup instructions while one contains a useful troubleshooting section. Move that section into the agreed main guide, replace links you maintain, and note the replacement on the retired page before archiving it. This is an example decision, not a reason to archive every old page.
Archive an individual page
First check whether the page relies on a parent's view restrictions; archiving can change that protection, so apply the required restrictions directly before proceeding. Check any nested pages you intend to include.
- Open More actions (•••) → Archive on the page.
- Add a note explaining the decision and replacement, if there is one.
- Confirm Archive, then record the completed action in your review.
Archived pages leave the content tree and quick search, but their links still work for permitted readers. Restore a page before editing it. You need permission to archive the item; ask a space administrator if the option is unavailable. Bulk cleanup through Content manager requires Premium or Enterprise. See Atlassian's archive instructions and permission details.
6. Copy this governance audit record
Copy these fields into a Confluence review page, one record per item. This is a manual record you maintain, with no app required.
| Field | Fill in during the review |
|---|---|
| Page | Title and link; what task it supports. |
| Owner and backup | People who can confirm the content and arrange changes. |
| Review | Reviewer, review date, and what was checked. |
| Audience | Intended readers/editors; access issues to resolve. |
| Decision | Keep / update / merge / link / archive, with a reason. |
| Follow-up | Specific action, responsible person, due date, and open/done status. |
| Completion | Link to the corrected or replacement page; who checked the result and when. |
| Next review | Agreed date and person responsible for starting it. |
Example: an onboarding guide needs an update
Review: 4 October 2026, by the support team lead. Finding: the guide names the previous escalation contact. Decision: update. Follow-up: the page owner replaces the contact by 9 October; a new team member checks that the linked handover page is accessible. Next review: 4 January 2027, or sooner if the process changes. These are illustrative details to replace with your own.
Checklist for closing each record
- Owner and backup have agreed their responsibilities.
- The content was checked against the current process, with unresolved questions recorded.
- The intended audience and actual access were reviewed.
- Duplicates and replacement links have a clear decision.
- Each unfinished action has a person and due date.
- The outcome, completion check, and next review date are recorded.
7. Close follow-ups and choose the next review
The coordinator should revisit open actions on an agreed date. Count reviewed pages and remaining actions separately: finding an issue is progress, but the issue remains open until someone checks the correction. Hand overdue or unowned work back to the space owner for a decision.
For a small space, the manual record may be enough. When deciding which pages to inspect across larger spaces, Content Health for Confluence adds a space overview and page health scores. Its Marketplace listing describes read-only analysis based on content metadata. Use those indicators to build a review queue, then have an owner verify accuracy and decide the action.
Carry the resulting maintenance habits into your team's daily work with the remote-team workspace and weekly review example.