Retirement is not deletion
Deleting an outdated knowledge-base article feels clean, but it often removes the only explanation of why a rule changed. The better move is to retire the article: remove it from the active answer path, preserve its history, and point every inbound reference to the approved replacement. That way the support queue gets a current answer while a later reviewer can still see what the team used before. A Philippines-based knowledge specialist can classify the article, find its references, draft the replacement, and prepare the redirect. The specialist should not decide that a policy has changed, approve the new wording on behalf of the business owner, or delete the audit history. Retirement is a controlled content change, not a cleanup race.
Classify why the article is stale
Not every stale article should be handled the same way. It may be factually wrong, incomplete, superseded by a new process, duplicated by a better article, or simply old but still correct. Each reason implies a different action: correction, expansion, redirect, merge, or a fresh review date. Write the reason in the retirement record so the next reviewer does not have to guess. Check the source of truth before deciding. A product page, a signed policy, a system field, or an approved process note may have changed. If the source cannot be found, the article is not automatically wrong; it may be unsupported. Mark it as unverified and route the question to the owner. The distinction between 'outdated' and 'unverified' matters because it changes who must act.
Find every inbound path
An article can be linked from the help center, a saved reply, a training deck, a chatbot answer, an internal bookmark, and a support macro. Search the systems you can access and record where the article appears. If you cannot search every system, say which ones were checked and which were not. A retirement that fixes the public help center but leaves an old macro in the queue has not finished the job. Build a reference list with the location, the owner, and the action required. Some references can be updated by the knowledge team; others need the owner of the macro, training material, or chatbot flow. Route those requests with a due date and a clear replacement link. Do not ask a busy queue owner to hunt for the new article; give them the exact destination.
Write the replacement before removing the old answer
The replacement should answer the same user question with the current rule, the current source, and the current escalation path. Keep the structure familiar so readers can compare old and new. If the change is material, add a short change note that explains what is different and when it took effect. Do not bury the change in a long revision history that nobody reads. Have the business owner approve the replacement content before the old article is retired. The knowledge specialist can prepare the draft, check the links, and confirm that the examples match the approved rule. The owner confirms the policy and the customer-facing commitment. If approval is delayed, keep the old article visible with a clear review flag rather than replacing it with an unapproved draft.
Stage the cutover
A safe cutover has a date, a sequence, and a rollback. Publish the replacement, update the highest-traffic references, verify that the old link redirects or shows a retirement notice, and only then remove the old article from the active search index. Check the top entry points after each step. If a link breaks or the new answer is wrong, restore the old path and record the reason. Tell the support queue what changed before the first shift that will use the new answer. A short note with the old title, the new title, the effective time, and the escalation contact is enough. Do not rely on the article being discovered in search. The people answering customers need to know that the answer changed and where to send a question if the new wording does not fit a real case.
Verify adoption and review dates
After the cutover, sample recent cases that used the old article and confirm that the new answer was available, findable, and correct. Check the redirect, the search result, the macro, and the training link. Record any residual old references and assign an owner. A retirement is complete when the old answer no longer reaches a customer and the new answer has been used successfully. Set a review date for the replacement and write it in the article metadata. A knowledge base is a living queue, not a finished library. Review high-risk articles more often, especially those involving money, access, safety, legal exposure, or a customer promise. Retire the replacement when it becomes stale, using the same controlled process rather than letting it drift.
Sources and limits
NIST, CISA, and the U.S. Government Accountability Office publish general guidance on information quality, access, and internal control. The U.S. National Archives provides records-management principles that help distinguish an official record from a convenience copy. These sources do not decide a specific company's retention schedule or content policy. Sources: https://www.nist.gov/cyberframework https://www.cisa.gov/ https://www.gao.gov/products/gao-14-704g https://www.archives.gov/records-mgmt