Verify a claim, not just a website.
A credible website can contain an old event page. An official account can announce a proposed change that has not taken effect. A shared flyer can omit the year. Start by listing the facts the reader needs: what is happening, who it applies to, when, where, how to act and what has changed.
Identify who owns each fact. An organizer can confirm event cancellation; the venue can confirm its address and access arrangements. A service department can confirm eligibility or a changed office location. A third-party listing is useful for discovery but may not be the authority for a deadline.
For official agency content, obtain the required internal factual review and publication approval. For an independent community resource, identify the publisher’s independent status and attribute information accurately. Do not make an independent summary look like an official notice.
Use a source hierarchy with a conflict rule.
| Source | Useful role | Check before relying on it |
|---|---|---|
| Responsible agency or organizer | Confirm the fact it controls | Current notice, scope, effective date and official identity. |
| Official venue or partner | Confirm details within its role | Whether its information covers this exact occurrence. |
| Credible original reporting | Add independently reported context | Publication date, named evidence and subsequent corrections. |
| Established event platform | Find registration or occurrence details | Organizer identity, year, ticket state and latest update. |
| Public social post | Discover a change or confirm an authorized announcement | Account identity, original post, date and supporting source. |
| Repost, screenshot or AI summary | Locate a possible lead | Find and inspect the original before treating it as evidence. |
On a small screen, scroll the table sideways to see every column.
A hierarchy is a starting point, not automatic truth. A newer unattributed repost does not override an older signed notice. If material facts conflict, inspect the source revisions and request resolution through the approved contact path. Until resolved, hold the affected instruction or publish only what is confirmed with a clear, useful qualification.
Use a dated verification record.
| Field | Entry to retain |
|---|---|
| Item and claim | Stable item ID plus the exact fact being checked. |
| Authority and URL | Organization responsible for the fact and original destination. |
| Source date and revision | Publication/update date, effective date and edition if available. |
| Check time | When the editor inspected that source, with time zone where relevant. |
| Conflicts and limits | Missing year, inconsistent venue or unconfirmed cost. |
| Decision | Verified for stated scope, hold, revise or remove; identify reviewer. |
| Affected versions | Website page, event occurrence, email and scheduled social revisions. |
| Next check trigger | Before publication, near occurrence or on a known change. |
On a small screen, scroll the table sideways to see every column.
A check timestamp records the work performed. It does not certify that a fact will stay unchanged. Keep source publication dates and editorial check dates separate. Preserve only the evidence the approved process needs; avoid unnecessarily copying personal data or entire copyrighted articles.

Worked example: a venue conflict.
Fictional Cedar Bay example. An event-platform page lists a community workshop at the library. A later post from the verified organizer says it moved to the recreation center. An old flyer still circulates without an update.
The editor checks that the post concerns the same dated occurrence and that the organizer owns the change. The recreation-center information is checked for the exact address and any relevant access instructions. The record identifies the old listing as superseded and the organizer’s announcement as the source of the change.
The website’s existing event destination is updated. Scheduled posts using the library location are paused or revised and reapproved. The editor checks the live result and records the change. A second event page is not created simply because the venue changed.
If the supposed organizer cannot be authenticated or the date does not match, the editor holds the disputed location and seeks confirmation. Filling the blank with the most plausible address would turn uncertainty into misinformation.

Check dates, numbers, links and media in context.
- Confirm the year, full date, local time zone and whether the source describes one occurrence or a series.
- Distinguish free admission from free registration and check any eligibility or reservation condition.
- Open the actual action destination and confirm it serves the current item, not a past edition.
- Trace an image to its original context and confirm permission before reuse; a familiar photograph does not verify an event.
- Check whether a cancellation, closure or correction has superseded the original announcement.
- Treat an AI-generated summary as a draft to verify against the original, never as an independent confirming source.
For urgent safety information, use the agency’s authorized emergency communication procedure and responsible source. A routine publishing checklist does not confer authority to issue emergency instructions.
Carry the source through approval and correction.
The historical GOV.UK fact-checking guidance (opens in a new tab) is a useful reference for separating factual review from content preparation in a government publishing process. It is UK guidance, not a municipal approval rule. The worksheet here is an original operational adaptation.
Connect the verified source revision to the exact copy approved for each channel in the content calendar. If a material fact changes after approval, reassess the affected versions before publication.
Use the correction guide for an error already live and the governance model to assign responsibility. The strongest evidence trail is short enough to maintain and specific enough to explain why a public statement was published.

