Philippines staffing blog ·

Set a knowledge article expiry date before customers see it

How to give published answers a review date, a named owner, and a safe fallback when the guidance lapses.

Set a knowledge article expiry date before customers see it help desk operations illustration

Direct answer

Operational guidance

Why an article needs an end date

A knowledge article describes a product, a policy, or a workaround at one moment. The product changes, the policy is revised, and the workaround is replaced, but the article stays published. An expiry date turns that silent drift into a scheduled decision. The date does not have to be exact, but it has to exist.

Without an end date, an old article looks as trustworthy as a current one. Agents copy the steps, customers follow them, and the first sign of trouble is a failed request. Add an expiry field to the article template and make it visible to the reviewer. A date that nobody sees is barely better than no date at all.

Choose the trigger that starts the clock

Start the clock from the event that makes the article risky, not from the day it was written. A billing article should expire when the next rate change is scheduled. A workaround should expire when the vendor fix is released. A policy answer should expire at the review date named by the client.

Some articles have no natural event, so use a fixed review interval instead. A twelve-month interval is common for stable process guidance and a ninety-day interval for fast-moving product detail. Record the reason beside the date so the next reviewer understands the choice. A date without a reason will be extended by habit.

Mark the owner and the review window

Every article needs one owner who can confirm or retire it. The owner is usually the person who knows the source material, not the person who happened to write the page. Name the owner in the article record and give them a review window before the expiry date. The window should be long enough to check the source and short enough to act.

Send the owner a reminder at the start of the window, not on the expiry date. The reminder should include the source link and the question the article answers. Ask for one of three outcomes: confirm, revise, or retire. A clear choice is easier to complete than an open request to review.

Handle an article that expires while the queue is busy

A busy queue tempts the team to extend every expiry date without reading the article. That habit defeats the control and leaves stale guidance in place. Instead, give the owner a short fallback: hide the article from customer-facing search until it is reviewed. The internal copy can remain available to agents with a visible warning.

If the article is the only answer for a common request, escalate the review rather than let it lapse quietly. Name a backup reviewer and a deadline for the decision. Tell the client which answers are under review so they are not surprised by a change. A controlled gap is safer than a confident wrong answer.

Tell agents what to use when the article lapses

Agents need a next step when an article expires, because the queue does not pause for the review. Point them to the approved fallback, the escalation path, or the saved reply that asks for more time. Put that instruction in the expiry notice rather than in a separate policy page. An agent who has to search for the rule will improvise.

Review a sample of tickets handled during the lapse and look for answers that drifted. If agents invented a workaround, capture it and send it to the owner as evidence. The lapse is also a test of whether the article was still needed. An article that nobody missed is a candidate for retirement.

Review expiry dates on a fixed cadence

Once a month, list the articles that expired, the ones that were extended, and the ones that were retired. Look for owners who extend without reviewing and for articles that expire repeatedly. A repeated extension usually means the review interval is wrong or the owner is overloaded. Fix the cause instead of adding another reminder.

Report the count to the client in plain language and name the decisions that came out of the review. Keep the retired articles in an archive so old tickets still make sense. Update the template when a new product or region changes the risk. The goal is a knowledge base that admits what it does not know.

Authoritative sources

Related planning pages