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.
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:
- Surge events. A large incident can put more people on the ground than your agency owns radios for. Mutual aid companies, a rehab group, extra command staff, and support personnel all need to hear traffic and be heard.
- Mutual aid interoperability. A neighboring department may run on a different system, a different band, or a different set of talkgroups. Handing an incoming crew a radio that is already programmed for your system is often faster and more reliable than trying to patch two systems together on the fly.
- Covering a failed system. Infrastructure fails. A tower goes down, a repeater loses power, a controller has a fault, or a fire station's fixed equipment is damaged. Borrowed portables or a loaned repeater can keep an agency talking while the primary system is repaired.
- Disasters and long-duration events. Extended operations exhaust batteries, chargers, and spares. A regional cache can backfill worn-out or lost gear over a multi-day event.
- Equipping crews who otherwise cannot talk to you. The worst version of a mutual aid response is a crew operating on your scene with no way to reach command. A shared or cached radio turns that crew from a liability back into a resource.
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:
- Radios pre-programmed with common interoperability channels so any responder can be handed one and reach a shared talk path.
- Fresh, charged, and rotated batteries. Batteries age whether they are used or not, so a cache needs a maintenance cycle, not just a shelf.
- Documented contents and a deployment procedure so the cache can be requested, released, transported, and accounted for under stress.
- A designated custodian who knows what is in it, keeps it current, and controls who may draw from it.
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.
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:
- Operating on a frequency or system requires authorization from whoever holds the license and controls access. Loaning a radio does not automatically grant the borrower the right to transmit on channels they are not authorized to use.
- Interoperability and mutual aid channels usually exist precisely so that outside agencies can be authorized to use them, often under defined sharing agreements or regional plans. That is different from putting an outside crew directly onto your agency's day-to-day talkgroups.
- Encryption adds another layer. If your system uses encryption, a borrowed radio needs the correct keys loaded, and key management is tightly controlled for good reason. Sharing keys is a policy decision, not a field decision.
- Who is allowed to program a radio should be spelled out. A borrowing agency should not reprogram a loaned radio without permission, because doing so can wipe the owner's configuration and create licensing problems.
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.
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:
- Ownership. Who owns the equipment, and does loaning it change that in any way? (It should not, and the agreement should say so.)
- Maintenance responsibility. Who keeps the gear serviceable, who pays for batteries and repairs, and who is responsible for keeping the programming current.
- Liability for loss or damage. If a borrowed radio is lost, stolen, or destroyed, who bears the cost, and how is that determined. Spell out normal wear versus negligence if you can.
- Return conditions. When is the gear returned, in what condition, to whom, and how is the return documented so both sides agree the loan is closed.
- Programming authority. Who may reprogram the radio, and the borrower's obligation not to alter configuration without permission.
- Authorized use. What channels and talkgroups the borrower is permitted to use, tied back to the licensing and authorization layer above.
- Activation and cost. How a loan or cache deployment is requested and approved, and how any costs are handled, which matters for disaster reimbursement.
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:
- Unique identifiers. Every radio needs a serial number and, ideally, a visible asset tag or unit number so it can be checked out and back in by a specific ID.
- A check-out record. Capture who received each radio, from what agency, when, and for what assignment. On a large incident, tie the radio to a person or a resource, not just to an agency.
- A running inventory. The custodian should be able to say at any moment how many radios are out, who has them, and how many remain. This is also what tells you when the cache is running low mid-event.
- A check-in record. Closing the loop is where most systems fail. The return has to be documented as deliberately as the issue, with condition noted, so a missing radio is caught immediately instead of at the next inventory.
- Accessory accountability. Batteries, chargers, spare antennas, and remote speaker microphones are easy to lose and expensive to replace. Track them too.
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:
- Power and battery. Confirm the radio powers up on a battery with real charge, not a battery that reads full but dies in an hour. Verify you have chargers and spare batteries that fit.
- Correct programming. Confirm the radio is on the channels and talkgroups you expect, with the right labels, so a crew member is not hunting for the right zone under stress.
- A live radio check. Key up and confirm two-way communication with the actual system and dispatch you intend to use, not just radio-to-radio in the parking lot. On trunked systems, confirm the radio actually affiliates and is authorized.
- Coverage where it matters. If the operation will be inside a large structure, below grade, or in a known dead zone, test there if you can. Coverage that is fine outside can vanish inside.
- Accessories. Test the speaker microphone or earpiece the crew will actually use, since a fault there can silence an otherwise working radio.
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:
- Cover the basics fast. Power, volume, channel or zone selection, push to talk, and how to send an emergency activation if the radio has one. Those five things cover most of what a crew needs in the first hour.
- Standardize where you can. If a region shares gear, agreeing on common programming layouts and consistent channel naming across a cache reduces the learning curve dramatically. A responder who has trained on the cache once can pick up any unit in it.
- Practice in advance. The neighboring agencies that plan and drill sharing before an event are the ones who benefit from it during an event. Fold cache radios and loaned gear into joint training and exercises so the first time a crew uses one is not on a real incident.
- Provide a quick reference. A simple laminated card in the cache showing the controls and the key channels helps a stressed, unfamiliar user far more than a full manual.
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
- Plan sharing before you need it. Programming, licensing, agreements, and training all have to be done in advance. You cannot build interoperability during the incident.
- Treat a cache as an ongoing commitment. Assign a custodian and keep radios, batteries, and programming current, or the cache will fail the day it is opened.
- Respect the licensing and authorization layer. A radio transmitting does not mean the use is authorized. Verify channel and system access with your radio administrator and licensing authority, and control who may program shared gear.
- Put it in writing. Ownership, maintenance, liability for loss or damage, return conditions, programming authority, and authorized use all belong in a signed agreement.
- Track every unit and accessory. Check gear out and back in by serial number so borrowed radios do not vanish and loans close cleanly.
- Test before you rely. A live radio check, correct programming, and a real battery, every time, before the gear reaches an assignment.
- Train for unfamiliar hardware. Cover the five basics, standardize programming across a cache, and drill sharing with neighbors so it is routine when it counts.
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.