How to Run an End-of-Year Documentation Cleanup in One Afternoon

Every team has a documentation graveyard: onboarding guides that mention tools you stopped using, process pages that describe how things worked two reorganisations ago, and five versions of the same template. Nobody fixes it because nobody owns it, and it is never urgent.

The end of the year is a good time to change that. Work slows down, people are reflective, and a cleaner wiki is a genuinely useful gift to your January self. You do not need a project; you need an afternoon and a rule.

The Rule: Archive Aggressively

Most cleanups fail because people try to update everything. Do the opposite. For each page, ask one question: would a new team member be misled by this?

• No, and it is still used: keep it.
• No, but nobody uses it: archive it.
• Yes: fix it today if it takes under ten minutes, otherwise archive it and add a note pointing to the right place.

Archiving is not deleting. It moves the page out of search and navigation while keeping the history.

Before You Start: Sort By Usage

Most wiki and documentation tools show page views or last-edited dates. Sort by both:

• High views, old edit date: your most dangerous pages. Lots of people read them, and they may be wrong. Check these first.
• Low views, old edit date: archive candidates.
• High views, recent edit date: probably fine.

The Afternoon Routine

Hour 1: The top 20 most-viewed pages. Read each one. Fix wrong facts, broken links, old screenshots and missing owners.

Hour 2: Duplicates. Search for common topics (“onboarding”, “expenses”, “deploy”, “holiday”). Merge duplicates into one page and archive the rest, with redirects or “moved to” notes.

Hour 3: Archive the long tail. Pages not viewed in a year, with no owner, go to the archive.

Final 30 minutes: Owners and dates. Add an owner and a “last reviewed” date to every page that survived. A page without an owner will be stale again by summer.

Make Pages Easier To Trust

Small additions make documentation dramatically more useful:

• “Last reviewed by [name] on [date]” at the top.
• “Who this is for” in one line.
• The answer first. Most people arrive with one question. See how to write an SOP people will follow.
• Plain language. The plainlanguage.gov guidelines are a practical checklist.

A Before And After

A typical stale paragraph, rewritten.

Before:

To request leave, raise a ticket in the old HR portal (see link) and email your manager, then once approved update the shared calendar spreadsheet. NB process may be changing in Q3.

After:

To request leave, submit it in the HR system under Time Off. Your manager approves it there, and it appears in the team calendar automatically. Last reviewed by Priya Shah, October 2026.

The new version removes the dead link, the manual steps and the vague warning, and says who checked it.

A Wrivio Context for documentation updates could say:

Rewrite this as clear internal documentation. Plain English, short sentences, answer first, numbered steps where there is a sequence. Keep every system name, step, role and requirement exactly as written. Do not add steps, warnings or links that are not in the original.

Press Ctrl+Shift+Space, paste the old paragraph after correcting the facts, and check the steps still match reality.

Ask The Team For Their Worst Page

Send one message before you start:

Before the holidays I am tidying our documentation. What is the one page that misled you or wasted your time this year? Reply with a link and I will fix or archive it.

People know exactly which pages are wrong. They have just never been asked. See how to write a Slack message that gets a fast reply.

Keep It Clean Next Year

• Put a recurring 30-minute “docs review” on the calendar each quarter.
• Make “update the docs” part of the definition of done for process changes.
• When someone asks a question in chat that the docs should answer, link the doc or fix it.

Common Questions

Should we delete old documentation or archive it?

Archive by default. Deleted pages lose history that occasionally matters, such as why a process changed. Archive removes them from search without losing them.

Who should own documentation?

Each page should have a named owner, usually the person or team that owns the process it describes. A central “documentation owner” rarely works on its own.

How do we stop people creating duplicate pages?

Make the right page easy to find: clear titles, a short index page for each topic, and a habit of linking rather than copying.

Is AI useful for documentation cleanup?

It is useful for rewriting outdated pages once you have corrected the facts, and for summarising long pages. It cannot tell whether a process is still accurate; only the people doing it can.

Download Wrivio for Windows to rewrite stale documentation into clear, current pages in seconds.