> ## Documentation Index
> Fetch the complete documentation index at: https://attend.hackclub.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Incidents: your log and Hack Club HQ

Attend keeps two kinds of incident record, and it matters which one you use.

| | Your event's incident log | Report to Hack Club HQ |
| - | - | - |
| Where | **Incidents** in your event's admin sidebar | Ticking **Escalate to Hack Club HQ** on a log entry, or the public [/incident](https://attend.hackclub.com/incident) form |
| Who sees it | The roles you tick on the incident (event admins, safeguarding lead, ops, …) | Hack Club HQ's safeguarding team only |
| Who is told | Nobody automatically | HQ by email and Slack. An **Emergency** priority rings the safeguarding team's phones |
| Use it for | Anything worth a record: a first-aid visit, a lost badge, a behaviour warning, a safeguarding concern | Anything HQ needs to know about or help with |

## The levels

Every incident, in your log and at HQ, carries one of four levels. The level sets how fast HQ responds when you escalate.

![HQ's triage chart: S0 to S3](https://mintcdn.com/hack-club/XmuXRe4BT8965HwT/organizers/images/triage-chart.svg?fit=max\&auto=format\&n=XmuXRe4BT8965HwT\&q=85\&s=a2377f5dae05d7a3406aa7457f99a410)

| Level | Response | Examples |
| - | - | - |
| **S0** High priority | ≈ 5 minutes | Medical emergencies, fire, evacuation, missing participant, organiser misconduct |
| **S1** Moderate priority | ≈ 1 hour | Racial discrimination, misogynistic behaviour or sexual harassment, homophobia or transphobia, disclosure of a safeguarding incident, participant-on-participant violence |
| **S2** Low priority | ≈ 12 hours | Disagreements between participants, microaggressions |
| **S3** Follow-up | After the event | Hack Club may follow up after the event to complete the log and check that the incident was handled correctly |

When in doubt, pick the higher level.

## Logging an incident

1. Open your event in the admin and click **Incidents**, then **New incident**.
2. Pick a category and a level (S0 to S3), link the participants and staff involved, and write down what happened and what you did.
3. Choose which roles on your team can see it. New incidents default to event admins and the safeguarding lead.
4. Save. The entry is private to your team; HQ is not notified.

## Escalating to Hack Club HQ

If the incident needs HQ, tick **Escalate to Hack Club HQ** on the form before you save, or open an existing incident and use the **Escalate to Hack Club HQ** panel.

HQ responds at the incident's level, so there is no separate priority to pick. You'll be asked for:

* **A number HQ can call you on.** This is required: a report HQ can't call back on is hard to act on.
* Whether **emergency services** have already been called. If they have, the report is treated as S0.

An S0 rings the safeguarding team's phones, so use it for things happening right now.

HQ receives your incident's summary, details, actions taken, location and time, with you as the reporter. Conduct incidents (behaviour, safeguarding, other) are also posted to the HQ Firehouse Slack channel; medical ones go to HQ only.

> [!WARNING]
>
> **Medical emergency?** Call your local emergency number and get the person help first. Escalate afterwards.

## What you see afterwards

Your incident shows an **Escalated to Hack Club HQ** banner with HQ's status (open, in review, resolved). HQ's notes and comments stay confidential; if they need something from you they will contact you on the number you gave.

Escalating twice does nothing: an incident is linked to one HQ report.

## Reporting without a log entry

The public form at [/incident](https://attend.hackclub.com/incident) still works for everyone, including organizers. It creates a report to HQ with no entry in your event's log. Participants, parents and volunteers should use it; organizers usually want the log so their team has the record too.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.