Review incidents over a period

Every incident — injury, bite, allergic reaction, behavioral — flows into the Incidents report once a teacher files it. The report gives you a rolled-up view: counts by type, status breakdown, and a flag on anything a parent hasn't acknowledged yet.

Run it

1. Reports → Incidents in the sidebar.
2. Pick center (or "All centers") and a date range.

Screenshot pendingThe Incidents report: status stat cards, an incidents-by-type chart, and an incident records table

Status lifecycle

• Open — filed but not yet closed out. Usually means follow-up is needed.
• Resolved — incident dealt with; awaiting final sign-off.
• Closed — fully complete; parent has been notified and acknowledged.

Open incidents older than 7 days are flagged as "stale" in Data Health. Close them or document why they're still open.

Parent notification column

A green checkmark means the parent has been notified. An amber warning means they haven't — follow up today.

If your Settings → Organization → Require Signature on Incident Reports toggle is on (default), parents must also sign the incident in their app. Their signature is required to move the incident to Closed.

Common use cases

Weekly safety review

Most centers review incidents weekly with the teaching team:

1. Filter to the past 7 days.
2. Check Incidents by Type — is one category spiking? (e.g., five bites in a toddler room this week).
3. Open each record that's still Open and move them along.

Incident pattern detection

Run for the past month. Look at the by-type chart:

• Injuries concentrated in one room — check the environment, playground equipment, supervision coverage
• Bites spiking in a young-toddler room — usually a transition period; bring it up in the next staff meeting
• Allergic reactions — double-check the meal logs tied to those kids; see Configure check-in methods for health-screening questions at drop-off

Licensing submission

Many states require an incident summary as part of annual licensing renewal:

1. Filter to the 12 months leading up to renewal.
2. Export CSV.
3. Attach to your licensing file.

Export and print

• Export CSV — Date, Child, Type, Body Location, Description, Action Taken, Status, Parent Notified. Filename: incidents-{start}-{end}.csv.
• Print — prints cleanly; the by-type chart renders on the first page.

Annotations at the bottom let you add context per period: "April incident spike tied to new toddler room transition — expected."

What the report does NOT show

• Immunizations — tracked on each child's profile and on the Health page, with their own Immunizations report
• Medications administered — tracked separately in the child's medical profile, not here
• Incident photos — click through to the incident detail page for photos and full documentation

Troubleshooting

"Parent Notified" column is all no-marks. Your teachers haven't been tagging parents on incident submission. Train the team to check the "Notify parents" box when filing. Or turn on the org-level Signature required on incident reports toggle so notification is built into the flow.

Report shows 0 incidents but I know there was one. Check your date filter — the incident date is when it occurred, not when it was filed. If a teacher filed a week late for an event two weeks ago, you need to include that earlier date.

Same incident appears twice. Possibly two teachers filed the same event from different angles. Click both — if genuinely duplicate, close one with a "duplicate of incident #X" note.

Export CSV is missing the description field. Verify you're looking at the right row — some incident types (e.g., observation) don't have a description required. The field will be empty, not missing.

Room filter doesn't show rooms. Incidents report doesn't support room filtering — it's center-level only. Use the Child column on the table to see which room a child was in at incident time.