Event incident report template: what your team should record

Someone has fallen near the entrance. Your front of house lead is helping, the radio is busy, and the venue manager wants to know whether that route can stay open. Later, you'll need to explain what happened. Right now, you need people to act on accurate information.

An event incident report should record when and where something happened, who reported it, what they actually observed, the response, and what still needs checking. Keep the first account intact, then add evidence, reporting decisions and corrective actions as the facts develop.

Below is a copyable event incident report template, followed by a fictional completed example. It's written for operators of paid events who need a record another shift, contractor or investigator can understand. You can adapt it to your event, but don't treat it as an official reporting form or a substitute for specialist records.

The regulatory examples follow Health and Safety Executive guidance for Great Britain and Information Commissioner's Office guidance on UK data protection. Requirements elsewhere differ. Your venue arrangements, event activities and circumstances will determine which additional procedures apply.

Deal with the incident before completing the report

The first thing you want to do is activate the relevant response. A steward shouldn't stop assisting someone to finish a mandatory description field. Your reporting process needs to work around the people managing the situation.

HSE's event emergency guidance calls for clear responsibilities, communication arrangements and procedures proportionate to the event's risks. Agree who receives reports and who can make operational decisions before doors open. The person taking notes may be different from the person directing the response.

For the message, use the location names on your actual site plan. "Person down, west foyer, beside accessible entrance" is more useful than "accident at the front" when the site has several entrances. State what help is needed and whether an immediate hazard remains. Follow the emergency plan for contacting responders.

Once someone can safely record the essentials, note the time, source, location and action taken. Complete missing details later and identify those later additions. If you need to close a route, move equipment or change the scene to protect people, do that. Record the change and its reason when circumstances allow.

Keep this report connected to your event contingency plan. The plan tells staff what to do when a particular situation develops. The report records what happened and what they did in this instance. Staff need access to both, with sensitive incident details restricted to the people who require them.

Decide which situations need an incident record

Set a clear internal reporting policy during your briefing. Include injuries, illness requiring assistance, threatening behaviour, safeguarding concerns, property damage, failed safety controls and near misses. Route specialist concerns through the appropriate procedure as well. A general event report should point to a safeguarding or medical record without copying its sensitive contents into the operational log.

A near miss deserves attention when someone narrowly avoids harm. Suppose an unsecured item falls into an empty public walkway. "Nobody injured" describes the outcome. It doesn't explain whether the item could fall again or whether the area can reopen. Record the circumstances and escalate the remaining risk.

Distinguish an incident from a routine service request. A request for directions usually belongs in customer service. Repeated reports that the accessible entrance is blocked need an operational response and may reveal a failed control. Let staff report uncertainty rather than forcing them to diagnose the category at the door.

You can combine duplicate notifications under one incident number after checking that they describe the same occurrence. Preserve each person's original account. Two reports about the west foyer could concern different people or different times, and merging them too early could hide a second incident.

Copy this event incident report template

Use one main incident record with linked accounts and attachments. The suggested fields below are an operational starting point. Review them with the people responsible for safety, privacy and relevant specialist services before using the form at a live event.

Event and record details

• Incident reference and current status:

• Event name, organizer and venue address:

• Event date and relevant phase, including setup or pack-down:

• Exact location and site plan reference:

• Time incident happened, if known, and source of that time:

• Time first reported and time this entry was written:

• Report writer's name, role and contact through the organization:

• Person coordinating the response and person reviewing this record:

• Related incident numbers, plans and specialist record references:

• Current version, amendment date and access restrictions:

Initial account and people involved

• What the reporter directly saw or heard:

• What someone else reported, with the source identified:

• Details not yet known or confirmed:

• Relevant conditions at the location:

• Person references for those affected and witnesses:

• Necessary contact details held in the restricted contact record:

• Assistance offered, accepted or declined, with source and time:

• Medical, security or safeguarding provider reference, where applicable:

Response and operational decisions

• Each action, its time and the person who took it:

• Help requested, recipient and acknowledgement:

• Area, activity or equipment restricted:

