# Event lessons learned register

Copy this file for each event edition. Keep the register in a shared team location with a named owner. Link to restricted source records instead of pasting attendee details, payment information or incident narratives into the register.

**Event / edition:** [name and year]

**Event date and time zone:** [date; IANA time zone]

**Register owner:** [name and role]

**Review date:** [date]

**Next-edition planning location:** [link or folder]

## Index

| ID | Area | One-line lesson | Decision | Owner | Next check |
| --- | --- | --- | --- | --- | --- |
| LL-01 | Registration | Arrival queue peaked just before opening | Test an earlier second lane | Operations lead | Before next venue walk-through |
| LL-02 | [area] | [specific observation] | [repeat / test / investigate / no action] | [person] | [milestone or date] |

## Lesson record — duplicate this block for each ID

**ID and area:** [LL-##; programme / registration / accessibility / venue / suppliers / communications / finance / other]

**What was planned:** [the intended condition or process]

**What was observed:** [a concrete success or problem; when and where]

**Evidence and access-controlled location:** [record name, owner and link; note missing evidence]

**Who or what was affected:** [describe the service or task, without unnecessary personal data]

**What remains uncertain:** [possible cause, data gap or conflicting account]

**Lesson for the next edition:** [one reusable principle, not a blame statement]

**Decision:** [repeat / test a change / investigate / no action, with reason]

**Action or experiment:** [specific change and observable result]

**Decision owner and delivery owner:** [names; they may differ]

**Next review:** [planning milestone or date]

**Status:** [captured / evidence needed / approved for next edition / in progress / verified / closed]

**Verification note:** [what happened after the next review or event; link to record]

## Worked fictional example: LL-01

**What was planned:** Two check-in lanes would open before doors.

**What was observed:** One lane opened at doors; staff saw a queue near the main entrance during the first arrivals.

**Evidence:** Door lead notes and scanner timestamps in the operations folder. No complete wait-time sample was taken.

**What remains uncertain:** Whether lane staffing or the arrival burst contributed more to the delay.

**Lesson:** Confirm lane staffing and opening readiness before publishing the arrival plan.

**Decision:** Test an earlier second-lane readiness check at the next venue walk-through.

**Owner / next review:** Operations lead, before the next event's door briefing.

**Verification:** Leave blank until the change has been tried and measured.

## Close and carry forward

- Merge duplicate observations while keeping their source links.
- Confirm the wording with people who supplied evidence; mark disputed findings as unresolved.
- Move approved actions into the next edition's working plan and keep the lesson ID as a cross-reference.
- Review the register before repeating a venue, supplier or registration setup. Record whether a change worked; do not mark a hypothesis as proven when it has only been assigned.