Patron Ejection Documentation Form

Complete it as soon as practical after the ejection, while the details are still fresh and before notes get mixed with later recollections. It is especially useful after any removal involving a dispute, repeated warnings, security intervention, or possible injury or damage. If your site has an incident log, this form can become the formal record attached to that log entry.

The staff member who directly handled or observed the ejection should usually complete it, with a supervisor reviewing it when required by policy. If multiple staff were involved, one person can draft the report and others can add their own statements or confirm the facts. The key is to capture firsthand observations, not secondhand summaries.

This template fits removals from retail stores, venues, offices, lobbies, campuses, and other controlled properties. It works for non-violent ejections, security removals, and incidents where a patron was asked to leave after policy violations or disruptive behavior. If the event escalated into a serious assault, emergency response, or law-enforcement report, this form should be paired with those records rather than used alone.

Yes, if any physical contact, restraint, escorting, or other force was used, it should be documented clearly and factually. Describe only what happened, who applied it, why it was necessary, and whether there were injuries or property damage. Avoid vague language like "handled appropriately" because it does not create a useful audit trail.

A consistent record helps supervisors review whether staff followed policy, whether warnings were given, and whether the response matched the situation. It also supports later review if a patron complains, a witness gives a different account, or a claim is made about injury or damage. The form is most useful when it includes time, location, names, witnesses, and a clear sequence of events.

Common mistakes include leaving out the reason for ejection, failing to name witnesses, and using vague descriptions instead of specific actions. Another frequent issue is skipping the follow-up section, which makes it hard to track bans, incident review, or notifications. The form should also avoid collecting unnecessary personal data beyond what is needed for the incident record.

Yes, you can tailor the reason list, method options, and follow-up actions to match your venue, property, or security policy. For example, a nightclub may need different escalation options than a corporate lobby or healthcare waiting area. You can also add conditional logic so force details only appear when force was used, which keeps the form shorter and easier to complete.

After submission, the report should route to the appropriate supervisor, security lead, or incident review queue. If your process requires it, the record can also trigger a case note, ban review, or follow-up task. The submitter should know whether the form is for documentation only or whether it starts an internal review.