Florida is the state Alyssa's Law was written for. Alyssa Alhadeff was a student at Marjory Stoneman Douglas High School in Parkland when she was killed on February 14, 2018. Her mother founded the movement that put the law on the books, and Florida was the first state to enact it in a form that specifically envisions a mobile, app-based silent panic alert reaching every classroom and every first responder in seconds.
That specificity is the point. Florida's version of Alyssa's Law is unusually prescriptive about how the mandate is satisfied — and unusually generous about which technology categories can satisfy it. For a Florida superintendent, safety director, or district IT leader, understanding the difference between "we've heard of Alyssa's Law" and "we can prove compliance to the Florida Department of Education" is worth a careful read of the actual statute, not just the marketing that surrounds it.
- Florida Statute 1006.07(4)(c) requires every public school in Florida to have a mobile panic alert system that reaches all first responders and law enforcement in real time
- The Florida Department of Education (FDOE) contracts with a designated statewide vendor whose cost is covered for districts — but districts are permitted to use alternative solutions that meet the statutory standard
- Compliance applies to all public schools, including charter schools; private schools may adopt equivalent programs voluntarily
- The statute explicitly permits mobile-app and software-based solutions — no wall-mounted hardware requirement
- The compliance question is not "did we buy the state vendor" — it's "does our silent panic alert reach all first responders in real time, and can we prove it in a drill"
Where the Law Lives in Florida Statute
Florida's Alyssa's Law lives inside Florida Statute 1006.07, the section that governs district school board duties for student conduct and safety. Subsection (4)(c) is the specific paragraph that carries the mobile panic alert requirement. It was added to the statute in 2020 as part of the ongoing legislative response to the Parkland shooting, and it sits alongside the broader Marjory Stoneman Douglas High School Public Safety Act provisions that reshaped Florida school safety after 2018.
If you or your district counsel want to read the primary source, that's where to look: Florida Statute 1006.07(4)(c). Anything a vendor or consultant says about "the Florida requirement" should trace back to that paragraph. If they can't cite it, they don't know it.
Almost every Alyssa's Law RFP that goes sideways in Florida does so because the district skipped the statute and started with the vendor pitch. A single reading of 1006.07(4)(c) — it takes ten minutes — is the fastest path to asking the right questions of everyone else.
What Florida's Version Actually Requires
The Florida statute is short and direct. Reduced to its operative properties, it requires every public K-12 school to have a mobile panic alert system with the following characteristics.
Silent
The alert cannot audibly signal to a potential attacker that police have been called. This rules out audible campus alarm-only systems as a standalone answer to Alyssa's Law — an audible alarm can be a companion feature, but it cannot be the silent-alert mechanism the statute requires.
Mobile
The word "mobile" appears in the statutory language. The alert mechanism must be usable from anywhere on campus by any staff member — not from a single fixed location. This is the language that opens the door for mobile-app-based solutions and effectively closes it on wall-mounted-button-only compliance.
Real-time to all first responders
Florida's language is broader than a strict "direct to law enforcement" phrasing. The statute says "all first responders" — meaning the alert should reach law enforcement, fire, and EMS as appropriate. In practice this usually means integration with the local dispatch center or PSAP that serves those agencies.
Coordinated with school security
The statute expects the panic alert system to coordinate with the school's existing safety and security infrastructure, not sit as a disconnected silo. This is where in-building notifications, campus-wide visual alerts, and coordination with school resource officers come in.
The word that does the most work in the Florida statute is mobile. It's the reason a smartphone-app or software-based solution can legally satisfy the mandate, and it's the reason a Florida district is not required to install physical panic buttons on every wall in every classroom to be compliant.
The State-Designated Vendor
Florida is one of the few states where the Department of Education has centrally procured a statewide vendor and offered that vendor's platform to districts at no direct cost. As of the latest FDOE procurement cycle, that designated vendor has been Raptor Technologies, and the platform is commonly branded as the Raptor Alert mobile panic app.
If your district uses the state-designated vendor and configures it correctly, you are considered compliant with the statute. That's the safest path for districts that want a one-decision compliance answer.
But — and this is important — use of the state vendor is not the only way to comply. Florida Statute 1006.07(4)(c) sets a standard, not a vendor mandate. Districts that have legitimate reasons to use a different solution (existing safety-tech investment, better integration with local dispatch, feature requirements the state vendor doesn't meet, or the need for a broader campus-wide alerting layer) may deploy their own compliant solution.
The oversimplification
"There's one Alyssa's Law vendor in Florida and we have to use it or we're out of compliance."
The reality
Florida sets a compliance standard. The state has centrally contracted with a vendor to make the easy path even easier. Districts that meet the standard through another solution — or that layer additional capabilities on top of the state vendor — are equally compliant.
What the State Vendor Doesn't Cover
The state-designated mobile panic alert app is designed to do one thing well: get a silent signal from a staff member's phone to first responders. That's exactly what the statute requires, and it's what the app is optimized for.
What it doesn't do, by design, is broadcast the same alert visually across every device on campus. When the panic alert fires, the app sends the signal outbound to police, fire, and EMS. It does not simultaneously push a lockdown message to every Chromebook, laptop, SMARTboard, and digital sign in every classroom. That visual, in-building notification layer is a separate concern — and one that most Florida districts eventually realize they still need to solve.
The mobile panic app answers "how do we tell the police?" It does not answer "how do the teacher in room 214 and the substitute in the media center know a lockdown is in effect within seconds of the button being pressed?" That is the gap where most Florida districts add a second layer.
The pattern most Florida districts settle on is a layered one. The state's mobile panic alert app handles the outbound signal to first responders. A separate campus-wide visual alerting system handles the inbound notification to every screen on campus. The two together form what the modern K-12 emergency response actually looks like.
Coverage: Public, Charter, and Private Schools
Florida's Alyssa's Law applies to all public schools, which under Florida law includes charter schools. Private schools are not required to comply, though many private and independent schools in Florida have adopted equivalent programs voluntarily — sometimes to meet parent expectations, sometimes to satisfy insurance requirements, and sometimes because it's simply the right thing to do.
District public schools
All Florida district-operated public elementary, middle, and high schools must comply. The FDOE-contracted vendor is available to every district at no direct cost.
Charter schools
Charter schools are considered public schools under Florida law and are covered by the mandate. Some charter operators use the state vendor; others procure their own compliant solutions independently.
Private schools
Not legally required to comply under 1006.07(4)(c). Many voluntarily adopt equivalent programs — especially larger private schools and those participating in the Florida Empowerment Scholarship or similar programs with associated safety expectations.
Career and technical centers
Public career and technical education centers operating as part of a district's school system are covered by the same standard as other public schools.
If you're not sure whether a specific school in your district falls under the mandate, the safest place to check is with your district's general counsel or the Florida School Boards Association — not with a vendor.
The Florida Compliance Program: What Good Looks Like
A Florida district that treats Alyssa's Law seriously runs a program, not a purchase. The program has predictable elements, and the best-run districts follow this sequence.
-
1Step 1
Anchor the program in the statute
Print out Florida Statute 1006.07(4)(c). Have your district general counsel confirm which schools in your district are covered and any local interpretations that apply. Everything downstream — vendor selection, procurement, training — should trace back to specific statutory requirements.
-
2Step 2
Decide on the state vendor or an alternative
For most districts, the state-designated vendor is the sensible default: it's free, it's pre-audited against the statute, and it removes procurement risk. If your district has a legitimate reason to use an alternative solution, document that reason in writing and be prepared to demonstrate statutory compliance to FDOE if asked.
-
3Step 3
Coordinate with local law enforcement, fire, and EMS
The statute says "all first responders." Meet with your local police or sheriff, your local fire department, and your local EMS provider. Confirm exactly how they will receive the alert, on what platform, and who at each agency is responsible for the receiving end. Get this in writing. Re-verify annually.
-
4Step 4
Add the in-classroom visual alert layer
The mobile panic app tells the police. It doesn't tell the teacher in the room next door. Add a campus-wide visual alerting layer that fires the same signal to every screen in every classroom in seconds. This is the layer AlertIO fills for Florida districts already using the state panic app.
-
5Step 5
Train every staff member
Every teacher, every administrator, every substitute, every food-service worker, every custodian. Every adult on campus should know how to trigger the alert and what to expect when someone else triggers it. Document who's been trained and when.
-
6Step 6
Drill quarterly with first responders participating
A drill without the receiving agencies participating is a partial drill. At least once a year, run a live drill with the actual local dispatch center to confirm the alert reaches the right console at the right agency on the right platform. Audit the timestamps.
-
7Step 7
Report to FDOE as required
Florida periodically requires districts to certify Alyssa's Law compliance and report on drill activity. Know your district's reporting cadence and calendar it. Missing a reporting deadline is one of the easier compliance failures to avoid.
-
8Step 8
Re-verify annually
Contacts change. Vendors update APIs. Dispatch centers migrate to new CAD systems. Staff turn over. What was compliant last September may have drifted by this one. An annual re-verification protects the district from silent decay in a life-safety system.
None of these steps is exotic. All of them are things a district safety director can plan out on a single page. The ones that skip a step tend to skip the same ones — the coordination meeting with first responders, the drill with the actual dispatch center, and the annual re-verification.
What Florida Districts Get Wrong
After several years of Florida districts operating under 1006.07(4)(c), a small number of failure patterns recur reliably.
"We downloaded the app, we're done"
Downloading the state mobile panic app to a handful of administrator phones and calling the program complete. In practice this leaves the vast majority of staff without the app, without training, and unable to trigger a silent alert in the moment. The statute requires that staff have the alert mechanism — not that the district technically owns a license.
Skipping the first-responder coordination
The single most common failure mode. The district enrolls with the state vendor, activates the app on staff phones, and never confirms that the local dispatch center actually receives the alerts. When the drill finally happens, everyone discovers that the receiving platform was misconfigured six months ago.
No in-classroom notification layer
Compliance with the outbound-to-police side of the statute is not the same thing as a functional lockdown program. Districts that don't add a campus-wide visual alert layer end up with a situation where police know about the incident before the teacher three rooms away does.
Assuming the vendor handles drills
The state-designated vendor provides the platform, not the drill program. Drilling is the district's responsibility. Districts that assume the vendor will remind them, schedule for them, or run the drill for them tend to discover their staff isn't proficient at the worst possible moment.
Not documenting the alternative-vendor decision
Districts that opt out of the state vendor and pick their own solution — for legitimate reasons — sometimes fail to write down why. When FDOE asks, or when a future superintendent revisits the decision, there's no paper trail. Write the decision memo when you make the decision. Not later.
Treating charters differently by default
Charter schools in Florida are public schools under the statute. Districts that assume their charter partners are separately handling compliance sometimes discover during an incident that the charter operator was under the same impression about the district. Confirm coverage in writing, per school, once a year.
Every one of these is a program-management failure, not a technology failure. The technology is the easy part.
How AlertIO Fits an Alyssa's Law Program in Florida
AlertIO doesn't replace the state mobile panic alert app. AlertIO fits alongside it as the in-classroom visual alert layer that turns a police-notification event into a whole-campus lockdown response.
The typical Florida deployment pattern looks like this. A staff member fires a silent panic alert from the state mobile panic app on their phone. That signal goes to local police, fire, and EMS as the statute requires. In the same instant, that same signal — via a simple webhook — fires an AlertIO full-screen visual alert to every enrolled device on campus. Every Chromebook, every laptop, every teacher workstation, every SMARTboard, every digital sign takes over its screen with a color-coded lockdown notification within seconds.
The state mobile panic app is the outbound leg of the response. AlertIO is the in-campus leg. They fire from the same trigger, but they solve different halves of the problem. Together they compress the awareness gap between "police have been called" and "every adult in the building knows" to under a minute.
Because AlertIO deploys as software on the devices the district already owns — Chromebooks, laptops, macOS, Linux, Windows, plus tablets and connected digital displays — there's no additional hardware, no wiring, no long installation project. A Florida district can add the AlertIO layer to an existing state-vendor deployment in a matter of weeks without touching the panic-app side of the stack.
Panic app alone
Police know within seconds. The teacher in room 214 finds out when someone runs down the hall or when the office finally gets on the intercom. Awareness gap: 60–180 seconds.
Panic app + AlertIO
Police know within seconds. Every staff member in every classroom knows within seconds. Awareness gap: under 10 seconds. Lockdown response begins in every room simultaneously.
What to Ask a Vendor in Florida Specifically
If you're evaluating solutions for a Florida district — whether the state vendor, an alternative panic alert vendor, or a companion visual alert layer — five Florida-specific questions separate real Alyssa's Law readiness from marketing copy.
"Show me your compliance mapping to 1006.07(4)(c)."
Not a general Alyssa's Law slide. A line-by-line mapping of your product's features to the specific language of the Florida statute. A vendor that can produce this quickly has done the work. A vendor that hedges has not.
"How do you integrate with our local dispatch center?"
Florida counties use a variety of CAD platforms. Your vendor's integration story for Miami-Dade County will be different from Alachua County's. Ask for a working integration with your dispatch center, not a generic answer. Test the answer in a live drill.
"What's the FDOE-reporting story?"
FDOE periodically requires districts to certify Alyssa's Law compliance and report drill activity. Ask your vendor what reports they generate to support that. If the answer is "we don't," you'll be building the reporting yourself.
"How does the alert reach a device that's asleep, backgrounded, or locked?"
This applies to both the panic-app side and any in-classroom alerting layer. Modern operating systems aggressively suspend background processes. A silent panic alert that fails when a device is asleep is a silent panic alert that will fail at exactly the wrong moment.
"What happens if the state vendor contract changes next year?"
FDOE procurement cycles happen. If the state's designated vendor changes, what does your district's transition look like? A vendor that assumes their contract is eternal is one to be cautious of. A vendor that has a documented data-portability and transition-support story is one to trust.
A vendor that answers all five directly and specifically is a vendor to pilot. A vendor that offers generic Alyssa's Law talking points instead of Florida-specific answers is not.
The Superintendent's Bottom Line for Florida
Florida's Alyssa's Law is one of the most concrete, actionable school safety mandates on the books anywhere in the country. The statute is short. The compliance standard is clear. The state has done more than most states to make the easy path free.
The failure modes are not technical. They're organizational. Districts fail Alyssa's Law compliance by treating it as a purchase decision instead of a program, by skipping the first-responder coordination meeting, by never running a live drill with the actual dispatch center, by leaving substitute teachers off the training list, and by never noticing that the vendor integration silently broke eight months ago.
Districts that succeed treat it as an operating program with a named owner, a quarterly drill cadence, and an annual re-verification. They pair the state's mobile panic alert with a campus-wide visual alerting layer so that "police know" and "everyone knows" happen at the same instant instead of two minutes apart. They document everything. They train everyone. They test the receiving end, not just the sending end.
If you're a Florida superintendent, safety director, or district IT leader, the right question to bring back to your team this week is the same one that closes every Alyssa's Law conversation worth having: if we had to fire a silent panic alert right now, would law enforcement receive it within 10 seconds, would every adult on campus know in under 30, and can we prove both to FDOE if asked? If yes to all three, you have a compliant Florida Alyssa's Law program. If any answer is no, you've just found the next thing to work on.
"Real-time to every first responder. Real-time to every classroom. Provable in a drill. Documented for FDOE."Four sentences. If your program can honestly say yes to all four, you're not just compliant with Florida Alyssa's Law — you have the safety posture the statute was written to produce. The compliance test worth writing on a whiteboard
AlertIO deploys on every device in your district in minutes — no hardware required — so the silent panic alert Florida mandates reaches every classroom, every screen, every second it matters. Request a demo →