Knowledge & Wikis
Part of Team knowledge and wiki software
Finding outdated knowledge before it causes mistakes
Use change signals, owner checks and a clear correction or retirement decision to find outdated internal guidance before colleagues act on it.
Look for signals that an instruction may no longer match the work, then ask a responsible person to verify it. An old edit date is a review prompt, not proof that a page is wrong. A recently edited page can also be wrong if its form, system or approval rule changed elsewhere.
Key facts about managing outdated knowledge
- Old edit date is a prompt, not proof of inaccuracy
- True
- Recently edited pages can still be wrong
- Yes, if underlying systems or rules changed
- Confluence Premium/Enterprise offers Last active filter
- Excludes pages with children
- Notion supports time-limited wiki verification
- Can expire and notify owners
Build a review queue
Start with pages that tell people to act: submit a request, use a template, contact a team or follow a sequence. Prioritise instructions whose wrong answer could cause repeated rework or a consequential mistake. Add pages to the queue when:
- a form, system, supplier or team responsibility changes;
- a reader reports that a step no longer works;
- search shows several plausible answers to the same question;
- an owner leaves or no longer controls the process; or
- a planned review point passes.
These signals call for investigation. They do not justify automatically deleting or replacing content.
Confluence Premium and Enterprise provide a content manager with filters for Last updated and deactivated owners. Its Last active filter excludes pages with children, so it cannot show every inactive page.
Notion workspace search can sort and filter results, and time-limited wiki verification can expire and notify the page owner. None of these signals checks whether the underlying process is still right.
Verify the instruction
Ask the page owner or current process owner to follow the guidance against the current workflow. Check that the named form opens for the intended reader, the steps match the system, the receiving team still exists and the exception route works. Check any separate file the page relies on, including its access. Use a safe example rather than a sensitive live request.
Record a decision: current, needs correction, cannot yet confirm or retire. If people may act on an unconfirmed instruction, show that uncertainty and give a contact route while it is checked. Do not renew a verification mark just because a reminder appeared.
Correct or withdraw the old answer
If the process still applies, fix the wording and supporting material, then ask someone unfamiliar with the change to follow the revised guidance. If the process has been replaced, point readers to the new answer and withdraw the old one using the product's appropriate method. Update live pages that still refer to it.
In Confluence Cloud, archiving removes an item from the content tree and quick search. It remains available in the archive and can be included in advanced search, while direct links continue to work and show an Archived label.
Before archiving, check inherited permissions: an item that relies on a parent to control who can view it may be exposed to a wider audience when archived. An archive keeps context; it does not correct other live instructions.
Keep a short record of what changed, who confirmed it and which related pages or templates were checked. If readers still need a private explanation after the correction, revisit the title, opening answer or exception route.
