A tip is not a case
Anonymous reporting, incident management, panic alerts, and threat assessment are different jobs. District RFPs that collapse them buy the wrong system.
School-safety software is sold as one category. It is not. A student tip, a lockdown, a Title IX file, and a behavioral threat assessment are different jobs, usually owned by different people, and often paid from different budgets. When a request for proposals treats them as one SKU, districts either overbuy a suite they will not run or underbuy a tip app and keep closing cases in email.
Anonymous reporting is the entry point. Accountable resolution is the product.
Four layers that should not be collapsed
Anonymous reporting / tip line. A student, parent, or staff member submits a concern without putting their name on it. The job is intake: web, app, SMS, sometimes a hotline, sometimes two-way anonymous follow-up. Sandy Hook Promise’s Say Something Anonymous Reporting System, Lightspeed StopIt, Anonymous Alerts, FaceUp’s school reporting, state lines such as Safe2Tell, and modules inside CrisisGo or Vector LiveSafe live here. Some of this layer is free. Some is priced per student. None of it, by itself, is a district system of record.
Incident / case management. After the signal exists, someone has to own it. Categories, playbooks, working-day clocks, conflict-of-interest gates, evidence, interviews, supportive measures, employee and student tracks, closure that cannot be faked by deleting a row. This is the operating system. NOW IMS is built for this layer, with protected intake as the front door.
Emergency communications / panic. Seconds-scale alerting, 911/PSAP, lockdown, roll call, visitor management, reunification. Raptor, Navigate360 Campus360, CrisisGo, and Alyssa’s Law hardware live here. A case platform is not a panic button, and a panic button is not a Title IX file.
Threat assessment and monitoring. Structured team process (for example CSTAG-style workflows) is one discipline. Device and account monitoring (Gaggle, Lightspeed Alert, and peers) is another. Both can feed a case. Neither replaces the record of what the district did next.
If your RFP’s scope of work is “anonymous reporting app,” you will evaluate tip lines. If it is “one governed record from first signal to final proof,” you will evaluate incident management — and you can still keep the tip line you already have.
What a tip line actually hands you
A good ARS does three things well: it makes reporting available, it can hide identity, and it can notify someone that a message arrived. After that, the district still has to:
- decide who may see the report, including when the named party is an employee or a campus administrator
- start the right procedure for bullying, Title IX, threat, self-harm, or a facilities issue
- run clocks that match policy or statute, on working days, not wall-clock fantasy
- keep evidence and messages without pasting protected tip text into a shared inbox
- prove, later, that the required steps happened
Sandy Hook Promise is explicit that Say Something is an anonymous reporting system with a national crisis center and curriculum — and that the hard work of local response remains with the school. That handoff is not a failure of the nonprofit. It is the design. The gap is on the district side of the handoff.
Lightspeed StopIt, especially after the February 2025 acquisition into Lightspeed’s K–12 suite, is a strong paid ARS with human review and adjacent device-safety products. It is still not a policy-grade case file for every incident type a district has to govern.
FaceUp is a serious whistleblowing and case-management product with a school origin story and a European compliance center of gravity. US district procurement, grant language, and school-safety statutes are a different motion.
Language to put in the next RFP
Ask vendors to answer in writing, with a screen or a data model, not a slogan:
- Where does reporter identity live relative to case facts? Can anonymous mode avoid writing IP address, caller number, or device fingerprint into the case record?
- What happens when the same person is a witness in one file and a subject in another?
- Can bullying, Title IX, threat assessment, and employee misconduct share one system without one team seeing another team’s protected fields?
- Are deadlines timers in the system (owners, escalation, working-day calendars) or dates in a spreadsheet?
- Can the model recommend, and is it blocked from dispatch, discipline, disclosure, and closure?
- If we already operate Say Something, a state line, or StopIt, can we keep it and still run our cases here?
- What is explicitly out of scope: 911, panic/Alyssa’s Alert, staffed 24/7 crisis counseling, EHR, public whistleblower portals?
If a vendor cannot show the case after the tip, they are selling a channel.
What NOW IMS is not
NOW IMS is not 911, a panic alarm, an Alyssa’s Alert system, or a staffed multilingual crisis center. Standard plans can accept reports at any hour; they do not include staffed human monitoring. The platform does not make a district compliant by existing. Boards, counsel, school-based teams, and public-safety partners still own staffing, training, and the compliance determination.
The practical move
Keep the reporting channel that students will actually use. Stop treating the inbox that receives it as the file. If you want a working session on how protected intake, playbooks, and closure proof sit next to a tip line you already have, book a 30-minute walkthrough.