Crowd-controller incident & ejection log
Records crowd-control incidents, ejections, exceptions, escalations, supporting evidence and authorised sign-off for a site or event. A live form your crew fills on their phones, not a Word template you retype on every site.
- Crowd-control incidents
- Ejections
- Exceptions
- Escalations
- Supporting evidence
- Authorised sign-off for a site or event
This form, the other 276 in the library and Eaco AI, live in your workspace the moment you subscribe. Branded to your business, ready on your phone in minutes. Cancel anytime.
Rendered from the live form itself. Your logo replaces the placeholder the day you subscribe.
When you need this form
Ejections are the moments most likely to end in a complaint, a claim or a police request weeks later. A patron refused entry, an intoxicated guest removed, a physical intervention at a barrier, a bag search dispute: each needs a contemporaneous log entry. Crowd controllers work under licence conditions, and the account written on the night carries far more weight than one reconstructed afterwards.
Handwritten logs get lost, smudged or filled in at shift end. A live entry captures the time, the location, the officers involved and any CCTV reference while the detail is fresh, with photos where appropriate. Venues, insurers and legal advisers all want that chain intact, and clients reviewing your performance want escalations reported, not buried.
What good looks like
- Time, gate or zone, and the officers present at the incident.
- What the patron did, in factual terms, without opinion or labels.
- Warnings given and the level of force, if any, used.
- Outcome recorded: refused entry, ejected, handed to police, medical treatment.
- Witnesses, CCTV camera reference and supervisor notification time.
Crowd-controller incident & ejection log, answered
Is this a PDF or Word template?
Neither. It is a live form: your crew opens it on their phones, ticks it through, attaches photos and signs on the glass. Every submission is timestamped, GPS-pinned and stored as proof.
What should a crowd controller record after an ejection?
The time and location, who was involved, the behaviour that prompted removal, warnings given, any force used, the outcome and witnesses. Keep it factual. Note the CCTV reference and when a supervisor was told.
Do event security incidents need logging if nobody was hurt?
Yes. Refusals, warnings and near misses build the pattern venues and insurers rely on when a complaint arrives later. A log with no entries gets treated as a log nobody kept.
Can I buy just this one form?
It comes with the plan: this form, the other 276 in the library and Eaco AI for $29 a month, GST included. Cancel anytime.
Forms that work alongside it
Browse all 277 formsAll included in the plan.