• Any changes made to protect people and why:

• Instructions given to staff or attendees:

• Decision to continue, suspend, close or reopen the affected activity:

• Decision maker, people consulted and evidence considered:

• Conditions for reopening and who checked them:

• Remaining uncertainty and the next review or handover:

Evidence and separate accounts

• Evidence reference, description and relevance:

• Person who recorded or supplied it and when:

• Original file location and authorized custodian:

• Witness account reference and time obtained:

• Any limitations, missing information or disputed detail:

• Preservation request, recipient and acknowledgement:

• Access or sharing record for sensitive material:

• Corrections or additional evidence, with author and date:

Escalation, follow-up and closure

• Relevant external reporting or notification requirements checked:

• Person responsible for each decision and submission:

• Advice obtained, decision, reasoning and time:

• Applicable deadline, source and follow-up date:

• Notification recipient, submission reference and acknowledgement:

• Corrective action, named owner and completion deadline:

• Evidence required to verify the action:

• Verifier, result and date checked:

• Unfinished actions or unresolved reporting decisions:

• Closure decision, reviewer and date:

• Retention category, review date and any preservation requirement:

Don't let the number of fields delay the first report. Your initial entry can be short while its status clearly says "response ongoing" or "awaiting review". You can collect later information through the same record without pretending it was available at the start.

Check how staff can submit a report if their usual device, connection or account is unavailable. A controlled paper copy may be appropriate for your arrangements. Decide who receives it, where it stays during the shift and how it becomes part of the main record without leaving copies unattended at the desk.

If someone transfers handwritten notes into the main report, identify the original author and the person making the transfer. Check the transcription against the original, retain the original according to your procedure and label any unreadable detail. Guessing a time or name to make a form look complete can create confusion later. Make the reporting route clear enough that a temporary steward can use it after the briefing, without needing access to unrelated attendee information or somebody else's account.

Use "unknown" when a fact hasn't been established and "not applicable" when a field genuinely doesn't apply. An empty reporting decision field could mean nobody checked it. A named reviewer and a dated pending decision make the unfinished work visible to the next person.

Write what you know and identify how you know it

The difference between observation and explanation matters. "I saw liquid on the floor beside the entrance mat" describes an observation. "The bar caused the fall" states a conclusion that requires evidence about the liquid, the fall and the connection between them.

Ask witnesses to describe where they were, what they noticed and what happened next in their own words. Record each account separately. If someone didn't see the fall but arrived afterwards, say so. Their account may help establish the response without establishing the cause.

Avoid turning a witness's description into a diagnosis. An attendee might say their ankle hurts. Record the attributed report if it's necessary for the incident record, and reference the medical provider's separate record where appropriate. Don't change it to "sprained ankle" because that sounds more complete.

The same care applies to behaviour. "Attendee shouted and struck the barrier with an open hand" is more useful than "aggressive customer". Describe the relevant conduct, the words that matter and the response. Don't infer intoxication, intent or a health condition from an impression.

If accounts conflict, keep the disagreement visible. A steward may remember a barrier being in place while a witness remembers an open route. Record who said what and what evidence could help resolve it. A smooth narrative is less useful than an honest record of uncertainty.

HSE's investigation workbook separates gathering information, analysing it, identifying controls and implementing actions. Follow that distinction in your paperwork. The initial report captures available facts; the later review considers causes. Use current reporting guidance for legal requirements, because this older workbook contains historical references.

A completed example for a fictional paid event

This fictional example shows how the template works. The names, times, records and event are fictional. It isn't a medical assessment, a determination of liability or a model decision about whether a real incident is legally reportable.

Imagine a ticketed evening performance at a hired venue in England. Admission is underway when a steward reports an attendee on the floor in the west foyer. The event's assessed emergency and medical arrangements are already operating.

First entry while the response is underway

• Incident reference: IR-014. Status: response ongoing.

• Event: Harbour Rooms Friday Session. Organizer: Harbour Events.

• Location: west foyer, entrance W on site plan SP4.

• First radio report: 18:42, recorded by control operator Jo.

