Building a Radio Cache for Large Incidents and Mutual Aid
On an ordinary shift your department has exactly as many portable radios as it has people who need one, and not one more. That balance holds right up until the day it does not: a working structure fire that pulls three mutual aid companies onto your ground, a wildland run that stretches into a second operational period, a search that puts twenty untrained volunteers in the woods with no way to talk to anyone. A radio cache is the pool of programmed, charged, ready-to-hand radios you reach for when the incident is bigger than your inventory. Built well, it turns an arriving crew into a talking crew in under a minute. Built poorly, or not at all, it leaves people standing in a parking lot with dead handhelds and no channel in common.
What a radio cache is and why it matters
A radio cache is a stored, ready pool of programmed portable radios, along with the spare batteries, chargers, and accessories that keep those radios useful for the length of an incident. It is not the same thing as your daily-issue radios, and it is not a drawer of broken units nobody wanted to throw away. It is a deliberate reserve, maintained on purpose, so that when demand spikes you can hand a working radio to a person who does not have one.
The reason it matters comes down to a simple mismatch. Your normal radio count is sized for a normal day. A large incident does not respect that number. Mutual aid crews arrive on their own systems, which may or may not reach your dispatch. Off-duty personnel get recalled and report without gear. Support roles that never carry a radio on a routine call suddenly need to hear traffic. Interoperability planning has spent years pointing out that the failure is rarely the radios themselves; it is that the right people cannot talk on a common channel at the moment it counts. A cache is one of the few things a single department can build on its own to close that gap.
The cache also buys you time and simplicity under stress. The middle of an escalating incident is the worst possible moment to be programming radios, hunting for batteries, or explaining channel plans. If that work is done in advance, the incident commander gets to think about the incident instead of the communications logistics.
What belongs in the cache
A cache is more than a stack of radios. It is a small kit that has to function without help from your shop or your regular supply room, because it will often deploy to a place that has neither. Plan the contents so an arriving user needs nothing else to get on the air.
- Portable radios, pre-programmed. Each unit loaded with the channels an outside crew is most likely to need: your primary dispatch and fireground or tactical channels, plus the shared interoperability channels your region has designated for cross-agency use. Label each radio with a unique number so it can be tracked.
- Batteries and chargers. At least one spare battery per radio, and enough charging capacity to keep the whole cache topped off between uses and during a long incident. A multi-unit charging bank or several individual chargers is worth the cost. Radios with no charged batteries are decorations.
- Speaker microphones. A remote speaker mic clipped to the shoulder is far more usable under a coat, in wind, or with gloves than a radio buried on a belt. Include one per radio where you can.
- A channel plan and quick-start card. A laminated card that lists the channel positions in plain language: what channel one is, what channel two is, and when to use each. Someone who has never touched your radios should be able to read the card and start talking.
- A deployment log or sign-out sheet. Paper or digital, the record of which numbered radio went to which person. This is your accountability backbone and your recovery tool.
- Documentation. The programming file version, the last test date, the battery rotation record, and contact information for whoever maintains the cache. Keep a copy in the case and a copy off-site.
- A rugged container. A hard case with foam cutouts protects the radios, keeps the accessories together, and makes it obvious at a glance whether anything is missing.
Do not guess at a round number. Pick the two or three incident types most likely to overwhelm you and count the radios each would demand. A multi-company structure fire, a large search, and a shelter activation will each give you a real figure. Build the cache to cover the largest of those, and you have a defensible size instead of an arbitrary one.
Programming for immediate use
The whole value of a cache collapses if an arriving crew has to figure out the radios. The programming goal is that a person who has never held one of your units can pick it up, turn the knob to a known position, and be understood. That takes discipline in how you build the code plug.
Keep the channel layout simple and consistent across every radio in the cache. The most-used channels belong in the lowest, easiest positions. If your quick-start card says channel one is dispatch and channel two is fireground, every radio in the case must match that card exactly. Mixed layouts across a cache are a guaranteed source of confusion at the worst time.
Program the shared interoperability channels your region has agreed to use, and program them with the same names and in the same positions that neighboring agencies use, so a mutual aid crew recognizes them. This is where a regional channel-naming convention earns its keep. If everyone within reach of your borders uses the same names for the common channels, a borrowed radio feels familiar instead of foreign.
Consider whether some cache radios should be locked down more than others. A radio handed to an untrained support volunteer might be limited to a single monitoring channel so they cannot accidentally transmit on a tactical channel. A radio handed to a company officer needs the full tactical set. You can build both configurations and label them clearly so the right one goes to the right person.
Finally, keep the master programming file under version control and write the version onto the documentation card. When a channel changes region-wide, you need to know at a glance which radios are current and which are not.
A radio that lights up is not a radio that works. Programming errors, weak batteries, and antenna problems only show up when you key up and confirm someone hears you on the right channel. Build a real radio check into every maintenance cycle, not just a battery check.
Keeping the cache maintained
A cache is a promise you make to your future self, and an unmaintained cache breaks that promise quietly. The radios sit in a case looking fine while the batteries lose charge, the programming drifts out of date, and a unit or two walks off without anyone noticing. Maintenance is what keeps the promise honest, and it is boring work that has to happen on a schedule.
- Battery rotation. Rechargeable batteries lose capacity if they sit fully drained or endlessly topped off. Set a rotation cycle so batteries are exercised and their condition checked. Replace any battery that no longer holds a usable charge, and record when each battery entered service so you can retire them on age.
- Programming updates. When your channel plan or a regional interoperability channel changes, every radio in the cache has to be reprogrammed and the documentation version updated. A cache full of last year's channels is a trap.
- Inventory. Count the radios, batteries, chargers, mics, and cards on a regular cycle and after every deployment. The case with foam cutouts helps here because a gap is visible. Log the count so you can prove the cache is complete.
- Testing. On each cycle, power up every radio, confirm the battery, and do a real transmit-and-receive check on the primary channels. Note any failures and pull those units for repair.
Assign the maintenance to a specific person or role, not to the department in general. A cache that is everyone's job is nobody's job. Put the schedule somewhere it will be seen, tie it to a recurring reminder, and keep the records where a chief or an auditor can find them.
Deployment and accountability
The moment the cache opens is the moment accountability starts. Radios are valuable, they are easy to pocket, and in the chaos of a large incident they scatter. Without a system, you will end an incident short several units and with no idea where they went. The fix is a simple, disciplined issue-and-recover process that runs every single time, even when it feels like there is no time for it.
Issue each radio by its unique number and write down who received it. A person's name, unit, or role next to the radio number is enough. This can be a clipboard at the cache, a form on a tablet, or a spot on the incident's accountability board, but it has to be captured as the radio goes out, not reconstructed later from memory.
During the incident, the deployment log tells the communications leader who is reachable and on what channel. If someone is not answering, the log shows which numbered radio they are carrying so you can troubleshoot the right unit. It also feeds accountability in the larger sense: a radio that is signed out to a person is one more confirmation of where that person is assigned.
Recovery is the half that gets skipped, and skipping it is expensive. As crews demobilize, collect radios against the same log, check each number off, and inspect the unit as it comes back. A radio returned with a dead battery or a cracked antenna needs to be flagged for service before it goes back in the case, or your next deployment inherits a broken unit. Reconcile the log before you close the case. Any radio still signed out is a radio to chase down while the trail is warm.
Departments rarely lose cache radios to theft. They lose them to a crew that drove home with a borrowed handheld still clipped to a turnout coat. A firm rule that no unit leaves the scene until it checks in its radio, and a demob point where that check happens, prevents most of the loss with no technology at all.
Regional and shared caches
Not every department can afford a large cache alone, and not every incident needs one every week. That is the case for building caches at a regional level or sharing them across neighboring agencies. Instead of five departments each buying a handful of radios that mostly sit idle, a region can pool resources into a larger, better-maintained cache that any member can request.
Sharing raises questions that have to be settled before an incident, in writing. Who owns the cache and who maintains it. How a member agency requests it and how fast it can arrive. Who programs it and to whose channel plan. How radios are tracked when they cross agency lines, and who is responsible if a unit is damaged or lost. These belong in a mutual aid agreement or a communications annex alongside your existing automatic and mutual aid arrangements, so that requesting the cache is a known procedure and not a favor negotiated over the phone at two in the morning.
A shared cache also strengthens the case for common channel naming. If the regional cache is programmed to the interoperability channels every member uses, then a borrowed radio behaves the same no matter which department is holding the incident. That consistency is much of the point. The cache is not only extra radios; it is a set of radios that everyone in the region already knows how to use.
Larger caches may live at a central location, a shared facility, or with the agency best positioned to store and maintain them. The storage choice matters less than two things: that the cache is maintained to the same standard a single department would apply, and that every member agency knows exactly how to get it moving.
A starter plan for a small department
A small department does not need a warehouse of radios to start. It needs a modest, honest cache it can actually keep ready. Begin with the scenario that scares you most and size to that, then grow as budgets allow.
- Start with a handful of radios. Even a small reserve, enough to equip one mutual aid company or a cluster of support personnel, changes what you can do on a bad day. A cache that exists and works beats a large one you keep meaning to build.
- Program them to a simple, documented plan. Dispatch, fireground or tactical, and the regional interoperability channels, in fixed positions, with a laminated quick-start card in the case.
- Buy the batteries and charging first, then the extras. A radio with a charged spare is worth more than two radios sharing one dying battery. Get the power situation right before you expand the radio count.
- Assign one owner. Name the person responsible for battery rotation, programming, inventory, and testing, and put the schedule on a recurring reminder.
- Use a sign-out sheet from day one. Even three radios can vanish. Start the accountability habit while the cache is small and it will scale with you.
- Talk to your neighbors. Before you outgrow a small cache, raise the idea of a shared or regional one. You may find partners who have been thinking the same thing.
The goal is not perfection on the first pass. It is a cache that is real, ready, and trusted, so that the first time you open it under pressure, it does exactly what you built it to do.
The radio cache checklist
Use this as a build-and-maintain checklist. Work through it once to stand the cache up, then return to the maintenance items on a schedule.
- Cache size chosen from a real worst-case scenario, not a round number
- Radios uniquely numbered and labeled
- Every radio programmed to the same channel layout, with dispatch and tactical in fixed low positions
- Regional interoperability channels programmed with common names and positions
- One spare battery per radio, minimum
- Charging capacity for the full cache plus a long incident
- Speaker mic per radio where possible
- Laminated quick-start channel card in the case
- Sign-out log or accountability sheet in the case
- Documentation: programming version, last test date, maintainer contact, off-site copy
- Rugged case with foam cutouts so gaps are visible
- Named owner responsible for maintenance
- Battery rotation cycle scheduled and logged
- Programming update process tied to channel-plan changes
- Inventory count on a schedule and after every deployment
- Transmit-and-receive test on every cycle, not just power-on
- Issue-and-recover process practiced, with reconciliation before the case closes
- Shared or regional agreement in writing if the cache is pooled
A radio cache only works if you know what is in it, whether it has been tested, and who is carrying each unit right now. RunBoard keeps your equipment and inventory records organized so battery rotations, programming versions, and sign-out logs live in one place instead of on a clipboard nobody can find. When the incident is bigger than your radio count, the last thing you should be doing is guessing at what you have.