Trunked Radio System Channel Assignment and Scanners

A trunked radio system is a two-way radio network in which many users share a pool of radio channels, while a controller assigns an available channel only when a group needs to talk. The group does not keep that frequency between calls; when the call ends, the channel goes back into the pool for another group. This guide explains the parts of a trunked system, how the channel assignment process works, and how listeners can recognize and follow one with a compatible scanner.

What a Trunked Radio System Is

“Trunking” is a way to use radio channels efficiently when many teams need short, occasional conversations. Instead of giving every department, work crew, or public-safety group a permanently assigned frequency, the system lets them share a smaller number of channels.

A trunked system has several parts:

Frequency: A specific radio frequency in the spectrum.
Channel: A radio path the system can assign for a conversation. In simple systems, this often corresponds to one frequency.
Talkgroup: A logical group of radios, such as security, maintenance, dispatch, or event operations.
Traffic channel: The channel currently carrying a voice or data call.
Control channel: A channel that carries system-management data on many trunked systems. It tells radios where to go for a call.
Site: A tower location and its associated radio equipment. Large networks can have several sites.

A talkgroup is not the same thing as a frequency. A maintenance team might use one frequency for its first call, another frequency for its next call, and still remain in the same maintenance talkgroup.

That is the central idea: users stay associated with their talkgroup, while the system handles the changing radio channel in the background.

How Radio Trunking Works

A conventional radio user usually selects a fixed channel assigned to a team. In a trunked system, the user selects a talkgroup and presses the push-to-talk button. The network then decides which available channel will carry that call.

A Call From Push-to-Talk to Release

A typical trunked call follows this pattern:

A radio user selects a talkgroup and presses push-to-talk.
The radio sends a request to the system, often through control signaling.
The controller finds an idle traffic channel.
The controller directs the radios in that talkgroup to the assigned channel.
The users talk while that channel is assigned to their call.
When the call ends, the channel is released and becomes available for another group.

The next call for the same talkgroup can use a different frequency. That temporary assignment is what separates trunking from a fixed-channel arrangement.

Many Groups Can Talk at Once

Sharing a channel pool does not mean every user hears or uses one conversation at a time. If several traffic channels are idle, separate talkgroups can receive separate assignments and hold conversations simultaneously.

For example, a stadium may have security, parking, medical, maintenance, and operations teams. Security can speak on one assigned traffic channel while maintenance uses another. The groups remain separated by talkgroup even though they draw from the same pool of frequencies.

When every traffic channel is busy, a new call may be delayed or denied, depending on the system’s design and priorities. That is why system planners still need enough capacity for periods when many groups need to talk at once.

How to Set Up a Scanner to Follow a Trunked System

A trunk-tracking scanner needs the correct system type and site information. Simply entering one active frequency may let you hear a fragment of traffic, but it will not reliably follow conversations when the system moves them to another channel.

Use this quick choice guide before programming anything.

Your Goal	Information You Need	Best Starting Point
Follow a known trunked system	System type, active site, channel list, and talkgroups	Use a scanner that supports that system family
Identify unfamiliar radio activity	Frequency, location, repeated data behavior, and any known system record	Confirm the system type before choosing a scanner mode
Use a two-way radio on the system	Administrator-provided programming and authorization	Follow the system operator’s instructions before transmitting.

Step 1: Gather the System Details

Find a reliable system listing from the operator, a documented radio database, or another authoritative local source.
Record the system family, the site you can receive, all listed frequencies for that site, and the talkgroups you want to hear.
Note whether the system uses digital voice or encryption.

A trunk-tracking scanner follows the system’s assignments. A basic receiver may tune one frequency but can miss replies when a conversation changes channels, and it may produce only digital noise on systems that use digital voice.

Step 2: Match the System Family and Site Capacity

Identify the radio system family before selecting a scanner programming mode.
Treat a frequency band as a clue, not proof of the system type.
Use the radio network’s own specifications to confirm its exact configuration.

EDACS systems commonly use groups of frequencies in the 800 or 900 MHz bands and can have up to 25 frequencies per tower site. Motorola trunked systems commonly use 400, 800, or 900 MHz frequency groups and can have up to 28 frequencies per tower site.

Those limits help when estimating a site’s potential channel capacity, but they do not tell you which site you are hearing. Nearby sites can use different channel lists, talkgroups, and coverage areas.

Step 3: Recognize LTR Activity Correctly

Select LTR mode only after confirming that the system is an LTR system.
Enter the complete site channel list rather than looking for one separate control frequency.
Check the received frequencies for activity.

LTR is a trunked system type. A data burst can be heard on each LTR system frequency around every 10 to 20 seconds, which helps distinguish LTR activity from a system with one continuously active control channel.

An LTR system can use a maximum of 20 channels, meaning 20 frequencies. If a supposed LTR site appears to exceed that limit, verify the system classification and make sure you have not combined frequencies from multiple sites.

