Event incident reporting form: fields that matter
Something has happened on site, and the team needs a record that is factual, short and usable by the people who decide what happens next.
The short answer
An incident reporting form should capture who reported, when and where, what was observed, who was told, what the venue or emergency services decided, and what is still unknown. It records facts and handovers, not opinions or blame.
Keep it to one page so a registration desk lead can complete it in a few minutes. Medical, security and emergency decisions stay with emergency services, the venue and other competent parties; the form only shows who was told and when.
What the form is for
The form gives the event owner, the venue and any later reviewer the same set of facts. It also shows that the right person was told at the right time.
It is not a statement of cause or fault. Insurers, the venue and legal advisers decide what the record is used for, so write only what was seen or said.
Fields to capture, and why
| Field | What to write | Why it matters |
|---|---|---|
| Reporter | Name, role and how to reach them during the event. | The reviewer can ask follow-up questions. |
| Date, time, place | Clock time noticed and the room or area, using the venue's own room names. | Matches the venue's own log. |
| What was observed | Plain facts: what the reporter saw or heard, in their words. | Separates observation from guess. |
| People involved | Roles or initials only, unless the person agrees to be named. | Limits personal data from the start. |
| Who was told | Name or role, time, and by what route. | Shows the escalation path was followed. |
| Decision taken and by whom | The venue, emergency services or authorised owner who decided. | Keeps authority with the competent party. |
| Still unknown | Open questions and who is finding out. | Stops guesses entering the record. |
| Form owner and storage | Who holds the original and who may read it. | Controls access; see the privacy page. |
Who completes it, and where it goes
The first person aware gives a verbal report to the on-site incident contact. That contact, or the person they nominate, completes the form while facts are fresh.
The original goes to the event owner or the named incident lead. A copy goes to the venue only if the venue's own procedure asks for one. Agree this before the event, using the responsibility matrix to show who completes, who reviews and who is informed.
Common mistakes
- Writing a conclusion such as the cause, or who was at fault, instead of what was seen.
- Naming people when a role would do.
- Leaving out the time the venue was told, which is the entry reviewers ask for first.
- Several versions of the form kept on different phones with no single owner.
- No line for what is still unknown, so assumptions harden into the record.
Worked example · Fictional example
A one-day forum, one attendee unwell
Fictional organisation and figures, for illustration only.
At a fictional fintech association's forum, a volunteer notices an attendee sitting on the floor of the foyer looking unwell. The volunteer tells the registration lead, who contacts the venue duty manager using the contact sheet.
The registration lead completes the form: reporter role, foyer, time the volunteer noticed, what was seen, the time the duty manager was told, and that the venue's first-aid team attended. The decision about the attendee's care is recorded as made by the first-aid team. Under still unknown: whether the attendee wants the association told anything further. The form is passed to the event owner and stored with access limited to two named people.
Use this yourself
One-page incident reporting form
Copy this into a shared form or printed sheet. Complete it in plain facts, and leave a field blank rather than guessing.
- Reporter name, role and contact during the event:
- Date and clock time first noticed:
- Location (use the venue's room name):
- What was observed, in plain words:
- People involved (roles or initials unless they agree to be named):
- Who was told, at what time, by what route:
- Decision taken, and who took it (venue, emergency services or authorised owner):
- Actions requested of the organiser by those parties:
- Still unknown, and who is finding out:
- Form completed by, time, and where the original is stored:
- Who has been given a copy and why:
Handle it in-house, or bring in help?
Your team can usually handle this when
- A small, single-room event with one clear on-site contact and a venue that supplies its own incident log.
- Your team has agreed a single place to store the forms and who may open them.
Outside planning help earns its fee when
- Several rooms, suppliers and volunteers all collect information in different ways.
- The organiser and the venue use different forms and no one reconciles them.
- A board or insurer wants a consistent record format before the event is approved.
Want the escalation route set up before the event?
A conference project lead can agree the form, the on-site contact and the venue's handover points with your committee and the venue, and brief the volunteers who will use them. The decisions on medical, security and emergency matters stay with the venue, emergency services and your authorised owners. Send your current contact list and any form you already use.
Questions organisers ask
Should the form include names of the people involved?
Use roles or initials unless the person agrees to be named or a competent party asks for names. Check with the venue and your data-protection contact before deciding what to keep.
Who decides whether to call emergency services?
Anyone on site can raise the alarm using the venue's own route. The decision about response belongs to emergency services and the venue's duty team. The form only records who was told.
How long should the form be kept?
Ask your legal adviser or data-protection contact and the insurer. Record the answer on the form's storage line so volunteers do not decide on their own.
Do we need a form for minor issues such as a lost badge?
No. Set a threshold with the event owner, for example anything involving injury, safety, security, harassment or a stoppage, and say that lower-level issues go on the normal issues log.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.