1. Templates
  2. Security
  3. Event Security
  4. Event Medical Incident Report Form

Event Medical Incident Report Form

An event medical incident report template — record the casualty, what happened and the first aid given so every incident is documented.

Description

An event medical incident report form gives first aiders and event medical teams a calm, consistent way to record any injury or illness on site. Every incident — from a minor cut to a collapse — should be documented at the time, both to protect the casualty and to give the organiser an accurate account if it is ever reviewed.

It captures the casualty’s name and type, the time and location of the incident, and the nature of the injury or illness. Free-text fields record what happened and the treatment or first aid given, along with the first aider’s name, followed by confirmation of whether an ambulance was called, whether the casualty was taken to hospital and whether they declined treatment — closed with the first aider’s signature.

Embed it on a tablet at the medical point or share the link so incidents are logged consistently across the event. It’s free — adapt the categories to your event, restyle it to your brand, and keep a clear, caring record of every incident.

Form fields

Everything the Event Medical Incident Report Form above collects — 12 fields across 2 pages, so you can see exactly what it captures before you make it your own.

Log a Medical Incident

  • Casualty name

    Short Answer Icon
    Short Answer
  • Casualty type

    Dropdown Icon
    Dropdown
  • Time of incident

    Time Icon
    Time
  • Location on site

    Short Answer Icon
    Short Answer

What happened

  • Nature of injury or illness

    Dropdown Icon
    Dropdown
  • Describe what happened

    Long Answer Icon
    Long Answer
  • Treatment or first aid given

    Long Answer Icon
    Long Answer
  • First aider name

    Short Answer Icon
    Short Answer
  • Was an ambulance called?

    Yes/No Icon
    Yes/No
  • Was the casualty taken to hospital?

    Yes/No Icon
    Yes/No
  • Did the casualty decline treatment?

    Yes/No Icon
    Yes/No
  • First aider signature

    Signature Icon
    Signature
Use Template Arrow Right Icon

Template FAQs

Common questions about the Event Medical Incident Report Form — what it captures, when to use it, and how to make it your own.

What is an event medical incident report?

It’s a record of an injury or illness that occurs at an event and the care given in response. It captures who was affected, what happened, where and when, and the treatment provided — so there’s an accurate account that protects both the casualty and the event team.

When should a medical incident be recorded?

At the time of the incident, or as soon as the casualty has been cared for. Recording it straight away captures accurate times, locations and details of treatment, which are difficult to reconstruct later and important if the incident is ever followed up.

What should the report include?

The casualty’s name and type, the time and location, and the nature of the injury or illness; an account of what happened and the first aid given; the first aider’s name; and confirmation of whether an ambulance was called, the casualty went to hospital or declined treatment.

Who should complete it?

The first aider or medic who treated the casualty, as they have first-hand knowledge of what happened and what was done. Event organisers and safety officers typically review completed reports to spot patterns and check that cover and procedures are working.

Why record if a casualty declines treatment?

Because it matters for the casualty’s welfare and for the record. Noting a refusal shows help was offered and documents the casualty’s decision, which protects everyone if the person’s condition changes later or the incident is reviewed after the event.

Is this medical incident template free?

Yes — it’s free. Create a Fun Forms account, adapt the injury categories and checks to match your event, restyle it to your brand, and embed it or share the link. No coding needed, and every incident is logged in one clear, consistent place.