Radio System Procurement: What to Look For Beyond the Spec Sheet

The sticker price is the smallest number you will pay

The first thing to understand about a radio proposal is that the headline number is deliberately incomplete. It is the price of getting you to sign. The real cost lives in the years after, and a good chunk of it is not on the page you were handed. Before you compare two proposals dollar for dollar, you have to reconstruct what each one actually costs across its full life, because the vendor with the lower sticker is frequently the one who moved the most cost into the recurring column where it is harder to see.

Build a total cost of ownership picture that runs at least ten years, and preferably matches the expected life of the infrastructure. At minimum, account for these lines, whether or not the proposal names them:

• The infrastructure itself: core equipment, site electronics, antennas, and the physical work to install and commission it.
• The subscriber units, which means every portable and every mobile radio, plus spares, batteries, chargers, and the accessories crews actually need to work.
• Programming and reprogramming labor, which recurs every time your talkgroups, your fleet, or a neighboring system changes.
• Annual service and support agreements, which are frequently structured to escalate.
• Software assurance or feature subscriptions, covered in more detail below and in our companion piece on recurring costs.
• Site costs you may not own directly: tower leases, backhaul connectivity, power, and generator maintenance.
• Training, both at rollout and for every new hire afterward.
• The eventual technology refresh, because nothing on this list lasts forever.

When you lay two proposals side by side this way, the comparison often inverts. Be honest about your incentives as a buyer, and be honest about theirs as a seller. A vendor's business is healthiest when it earns predictable revenue from you every year, not when it hands you a system and walks away. That is not a scandal, it is just the shape of the industry, and the shape of the industry is exactly why you have to model the recurring lines yourself rather than trusting that the sticker tells the whole story.

Coverage: demand a real study, not a colored map

Coverage is where the gap between the sales presentation and reality is widest, and it is also the one that gets crews hurt. A radio that does not work in the back stairwell of a big-box store, in the sub-basement of a parking structure, or in the dead pocket on the far side of the county is not a communications tool, it is a liability with a battery. You cannot evaluate coverage from a glossy map, and you should be suspicious of any proposal that offers one as proof.

What you want is a predictive coverage study built for your actual geography, followed by a contractual coverage guarantee you can enforce. Those are two different things and you need both. The study is the promise. The guarantee is what happens when the promise breaks.

When you read a coverage claim, force these questions to the surface:

• What signal level is being guaranteed, and is it measured for a portable radio worn on the body, not a mobile radio bolted to a truck with a roof antenna? The difference is enormous and vendors know which number looks better.
• Is the guarantee for outdoor coverage, or does it include in-building penetration? Structures kill signal, and your worst incidents happen inside them.
• What percentage of your service area, and what percentage of the time, is the guarantee written for? A promise of coverage across most of the area most of the time can still leave a specific stairwell dark on a specific bad night.
• How will coverage be verified after installation, who pays for that acceptance testing, and what is the remedy if it fails? Get the remedy in the contract before you sign, not after crews start reporting dead spots.

Insist that acceptance testing use a documented, drive-and-walk methodology across a defined grid, with a pass threshold agreed in advance. If the vendor is confident in the design, they will not flinch at a rigorous acceptance test, because they expect to pass it. Resistance to a firm acceptance standard is itself a data point.

Standards compliance and true interoperability

Interoperability is the single most important reason public safety radio standards exist, and it is also the area where marketing language is loosest. The relevant open standard suite for land mobile radio in public safety is P25, defined under the TIA-102 family of standards. The point of P25 is that equipment from different manufacturers can work together on the same system and across neighboring systems, so that when a large incident pulls in mutual aid, everyone can talk.

The trap is the phrase "P25 compatible," which is not the same as "P25 compliant," which is not the same as independently verified. A responsible way to check the last of those is to look for evidence tested under the P25 Compliance Assessment Program, the standardized process for confirming that equipment meets the published requirements and interoperates as claimed. Ask for the actual compliance documentation. Do not accept a logo on a brochure as proof.

Standards compliance protects you in two directions at once. It protects your mutual aid, because a compliant system speaks the same language as your neighbors even if they bought from a different vendor. And it protects your wallet, because a genuinely open, standards-based system means your next subscriber-radio purchase is not automatically locked to one manufacturer. A vendor benefits when their features quietly drift outside the standard, because proprietary features are the strongest form of lock-in there is. Your job is to keep the essential functions on the standard side of the line.

Two practical points that predate this purchase but still bind you. First, narrowbanding requirements reshaped the VHF and UHF landscape years ago, and any equipment you buy must operate within the current channel bandwidth rules. Second, whatever you buy has to coexist with the regional and statewide interoperability plans your mutual aid partners rely on. Bring the people who run those regional systems into your evaluation early. They will tell you in ten minutes about compatibility problems a vendor would take a year to admit.

The feature licensing trap

Here is a pattern that catches departments repeatedly. The demonstration shows a system that does everything: encryption, location tracking, advanced call handling, over-the-air programming, text and data features, the full picture. What is not always said out loud is that a meaningful share of those capabilities are not included in the base price. They are licensed features, and the license may be per-radio, per-year, or both.

The hardware in your hand is frequently capable of far more than it is licensed to do. You may be carrying a radio with encryption built into the chip, unusable until you pay to unlock it, and payable again on every unit. Features you assumed were bundled can turn out to be a recurring line that grows every time you add a radio to the fleet. This is closely related to the subscription question, and because it deserves its own full treatment, we cover the mechanics of subscription and feature licensing in a companion piece; here the point is narrower, which is that you cannot evaluate a proposal until you know which capabilities are permanent and which are rented.

