In 30 seconds
Knowledge goes stale unless someone keeps it current. Give each source an owner and a review habit, and mark when it was last checked. This matters as much as any AI you build on top of it.
Why this comes up
A document that was accurate in March can be wrong by September: a price changed, a policy was updated, a supplier changed terms. Nobody edited the document, so it looks fine. It is quietly wrong.
An AI answering from stale knowledge produces confident, wrong answers, and hides the staleness behind a smooth response. Keeping knowledge current is how you prevent that at the source.
Give every source an owner
Knowledge that nobody owns will drift. For each source your workflow relies on, name one person responsible for keeping it correct. This is not about blame; it is about making sure someone is actually looking.
Set a review cadence that matches the content
Different knowledge ages at different speeds:
- Stable knowledge, a core process or a durable rule, can be reviewed roughly yearly.
- Changing knowledge, prices, product details, current procedures, needs more frequent review.
- Fast-changing knowledge, anything tied to a vendor or a temporary arrangement, may need review monthly, or should not be stored as fixed knowledge at all.
Match the review cadence to how fast the content actually changes.
Make freshness visible
Mark each source with when it was last reviewed. This does two things: it lets people judge whether to trust it, and it lets you find overdue sources at a glance. A visible review date is a small habit with a large payoff.
For a workflow that uses retrieval, keep the searchable set to current, reviewed sources, and remove or archive the rest. See how to prepare documents for AI.
A small example
An assistant kept quoting an old delivery fee. The fee lived in a document nobody owned. Assigning an owner, setting a quarterly review, and stamping the review date meant the next change was caught promptly, and staff could see the source was current before trusting it.
What this does not solve
A review habit keeps knowledge fresh; it does not guarantee the reviewer catches every error, and it adds ongoing work. Accept that maintenance is part of the cost of a knowledge system, and plan for it rather than hoping documents stay correct on their own.
Good enough to move on when
- Every relied-upon source has a named owner.
- Each source has a review cadence matched to its content.
- Sources show when they were last reviewed.
- Overdue sources are easy to find and address.
