🛡️ Free school evidence tool

Bullying Incident & School Response Evidence Tracker

Document what happened, where, who witnessed it, when the school was told and what the school said it would do. The dashboard then surfaces repeated locations, repeated people and overdue follow-ups.

Record facts, not conclusions. Bullying definitions and school duties vary by state and district. This tool helps preserve your chronology and evidence; it does not decide whether conduct legally qualifies as bullying.

1. Case setup

Child / initialsSchoolSchool year

2. Pattern dashboard

3. Add incident

DateTimeTypeLocationPerson / group involvedWitnessesReported toFollow-up due

What happenedSchool response / promise

Drop screenshots, PDFs or photos hereor click to choose files. Stored locally in this browser using IndexedDB.

4. Export and backup

JSON backs up the incident log and evidence index. Because attached files can be large, the file blobs themselves stay in IndexedDB on this device; keep original screenshots/documents somewhere you control.

Connect incidents to the rest of the school record.

IEPNest can keep meetings, school communication, services and support-plan evidence beside this chronology.

Explore IEPNest →

What makes an incident log useful

A useful log answers the same questions every time: when, where, who, what happened, who saw it, who was told, what response was promised, and whether that response actually occurred. Consistency makes patterns visible without exaggerating them.

Why school response belongs in the same record

An incident chronology without the response chronology is only half the story. The follow-up field makes unanswered reports and repeatedly missed promises visible before a meeting.