• Writer: Jo, event control. Entry written at 18:43.

• Source: steward Sam's radio message from the west foyer.

• Initial account: Sam reported one attendee sitting on the floor beside the entrance mat. Sam did not see how the attendee reached the floor.

• Immediate response: Sam requested the onsite medical team and told control that the entrance needed managing while assistance arrived.

• Unknown: time of fall, cause, clinical condition and whether anyone else was affected.

This entry is deliberately limited. Jo hasn't invented an exact time for the fall or written that the attendee slipped. The record establishes when control heard about it and what support was requested. Another team member can act without treating an assumption as a finding.

Response entries added as information arrives

• 18:43: duty manager Alex instructed the entrance team to pause admission through entrance W under the event plan. Alex requested the venue manager's attendance.

• 18:44: medical team lead Leila acknowledged arrival at the west foyer. Clinical details remain in the provider's restricted record M-022.

• 18:45: venue manager Pat attended. Pat reported visible moisture beside the entrance mat. Jo attributed this observation to Pat.

• 18:46: Pat and Alex reviewed the affected route and kept entrance W closed. Staff directed arrivals using the venue's agreed alternative arrangement.

• 18:47: Pat requested cleaning and inspection of the foyer. The report notes that cleaning would change the floor condition.

• 18:53: Pat recorded completion of cleaning and an inspection of the affected area. Evidence reference E3 identifies Pat's inspection note.

• 18:56: Alex recorded the decision to reopen entrance W after consultation with Pat and confirmation that staff were in position. The reason and remaining monitoring arrangements appear in decision D1.

For a real event, the reopening decision needs the right competence and information for the circumstances. The fictional times don't establish a safe response target. Nor does cleaning prove what caused the fall. It records a control applied to the condition Pat observed.

Accounts and evidence recorded separately

Sam's account W1 states that he heard someone call for help, turned towards the entrance and saw the attendee sitting on the floor. He didn't observe the fall. His account supports the first response timeline without establishing how the incident started.

Witness W2 reports seeing the attendee lose balance near the mat. The account doesn't establish whether the attendee's foot contacted the mat. Jo records W2's location and the limits of the view, rather than converting "near the mat" into "tripped over the mat".

Pat's observation of moisture is recorded at 18:45. The review must establish what that observation can tell it about conditions earlier. Rain outside and wet footwear might be relevant enquiries, but neither becomes the confirmed cause through repetition in the report.

Evidence E1 is the control log extract. E2 is a location photograph taken after the route closed and before cleaning. E3 is the venue inspection note. Each entry identifies its creator, capture time and storage location. The photograph shows the floor condition at its capture time, not the entire incident.

Open decisions at the first handover

At 19:15, Alex hands responsibility for the incident review to operations lead Priya. The operational response is complete, but the report remains open. Priya must check outstanding facts, assess reporting requirements with the responsible parties and confirm the corrective actions.

The record says "reporting decision pending Priya's review". It doesn't say "not reportable" merely because nobody called an ambulance. Priya records the applicable requirements, who has the reporting duty and the decision reached when enough relevant information is available, without delaying any required notification.

Action A1 asks Pat to review the entrance arrangement against the relevant assessment and document any changes before the next event. Action A2 asks Alex to check that future briefings explain how staff report floor conditions. Each action has an agreed deadline and verifier in the restricted working record.

At this point, nobody has concluded that a briefing failure or the mat caused the incident. Those are review questions. Correcting a potentially weak arrangement can be sensible while the cause remains under investigation, provided the report explains that distinction.

Preserve evidence without creating another hazard

Your evidence list should help someone find the original material. "Photo in the group chat" isn't enough when several people have forwarded compressed copies with different timestamps. Identify the original file, who holds it and what it depicts.

Where safe and appropriate, record the scene before changes and record what changed afterwards. Don't ask anyone to recreate a fall, move a casualty for a photograph or leave a hazardous route open for the sake of documentation. The response takes priority.

