Philippines staffing blog ·
Give every knowledge base article an owner and a review date
An article without a named owner ages quietly, so each page needs a scope, a reviewer, a trigger, and a removal path that someone will actually follow.

Direct answer
Operational guidance
Assign an owner by subject, not by seniority
An article owner is the person who can confirm the content is still true, not the most senior person available. Assign by subject so the owner can answer a question about the article without research. One owner per article is enough; a committee will not review anything. Record the name in a field the tool can report on. Write the owner's role beside the name so a replacement can be found when the person moves.
Give the owner a small, realistic set. An owner with two hundred articles will review none of them, while an owner with five may keep them current. Balance the load by subject area and adjust when the catalog grows. The assignment should be visible to the owner, not buried in a spreadsheet only the manager can open. Count the articles per owner once a quarter and rebalance before the list becomes a formality.
Define the scope in the article
State what the article covers, which product or plan it applies to, and which requests it should answer. A scope sentence lets a reader decide in seconds whether the page is relevant. It also tells the reviewer what to check when the product changes. Without a scope, every article looks like it applies to everything. Put the scope in the first paragraph, not in a metadata field that agents never open.
Include the conditions that make the article wrong, such as a plan tier, a region, or a temporary policy. Reviewers can then test the boundary instead of re-reading the whole page. Agents can also route a request that falls outside the scope without guessing. A precise scope prevents the slow drift that turns a correct article into a misleading one. Test one out-of-scope request during review to confirm the article tells the reader to stop.
Set a review date and a trigger
Use two signals: a calendar date and an event. The date ensures the article is read even when nothing seems to change, while the event catches a launch, a policy change, or a pricing update. Write the event in the article's metadata so the owner sees it. A date alone misses real changes, and an event alone misses quiet decay. Record both in the article header so a reader can see when the next check is due.
Choose a review interval that matches how often the subject changes. A password reset article may need a quarterly check, while a legal notice may need review only when the law changes. Do not apply one interval to the whole catalog. The interval should be a decision, not a default that nobody remembers setting. Explain the interval in the knowledge base guide so a new owner understands why the dates differ.
Make the review a short, recorded task
A review should take minutes: open the article, test the links, confirm the steps against the current system, and record the result. Ask the reviewer to note the version tested and the date. A review that requires rewriting the article will be postponed. Keep the task small enough to finish between tickets. Give the reviewer a short checklist that ends with the decision to keep, correct, or retire.
Record the outcome as current, corrected, or retired. A current result is still evidence, because it shows someone checked. Store the record with the article so the next reviewer can see the history. A review without a record is indistinguishable from no review at all. Include the reviewer's name and the date so the next check has a starting point.
Retire articles that no longer help
Give every article a removal path. When a product is retired or a process is replaced, the article should leave the agent's view quickly and stay readable for audit. Archive it rather than deleting it, and add a note that names the replacement. An old article that remains searchable will be used by someone under pressure. Tell agents where retired content went, because a page that vanishes without explanation creates doubt.
Check saved replies and macros for links to the retired page. A dead link in a template is worse than a missing article because the agent may send it without noticing. Update the template in the same change window. The retirement is complete when no active workflow points at the old page. Search the template library for the article title and its old links, not only for the URL.
Report on the catalog, not the count
Report how many articles are overdue for review, how many were reviewed on time, and how many were retired. A count of total articles says nothing about whether they help. Pair the review numbers with search and usage data to see which pages agents actually open. A popular overdue article is a bigger risk than an unread one. Show the oldest overdue item first, because it has had the most time to mislead a customer.
Share the report with the client in plain language and name the articles that need a decision. A client who sees three overdue policy pages can assign an approver; a client who sees a percentage cannot act. Keep the list short and specific. The goal is decisions, not a dashboard. Ask for a decision on each named article and record the answer in the next report.
Keep the owner list current when people leave
Check ownership when someone changes role or leaves, and reassign before the account is closed. Orphaned articles are usually created by a departure, not by a planning failure. Add the check to the offboarding checklist and confirm it in the same week. A missing owner is invisible until the next product change. Give the departing owner a short handover task for the articles that need context.
Ask each owner to confirm their list once a quarter. A confirmation is cheap and catches the drift that a quarterly report cannot see on its own. If an owner cannot confirm, reassign the article rather than leaving it unowned. Ownership should be a live fact that the team checks, not a field set once at creation and never read again. Remove the confirmation burden from anyone on leave, and reassign those articles before the absence begins.
Authoritative sources
- NIST SP 800-53 Rev. 5 security and privacy controls
- ISO 18295-1:2017 customer contact centres
- BLS Occupational Outlook Handbook: customer service representatives
- NIST Cybersecurity Framework 2.0