Built for NY Ed Law §2-d · bilingual EN/ES

Every bus incident
documented, acted on,
and defensible.

Mobile incident reporting that replaces Google Forms and spreadsheets — so your next board meeting has a paper trail, not a pile of emails.

Registro de incidentes para distritos escolares — cada caso con constancia.

Watch 3-min walkthrough Request district pilot
Ed Law §2-d ready SSO via Clerk US data residency Aggregate-only reports
Incident #2041 · 2026-04-17
OpenClosed
Route
Route 14 · AM
Bus
B-42
Reporter
Monitor — S. Rivera
Student struck head on window frame during sudden brake near 4th & Elm.
Moderate Parent contact Driver retrain
07:02:11 Incident filed
07:02:14 Principal notified by email
07:14:22 Viewed by admin
09:15:03 Action logged & parent contacted
09:15:04 Closed · 2h 13m
Your Tuesday, reframed

A student bumps their head.
Here's what happens next.

Three people's jobs change on a Tuesday morning. See how the same hour looks on Google Forms vs. Yellow Threads.

Bus Monitor · 7:02am

Reporting, on a moving bus.

Digs for the paper form. Photographs it at end of run. Emails the office hoping someone opens it.
Opens Yellow Threads on her phone. Pre-filled route, bilingual form, one tap to submit. Confirmation in 3 seconds.
Filed in 00:38
School Principal · 7:14am

A real email, not another Slack ping.

Sees the email hours later after chasing it across Google Forms, a shared sheet, and three group texts.
One email with the incident card. Clicks through, logs required action (Parent Contact + Driver Retrain), closes it.
Closed in 2h 13m
Superintendent · Monday 9am

A board-ready PDF, already written.

Asks the transportation director to pull numbers. Waits five days. Gets a sheet with named students and no trend data.
Opens last month's aggregate report. Sees which schools need attention, why, and what was already done. Forwards it.
Generated on Day 1
A week at a district

This is what a real week
of incidents looks like.

Aggregate, anonymized, timestamped. Your admins see the pattern before it becomes a phone call from a parent.

Route
Incident
Reported
Resolution
Status
Sample data for illustration. Real reports never contain student names — only aggregated context.
Spanish is not an afterthought

Your drivers and monitors
work in two languages. So does this.

Every form, every notification, every PDF label — translated by humans who know school transportation, not a LLM string-swap. District admins can pin the default per school.

English

Report an incident

4th Ave & Elm Street
Sudden brake Head injury Verbal altercation Missed stop
Low Moderate High Critical
Español

Reportar un incidente

Ave. 4 y Calle Elm
Frenazo brusco Lesión en la cabeza Altercado verbal Parada omitida
Leve Moderado Alto Crítico
Trust & compliance

Your DPO's questions, already answered.

Built for New York's Ed Law §2-d from day one — not retrofitted. We'll send the DPA draft, the security summary, and a signed NIST P-TECH alignment letter before the first meeting.

Download security packet

Ed Law §2-d ready

Parent bill of rights, DPA template, and supplemental information page included.

SSO via Clerk

Google Workspace, Microsoft, or magic-link email. No passwords for drivers.

US data residency

Data stays in US-East. No third-party tracking. Aggregate-only monthly reports.

We'll migrate your forms

Two years of past Google Forms imported for you — mapped, deduplicated, searchable.

Drivers protected too

Documentation cuts both ways. When a parent asks what happened, the record shows who acted and when.

Board-ready reports

Monthly PDFs auto-generated with district branding. No student names. Ever.

Bring it to your district.
We'll do the rest.

We run a two-week, no-cost pilot with one school. Your IT team does nothing. Your drivers download nothing. If it doesn't work, you keep the data and we go away.

Request district pilot Watch 3-min walkthrough