If CCTV may be relevant, contact its authorized custodian promptly through your agreed process. Identify the incident, location and relevant time range. Ask them to preserve potentially relevant footage under the applicable procedure, and record whether they acknowledged the request. A request sent isn't confirmation that footage is secure.

Avoid gathering every available image or exporting an entire attendee list because it might become useful. Decide what evidence is relevant, why it is needed and who should access it. Keep an attachment reference in the report when the actual material requires tighter access.

Treat radio times carefully. A radio log may tell you when a message was entered, while a camera records a different clock. If comparing them, note any checked time difference. If you cannot reconcile the clocks, preserve that uncertainty instead of adjusting times until they agree.

When someone supplies a later correction, add the correction with their name and date. Retain the earlier entry and explain the change. Quietly replacing the first account makes it harder to understand what the response team knew when it made a decision.

Check external reporting and notifications separately

An internal event incident report doesn't establish that you've met every external duty. In Great Britain, RIDDOR means the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations. Its reporting categories differ according to the circumstances and the people affected.

Use HSE's current guidance on reportable incidents when assessing the facts with the responsible person. It covers specified worker injuries, certain dangerous occurrences and relevant injuries to people who aren't at work. Treatment at the venue, or an ambulance attending, doesn't by itself settle the reporting question.

Identify who must make the report and by when under the applicable rules. Put the actual deadline and its source into the incident record. Don't copy a universal "report within twenty-four hours" instruction into your template. Different categories and notification duties can have different requirements.

There may also be venue, employer, insurer, licensing or other notification requirements relevant to the incident. Assign each decision to a named person. "The venue knows" leaves uncertainty about whether anyone has checked a separate duty, made a submission or received an acknowledgement.

Review your event insurance arrangements with the relevant adviser and check the actual policy conditions. Keep factual incident information and insurance correspondence linked. Avoid promising a witness or attendee that your insurer will pay a claim before the responsible parties have assessed it.

Record a decision not to report when the responsible person has assessed that requirement, including the basis and information considered. If significant new facts arrive, reopen the decision. An early conclusion shouldn't prevent a later review of changed circumstances.

Keep personal details out of the general operations log

The event team may need to know an entrance is closed and where arrivals should go. They usually don't need an injured attendee's full name, home address or medical history to carry out those instructions. Separate operational updates from restricted personal records.

ICO guidance on special category data explains that processing such information requires both a lawful basis and an applicable additional condition. Health information can fall within this protected category. Have the appropriate privacy arrangements reviewed before the event rather than assuming a completed incident form supplies permission.

In practice, use a person reference in the general incident record and store necessary identifying details where authorized staff can retrieve them. Decide which roles need the full report, which need selected facts and which need only an operational update. Apply the same distinction when sharing information with suppliers.

Don't promise absolute confidentiality to witnesses. Explain how your organization handles their information under its procedure, and route specific access or disclosure questions to the responsible person. You may need to share relevant information through an authorized process, but that doesn't justify circulating the whole report to everyone involved in the event.

If a ticket or order reference helps resolve a specific enquiry, record only what's necessary. Don't paste unrelated buying history or marketing preferences into the incident report. Ticket administration and incident investigation have different purposes, even when they concern the same attendee.

Turn the review into completed actions

Once the immediate situation is stable, appoint someone with the appropriate competence and authority to coordinate the review. Serious, complex or specialist incidents need the relevant expertise. Your general event form can organize the records without pretending its author can determine every technical or clinical question.

Start with the unresolved questions. Which control was expected to work? What evidence shows whether it was present? What changed during the event? Who needs to explain that change? Keep proposed explanations separate from established findings as you work through the evidence.

Use your event risk assessment to check the affected arrangements. If it says staff inspect the entrance during wet weather, establish whether that inspection happened, what it found and what followed. "Remind staff to be careful" doesn't answer those questions or explain the change needed.

Write actions so another person can verify completion. "Pat to review entrance layout with the competent adviser before the next public opening and record the approved changes" describes a task and an outcome. The action record still needs its actual deadline, reviewer and evidence location.

