Set a review date on every article
A knowledge article should carry the date it was last checked, not only the date it was written. Add an owner and a next review date to the article record. The owner may be a product lead, a support lead, or a named specialist. An article without an owner has no one to notice when it goes stale.
Choose a review interval that matches how often the underlying process changes. A refund policy may need a quarterly check, while a product name change may need a review within days. Record the interval and the reason beside the article. A single annual review for everything lets fast-moving pages rot.
Make the review a small task rather than a full rewrite. The reviewer confirms the link works, the policy is current, and the example still matches the product. Record the result as keep, update, redirect, or retire. A short decision is easier to complete than an open-ended edit.
Report the number of articles past their review date each month. A rising count shows the review capacity is too low or the interval is unrealistic. Name the oldest and riskiest pages first. The report should prompt a decision, not just display a backlog.
Keep the review task small enough to finish in one sitting. Reading an article, checking two links, and recording a decision should take less than half an hour. Record the average time per review. A review that takes a whole afternoon will be postponed until the page is dangerous.
Define the retirement triggers
A retirement trigger should name the condition that makes the article unsafe or useless. Common triggers include a discontinued product, a replaced policy, a merged workflow, or a page that no longer answers a real question. Write the trigger beside the review result. Without a trigger, retirement becomes a matter of taste.
Separate a retirement from a rewrite. A rewrite keeps the URL and replaces the content, while a retirement closes the page and sends the reader elsewhere. Record which decision was made and why. A page that should be retired is often rewritten for months instead.
Check whether the article is the only source for a process or a policy. A single page may carry a legal or safety instruction that another team still needs. Record the dependency before retiring it. Move the instruction to an owned page first if it is still required.
Set an expiry for a temporary article, such as a launch note or a one-time exception. Record the expiry date when the page is published. A temporary page without a date becomes permanent by default. The review should be automatic for that page family.
Give every retirement trigger a test the reviewer can apply. A discontinued product is easy to confirm in the catalog, while no longer useful needs a reader, a question, and a date. Record the evidence used. A trigger that depends on opinion will be argued instead of applied.
Retire with a redirect and a pointer
Send the old URL to the best replacement, not to the knowledge base home page. A reader who followed a link deserves the closest answer. Record the redirect target and the date it went live. A home-page redirect tells the reader that the work was not considered.
Add a short note on the replacement page when the old article covered a different case. Explain what changed and where the new instruction lives. Record the note and the owner. A silent replacement can leave the reader unsure whether the old rule still applies.
Keep the retired page's title in the redirect map so search and bookmarks resolve cleanly. Record the old title, the new URL, and the retirement date. Test the redirect from a bookmark and from an internal link. A redirect that works only from the site search is not enough.
Notify the teams that used the page before the retirement takes effect. Name the replacement and the date, and ask for objections with a deadline. Record the notice and the responses. A team that learns after the change will keep using the old copy.
Check the redirect after thirty days instead of only on the day it is set. A later page move or a site update can break the path. Record the check and the result. A redirect that was correct once is not a permanent control.
Keep the decision trail
Record the reviewer, the date, the trigger, and the decision for every retired article. Store the record with the article history rather than in a chat. A later reviewer should be able to see why the page was closed. The trail protects the team when a reader asks what happened.
Keep a copy of the retired content for the retention period the client requires. Mark it as retired and limit access to the people who need it. Record where the copy is stored and who can retrieve it. Deleting the only copy can make a later dispute impossible to answer.
Review the retirement list each quarter for pages that were closed too early. A replacement may have lost an important exception or a required step. Record the finding and reopen or repair the page. Retirement should be reversible when the evidence changes.
Report the number of retirements, redirects, and reopened pages beside the overdue review count. A healthy knowledge base retires pages as well as updates them. Record one improvement to the review or redirect process. The report should show the library is being maintained, not only measured.
Assign the retirement list to one owner who can answer questions about it. A shared folder without an owner becomes a place to store decisions nobody explains. Record the owner and the monthly review time. The trail is only useful if someone can walk a reader through it.
For the next step, compare this workflow with Audit a shared knowledge base before it slows a support team and the operations guide. For access and oversight, use the authoritative planning reference alongside your own policy.
