Guest Incident and Injury Report Form

Use it for guest slips, trips, falls, minor injuries, property hazards, and other on-site incidents involving visitors or customers. It is also useful when no injury occurred but the event still needs a record. If the event involves an employee, use an employee incident form instead. Keep the scope tied to guest-facing events so the fields stay relevant and easy to complete.

Complete it as soon as possible after the incident, ideally while details are still fresh and the scene has not changed. It should be used every time a reportable guest incident occurs, not only when there is visible injury. If your site has multiple locations or shifts, make the form available for each location so reporting is consistent. Delayed reporting often leads to missing witness details and incomplete scene notes.

The form is usually completed by the manager on duty, supervisor, security lead, or another designated responder who can document the scene and immediate actions. A witness or front-line employee may start the report, but a responsible reviewer should confirm the details before it is closed. If your process allows guest input, keep that separate from staff observations. The key is to assign one clear owner so the report does not stall.

Yes, if you collect names, contact information, photos, or medical details, include a clear consent or disclosure statement and limit fields to what you actually need. That supports data minimization and helps avoid unnecessary PII collection. If the report may be used in a legal or insurance review, keep the wording factual and avoid speculative fields. For accessibility, make sure the form meets WCAG 2.1 AA expectations, including clear labels and usable validation messages.

Common mistakes include leaving out the exact time and location, writing vague incident summaries, and skipping witness details when they are available. Another frequent issue is collecting too much personal data, such as unrelated medical history, instead of only the minimum necessary information. Users also forget to document what happened immediately after the incident, which is often the most important part of the record. The form works best when it is completed in a factual, step-by-step way.

Yes, the incident type, location, and scene condition fields can be tailored for hotels, retail stores, event venues, restaurants, or apartment communities. You can add conditional logic so extra fields appear only when they apply, such as pool area, parking lot, or elevator. Keep the core structure intact so every report still captures the same essential facts. That makes review and trend analysis much easier later.

It can be linked to ticketing, case management, insurance intake, or internal audit workflows so follow-up tasks are tracked after submission. Scene photos and witness details can be attached to the record for later review. If your team uses a safety log or corrective action register, map the follow-up owner and due date fields into that process. The goal is to turn the report into an actionable record, not a dead-end document.

An ad hoc message usually misses key fields, uses inconsistent wording, and is hard to search later. This template standardizes the report so every incident includes the same core facts: what happened, where, who was involved, what was done immediately, and what needs follow-up. That makes it easier to review patterns, assign action items, and keep an audit trail. It also reduces back-and-forth when managers need clarification.