Step 4: Program, Test, and Save the Working Setup

Create a new system entry in the scanner and choose the confirmed trunked system type.
Add the complete frequency list for one receivable site using the programming method required by the confirmed system type.
Add the talkgroups you want to monitor, if the scanner supports talkgroup selection.
Monitor during a period when the system is known to be active.
Confirm that the scanner follows both sides of a conversation even when the system moves the call to a different traffic channel.
Save the working configuration as a separate site or system profile.

If you hear control data but no voice calls, check that you selected the correct system family, site, and talkgroups.

Trunked Radio vs. Conventional Radio

Trunking trades fixed channel ownership for automatic, temporary access to a shared pool.

A conventional system can be simpler: one group uses one assigned channel, and users manually choose that channel. That works well when only a few groups need radio service or when each group talks heavily enough to justify a dedicated frequency.

Feature	Conventional Radio System	Trunked Radio System
Channel selection	User selects a fixed assigned channel	Controller assigns an available channel
Group identity	Usually tied closely to a channel	Defined by a talkgroup
Channel use	One group may reserve a channel even when idle	Idle channels can serve another group
Best fit	Small, simple operations	Many groups with changing call demand
Management needs	Basic channel planning	Controller, programming, site, and talkgroup management

Trunking can serve many users with fewer channels because not every team needs to talk at the same moment. It can also support features such as group calling, radio identification, priority handling, and disabling a lost radio, depending on the system.

Better channel efficiency does not automatically mean a cheaper deployment. A trunked network may require controllers, compatible radios, site equipment, programming, coverage planning, maintenance, and backup capacity. An organization should compare the total system cost and complexity, not just the number of frequencies.

Common Trunked System Types and Special Cases

Several system families use trunking, and a scanner must support the one you are trying to follow.

Motorola and EDACS Systems

Motorola and EDACS are established trunked-system families commonly found in older commercial, public-safety, and shared radio networks. Many systems in these families use a control channel that sends instructions to subscriber radios.

A scanner must be configured for the correct family. The radio must interpret the system’s signaling properly.

LTR Systems

LTR, short for Logic Trunked Radio, handles signaling differently from other trunked-system families. Its regular data bursts appear on the individual system frequencies.

Use the proper programming method for the system you are monitoring.

Multi-Site Networks

A large trunked system may have multiple tower sites. Each site can have its own frequency set, and the talkgroups you hear can vary with location, radio traffic, and system design.

Program the site you can actually receive. Mixing channels from nearby but separate sites can prevent a scanner from following calls correctly.

Digital Voice and Encryption

Trunking and digital voice are separate concepts. Trunking decides how a channel is assigned; digital voice determines how audio is encoded.

Encryption is separate from both. A trunked system can have unencrypted talkgroups, encrypted talkgroups, or a mix of both. A scanner cannot monitor encrypted talkgroups, and trunking by itself does not make every conversation private.

How to Confirm You Are Following the System Correctly

Use this checklist after programming a scanner or evaluating a system:

The scanner identifies the correct system family and site.
It follows a complete conversation, including replies.
It moves between traffic channels without losing the talkgroup.
Talkgroup labels or IDs match the activity you hear.
You do not assume every signal in the same frequency band belongs to one system.
You keep nearby sites separate unless documentation confirms they belong together.
You recognize that encryption, incompatible digital voice, weak reception, and an incorrect system type can all prevent intelligible monitoring.

A correctly configured scanner should make trunking feel almost invisible: you choose a talkgroup or scan list, and the receiver follows the system’s temporary channel assignments for you.

Next, enter one confirmed site into a compatible scanner and test it during known radio activity.

Frequently Asked Questions

How does radio trunking work?

Radio trunking works by assigning an available channel from a shared pool when a user starts a call, then returning that channel to the pool after the call ends. Users select talkgroups rather than fixed frequencies, so the same talkgroup can use different traffic channels for different calls. Multiple talkgroups can communicate at the same time if enough channels are available.

Can any scanner follow a trunked radio system?

No. The scanner must support the system’s trunking family and, where applicable, its digital voice format. A conventional scanner can scan individual frequencies, but a trunk-tracking model is needed to follow channel changes automatically. Follow applicable rules when operating or transmitting with radio equipment.

Does trunking make radio conversations private?

No. Trunking organizes and assigns calls; it does not automatically encrypt them. A trunked system may make casual listening less straightforward because calls move between frequencies, but compatible scanners can follow unencrypted systems. Encrypted talkgroups remain unavailable to scanners.

How many channels can an LTR system use?

An LTR system can use a maximum of 20 channels, or 20 frequencies. It does not rely on one separate dedicated control channel, and its data bursts can appear across the system frequencies. Confirm the frequency list before programming the system.

What should I collect before programming a trunked system?

Collect the system type, the specific site you can receive, the complete site frequency list, and the talkgroups you want to monitor. The essential operating model is that a completed call releases its assigned channel for another group.