Get Started Free
🎉 Events & Weddings

Free On-Site Event Incident Report Form Template

Log an incident the moment it happens: what occurred, who was involved, action taken and follow-up owner. A free event incident report form.

~10 min
Live Preview

Quick answer

Log an incident the moment it happens: what occurred, who was involved, action taken and follow-up owner. A free event incident report form.

Incident notes written hours later lose the detail an investigation needs. This form is completed at the point of occurrence — time, location, description, people involved, immediate action, escalation and the follow-up owner — on a phone, from wherever the incident is.

Disclaimer: this form records what happened at the time it was observed. It is not a legal, insurance or safeguarding determination; report incidents to the body your event policy requires.

Methodology: the 7 fields follow the order incidents and resolutions is worked in — capture first, confirm second — and every response is time-stamped so the record can be reconciled later.

💡

About this template

The On-Site Event Incident Report Form is for organizers, stewards and venue teams who must record what happened during an event: injuries, damage, security issues, supplier failures and guest complaints.

Because entries are time-stamped and location-tagged, a pattern across a multi-day event becomes visible instead of dissolving into verbal handovers.

🗂️

Template at a Glance

Seven facts about the Event Incident Report Form, in the order you will need them.

TemplateEvent Incident Report Form
CategoryEvents & Weddings
FormatForm for incidents and resolutions
Time to completeAbout 10 minutes per response
What you getOne structured record per respondent — date and time of the incident through escalated to whom, and follow-up owner — collected in a sortable, exportable list
Best forStewards and security · Duty managers · Organizers and clients
CostFree to copy, customize and reuse on FormLM
📥

What You Collect

What respondents actually fill in for incidents and resolutions. Every line can be renamed, removed or added to once you copy the template.

🖥️

Live Preview

Sample layout of the Event Incident Report Form as respondents see it, on desktop and mobile.

…
Fill it in to see how responses flow.
📦

What's Included

Everything the Event Incident Report Form ships with before you customize it.

1

Reported from the point of occurrence

Mobile form, completed where the incident is.

2

Categorized for pattern reading

Injury, damage, security, supplier or complaint as a field.

3

Action and escalation recorded

What was done, and who now owns the follow-up.

4

Time-stamped evidence

Entries that hold up in a review or insurance claim.

🧭

How It Works

Four steps from a copy to a usable record of incidents and resolutions.

1

Use this template

Copy the form and its field structure into your FormLM workspace — free.

2

Customize

Set the incident categories to the ones your risk assessment covers, and add a safeguarding route if needed.

3

Share and collect

Give stewards and team leaders the link or a QR on their briefing card.

4

Review and act

Review the log at each shift change, and pass open follow-ups to a named owner.

🗓️

When to Use This Template

Three moments where a structured form beats an email thread or a paper sheet for incidents and resolutions.

1

Public and high-capacity events

Many small incidents that need one record.

2

Multi-day programs

Continuity across a changing crew.

3

Insurance and client reviews

Contemporaneous evidence of how things were handled.

👥

Who Is This For

Built for the people who carry incidents and resolutions after the form closes.

Stewards and security

A record they can complete standing up.

Duty managers

Escalation and ownership visible at shift change.

Organizers and clients

The event's actual incident picture.

⭐

Key Features

What makes the Event Incident Report Form a working instrument rather than a blank page.

📝

Sample Questions Inside

The exact wording respondents see in the Event Incident Report Form, in order — starting with date and time of the incident. Every question can be renamed, dropped or extended.

  1. Date and time the incident occurred
  2. Location, gate or room where it happened
  3. Which category does it fall under? (injury / damage / security / supplier / complaint / other)
  4. Describe what happened, as you saw it (open)
  5. Who was involved, and were there witnesses?
  6. What immediate action was taken?
  7. Who was it escalated to, and who owns the follow-up?
❓

Frequently Asked Questions

What should an event incident report contain?
Time and location, incident category, a factual description, people involved and witnesses, the immediate action taken, who it was escalated to, and the follow-up owner. Keep it factual, not interpretive.
Who completes an incident report at an event?
Whoever witnessed or handled it, usually a steward, team leader or duty manager — ideally at the time, since memory degrades quickly and a queue of incidents forms around the same period.
Are incident reports the same as risk assessments?
No. The risk assessment predicts exposure before the event; the incident report records what actually happened. Read together, they show whether the assessment matched reality.
Is the Event Incident Report Form free to use?
Yes. Copying it into your workspace brings all 7 fields — date and time of the incident through escalated to whom, and follow-up owner — and there is no charge to collect or export responses.
Can I change the fields on Event Incident Report Form?
Yes, and you should — swap location, gate or room for your own room names, session titles or package tiers before the first response arrives.
How many responses can Event Incident Report Form collect?
Unlimited responses, held in one sortable list keyed to incidents and resolutions.
Where do responses to the Event Incident Report Form go?
Each submission is stored in one time-stamped list keyed to incidents and resolutions, so nothing has to be retyped. The practical step is to review the log at each shift change, and pass open follow-ups to a named owner.
Why start from Event Incident Report Form instead of a blank form?
A blank form gets answered differently every time. This one fixes the sequence — date and time of the incident first, escalated to whom, and follow-up owner last — so responses stay comparable.
📚

Methods & terminology behind this template

Rubric Benchmark report Workshop summary report guide

Put the Event Incident Report Form to work on your next event

Copy it into your workspace, adjust the fields to your format and send the link — free to start.