# Event fact sheet — editable internal template (English)

Copy this file for one event edition. Replace bracketed fields only after the responsible owner confirms them. Keep unpublished details in the internal copy. `PENDING` is not approved public wording.

## Control

| Field | Value |
| --- | --- |
| Event and edition | [Event name / edition] |
| Working sheet owner | [Name / team] |
| Approver for changes affecting attendees | [Name / team] |
| Last full review | [YYYY-MM-DD, time zone] |
| Next planned review | [YYYY-MM-DD, time zone] |
| Public event page | [Published URL or PENDING] |
| Support route | [Published contact URL or PENDING] |

## Fact register

Use one row for each fact that can change independently. Add rows for each day, ticket type, venue entrance, session, or access detail as needed. Record a direct owner confirmation or source record; a copied social post is not the original source.

| ID | Fact / visitor question | Exact proposed public value | Status: CONFIRMED / PENDING / WITHDRAWN | Authoritative source or confirmation link | Fact owner | Verified by / date | Next review trigger | Where this fact appears |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| F01 | What event and edition is this? | [Name and edition] | PENDING | [Owner-approved event record] | [Name] | [Name / YYYY-MM-DD] | Name or edition changes | [Page / email / partner] |
| F02 | When does it start and end? | [Unambiguous date, local times, named time zone] | PENDING | [Confirmed programme] | [Name] | [Name / YYYY-MM-DD] | Schedule changes | [Page / ticket flow / email] |
| F03 | Where should an attendee arrive? | [Venue, address, correct entrance] | PENDING | [Venue confirmation] | [Name] | [Name / YYYY-MM-DD] | Venue or entrance changes | [Page / map / arrival email] |
| F04 | Where does registration begin? | [Full published URL] | PENDING | [Ticket configuration] | [Name] | [Name / YYYY-MM-DD] | Sales window changes | [Page button / partner copy] |
| F05 | What price or fee is shown? | [Amount, currency, applicable fees, sales window] | PENDING | [Live checkout and approved price record] | [Name] | [Name / YYYY-MM-DD] | Price or fee changes | [Page / checkout / email] |
| F06 | How can a visitor ask for help? | [Public contact route and expected use] | PENDING | [Support owner confirmation] | [Name] | [Name / YYYY-MM-DD] | Route changes | [Page / email / partner copy] |
| F07 | What access information is confirmed? | [Specific confirmed detail or “details to follow”] | PENDING | [Venue / access owner confirmation] | [Name] | [Name / YYYY-MM-DD] | Arrangement changes | [Page / arrival email] |

## Publication destinations and release check

Do not mark a destination complete merely because a draft looks correct. Open the published version as a visitor. Check a phone and desktop view where relevant.

| Destination | Draft or scheduled URL | Fact IDs used | Copy approved by / date | Published URL or sent message ID | Live check: date, price, link, contact, mobile | Reviewer / time | Status / follow-up |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Event page | [URL] | [F01–F07] | [Name / date] | [URL] | [Findings] | [Name / time] | [Open / done] |
| Ticket or registration flow | [URL] | [F02, F04, F05] | [Name / date] | [URL] | [Findings] | [Name / time] | [Open / done] |
| Attendee email | [Draft or campaign ID] | [IDs] | [Name / date] | [Sent message ID] | [Link and fact check] | [Name / time] | [Open / done] |
| Partner asset | [File or draft URL] | [IDs] | [Name / date] | [Partner-published URL] | [Link and fact check] | [Name / time] | [Open / done] |

## Change and correction log

| Time / time zone | Fact ID | Previous value and status | New value and evidence | Decision / approver | Destinations to update | Published replacement checked by / time |
| --- | --- | --- | --- | --- | --- | --- |
| [YYYY-MM-DD HH:MM zone] | [F##] | [Old value] | [New value / source] | [Approved / held / name] | [Page, email, partner, ticket flow] | [Name / time or pending] |

At close, save a dated copy labelled with this edition. Start the next edition from a blank template and verify every field again.