# Incidents (/docs/incidents)



The **Incidents** app is where your team documents anything that goes wrong on the water, on the trail, or on the lot. Each incident is a single case file for one real-world event — a collision, an injury, equipment damage, or a near-miss — that gathers everything related to it in one place: a written record, photos and documents, signed waivers, and links to the booking, customer, equipment, and guests involved.

You'll find it under **Incidents** in the dashboard sidebar (`/dashboard/incidents`).

<Callout type="info">
  Incidents replace the older **Instance Reports** feature. Where Instance Reports were tied to a single equipment unit and a single booking, an incident can span multiple equipment units, link a customer and specific guests, and exist even when no booking or equipment is involved. If you're looking for where equipment paperwork went, it's here.
</Callout>

What an incident captures [#what-an-incident-captures]

Every incident has a small set of core details and several things you can attach to it:

* **Title** — a short headline for the event (required).
* **Occurred at** — when the event happened (required; defaults to now).
* **Summary** — an optional one-line description. The full narrative lives in notes.
* **Incident location** — optional free text for the physical spot ("Dock B, slip 4", "north trailhead"). This is separate from your business location.
* **Status** — **Open** or **Closed**.

Beyond the core details, an incident can link to a **booking**, a **customer**, one or more **equipment units**, and specific **booking guests**, and can carry **notes**, **file attachments**, and **waivers**. See [Linking records](/docs/incidents/linking-records) and [Notes, attachments & waivers](/docs/incidents/evidence) for how each works.

The lifecycle [#the-lifecycle]

Incidents have a deliberately simple lifecycle:

| Status     | Meaning                                                                        |
| ---------- | ------------------------------------------------------------------------------ |
| **Open**   | The incident is active — still being documented, investigated, or followed up. |
| **Closed** | The incident is resolved. Closing stamps a closed-at timestamp.                |

You can reopen a closed incident at any time, which clears the closed-at timestamp. There are no intermediate statuses, severity levels, or assignees — the title, summary, and notes carry all of the detail.

Where to find it [#where-to-find-it]

1. Click **Incidents** in the dashboard sidebar to open the incident list.
2. The list shows every incident at your current location, with status, occurred date, linked booking and customer, equipment count, and an evidence count (attachments and notes).
3. Click any row to open the incident's detail page, where all editing and linking happens.

Permissions [#permissions]

Access to the Incidents app is controlled by the **Incidents** permission (`incidents: manage`). Team members need this permission to view or edit incidents; administrators have access automatically. See [Configure Roles and Permissions](/how-to/team/configure-roles-and-permissions).

Related How-To Guides [#related-how-to-guides]

* [Create an Incident](/how-to/incidents/create-an-incident)
* [Link Records to an Incident](/how-to/incidents/link-records-to-an-incident)
* [Add Notes and Attachments](/how-to/incidents/add-notes-and-attachments)
* [Attach Waivers to an Incident](/how-to/incidents/attach-waivers-to-an-incident)
* [Close or Reopen an Incident](/how-to/incidents/close-or-reopen-an-incident)