Consider the resources required. If a change needs additional staff, equipment or venue work, identify who can authorize it and record the decision. Leaving an unfunded instruction in a report doesn't change the next event's arrangements. Where the necessary control remains unresolved, escalate the decision about the affected activity.

Don't use refund cost or lost sales to decide how seriously to investigate potential harm. Record commercial consequences separately where useful for managing the business. They can help you understand disruption, but they don't establish whether the response or the resulting controls were adequate.

Make the handover explicit when people leave site

An incident can outlast the people working the shift when it began. Before the response lead leaves, record who now owns the record and confirm that person has received the handover. Sending a message to an unattended inbox doesn't establish that someone has taken responsibility.

The receiving person should be able to identify the current restrictions, outstanding decisions, next deadlines and evidence still being sought. If a supplier holds relevant material, include the supplier's agreed contact and the preservation request reference. Keep personal contact information in the restricted contact record where appropriate.

For the fictional foyer incident, Priya needs to know whether entrance W is open, what monitoring continues and who will review Pat's inspection note. She also needs to know which reporting questions remain unresolved. The fact that the performance is underway doesn't answer any of those questions.

Ask the receiving person to confirm their understanding of the next task. This is especially useful when responsibility moves between the organizer and venue, because each may assume the other is handling the same decision. Record agreed responsibilities without trying to transfer a legal duty through an informal handover.

If information arrives after the event, link it to the original record. A witness may contact the venue while an attendee contacts the organizer. Have a process for referring those messages to the responsible reviewer so the investigation doesn't develop two separate versions of the same incident.

Handle incomplete accounts without filling the gaps yourself

Sometimes the person affected leaves before you can speak to them. Record what you know, how you know it and any reasonable follow-up through your approved process. Don't invent a contact detail or mark "declined assistance" because nobody can find the person. Leaving and declining are different facts.

Someone may also decline to provide a witness account. Note the relevant fact without pressuring them into agreeing with an account written by someone else. Where a formal investigation or specialist procedure applies, refer the matter to the person responsible for that process.

A report about threatening behaviour needs the same discipline. Record the observable conduct and relevant attributed words, followed by what staff did. Keep allegations identified as allegations while the responsible people assess them. Avoid sharing an unverified description across the entire team as though it were an established finding.

For a near miss, describe what almost happened and the remaining condition. If a delivery trolley enters an occupied queue without making contact, the absence of injury doesn't resolve the route conflict. Record how the movement stopped, who secured the area and what requires review before another delivery.

Reports can also arrive through customer service after everyone has gone home. Preserve the message as received, note when it reached your organization and identify whether the sender's incident time is exact or estimated. Refer any immediate concern through the appropriate procedure rather than waiting for the next scheduled review.

You won't always resolve every difference between accounts. A useful final report can state what the evidence supports, what remains uncertain and what actions follow anyway. Explain the limits of the finding so next month's event team doesn't treat an unproven explanation as the basis for its plan.

Decide when the record can close and how long to keep it

Closing the immediate response and closing the investigation are different decisions. You may reopen the entrance while reporting checks or corrective actions remain unfinished. Use statuses that show this, with a named person responsible for the outstanding work.

Before closure, check that required decisions are recorded, relevant notifications have evidence, actions have been verified and the necessary plans or briefings have changed. If a task remains open, document who will monitor it and why the record's status is appropriate. Don't hide unfinished work behind a final signature.

ICO's storage limitation guidance explains that retention depends on the purpose and that UK GDPR doesn't set one period for every record. Apply a documented retention schedule that accounts for relevant obligations and preservation needs. Confirm specialist requirements rather than inventing a single deadline for every event incident.

For the next briefing, use an appropriately anonymized account of what staff need to do differently. Remove details that identify someone unnecessarily, including combinations that make a person obvious to the team. Keep the complete restricted record available only through your authorized process.

Before your next event, test the template with the people who'll actually use it. Ask a steward to report a fictional incident, have control record it, and hand it to the next responsible person. Check whether they can find the location, understand the uncertainty and identify the unfinished decisions. Fix anything that makes that handover harder.