How to Write a Phone System RFP for Schools and Government

A phone system RFP that produces comparable bids does five things. It lists every building and every line the system has to carry, including the analog lines behind fire panels and elevators. It states the 911 requirements in plain terms. It makes every bidder price the same sample month, taxes and surcharges included. It asks how the contract renews and how much notice ends it. And it asks where support staff sit and how fast they respond. A free RFP requirements template covering all of this is available to download and edit.

Most phone system RFPs we see from school districts and local governments are written under deadline, often by someone who also runs the network and the help desk. The usual result is a document that describes handsets and features in detail and leaves out the parts that decide what the system costs and whether it works on a bad day. Here is what to put in.

Start the scope with buildings, not handsets

Bidders can only price what you list. Before anything about features, write down how many buildings are in scope, the approximate number of users and extensions in each, and which buildings have seasonal call patterns, such as a school front office in August.

Then list every line the current system carries that is not a desk phone. Fire alarm panels, elevator phones, security alarm dialers, and fax machines often run on analog copper lines that nobody has inventoried in years. If the RFP does not name them, the winning bid will not include them, and they surface at cutover as a change order or a line left running on the old carrier.

Finish the scope with the systems that touch the phones: overhead and IP paging by zone, bell schedules in schools, mass notification, and how calls are handled after hours. A phone system RFP that ignores paging produces a system that cannot page.

Write the 911 requirements in plain language

Two federal rules apply to multi-line telephone systems, and the RFP should list both under its mandatory requirements.

Kari’s Law requires that anyone can dial 911 directly, with no prefix such as 9, and that the system sends an alert to someone on site when a 911 call is placed. RAY BAUM’S Act requires that a 911 call carries a dispatchable location: the street address plus the building, floor, or room that a responder needs to find the caller. Ask each bidder how their system delivers both in every building. Then ask how a new room or building gets added to the 911 map after go-live.

If analog life-safety lines are being replaced, require that the replacement meets NFPA 72 and UL 864 and passes inspection by your fire marshal. For schools, add FERPA handling of call recordings. Our post on phone system compliance laws covers the 911 rules in more detail.

Make every bidder price the same month

The monthly rate is the easiest number to compare, and it is rarely the number that shows up on the bill. Three kinds of charges tend to appear on the first invoice without having been on the quote: federal and state taxes and regulatory surcharges, E911 fees charged per number or per location, and one-time charges for number porting and activation.

The fix is a pricing format, not a negotiation. Ask every bidder to itemize one-time costs (equipment, installation, cabling) separately from recurring costs (per seat, per site, support), and then to price one complete sample month at your actual line count with every tax, surcharge, and fee included. Score that sample month. Optional add-ons belong in their own section so they do not inflate one bid and disappear from another.

Evaluate cost over the full term, not the first month. A bid with lower monthly pricing and a hardware refresh in year three can cost more than one with a higher rate and no refresh.

Ask how the contract renews and ends

Many telecom agreements renew automatically for another full term unless written notice is sent inside a set window before the end date. That notice date, not the end date, is the last day you can choose to compete the contract again.

Require bidders to state the term length, the renewal terms, the notice period in days, and how notice must be delivered. When you award, put the notice date on the procurement calendar. Your purchasing office or counsel should review the final contract language; the RFP’s job is to make sure the terms are visible before you score.

Ask where support lives and how fast it answers

Support is where phone vendors differ most and where RFPs ask the least. Ask for support hours and after-hours emergency coverage, where the support staff are located, response and resolution targets by severity, and what is handled remotely versus on site. Ask what training is included for staff and for the people who will administer the system.

Then ask for references from organizations of a similar size and type, and call them. A reference from a district or county that went through a hard month will tell you more than one that has never needed to call. Our guide to choosing a VoIP support provider goes further on local versus remote support.

If you buy through a cooperative contract

Cooperative purchasing agreements let a public buyer order from vendors who have already been through a competitive process, which can save months. They settle who you are allowed to buy from. They do not settle what you are buying. Write the scope, the 911 requirements, and the pricing format anyway, and use them in the mini-bid or quote request that goes to vendors on the contract. The template works for both routes.

Set the evaluation weights before the bids arrive

Decide how much each part of the response counts before anyone opens a bid: responsiveness to scope and compliance, total cost over the term, support model and location, relevant experience and references, and the implementation plan. Writing the weights first keeps the decision from bending toward whichever bid looks best on the one number that is easiest to compare. For schools, our K-12 phone system evaluation checklist covers what to test once a system is shortlisted.

Frequently Asked Questions

What should a phone system RFP include?

A complete scope by building, including analog lines for fire panels, elevators, alarms, and fax; Kari’s Law and RAY BAUM’S Act requirements; paging and notification needs; an itemized pricing format with a fully loaded sample month; renewal and notice terms; support hours and response targets; and evaluation criteria with weights.

How do I compare phone system bids fairly?

Require every bidder to price the same sample month at your real line count with all taxes, surcharges, and fees included, and score total cost over the full contract term. The monthly rate alone hides too much.

Do I need a full RFP if I buy through a cooperative contract?

The cooperative contract replaces the competitive process, not the scope. You still need a written scope and a pricing format to get quotes you can compare from vendors on the contract.

Is there a free phone system RFP template?

Yes. True IP Solutions publishes a vendor-neutral RFP requirements template for phone system projects. It downloads with no form, and you can edit it and publish it as your own.