# Event date discrepancy audit

Event / edition: ______  Approved date, local time, venue and status: ______  Approved by/date: ______

| Surface and URL | Date/time/venue currently seen | Approved value | Root source or system | Correction owner | Updated at | Attendee-view verification and evidence |
|---|---|---|---|---|---|---|
| Landing page and ticket CTA | | | | | | |
| Schedule, speakers, FAQs and footer | | | | | | |
| Registration form, success page and email | | | | | | |
| Ticket provider listing and purchase URL | | | | | | |
| Poster, banner, PDF and calendar file | | | | | | |
| Title, description, social image and Event markup | | | | | | |
| Each language route and old edition link | | | | | | |
| Venue, sponsor and external directory | | | | | | |

## Triage
- [ ] Is this an isolated typo, an actual reschedule, or a separate edition?
- [ ] Does the published site disagree with itself, or is only an external/search display stale?
- [ ] Have ticket holders been told what remains valid and where to get help?
- [ ] Does the published Event markup match visible facts and correct status?
- [ ] Were mobile, first/repeat visit and purchase destination checked?
- [ ] For a stale search display, was the exact URL and last crawl inspected?

Public correction notice / support contact: ______
Open discrepancies and next review owner/date: ______