content governance - determining ownership and expected lifespan/duration

Great questions! I've seen many variations on this answer...

Typically I default to the page Owner as being the person responsible for updating / curating the page. Practically this almost never happens, so I try to focus on the high value/impact pages (e.g. critical policies, updates, etc). For those it's worth reaching out to owners to build a relationship and get buy-in for them to actually monitor and perform updates.

In terms of a lifecycle, I stole an idea from inventory management called cycle counting. Basically I identify important content and label is "Yearly", "Quarterly" or "Monthly" (you can use different time scales. I then check that content on a year/quarterly/monthly basis (or make the owner do it). This helps ensure content is regularly reviewed.

Which page gets which label is a bit subjective, but the more important it is for something to be accurate the more frequently I'll look at it.

You can also setup automations to inform folks if there hasn't been an update in X period of time - great for Confluence to flag things automagically.

I rarely see organizations have a specific individual/team who manages Confluence - typically it's split up amongst whichever team publishes the content, although common titles I've seen are "Project Manager", "analyst" etc... 

Hi @Jay Maechtlen

@Rob Hean's answer provides a solid overview of the strategic side. I just wanted to share some ideas for practical steps to bring it to life, especially since you're on Premium and have access to many native tools.

For ownership, I would not leave this informal. Confluence Premium's Content Manager lets you filter pages that have no active owner, which surfaces exactly the orphaned content problem Rob described: people who left the company still listed as owner. From there, you can bulk reassign ownership to a current team member in one action, rather than chasing this page by page.

For the review cadence itself, I would build a lightweight governance dashboard rather than relying on memory or spreadsheets. Add a Page Properties macro to each governed page with fields for Owner, Review Frequency, and Next Review Date, then add a Page Properties Report macro on a hub page that pulls all of them into a single sortable table. That single table becomes your actual tracking mechanism for the cycle counting approach Rob mentioned.

For evidence rather than guesswork about lifespan, Confluence's built-in analytics show views and last update per page, so I would use pages with near-zero views over 90 days as a trigger for review or archiving, rather than only going by calendar age. Content Manager also lets you sort and bulk archive directly from that same view.

On the automation side, native rules can watch for a page going stale past a set number of days and notify the owner or add a review label, which covers the basic case without needing anything extra. If you need more than that, there is a category of dedicated content lifecycle apps on the Marketplace built specifically around ownership tracking and scheduled review workflows, worth a look if native rules stop scaling for you.

Cheers, Martin