Measuring Your Radio Coverage: How to Actually Find Your Dead Spots

Why Assumed Coverage Is Dangerous

Radio coverage is one of the few pieces of your operation that is invisible until it fails, and it usually fails at the worst possible moment. Crews spend years keying up from the same familiar spots, get a solid response every time, and quietly conclude the whole district is covered. That conclusion has never actually been tested. It is a habit dressed up as knowledge.

The danger is that assumed coverage tends to be strongest exactly where you least need it and weakest exactly where you most need it. The apparatus bay, the main roads, and the station parking lot almost always talk fine. The flooded basement of a commercial building, the back stairwell of a mid-rise, the bottom of a ravine on a rural road, and the far corner of your district where two towers hand off to each other are where portables go quiet. Those are also the places where a firefighter is most likely to be alone, low, disoriented, or trapped.

When you have not tested, you cannot answer the questions that matter. Can a member call a mayday from the third sub-basement of that hospital wing. Can command hear an emergency traffic transmission from the far side of the industrial park. Does your accountability system depend on a radio link that simply is not there in half the buildings you enter. If the honest answer is "we think so," you do not have coverage, you have optimism.

Talk-In and Talk-Out Are Not the Same Test

The single most common testing mistake is checking only one direction. Radio communication has two paths, and they do not always both work.

• Talk-out is your ability to transmit and be heard. You key up from the basement and dispatch or command hears you. This is the path that carries a mayday out.
• Talk-in is your ability to receive. Dispatch or command keys up and you hear them clearly. This is the path that carries the evacuation order, the accountability check, and the "we are pulling everyone out" message in.

These two paths can fail independently. A portable can often be heard but cannot hear, or hear but not be heard, because the tower transmitter and receiver have different power, different antenna heights, and different noise conditions. A member who can hear command perfectly may not realize their own transmissions are breaking up into nothing on the other end. That is the worst failure mode, because it feels like everything is fine right up until no one answers the mayday.

Every test you run has to check both directions explicitly. Do not accept "I heard them" as proof of coverage. The tester keys up and asks for a specific readback, and the other end keys up and asks for one too. Both parties confirm out loud what they received. If either direction is marginal, that spot is marginal, full stop.

Low-Cost Drive Tests and Walk Tests

You do not need a spectrum analyzer or a paid propagation study to start. You need a portable radio identical to what your crews carry, a second person on the other end of the link, a paper map or a mapping app, and a notepad. The method is simple and it is honest.

Drive testing covers the district at road level. Take the portable (not the mobile in the apparatus, which has far more power and a roof antenna and will lie to you about what a handheld can do) and drive your response area. Stop at regular intervals and at every spot you suspect. At each stop, both ends exchange a short scripted transmission and rate it. Pay special attention to district edges, valley bottoms, dense downtown blocks, tunnels, underpasses, and the zones where you know one tower hands off to another.

Walk testing covers what the drive cannot: the inside of buildings and the vertical dimension. Coverage at the curb tells you nothing about coverage in the fourth-floor interior stairwell. Walk the portable into and through the structures that matter, floor by floor, into basements and stairwells and interior rooms, and test both directions at each point.

Use a plain, consistent rating so different testers produce comparable results. A simple scale works well:

• Good: clear, full-quieting, no effort to understand, both directions.
• Marginal: readable but noisy, scratchy, requires repeats, or fine one direction and rough the other.
• None: cannot establish reliable two-way contact.

Record the location, the rating, the direction that failed, the channel or talkgroup, the date, and the radio model. A rating with no location and no channel is a rumor. A rating with all of them is data you can act on and defend.

Testing the Places That Actually Fail

Buildings eat radio signals. Concrete, steel, below-grade construction, metal roofing, low-emissivity glass, and sheer building depth all attenuate portable signals, and the effect stacks with distance from the tower. These are precisely the structures where interior crews operate for long stretches, so they deserve deliberate, methodical testing rather than a quick check from the lobby.

Prioritize the structures where a coverage failure would be most consequential:

• Basements and sub-levels. Below-grade is the classic dead spot. Test every level down, in the interior, not just at the base of the stairs.
• Stairwells and their landings. Enclosed stair shafts behave very differently from the open floors around them, and they are the primary vertical travel path.
• Large-footprint and hardened buildings. Hospitals, big-box retail, warehouses, parking structures, schools, and industrial plants. Deep interior rooms far from any exterior wall are the weak points.
• Mid-rise and high-rise interiors. Upper-floor interiors, elevator lobbies, mechanical rooms, and any core spaces.
• Low terrain across the district. Ravines, riverbanks, cuts, and shadowed valleys where terrain, not construction, blocks the path.

When you find a building that fails, do not just mark it dead and move on. Note where inside it fails, at what floors or areas, and in which direction. A building where only the third sub-basement loses talk-out is a very different tactical problem from a building that is dark throughout, and your crews need to know which one they are walking into.

Test on the Real Channels and Infrastructure

A test only tells you the truth if it uses the exact system your crews will use on the incident. This trips up a lot of well-intentioned testing.

