Trunked vs conventional two-way radio — choosing the right system for large facilities.

Trunked and conventional two-way radio are different channel-sharing architectures. The distinction matters when sizing a radio system for a large facility: a conventional system gets expensive fast because each independent group of users needs its own dedicated channel pair, while a trunked system allows multiple user groups to share a pool of channels dynamically. For a single building with a handful of user groups, that efficiency gain often doesn’t justify the infrastructure cost of trunked equipment. For a large campus, a multi-building complex, or a facility with high radio traffic, it does — and the operational difference becomes significant during peak periods when channel demand is highest.

How conventional radio systems work

A conventional radio system assigns each user group a dedicated channel. Security operations on Channel 1. Maintenance on Channel 2. Facilities management on Channel 3. When security wants to transmit, they key up on Channel 1. All security radios receive the transmission; no one else does. The channel capacity is fixed: if two security supervisors try to transmit simultaneously, one blocks the other and the blocked transmission is lost or has to wait for the channel to clear.

The simplicity of conventional systems is their primary advantage. Each radio knows exactly which channel its group uses. There is no infrastructure controller that must be healthy for the radio system to function — a repeater failure on Channel 1 affects only the group assigned to that channel, not the entire system. A conventional two-way radio system can function in simplex (radio-to-radio direct) mode with no infrastructure at all. For most commercial facilities with fewer than five or six user groups and moderate radio traffic, a conventional system is the correct choice. Adding channel capacity is as simple as adding a repeater and assigning a new frequency pair.

How trunked radio systems work

A trunked radio system uses a controller — hardware or software — to dynamically assign channels from a shared pool to user groups as needed. When security transmits, the controller allocates an available channel, connects all security radios to that channel for the duration of the call, and releases the channel back to the pool when the transmission ends. If two security supervisors transmit simultaneously, the controller queues one and connects the other — both transmissions complete, sequentially, without blocking each other permanently.

The efficiency gain of trunking comes from the statistical reality that not all user groups are transmitting simultaneously. A conventional system with 10 user groups needs 10 dedicated channels. A trunked system supporting the same 10 groups may function on 5 channels, because at any given moment only 2–3 groups are actually transmitting. The trunking efficiency ratio — supported user groups to required channels — improves as user group count grows and average channel occupancy remains well below 100%.

Channel efficiency — when trunking actually matters

The efficiency calculation has a practical ceiling: a trunked system needs enough channels to handle peak traffic, not just average traffic. If the system is consistently near 100% channel occupancy during peak periods, adding user groups doesn’t increase efficiency — it creates a queue where transmissions are delayed at the worst possible times. The right trunking design includes a traffic analysis that estimates peak channel demand, not average demand.

Infrastructure cost — where trunking gets expensive for single buildings

A trunked radio system requires a system controller that manages channel allocation in addition to the repeater infrastructure that a conventional system also requires. The controller adds cost, complexity, and a single point of failure that a conventional system doesn’t have. A trunked controller failure takes all user groups off the air simultaneously; a conventional repeater failure takes one group off the air. Most enterprise trunked systems address this with redundant controllers, which adds another hardware cost.

For a single building with 3–6 user groups and moderate traffic, the incremental cost of trunked infrastructure over conventional — typically $15,000–$50,000 for the controller hardware and programming — is rarely justified by the channel efficiency gain. The cases where trunking makes sense in a single-building deployment: facilities with consistently high radio traffic during peak operations (casinos, large hospitals, major event venues); facilities with 10+ user groups where the conventional channel count would require dedicated frequencies for each group; and facilities that connect to a campus-wide or jurisdiction-wide trunked system and need compatibility with the existing infrastructure.

When conventional is still the right answer

For the majority of commercial facilities — office buildings, mid-size retail, light industrial, multi-tenant commercial — a conventional system with 2–4 channels is the correct and cost-effective specification. The simplicity of maintenance, the lower infrastructure cost, the tolerance for single repeater failures, and the straightforward training for end users all favor conventional when trunking’s efficiency gain is marginal.

The question to answer before specifying trunked infrastructure is: what is the actual peak channel occupancy under a conventional configuration? If conventional channels are regularly blocked — users waiting for channel access during shift changes or emergency events — trunking solves a real problem. If the conventional channels would be idle 80% of the time with peak occupancy under 30%, trunking solves a problem that doesn’t exist at the cost of significant infrastructure complexity.

The public-safety radio dimension

ERCES systems in commercial buildings provide first responders with in-building radio coverage on the public safety frequencies — which may themselves be a trunked P25 system operated by the local jurisdiction. The BDA that provides that coverage operates on public safety frequencies, not the building’s own commercial radio system. The two systems coexist but serve different users and different frequency bands. The ERCES primer covers how in-building public safety radio coverage is mandated separately from the building’s commercial radio infrastructure. Our ERCES services handle the public safety radio coverage side of commercial buildings nationwide; the commercial two-way radio system serving building operations is a separate scope requiring its own channel planning, frequency licensing, and system design. The low-voltage contractor selection post covers the licensing and experience criteria that separate a radio contractor who has designed one system from one who can match the right architecture to the building’s actual traffic profile and user group structure.