Lulu’s Law mandates that the Federal Communications Commission issue an order, within 180 days of enactment, providing that a shark attack is an event for which a Wireless Emergency Alert (WEA) may be transmitted. The bill references the existing regulatory definition of "Alert Message" in 47 C.F.R. § 10.10(a) and otherwise contains no implementing details, standards, or funding.
The measure is narrowly drafted: it does not itself require any federal, state, or local agency to transmit an alert, nor does it set criteria for when an alert should go out, who decides, or how to limit geographic scope. That narrowness leaves key operational and policy choices to the FCC, FEMA, state and local authorities, and the wireless industry — and creates a host of implementation questions that will matter to public-safety officials, carriers, and coastal businesses.
At a Glance
What It Does
The bill directs the FCC to issue an administrative order classifying a shark attack as an event eligible for transmission via the WEA system, based on the existing regulatory term "Alert Message" in 47 C.F.R. § 10.10(a). It creates an administrative obligation for the FCC (a 180‑day deadline) but does not itself add technical protocols or operational thresholds.
Who It Affects
Primary actors affected include the FCC (rulemaking and order issuance), FEMA (administrator of the WEA program), wireless carriers that deliver WEA messages, state and local emergency managers who request alerts, and coastal stakeholders such as beach municipalities and tourism operators.
Why It Matters
The bill changes what types of events the WEA framework can encompass, potentially lowering the bar for localized, situational public-safety alerts on mobile devices. That expansion intersects with tradeoffs between immediate public safety notification and the costs of false or frequent alerts, along with technical and coordination burdens for agencies and carriers.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Lulu’s Law is short and tightly focused. It defines "Alert Message" by reference to the current federal regulation and then imposes a single duty on the FCC: within 180 days, issue an order providing that a shark attack is an event for which a Wireless Emergency Alert may be transmitted.
The bill does not itself change the structure of the WEA program, create new funding, or spell out who within the emergency-management ecosystem should initiate such alerts.
Practically, the bill forces the FCC to make a policy decision about how shark attacks fit into existing WEA categories (for example, "Imminent Threat" or other issuer-defined categories) and to prepare whatever administrative action is necessary to allow such messages. That will likely require coordination with FEMA, which operates the Integrated Public Alert and Warning System and manages WEA implementation details, as well as with wireless carriers that must support message types, geographic targeting, and message formatting.Because the statute uses permissive language — that a shark attack "may" be transmitted — it leaves trigger criteria, message content, verification protocols, and geographic granularity to implementing authorities.
Local emergency managers would still need to decide whether an incident warrants a WEA, and carriers will have to route and deliver those messages within existing technical constraints (character limits, geofencing accuracy, and delivery priority). The absence of statutory standards or funding means the real-world effect will depend on subsequent FCC orders, interagency guidance, and operational choices by state and local officials.
The Five Things You Need to Know
The bill requires the FCC to issue its order within 180 days of enactment; it does not itself require any agency to transmit a WEA.
It ties the term "Alert Message" to 47 C.F.R. § 10.10(a), anchoring the change within the existing WEA regulatory framework rather than creating a new alert mechanism.
Lulu’s Law uses permissive language ('may be transmitted'), leaving trigger thresholds, verification procedures, and issuing authority unspecified.
The bill contains no appropriations or grant authority to fund FCC, FEMA, carrier, or local implementation costs.
Implementation will depend on FCC rulemaking or order language and coordination with FEMA and wireless carriers to update technical settings, geotargeting, and issuer policies.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — "Lulu’s Law"
This single-line provision provides the act's name. It has no operative effect but signals legislative intent and frames the subject for stakeholders and agencies that will implement the statute.
Definition — adopts existing regulatory 'Alert Message' term
Subsection (a) incorporates the existing regulatory definition of "Alert Message" by reference to 47 C.F.R. § 10.10(a). By doing so the bill avoids re‑defining the technical contours of WEA and anchors the new event-type inside the current legal and technical architecture for emergency alerts. This choice narrows the statutory footprint but also shifts detailed definitional work to the existing regulatory framework and agencies that maintain it.
Mandate to FCC — order permitting WEA for shark attacks (180‑day deadline)
Subsection (b) imposes a ministerial but consequential duty on the FCC: issue an order providing that a shark attack is an event eligible for an "Alert Message" within 180 days. The practical effect depends entirely on the language of the FCC order and any coordination with FEMA and wireless providers. The provision does not allocate funds, set operational criteria (e.g., evidence thresholds, issuer authorization, geographic radius), or change which authorities may request WEAs; it merely directs the FCC to create the regulatory permissibility.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Coastal beachgoers and swimmers — they could receive immediate mobile warnings of nearby shark attacks, enabling faster evacuation or avoidance of impacted waters.
- Local public-safety agencies and lifeguard services — the availability of WEA as a delivery option gives them a high‑priority, ubiquitous channel to reach residents and visitors quickly during acute marine hazards.
- Tourists and seasonal visitors — when used precisely, targeted alerts can reduce injury and clarify beach closures, protecting unacquainted visitors who may not see local signage.
Who Bears the Cost
- Federal Communications Commission — the agency must draft and issue an order, coordinate with FEMA and industry, and potentially oversee implementation without dedicated new resources.
- State and local emergency managers and lifeguard services — they will shoulder operational costs for verification, decision-making, and drafting of WEA messages, plus training and new protocols to avoid misuse.
- Wireless carriers — carriers must support any technical or configuration changes required to classify and deliver shark‑attack alerts, and they may face increased customer inquiries and testing burdens without reimbursement.
Key Issues
The Core Tension
The central dilemma is balancing the value of rapid, mobile warnings for potentially life‑threatening marine incidents against the risks of over‑notification: unnecessary alerts can cause panic, economic harm to coastal businesses, and alert fatigue that undermines future compliance. The bill expands the universe of WEA‑eligible events without setting the operational guardrails needed to manage that tradeoff.
The statute's brevity creates several implementation puzzles. Most importantly, it does not define when a shark attack crosses the threshold for a WEA.
WEA is typically reserved for imminently life‑threatening situations; without statutory or regulatory criteria, local issuers, FCC, FEMA, and carriers must align on standards — for example, whether confirmed attacks only, multiple incidents, or credible threat information suffice. Those choices affect false positive risk and public trust in alerts.
Operationally, WEA has technical limits: short message length, imperfect geofencing (especially offshore), and a delivery priority system designed for large populations. Translating an offshore or localized marine incident into an effective geotargeted WEA without over-notifying nearby communities is nontrivial.
The bill also provides no funding for additional training, verification tools, or public education campaigns, shifting costs to local governments and carriers. Finally, widening WEA's scope raises legal and reputational risk: poorly targeted or unnecessary alerts can prompt litigation, economic losses for beach-dependent businesses, and long-term erosion of public responsiveness to emergency messages.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.