Tier 1 sources
Official regulator, government, court, peer-reviewed paper, public company statement or primary report.
Incident source verification
A safer public incident database starts with source discipline.
GCCAP incident intelligence creates authority without accusation by classifying each source, recording what is known and identifying the evidence gap before any public release.
SOURCE VERIFIEDPublic incident entries require reliable sources, neutral wording and evidence-gap analysis before release.
GCCAP EVIDENCE VIEWSOURCE VERIFIED
Evidence standard
Incident record fields
Every public incident must be reduced to verifiable facts and an evidence question, not blame.
Date and locationWhen and where reliable public sources say the event occurred.
Airline/caterer namingNames appear only when already reported by reliable public sources.
Reported consequenceDiversion, illness report, facility action, recall, warning, re-catering or disruption where documented.
Evidence that would matterTemperature history, cart, stage, flight, timestamp, dwell time, custody and corrective action.
Safe inclusion statusPublic-candidate, needs-review, background-only or internal-only.
Governance
Release safeguards
This page builds trust by showing the review method before any public incident material is released.
- 01
Use reported, alleged or publicly documented language where appropriate.
- 02
Do not infer fault, causation or liability beyond the source material.
- 03
Focus on evidence gap, operational consequence and review value.
- 04
Keep private clients, supplier stack and hardware pathway out of public incident notes.
- 05
Use the daily incident watch as a source queue, not an automatic public feed.
Turn incident uncertainty into evidence questions.
Source discipline helps auditors, insurers and procurement teams understand which records matter before an incident is reviewed.