The Emergency Alert System and Wireless Emergency Alerts
In this document, the Federal Communications Commission (FCC or Commission) amends its regulations governing the Emergency Alert System (EAS) and Wireless Emergency Alerts (WEA) to add a new event code, MEP, to allow alert originators to issue an alert to the public about missing and endangered persons (MEP) whose circumstances do not meet the criteria of "America's Missing: Broadcast Emergency Response" (AMBER) alerts.
What this rule actually says
The FCC added a new alert category called MEP (Missing and Endangered Persons) to the Emergency Alert System and Wireless Emergency Alerts that broadcast on phones and emergency radio. This lets police and authorized agencies issue emergency alerts about missing people who don't qualify for AMBER alerts—like missing seniors with dementia or endangered adults. Think of it as a formal broadcast channel alongside weather alerts and child abduction warnings.
Who it applies to
- If you're building an emergency alert platform or integration: You need to support the MEP code if your system processes, routes, or displays EAS/WEA messages.
- If you're a telecom carrier or broadcast station: You must implement MEP alert handling in your systems (most indie founders are not in this category).
- If you're building a missing persons app: Only applies if your product directly integrates with or relies on official EAS/WEA channels—most AI chatbots or support tools won't.
- Jurisdiction: This is U.S. federal (FCC), so only relevant if operating in the U.S. market.
- Data scopes: This rule governs the *transmission* of alert messages through official channels, not data collection. If your app collects missing person reports or medical info, this doesn't directly regulate that (other laws do).
What founders need to do
- Assess if you're affected (1 day): Does your product receive, transmit, or display official EAS/WEA alerts? If no, stop here. If yes, continue.
- Review FCC MEP specifications (2-3 days): Read the updated EAS/WEA technical standards on the FCC website to understand MEP event code formatting and handling requirements.
- Update your systems (3-5 days): Modify any alert-parsing, routing, or display logic to recognize and properly handle MEP alerts alongside existing alert types.
- Test with your infrastructure provider (ongoing): Work with your telecom or broadcast partner to ensure MEP alerts transmit and display correctly in your app or system.
- Document your compliance (1 day): Keep records showing your system handles MEP alerts per spec. No formal filing required, but documentation matters if audited.
Bottom line
Monitor only unless you're directly building emergency alert infrastructure—most indie AI founders (medical scribes, chatbots, hiring tools) have zero compliance work here, but creators of missing persons platforms or alert-adjacent products should spend a day checking if this applies.