On this page
- Evidence snapshot
- Name the owner of each article
- Date the source, not just the edit
- Data and decision boundary
- Record what changed in the client's words
- Retire an article instead of editing it into confusion
- Test the article on a live call
- Review linked articles after a change
- Copy-ready call and handoff lines
- Keep a change log agents can read
- Schedule a quarterly drift check
- Questions managers ask
- Keep planning
- Sources
A knowledge article rarely fails all at once. It drifts when a client changes a policy, a form, or a phone menu and the article keeps the old step. Agents lose trust in the library, then write their own notes beside it. The fix is a small maintenance routine that makes ownership, source dates, and retirement visible before the next call.
Evidence snapshot
Name the owner of each article
Every article needs one owner who can say whether it is current. The owner may be a team lead, a client contact, or a knowledge manager, but the name must be visible on the page. A shared inbox is not an owner because no one is accountable for the next review. Put the owner beside the source date so the two travel together.
Give the owner a small set of articles rather than the whole library. A short list can be checked in a few minutes, while a large list invites a shallow review. Record the date of the last check and the next one. When the owner changes, hand over the list in writing with the open questions. The handover should name the articles with an open question and the date the answer is due.
Date the source, not just the edit
An article can be edited today and still describe a policy from last year. Record the date of the client document, the email, or the call that supports the steps. That source date is what a reviewer needs when the article conflicts with a live call. Keep the link or the message identifier with the article. A page without a source date should be treated as unverified until the owner supplies one.
Do not let a formatting change reset the source date. A new heading or a corrected typo does not prove the content is current. Separate the edit history from the source history in the page metadata. The agent should be able to see both without opening a second tool. Label the two dates clearly so an agent does not mistake a recent edit for a recent review.
Data and decision boundary
Use this table as a starting point, then match each row to the client's tools and call guide. The manager column stays outside the team member's normal authority.
| Data or request | Team member can | Manager keeps |
|---|---|---|
| Article owner | Checks the page and reports a gap | Assigns the owner and the review date |
| Source date | Uses the date shown on the page | Confirms the client document |
| Retired article | Uses the replacement link | Approves retirement and notice |
| Live-call test | Reports a workaround | Fixes the article or the process |
Record what changed in the client's words
When a client sends an update, save the sentence that changes the work. A message that says the grace period is now ten days is more useful than a summary that says policy updated. Put the exact phrase in the change note and link it to the article. The wording protects the queue when a customer disputes what they were told.
Ask the client to confirm the change before the article goes live. A forwarded email may be a draft or a local practice rather than an approved rule. Record who confirmed it and when. If the confirmation is verbal, write the time and the person on the change note. Keep the confirmation with the article so the next reviewer can see who approved the wording.
Retire an article instead of editing it into confusion
Some articles should be retired rather than updated. A process that no longer exists, a product that was withdrawn, or a script replaced by a new system can confuse an agent even if the page says old. Mark the article as retired and remove it from the search results the agents use. Keep the record for history, but do not leave it in the working path.
Tell the floor which article was retired and what replaces it. A silent removal makes an agent think the page is broken and search for a copy. Add the replacement link and the retirement date to the notice. Review the retired list each quarter to confirm nothing still depends on it. The notice should sit where the old link used to be so an agent cannot miss it.
Test the article on a live call
Choose one recent call that used the article and read the note beside the steps. Did the agent follow the page, skip a step, or add a workaround? A workaround written in a case note is a signal that the article is incomplete or wrong. Ask the agent what they would change before the next call. Record the version of the article the agent actually opened during the call.
Run the test with a new agent and a tenured agent. The new agent shows whether the steps are learnable, while the tenured agent shows where experience fills a gap. Record both results on the article. The test is short, but it catches the drift that a desk review misses. If the two agents describe different steps, the article has a gap that training alone will not fix.
Review linked articles after a change
A change to one article can break the steps in another. If the refund article changes, the escalation article and the billing script may now point to the wrong queue. Follow the links from the changed page and check each one. Add the linked review to the change checklist. The change checklist should name the pages that must be reread, not only the page that changed.
Keep the link map small enough to inspect by hand. A page with twenty links is hard to maintain, and a missing link is easy to miss. Name the owner of each linked page and the date it was last checked. The review is complete when every link resolves and the steps still agree. A broken link should be fixed before the changed article goes live, not after a customer call.
Copy-ready call and handoff lines
Reporting drift after a call
The article said the grace period was five days, but the client's note says ten. I followed the client note and I am flagging the page so the owner can update it before the next shift.
Retiring an article
This page describes the old refund portal, which closed last week. I am marking it retired, linking the new process, and telling the floor which article to use instead.
Keep a change log agents can read
Write a short change log in the same place agents look for the article. Each entry should say what changed, who confirmed it, and when it took effect. Avoid internal ticket numbers as the only description. An agent should be able to scan the log before a shift and know what is new. The log should be short enough to read at the start of a shift and specific enough to act on.
Do not bury a customer-facing change in a long policy update. Put the change at the top with the affected call types. If the change alters a promise, add the approved wording. Review the log at the shift brief and remove entries that are no longer relevant. An entry that says several updates is not a change log because no agent can tell what is different.
Schedule a quarterly drift check
Set a quarterly review for every article in the working library. Check the source date, the owner, the links, and one live-call example. Look for an article that has not been read in a quarter even though the client changed a system. The review should produce a short list of fixes, not a report. Assign the review to the owner and put the date on the page so it is not lost in a calendar.
Use the results to change the routine, not only the pages. If most drift comes from one client contact, ask for a standing update. If it comes from one system, add the check to the release process. The next quarter should start with fewer surprises than the last. The review should end with one process change and one owner, not a list of good intentions.
Questions managers ask
Who should own a knowledge article?
One named person who can confirm the source and the review date. A team inbox can support the work, but it cannot be the accountable owner.
Should outdated articles be deleted?
Retire them from the working path and keep a record for history. Deleting silently leaves agents unsure whether the page moved or disappeared.
Sources
- ISO 18295-1:2017 Customer contact centresInternational Organization for Standardization, 2017. Requirements for customer contact centre processes, people, and performance.Source 1
- GAO-20-283G: Assessing Data ReliabilityU.S. Government Accountability Office, 2020. A practical framework for documenting data sources, testing reliability, and stating limitations.Source 2
- NIST Cybersecurity Framework 2.0National Institute of Standards and Technology, 2024. Govern, identify, protect, detect, respond, and recover functions used for control ownership.Source 3
- Privacy and Data Security GuidanceFederal Trade Commission, 2026. Business guidance on protecting customer information and honoring privacy commitments.Source 4
