The bill directs the Director of the Federal Protective Service (FPS), in coordination with the Secretary of Homeland Security, to develop and implement guidance on emergency communication for law enforcement–related events in federal buildings protected by FPS. The guidance is intended to standardize when and how tenants are notified of violent threats and to ensure tenants receive actionable safety instructions.
This matters for any federal agency that occupies space in FPS-protected buildings because it centralizes alert expectations, creates named implementation responsibilities at the building level, and requires periodic testing and a short report to Congress — all of which can change operational practices for security officers, facility managers, and tenant agencies.
At a Glance
What It Does
The bill requires the FPS Director to publish guidance within one year on emergency communications about law enforcement–related events for federal tenants in FPS-protected buildings. The guidance must include protocols for notifying tenants about violent threats within approximately 150 feet of a building and must require tenants receive safety instructions for immediate or heightened threats.
Who It Affects
Federal tenant agencies and their employees occupying space in FPS-protected buildings, the Facility Security Committee (and its designated official) at each building, the FPS and DHS for coordination and oversight, and private security or facility contractors who operate notification systems.
Why It Matters
By setting a uniform expectation for when and how tenants get notified, the bill shifts some implementation duties to building-level security officials and FPS, creates an obligation for periodic testing, and demands a concise report to Congress — all steps that can alter procurement, training, and day-to-day emergency operations in federal facilities.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill defines “law enforcement-related” events as those that require a law enforcement response and directs the FPS Director, working with DHS, to create guidance for notifying federal tenants in buildings under FPS protection. That guidance must be completed and implemented within a one-year timeframe set by the statute.
It is intended to cover violent threats and incidents that occur in or near federal building perimeters and to standardize both timing and content of alerts.
On content, the statute specifies the guidance should include best practices and protocols: standard operating procedures to inform tenants in a timely manner about violent threats occurring in the building or within roughly 150 feet of the perimeter (explicitly calling out firearm events, other weapons threats, suspected or confirmed terrorism, and suspicious devices) and instructions tenants should follow when facing an immediate threat or heightened risk. The bill assigns the building-level implementation responsibility to the designated official of each building’s Facility Security Committee and directs the FPS Director to confirm that each department or agency has such a designated official consistent with Interagency Security Committee (ISC) guidelines.Beyond notification content and delegation, the bill requires FPS to ensure tenants are able to respond to law enforcement–related crises and to conduct periodic testing to prepare for such events.
Finally, FPS must submit a concise electronic report to Congress within one year — limited to ten pages — describing the best practices and protocols implemented, and provide a briefing outlining any support needed to keep FPS-protected buildings safe. The statute leaves the specifics of format, technology, and training to the guidance process but creates clear timing, content boundaries, and assignment of implementation responsibility.
The Five Things You Need to Know
The FPS Director must develop and implement emergency communication guidance within one year of enactment.
Guidance must cover threats occurring inside a building or within approximately 150 feet of the building perimeter, explicitly including all firearm events, other weapons threats, terrorism threats, and suspicious devices or materials.
The designated official of a building’s Facility Security Committee is responsible for implementing the guidance at each FPS-protected building; FPS must confirm each agency has such an official consistent with ISC guidelines.
FPS must ensure tenant readiness by conducting periodic testing of crisis response procedures to prepare for law enforcement–related events.
Within one year, FPS must submit an electronic report (no longer than 10 pages) to Congress on implemented best practices and provide a briefing on additional support needed to maintain building safety.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the Act’s name as the “Federal Building Threat Notification Act.” This is purely administrative but signals Congressional intent to prioritize tenant notification and guidance development.
Key definition — 'law enforcement-related'
Defines the statute’s operative trigger: a ‘law enforcement-related’ event is one that requires a law enforcement response. That narrow definition frames what incidents the guidance must cover and excludes broader emergencies that do not require police intervention (for example, most medical incidents or routine building system outages).
Mandate and timeline for guidance
Requires the FPS Director, in coordination with the Secretary of Homeland Security, to develop and implement guidance for emergency communications for federal tenants in FPS-protected buildings no later than one year after enactment. Practically, agencies should expect an interagency drafting process, stakeholder outreach to tenant agencies, and decisions about delivery mechanisms (PA systems, SMS, email, mass notification software).
Minimum contents of the guidance
Specifies two content areas the guidance must address: (A) SOPs to inform tenants in a timely manner about violent threats in the building or within roughly 150 feet of the perimeter, including explicit categories like firearm events, terrorism, and suspicious devices; and (B) instructions tenants should follow in response to immediate threats or heightened risk. This provision constrains the guidance’s scope and forces FPS to address identification thresholds, message content, and actionable tenant behaviors.
Facility Security Committee responsibilities and agency confirmations
Assigns implementation responsibility to the designated official of each building’s Facility Security Committee and requires FPS to confirm that each department or agency occupying FPS-protected space has such a designated official, consistent with ISC guidelines and applicable law. This creates a named compliance point at each building and ties the guidance to existing ISC structures rather than creating a parallel framework.
Tenant readiness and periodic testing
Directs FPS to ensure federal tenants can adequately respond to law enforcement–related crises and to conduct periodic testing. That requires decisions about exercise cadence, standards for evaluating tenant readiness, whether tests are announced or unannounced, and how results feed back into training and resource allocations.
Congressional report and briefing
Mandates an electronic report to Congress, coordinated with DHS, due within one year and limited to no more than ten pages describing the best practices and protocols implemented under the Act. It also requires a briefing to present any information on support needed to maintain FPS-protected building safety. The page cap compels a concise, prioritized report rather than a comprehensive operational manual.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- Federal tenants and employees — receive standardized, timely notifications and clear instructions during violent or law enforcement–related incidents, which can reduce confusion and improve personal safety decisions.
- Facility Security Committee officials — gain a clear mandate and a centralized set of best practices to guide local implementation, which can reduce ambiguity about roles during an incident.
- First responders and on-site security teams — benefit from pre-established notification protocols that can improve coordination and reduce response friction when multiple agencies share a building.
- DHS and FPS leadership — gain a standardized framework to evaluate building readiness across agencies and to justify resource requests with consolidated reporting to Congress.
Who Bears the Cost
- Tenant agencies and departments — must allocate staff time and possibly funding to implement guidance, appoint Facility Security Committee officials, participate in testing, and adapt local procedures and training.
- Facility Security Committee designated officials — take on implementation and ongoing compliance duties, including organizing drills, maintaining notification systems, and liaising with FPS; this can be a significant operational workload.
- FPS and DHS — must devote personnel and possibly contract resources to develop, coordinate, and support implementation of guidance, run testing programs, and compile the required Congressional report within tight timeframes.
- Security system contractors and vendors — may face new technical requirements to support standardized messaging, geofencing (to cover the ~150-foot perimeter), and integration with federal tenant directories, leading to procurement and upgrade costs.
Key Issues
The Core Tension
The central dilemma is between speed and specificity: the bill aims to get fast, standardized alerts into the hands of tenants to improve safety, but broad, rapid notifications risk false alarms, operational disruption, and interference with sensitive law enforcement operations; conversely, tighter controls to avoid these harms will slow notifications and may reduce their life‑saving value.
The statute sets clear high-level requirements but leaves numerous operational choices to FPS and DHS. The roughly 150-foot perimeter benchmark is a blunt metric that will be hard to apply in dense urban settings, multi-building campuses, or where public sidewalks and shared commercial spaces abut federal facilities.
Implementers will need to translate that distance into geofencing rules, floor-by-floor message triggers, or other technical methods — choices that will materially affect who receives alerts and how quickly.
The bill requires periodic testing and a concise report to Congress but does not provide funding, penalties, or enforcement mechanisms for noncompliance, nor does it prescribe message formats, integration standards, or privacy safeguards for tenant data used in notification systems. Those omissions create risks: agencies may interpret the guidance unevenly, testing could become perfunctory if unfunded, and notification systems could produce false or overbroad alerts that disrupt operations.
The ten-page report limit will force FPS to prioritize high-level findings over detailed implementation challenges, potentially obscuring complex resource or interoperability needs from Congressional view.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.