Problem
An AI answer can describe outdated information as if it were current. People need to know when an answer has not been checked against recent sources.
Solution
Show a notice when a time-sensitive answer relies on the model’s training data. Include the model’s published knowledge cutoff where available, and explain that it does not guarantee complete knowledge before that date.
Distinguish an answer checked against current sources from one that was not. If search is available, offer a way to check the information and show the sources used.
Keep the notice attached to the relevant answer. A warning on every response is easy to overlook.
Use when
The assistant answers questions about changing information and may rely on training data.
Don’t use when
The answer is drawn from supplied material or retrieved sources, or the task is generation rather than recall. A cutoff notice on a rewritten paragraph is noise attached to an operation the cutoff doesn’t affect.
Trade-offs
Frequent notices become easy to ignore, while missing a notice can give false confidence. Detecting time-sensitive questions is imperfect. A cutoff date helps explain a limit but does not establish that an answer is accurate.
Checklist
- Does the notice appear on time-sensitive answers rather than all of them?
- Is a specific date given rather than a vague warning?
- Does the date track the model actually used?
- Can the viewer tell whether this answer was checked against live sources?
- Is the absence of sources meaningful in this product?
- Does the model picker show cutoffs alongside the names?
- Is there a one-click path from the notice to a search-backed answer?
- Does the notice survive copying or sharing the answer?
- How does it read on the tenth occurrence in one session?
- Is the notice suppressed when the answer came entirely from supplied material?
Compare
Claude publishes per-model training cutoffs in its documentation, which makes the property checkable rather than folkloric, and leaves surfacing it to the product built on top. ChatGPT mostly resolves the question by searching when a query looks current. A disclosure problem becomes a retrieval one, and the viewer is left to infer from the presence of sources. Perplexity sidesteps the pattern almost entirely by retrieving for nearly everything, so its equivalent risk is a stale source rather than a stale model. GitHub Copilot shows the same limit in its sharpest form, suggesting code against the library versions present in its training data, so a stale cutoff surfaces as a deprecated API call rather than as a wrong fact.
Related
Citation chip and Source list show material used to check an answer. Mode switch can enable search. Refusal applies when the assistant lacks enough information to answer. Model picker can show each model’s cutoff.