Find the claims that need checking
Mark numbers, dates, prices, availability, qualifications, promised benefits, quotations and comparisons. For each, record the source, its date, the scope of the information and the person who can approve it. “Available everywhere” needs a different check from a general description of a working method.
Separate organisation-specific facts from public information. A team may confirm its normal response process, while a sector statistic needs its original source. If evidence is missing, describe a possibility as such or remove the claim.
- Sensitive claims marked in the draft.
- Source and owner associated with each claim.
- Wording adjusted when evidence is absent.
Return to the right source
For a technical rule, read the document defining it; for a supplier announcement, the original post; for an internal figure, the approved record. Commentary can clarify a topic, but the statement it attributes to the original source still needs checking.
Record publication and event dates when they differ. Check that the document addresses the product version, territory and period your page describes. Do not turn a limited observation into a general promise.
- Primary source found where possible.
- Version, period and territory match.
- Quotation or paraphrase reflects the document.
Connect evidence to published wording
In the editorial register, link the reference to the precise passage, date checked and content owner. Readers do not need the internal spreadsheet, but a specialised claim often benefits from a nearby source link. If you quote a client or show its logo, confirm permission and publication context.
For a case study, separate work delivered, observed measure and interpretation. A campaign or price change at the same time may prevent attributing a result to the website alone. The case-study guide gives a cautious structure.
- Claim register available to editors.
- Useful public links near the claim.
- Quotation and visual permissions checked.
Define review triggers
Set a next check for changing facts: prices, software versions, hours, people, figures and rules. Add immediate triggers such as a service change, a reported correction or an announcement from the primary publisher. A style review alone is insufficient.
When a fact becomes uncertain, correct the page and its translations, then log the change. If two pages answer the same question differently, designate a main editorial source and link or merge the others.
- Review date or event defined.
- Translations and related pages included in corrections.
- Short change history retained.