Writing an RFP for a Mass Notification System

mass notification system rfp

Facing a blank page and a deadline? A strong mass notification system RFP states your alert scenarios, required channels, integration needs and scoring rules plainly, so vendors answer the same questions and you can compare them fairly.

This page narrows the wider mass notification system topic down to the procurement document itself.

Item Value
IPAWS created under Executive Order 13407, signed June 26, 2006
Alert pathways IPAWS integrates EAS, WEA, National Weather Radio All Hazards and internet-based systems
Law extending IPAWS to wireless devices Warning, Alert, and Response Network Act, 2006
IPAWS Modernization Act P.L. 114-143, passed 2016
Law requiring minimum requirements for IPAWS users P.L. 116-92, 2019
Year the EAS replaced the EBS 1994

The figures come from the Congressional Research Service primer on IPAWS, which summarises the history of US public alerting. Laws and programmes change, so check the source before you rely on them.

What a mass notification system RFP has to settle first

A good RFP begins with a plain statement of purpose: who sends alerts, to whom, and about what. Vendors cannot design or price against a vague goal, so write this down before you draft a single requirement.

Next, list the scenarios the system must handle. Each one becomes a test you can put to bidders later:

  • Severe weather warnings for a campus, city or site
  • Lockdown, evacuation or shelter-in-place instructions
  • Utility, network or IT outages that affect staff or residents
  • Public health or safety notices
  • Routine operational messages that keep the system familiar to users

Then separate your audiences. Employees, students, residents and visitors rarely share the same contact data, so say which records you already hold and which the vendor must help you collect.

How IPAWS and federal alerting rules shape your requirements

If you are a government body in the United States, the IPAWS gateway is likely to feature in your RFP. According to the CRS report, the system is designed to receive and authenticate one message from an authorized originator and send that single alert across many networks at once.

The same report says IPAWS authenticates, validates and distributes alerts across four pathways:

  • The Emergency Alert System (EAS)
  • Wireless Emergency Alerts (WEA)
  • National Weather Radio All Hazards
  • Internet-based systems

The history explains why these pathways exist. The CRS primer notes that the FCC replaced the Emergency Broadcast System with the EAS in 1994, and that IPAWS was created under Executive Order 13407, signed on June 26, 2006. In 2006 Congress also passed the Warning, Alert, and Response Network Act, which extended IPAWS to wireless devices.

A person in a gray jacket writes on a sheet of paper at a white desk.

Later laws added expectations that bidders should be able to address. The CRS report says the IPAWS Modernization Act of 2015 (P.L. 114-143) was passed in 2016, and that P.L. 116-92 in 2019 required FEMA to develop mandatory minimum requirements for state, local, territorial and tribal governments that use IPAWS.

Ask each vendor to explain, in writing, how its platform connects to IPAWS and which of your obligations it supports. Do not accept a general statement of compatibility.

Requirements worth writing into the RFP

Turn your scenarios into numbered, testable requirements rather than adjectives such as “robust” or “user-friendly”. These are the areas most RFPs cover:

  • Channels: which of voice, text, email, app, sirens, digital signage and public pathways must be supported.
  • Targeting: sending by map area, group, role or location, not only by list.
  • Accessibility and language: support for people with disabilities and limited English proficiency.
  • Security: user authentication, permission levels and audit trails for every sent message.
  • Reporting: delivery and response records you can export after an incident.
  • Training and support: what the vendor provides before launch and during an event.

The accessibility item has a public-sector basis. The CRS report says P.L. 114-143 codified requirements that IPAWS be adaptive to geographic locations, accessible to people with disabilities and limited-English proficiency, and improved in resiliency and security.

Reliability deserves its own section. The same CRS report lists asserted network connectivity issues and outages among the topics Congress may consider, so ask bidders how their service stays up when a network does not.

How do you score proposals fairly?

Publish your scoring method in the RFP itself. Bidders then know what matters, and your evaluation panel has a record that supports its decision.

  1. Set weighted criteria, such as functionality, security, support, references and price.
  2. Require every vendor to answer in the same format, so that answers line up side by side.
  3. Score each requirement independently before the panel discusses the results.
  4. Run a scripted scenario test using your own list of situations rather than a vendor’s prepared presentation.
  5. Contact customer references that resemble your organisation in size and type.

Pricing needs a standard template. The CRS report records asserted concerns about initial and ongoing costs as a factor in IPAWS adoption, so request both set-up and recurring charges. Our guide to mass notification system cost covers pricing in more depth.

Where the RFP ends and wider event planning begins

A notification tool is only one part of an emergency response. Decide early whether you want messaging alone or also incident workflows, risk monitoring and task tracking.

If the wider scope is on your list, read about critical event management before you finalise the document, because it affects the requirements and the scoring. Many buyers split the two needs into separate procurements.

Whatever you buy, a procurement document does not replace your own emergency plan. For personal safety instructions during a real event, follow your official local emergency authorities.

Frequently asked questions

Who should help write the RFP?

Show answer

Bring in emergency management, IT, legal, communications and procurement staff at the start. Each group sees different risks, and early input avoids rewrites after bids arrive.

Does every RFP need an IPAWS section?

Show answer

No. It matters mainly to public bodies that are, or plan to become, authorized alert originators. The CRS report says FEMA manages IPAWS and the FCC sets operational rules for the EAS, so a private organisation alerting only its own staff may not need that pathway.

How detailed should the scenarios be?

Show answer

Detailed enough that two vendors would run the same test. Name the audience, the trigger, the channels and the time you expect a message to take, then ask bidders to show the steps.

What should I ask about outages?

Show answer

Ask for the vendor’s failover design, how it handles a carrier or internet disruption, and what its service record shows. Request written answers so you can score them against competitors.