Before you sign, build a simple two-column list. On one side, every feature that comes with the hardware and stays yours for the life of the radio. On the other, every feature that requires an ongoing license, with the cost per unit and the renewal terms. Then ask the questions vendors would rather you did not:

• If I stop paying the annual software or feature fee, what stops working, and does the radio keep its basic voice function or degrade further?
• Is encryption a one-time purchase or a recurring license, and does the license travel with the radio or expire?
• When I add radios in year three, do the new units cost the same per-feature rate, or does the price change once I am committed?
• Are there features on this hardware that are disabled today and can be enabled later, and what will they cost when I need them?

Maintenance, lifecycle, and the subscriber replacement cycle

A radio system has two clocks running at different speeds. The infrastructure clock is slow, measured in a decade or more before a major technology refresh. The subscriber clock is faster. Portable and mobile radios take abuse, and even the ones that survive the abuse eventually fall off the manufacturer's support list. When a subscriber model reaches end of life, replacement parts dry up, software updates stop, and the day comes when a failed radio cannot be repaired at any price. That day arrives whether or not you budgeted for it.

Plan the subscriber replacement cycle from the start, and plan it as a rolling program rather than a single catastrophic year where every radio ages out at once. Ask the vendor for the expected support lifespan of the specific subscriber models you are buying, in writing, and ask how much warning you will get before a model is declared end of life. Then set aside money every year so the replacement is a scheduled expense, not an emergency.

On the maintenance side, understand exactly what the service agreement covers and what it excludes:

• Does the agreement cover infrastructure only, or subscriber repair too, and what is the turnaround time on a failed portable?
• Are software updates and security patches included, or are they a separate line, and how long will this generation of software be supported at all?
• What is the guaranteed response time if a site goes down, and what is the penalty if the vendor misses it?
• Can your own technicians be trained and authorized to do routine work, or is every task locked behind a service call you pay for?

The answer to that last question tells you a lot about the relationship you are entering. A vendor confident in the product tends to be comfortable letting you do basic maintenance. A vendor whose revenue depends on service calls tends to make sure you cannot.

Migration and backward compatibility

You are almost never buying into an empty field. You have radios in service today, mutual aid partners on their own systems, and a cutover window during which both the old and new systems have to work at the same time, because you cannot take your crews off the air to flip a switch. Migration is where good technical designs meet bad operational reality, and it is worth as much scrutiny as the coverage study.

Ask how the transition actually happens on the ground. Can existing radios be reprogrammed to operate on the new system during a transition period, or must every unit be replaced before the new system goes live? A phased migration that lets you move stations or divisions in stages is far safer than a hard cutover, and far kinder to the budget, because it spreads the subscriber replacement across more than one fiscal year.

Backward compatibility with your neighbors matters just as much as compatibility with your own old gear. If a mutual aid partner is a generation behind, or is planning their own upgrade on a different timeline, the new system still has to talk to them on the incident scene. Standards compliance is what makes this possible, which is one more reason to hold the line on genuine standards conformance rather than accepting proprietary shortcuts that work beautifully until the moment an outside crew keys up on your fireground.

Contract terms: ownership, escalation, and the exit

The contract is where the deal is really made, and it is the part most likely to be skimmed because it is dense and unglamorous. Slow down here. A few clauses will determine whether this purchase ages into a stable asset or a slow financial bleed.

First, ownership versus subscription. Are you buying equipment that becomes yours, or are you entering an arrangement where you are effectively renting the capability for as long as you keep paying? Neither is automatically wrong, but they are radically different commitments, and the difference has to be named plainly before you sign, not discovered in year four. If any part of the system is subscription-based, understand precisely what you own outright and what evaporates the day the payments stop.

Second, escalation. Recurring fees frequently include an annual increase, and if that increase is uncapped or tied to a vague index, your predictable line item quietly becomes an unpredictable one. Negotiate a hard cap on annual escalation, stated as a fixed percentage, for the full term. This single clause protects more of your future budget than almost anything else in the document.

Watch for these as well:

• Price protection on future subscriber-radio and accessory purchases, so the units you add later are not repriced once you are locked in.
• Clear terms on what happens at the end of the agreement, including whether the system keeps functioning and what a renewal will realistically cost.
• Data and configuration ownership, so your talkgroup structure, your programming, and your records belong to you and are portable if you ever change vendors.
• Defined performance remedies, so a missed coverage guarantee or a missed response time has a consequence the vendor actually feels.

References, site visits, and the questions they hope you skip

Every vendor will hand you a list of happy references. Take it, and then go past it. The references on the list were chosen because they will say nice things. The department you actually want to talk to is one that has lived with the system for five or six years, long enough for the honeymoon to end and the real support relationship to show itself.

Find similar departments the same size as yours, with similar geography and similar apparatus, and call them whether or not they are on the list. Ask a regional interoperability coordinator who they hear complaints about. When you visit a reference site, do not just watch a scripted demonstration. Ask to see the system on an ordinary day, and put these questions to the people who use it, not the people who sold it:

• What broke that you did not expect, and how long did it take to get fixed?
• What did the second and third year cost compared to what you were quoted at signing?
• What features did you assume were included that turned out to be licensed?
• How did coverage hold up in the buildings and terrain that worried you most?
• If you were doing this over, what would you put in the contract that you left out?

That last question is the most valuable one you can ask, because the answer is a free list of the mistakes you are about to have the chance to avoid. Write down what you hear and carry it straight into your own negotiation. The point of all of this is not to treat vendors as adversaries. Plenty of them build good systems and stand behind them. The point is that you and the vendor have different incentives, both of them legitimate, and the only way to land a deal that serves your crews for the next fifteen years is to do the homework the spec sheet was designed to make you feel you could skip.