Planning the Changeover Before a Radio System Upgrade
In addition to reaching dispatch and for the dispatcher to reach field personnel, there will always be a need for communication during a radio system upgrade. Therefore, the integration of personnel needs to be considered along with the coordination of the equipment installation, changes to the RF site and radio programming.
The changeover, often called the cutover, is the planned move from the existing arrangement to the new one. The July 2025 Emergency Communications System Lifecycle Planning Guide, published by CISA with SAFECOM and NCSWIC, recommends planning that transition for both moderate upgrades and larger replacements. Its considerations include downtime, backup communications, training, and interoperability. Those decisions belong in the project schedule before equipment is disconnected.
Review the Equipment That Will Remain in Service
An upgrade does not necessarily mean replacing every component at the site. The project team should identify which antennas, feedlines, filters, duplexers, and combiners will remain, which will be changed, and which will be used temporarily. Existing equipment should be evaluated against the proposed configuration rather than accepted solely because it currently works.
For example, a change in transmit frequencies should prompt a review of the combiner and filtering arrangements. TX RX Systems describes diagnostic testing and equipment tuning as part of its field services, including checks of signal loss, isolation, and transmitter interactions. That work can help determine whether existing hardware is suitable, needs adjustment, or should be replaced. Retuning is not appropriate for every component or frequency change.
Put the Sequence of Work in Writing
The crew requires more than just a date for the installation. A logical change-over plan should outline the sequence of work, which services will continue to operate at various stages, and who will authorize continuation or cessation. The dispatch personnel, system manager, integrator, and field team must be working from the same version of documents.
A useful example appears in Northampton, Massachusetts’s 2020 P25 procurement. Its cutover requirements addressed dispatch transitions, scheduled downtime, operation of old and new systems, personnel schedules, training, and fallback arrangements. Those were requirements for that project, not a universal schedule. They illustrate the operational detail that needs attention alongside the equipment installation.
Check That the Backup Will Still Be Available
A backup arrangement needs to remain usable during the actual work. As a practical example, a spare radio may not provide an independent fallback if it relies on the same repeater being taken out of service. Similarly, a broadband alternative needs its own coverage, access, and communications requirements confirmed before staff are told to use it.
CISA and NCSWIC guidance on PACE planning emphasizes checking the dependencies of alternate communications methods and practicing their use. Applied to an upgrade, this means identifying the method personnel will use during an interruption, who announces the switch, and how users return to normal operation.
Returning to the previous configuration is a separate decision. Before the work begins, the team should identify the steps needed to restore it and the point beyond which an immediate return is no longer practical. Temporary communications and restoration of the old arrangement should not be treated as the same task.
Verify Performance Before Moving to the Next Stage
Testing should answer specific questions about the installation. The agreed scope may include transmitter output, receiver performance, signal levels, and unwanted RF activity. TX RX offers RF testing that includes receiver testing, output power assessments, spectrum analysis, and advanced spectrum logging. The project team can use the relevant measurements to evaluate equipment rather than relying only on status indicators.
One helpful approach is to document the existing configuration along with relevant measurements before modifying equipment; and then perform the same applicable tests afterwards. Any difference from expected values should be investigated prior to proceeding to the next phase as the cause could become difficult to identify once additional modifications are made. Coverage verification also requires development of its own documented procedure; merely successfully completing a radio call near the equipment room does not verify satisfactory coverage over the entire service area.
Prepare the People Who Will Use the Changed System
The CISA lifecycle guide includes training users and technicians as part of implementation. For a local project, that should translate into practical instructions covering channel or talkgroup changes, temporary communications arrangements, and the process for reporting a problem. Staff joining the next shift need the same information as those present during the work.
Where the project connects LMR with broadband services or another agency’s system, those connections should be included in the approved operational checks. The relevant dispatchers and radio users need to confirm the intended communications, rather than assuming that a working component proves the complete connection is ready.
Bring RF Support Into the Plan Before the Switch
TX RX Systems provides network assessments, interference investigations, signal level mapping, and RF technical training. Its field services also include equipment tuning and site evaluation. These capabilities give integrators and system managers support for the RF work surrounding an upgrade, from assessing retained equipment to investigating an unexpected result during commissioning.
When upgrading a system includes connecting LMR to broadband services or a neighboring agency’s system, those interfaces should be part of established operational checks. Instead of presuming a functioning component verifies that all connections are ready for intended communication, participating dispatchers/radio operators must confirm intended communication.
Finish With Accepted Results and Usable Records
The CISA lifecycle guide distinguishes moving into operation from final acceptance, which depends on addressing deficiencies and meeting the agreed requirements. Installation completion alone should not close out unresolved performance issues.