Borrowing, Sharing, and Caching Radio Equipment Between Agencies

When a system fails or a surge event pulls in crews from three counties, the radio in someone's hand is only useful if it can talk on your channels and someone knows where it came from. Sharing radio gear between agencies is a proven way to close that gap, but it works only when the programming, licensing, agreements, and tracking are settled long before the tones drop. This guide covers the practical and policy side of lending, pooling, and pre-positioning portable radios.

In this guide
  1. Why radio sharing matters
  2. Cache radios and regional interoperability caches
  3. Programming, licensing, and authorization
  4. The written agreement is the whole game
  5. Tracking and inventory so gear does not vanish
  6. Testing borrowed equipment before you rely on it
  7. Training crews on unfamiliar radios
  8. Takeaways

Why radio sharing matters

Communications is the one function that touches every other function on a scene. When it breaks, or when it cannot reach the people who just arrived to help, nothing else works the way it should. Sharing radio equipment between agencies exists to solve a handful of predictable, recurring problems:

The common thread is that the need is sudden and the preparation is not optional. You cannot program, authorize, and train your way into interoperability during the incident. The work happens in advance, in quiet periods, with agreements signed and gear tested.

Cache radios and regional interoperability caches

A radio cache is a stockpile of portable radios (and usually batteries, chargers, spare antennas, and sometimes a deployable repeater) held ready to loan out. Caches are maintained at different levels. Some agencies keep a small internal cache of spares. Many regions maintain a shared interoperability cache managed by a county, a council of governments, a regional communications authority, or a state emergency management office. The specific ownership and management model varies widely, so confirm how your region's cache is organized rather than assuming.

A well-run cache is more than a box of radios. It typically includes:

The value of a cache is that it is a known, tested quantity. Everyone who might use it can plan around a consistent set of channels and a consistent piece of hardware. That predictability is worth as much as the radios themselves.

A cache is a maintenance commitment, not a purchase

The failure mode for caches is neglect. Radios sit for months, batteries die, programming drifts out of date as the system changes, and no one notices until the cache is opened during an emergency and half of it does not work. Assign a custodian, put the cache on a recurring inspection and battery-rotation schedule, and reprogram it whenever the underlying system changes.

Programming, licensing, and authorization

A borrowed radio is not plug-and-play. To work on your system it has to be programmed with the correct channels, talkgroups, encryption keys (if any), and system parameters. On trunked systems the radio may also need to be recognized by the system, which can involve an identifier that the system administrator has to enroll or authorize. This is technical work performed by qualified personnel using the right software and cables, and it is not something a crew does at the tailboard.

Programming sits on top of a licensing and authorization layer that you do not get to improvise. Radio spectrum is regulated, and the authority to operate on a given channel or system rests with a license holder and, on shared systems, with a governing body that controls access. A few principles that hold generally:

Because the rules around licensing, system access, and authorization differ from region to region and system to system, treat the specifics as something to verify with your radio administrator and your licensing authority. Do not assume that because a radio physically transmits, using it on a given channel is authorized.

Program for the mission, not just the moment

Decide in advance what a shared radio should be programmed for. Loading an incoming crew onto a shared interoperability talkgroup is usually the right answer, and it keeps your internal channels clean while still giving command a common talk path. Sorting this out in advance, with your radio administrator, means the cache is already correct when it is opened.

The written agreement is the whole game

Every discussion about sharing radios eventually comes back to one question: what did we agree to, in writing, before this happened? A handshake works fine until a radio is lost in a swiftwater rescue, dropped off a roof, or simply never comes back. A written agreement, often a mutual aid agreement or a specific memorandum of understanding, should answer the predictable questions before anyone is under pressure. At minimum, address:

None of this is exotic. It is the same set of questions any organization asks when it lends valuable equipment to another organization. Radios simply add the wrinkles of licensing and programming, which is why the agreement should reference those explicitly.

Tracking and inventory so gear does not vanish

Loaned equipment disappears in the fog of a large incident. Radios get handed to a crew, the crew rotates out, the radio goes home in a pocket, and three weeks later no one can say where it is. Prevent that with disciplined tracking that starts the moment a radio leaves the custodian's hands:

Good tracking is not bureaucracy for its own sake. It is what lets you recover expensive gear, close out an agreement cleanly, and honestly answer for public property when the after-action review asks where everything went.

Testing borrowed equipment before you rely on it

The moment to discover that a borrowed radio does not work is not when a crew is inside a structure calling a Mayday. Test before you rely, every time:

Untested gear is a false sense of security

A radio that a crew believes works but does not is more dangerous than no radio at all, because the crew plans around communication they do not actually have. Build a quick radio check into the issue process so no borrowed unit reaches an assignment without a confirmed live check.

Training crews on unfamiliar radios

A radio a firefighter has never held is a hazard under stress. Models differ in how you change channels, adjust volume, transmit, send an emergency alert, and read the display. When you loan gear to another agency, or borrow it, assume the user is unfamiliar and close that gap:

This is where planning ahead pays off most visibly. When neighboring agencies have agreed on shared channels, standardized cache programming, signed the agreements, and trained together, interoperability stops being a scramble and becomes a routine. A crew arrives, gets handed a radio they recognize, keys up on a talkgroup they know, and is immediately part of the operation. That is the entire payoff, and it is only available to agencies that did the work before the incident.

Takeaways

Keep your equipment, agreements, and records in one place

Sharing radios well comes down to organization: knowing what you own, who has it, what condition it is in, which agreements govern it, and when it is due back. RunBoard helps departments keep equipment inventory, mutual aid agreements, and check-out and return records organized in one place, so when a surge event or a system failure hits, the custodian can answer where every radio is and what the agreement says without digging through a filing cabinet. The gear still has to be programmed and tested by qualified people, but the accountability around it does not have to live in someone's memory.