You build an amazing system for your content – clean pages, smart structure, everything in its place. But, give it 3 to 6 months and it’s total chaos all over again. Pages go stale. Navigation breaks down. And your team quietly goes back to asking you for information because they don’t trust the docs. Sound familiar?

This post is your way out of that cycle!

A quarterly cleanup won’t fix it all 100% but it will keep your system usable, trustworthy, and clean enough to stop the rot. I’ve made all the mistakes, rebuilt my system more times than I care to admit, and finally landed on a system that holds up. What I’ve learned is this: you don’t need a total overhaul – you just need an easy process you can actually stick with.

Let’s walk through the checklist that makes it possible.

Attack Stale Content

Let’s start with the low-hanging fruit – old junk that no one touches anymore. I used to pretend like it wasn’t there because it felt overwhelming to deal with, but eventually it started to bite me. Someone would use a three-year-old process page and mess something up because of course it was wrong.

Now I use Advanced Search in Confluence to find everything last updated more than six months ago. You pick the range – maybe it’s 3 months, maybe 12 – but for me, 6 months is the sweet spot. Anything that hasn’t been touched since then gets a quick review.

I ask myself one question: Is this still relevant?

Yes? I add a “Last Reviewed [DATE]” note in the page and move on.

No? I archive it right then and there. Gone.

Bonus tip: I set the page status to “Verified” when I update it, and then use automation to remove that status after 90 days. That way, next quarter, I can just search for pages without that status. I have added the guide to set this up in the bonus content:

The first time I did this, I found over 50 pages across our core space that hadn’t been touched in over a year – and some of them were still being shared with others. It was a mess. I cleaned it up, updated content, archived the irrelevant things and just doing that made a massive difference in how people trusted the space.

Confirm Content Owners

Oh man, this one stung more than once.

A teammate left the company and nobody realized they still owned a bunch of key process pages. People were afraid to edit them. One team even duplicated a page just so they could maintain “their own version.” Chaos.

Every quarter now, I run through the Content Manager in Confluence. If you’re on the Free plan, you’ll have to check page-by-page, but Premium lets you bulk update. I scan the list of Page Owners and check if any are outdated—either people who’ve moved roles, left, or just clearly aren’t maintaining the page.

Ownership matters more than I thought. If a page doesn’t have a clear owner, people stop trusting it. They don’t say that, but they avoid it. And then Teams/Slack/Discord gets noisy again. I usually assign page ownership based on who knows the process best – not who created the page – and I’ll tag them with a note like “Hey! Can you be the go-to for this page?”

It’s simple, but it creates accountability without a big dramatic policy.

Review the Space Homepage

Your homepage is probably lying to you.

Mine was. It still had links to tools we’d stopped using a year ago and a teammate list that showed two employees who had since moved to other teams or left the company and was even missing some team new members. Whoops! It’s one of those things that feels important but also invisible – until a new hire sees it and you realize… oh no, this is what we look like to the team. A hot mess!

Every quarter, I make it a point to clean up the homepage. I don’t try to make it crazy fancy. I just make sure:

• The top links are still used
• The intro copy isn’t cringey or outdated
• There’s a clear “Start Here” section that works for new folks

If you want a full deep dive on building a space homepage that actually helps people, I wrote an entire guide: How to Build an Intuitive Confluence Space Homepage. But for the quarterly review, just focus on making sure it doesn’t send people in the wrong direction.

Consolidate Duplicated Content

You ever search something in your space and see three different pages… all slightly different… and you have no clue which one to trust?

Same.

During a recent cleanup, I searched for “onboarding checklist” and found five pages. Two were ones I had forgotten about. One was titled “DO NOT USE.” The other two were nearly identical – but had the order of items rearranged. Yikes.

So now I make this part of the cleanup: If I come across duplicate or conflicting content, I pick one to keep, move everything into it, and mark the rest with a giant red warning banner that says, “Deprecated. See updated version: [link].” Then I just archive it.

It’s manual. It’s messy. But it’s better than letting people guess.

Audit Page Labels

I used to ignore page labels. But it turns out – they’re gold if you set up a simple system.

Now I use labels like review-annual, how-to, and system-x to tag content so I can group and filter it. During the cleanup, I open the Content Manager and just scan the labels column. I fix anything that’s off, remove junky one-off labels, and standardize anything that should match a pattern.

Labels are especially useful if you’re using macros or trying to automate review cycles. It’s not flashy, but it pays off. I once found 5 variations of the same label: training, training-doc, training-steps, user-training, training-enduser… and none of them worked consistently.

Start small. Use 4–5 consistent labels. Build from there.

Review New Content for Consistency

This one’s sneaky. Because everyone’s working, everyone’s creating. But not everyone is thinking, “What does good documentation look like?”

I use the same Advanced Search trick – pick a date range from the last 6 months – and look for any page that was created or updated recently. Then I skim: Is it following our style? Are the headings clear? Is it scannable?

I’m not trying to be the documentation police, but if we don’t course correct every now and then, the space turns into a wall of half-finished pages that no one wants to use. So I’ll leave comments, update formatting, or send a Slack like, “Hey this page is great – mind if I clean it up for consistency?”

Usually, people are relieved. They want their stuff to be readable. They just didn’t know what “good” looked like.

Archive Unused Spaces

Okay, this one hurt a little. Because I had built some of those spaces myself.

But if a space hasn’t had any activity in a year, isn’t linked from anywhere, and content has no owner? It’s probably not worth keeping around. I now check our usage analytics and look for ghost towns.

If I’m not sure, I ask: “Is anyone still using the [Name] space?” Most times, I get silence… or a relieved “Oh wow yeah, you can get rid of that that.”

Want the Full PDF Version?

This blog post gives you the core tasks. But the full cleanup checklist goes deeper with these bonuses:

• Automation Flow: Flag Stale Content
• Guide: Identifying and Managing Page Ownership
• Templates: Instant Messages and E-Mail Templates for your team.