Test on the actual fireground channels and talkgroups, not just the dispatch channel. Many systems route dispatch and tactical traffic through different resources. A talkgroup that leans on a repeater or a specific tower may cover a building fine, while a simplex tactical channel that talks radio-to-radio directly can behave completely differently in the same spot. If your operations move to a direct radio-to-radio channel inside the structure, that direct mode is what you must test inside the structure, because it has no infrastructure helping it at all.

Test the infrastructure path you actually depend on. If your coverage relies on a specific repeater, a vehicular repeater, or a bi-directional amplifier system in certain buildings, test with that path in its normal operating state. If a building has an in-building signal enhancement system, confirm it is actually powered and working, because these systems fail silently and a failed one leaves you with worse-than-nothing false confidence.

• Test dispatch, tactical, and any mutual-aid channels separately. Do not assume one stands in for another.
• Test both repeater-assisted and direct radio-to-radio modes wherever crews use both.
• Note which channel each result belongs to. A spot can be Good on one and None on another.

Turn Your Crews Into Sensors

A formal test day gives you a snapshot. Your crews give you a continuous feed, if you build the habit of collecting it. Every member is already in your problem buildings and your low terrain on real calls, and they already notice when a radio goes rough. The gap is that most of that knowledge dies as a comment in the cab on the way back to quarters and never becomes a record anyone can use.

Make reporting a coverage gap as routine as reporting a broken piece of equipment. Keep it dead simple, because a complicated form guarantees silence:

• Where did the radio fail. Address, and where inside if it was a building.
• Which direction failed. Could not hear, could not be heard, or both.
• Which channel or talkgroup was in use.
• When, so patterns tied to system load or weather can surface.

Two benefits come out of this. First, crews confirm or challenge your formal test results with real-world experience, and reality always wins. Second, the act of reporting keeps coverage awareness alive, so members go into structures already thinking about where they might lose contact and what they will do about it.

Mapping and Recording So the Data Is Usable

Test results that live in one officer's memory or a notepad in a desk drawer are worthless in an emergency. The goal is a record any member or incident commander can pull up and read at a glance, and that survives staff turnover.

At minimum, your coverage record should let you answer, for any location, three questions: is coverage good, marginal, or absent here, which direction fails, and on which channels. That can be a color-coded map of the district (green, amber, red), a list of known dead-spot buildings with the specific interior areas noted, or ideally both. Keep the raw fields behind it so results stay comparable and re-checkable:

• Location, precise enough to find again, including floor or area inside a building.
• Rating (good, marginal, none) and the direction that failed.
• Channel or talkgroup and the radio model tested.
• Date tested and who tested it.

The highest-value move is to connect coverage knowledge to pre-planning. A building pre-plan that lists hydrants, hazards, and layout but says nothing about radio coverage is missing a life-safety detail. If a building has a dead sub-basement, the pre-plan should say so, and it should say what the plan is (relay member posted at the stairwell, a runner, a specific hard channel, a vehicular repeater positioned at a certain door). That way the coverage limitation and its workaround arrive together, at the moment the crew is sizing up the building, not as a surprise after they are already inside and quiet.

Engineering Study Versus Procedural Workaround

Field testing tells you where the problems are. It does not always tell you how to fix them, and it is not meant to. The important judgment is knowing which gaps you can manage with procedure and which ones need professional help.

A procedural workaround is appropriate when the gap is contained, understood, and manageable with tactics your crews control. A single building with a dead basement can be handled with a posted relay member, a runner, a positioned repeater, or a switch to a specific channel that works there, all written into the pre-plan and trained on. An edge-of-district road with a known dead stretch can be handled by awareness and by knowing where coverage returns. These fixes cost little and can be in place tomorrow.

A professional engineering study is warranted when the pattern is broad, systemic, or safety-critical and no reasonable procedure covers it. Large sections of the district with no reliable talk-out, a critical building type your crews cannot communicate in at all, coverage that seems to degrade under load or in bad weather, or handoff problems between towers across a wide area point to system-level causes that field testing can flag but not diagnose. These involve tower siting, transmitter power, antenna systems, frequency planning, and interference analysis, and they call for people with the instruments and the credentials to measure signal formally against recognized public-safety coverage standards and to design a real remedy.

Your field data is not wasted when you call in a professional. It is exactly what makes the study efficient and credible. Handing an engineer a documented map of confirmed dead spots, with directions and channels noted, turns an open-ended and expensive investigation into a focused one, and it gives your funding request the concrete, defensible evidence that budget officers and commissioners need to see.

Takeaways

• Untested coverage is a guess. The places you never test are usually the low, deep, edge-of-district places where a mayday is most likely and most likely to go unheard.
• Always test both directions. Talk-in and talk-out fail independently. Being heard is not proof you can hear, and hearing is not proof you can be heard.
• You can start for almost nothing. A portable identical to your crews', a partner on the other end, a map, and a notepad, with a plain good/marginal/none rating, will find most of your dead spots.
• Test the real system. Use the actual portables, the actual fireground channels and talkgroups, the actual infrastructure, held and carried the way crews really carry it.
• Make crews part of the sensor network, keep reporting simple, and always close the loop so the reports keep coming.
• Record it so it is usable and tie it to pre-plans, then re-test after any system change, new construction, or tower work, because coverage is never finished.
• Know the fix line: contained gaps get a trained procedural workaround; broad, systemic, safety-critical gaps get a professional engineering study, backed by the field data you already collected.