How to plan radio channels and calls for an event team

Your door supervisor is asking for help, production is talking through a delivery, and somebody has left their radio transmitting inside a pocket. Everyone has a handset. The person who needs an answer still can't get one.

An event radio communication plan should decide who talks to whom, which channels they use, how urgent messages interrupt routine traffic, and what happens when a radio or the whole system fails. Start with the decisions your team needs to make during the event, then ask your radio supplier to configure and test a system that supports them.

The useful result is a short operating sheet your team can follow under pressure, backed by a technical plan the appropriate supplier or venue specialist owns. You don't need your stewards learning frequency programming at the briefing. You do need them to know who answers when they call.

This guide works through channel assignments, call signs, everyday calls, urgent traffic and a practical rehearsal. The examples describe an imaginary paid music event. Adapt the arrangements with your venue, suppliers and safety leads before using them at your own event.

Start with the conversations the event needs

The first thing you want to do is trace a few ordinary problems through the team. A ticket needs checking. A delivery arrives at the wrong entrance. A queue starts obstructing an access route. Who notices, who can act, and who needs to know the result?

Write the roles down before counting handsets. Your admissions supervisor might resolve routine ticket questions without involving event control. The same supervisor might need security and the duty manager for an entrance problem. Those conversations have different participants, even though they start in the same place.

Our imaginary show has an admissions team, a security contractor, a production crew, a medical provider and a duty manager at event control. The venue has its own procedures and staff. Some people need continuous contact within their department; others need to coordinate across departments at particular moments.

That distinction helps you avoid putting every conversation on one busy channel. It also prevents the opposite mistake, where each department can talk easily among itself but nobody has a dependable route to the person making an event-wide decision.

Your broader event communication plan should already cover audiences, approved information and responsibilities. The radio plan adds the operating detail for the people delivering the event on site. Keep attendee email schedules and sponsor approvals in that wider plan rather than copying them into a handset guide.

Ask the venue and contractors what systems they already use. Security may arrive with its own radios, while the production supplier uses an intercom for show cues. Neither system automatically connects to your hired handsets. Establish how the relevant leads will communicate before assuming a shared channel exists.

Confirm the radio service before assigning channels

A channel number on a radio is a programmed setting. It doesn't, by itself, tell you the frequency, legal permission, coverage or compatibility with another handset showing the same number. Your supplier needs to confirm those details for the equipment, place and work involved.

In the UK, Ofcom's guidance on programme-making and special events covers radio equipment used directly in association with performances and events, including talkback. Ask the supplier which authorisation applies to each proposed system and who holds it. Don't assume an ordinary business radio arrangement covers every production use.

For a US event, ask the supplier to identify the permitted service and users. The FCC's GMRS eligibility rules describe individual licensing and immediate-family operation. One person's family licence does not automatically authorise a crew of unrelated employees to use those radios. Have the supplier verify a suitable arrangement for your team.

In Australia, ACMA's citizen band radio rules explain that users share frequencies, identify channels reserved for emergencies and data, and distinguish repeater licensing. An event channel list must respect those restrictions. A channel that looks quiet isn't necessarily available for your routine operations.

These examples explain why a copied channel list isn't a legal or technical plan. Your local rules, licence conditions and venue arrangements govern what you can use. Record the supplier's contact and confirmation in the technical paperwork, then distribute the simpler operating assignments to staff.

Be equally clear about rental responsibilities. Ask whether the supplier provides programming, frequency coordination where needed, coverage testing, replacement equipment and support during the show. Get the agreed service confirmed in writing. Otherwise you can discover on event morning that the quotation covered a box of handsets and nothing else.

Use enough channels to separate busy conversations

There isn't a universal number of channels for an event of a particular size. A compact conference may have different communication needs from a music show with the same attendance. The useful question is which conversations must happen at the same time without blocking each other.

For our example, imagine that the supplier has confirmed suitable programmed channels and the venue has approved the operating arrangement. The admissions team needs routine contact with its supervisor. Production needs to coordinate equipment and stage activity. Event control needs contact with the leads responsible for decisions across the site.

A simple operating allocation could look like this:

• Coordination channel: Event control, the duty manager and designated department leads exchange requests and instructions that affect other teams.

• Admissions channel: The admissions supervisor and door team handle routine entrance and ticket queries, with a defined route to event control.

• Production channel: The production lead and relevant crew coordinate their work without filling the coordination channel with equipment conversations.

• Contractor systems: Security and medical leads use their agreed internal systems and maintain the tested contact route to event control.

Those are roles for channels, rather than frequencies or recommendations to use particular public channel numbers. Your supplier might deliver the arrangement differently. Your medical or security provider might also require a different reporting route, which you should agree together rather than replacing with this example.

Each separate channel creates a listening responsibility. If admissions reports something that needs the duty manager, who transfers the request and listens for the answer? Name that person. A department can appear well connected while its supervisor is away from the only radio that reaches event control.

You may need a supervisor with two radios or a configured system that supports the required communication. Let the supplier assess the equipment. Don't assume a scanning handset hears every important transmission while its user is talking or listening elsewhere. Test the actual setup and brief its limitations.

It's usually better to have a clear, staffed arrangement than a long channel list that nobody can monitor. If a channel has no responsible listener or no distinct purpose, ask why it exists. Keep enough capacity for the event's work without asking every team member to manage the whole network.

Decide who answers as event control

"Call control" only helps if somebody answers. Identify the person covering that role, where they will work, the hours they cover and how relief works. At a smaller event, this might be your duty manager in a quiet office. Larger or more complex events may need a dedicated control function.

Choose the location for listening and coordinating. A manager standing beside the stage may carry the correct radio and still miss calls. Check noise, power, access to plans and the ability to speak with the venue and contractor leads. Test the working position rather than accepting a room name on a plan.

Control also needs clear authority. It can receive a report, contact the right lead and record what happens. That doesn't make every person answering the radio authorised to stop a show, alter security arrangements or give medical instructions. Your safety and management plans decide those responsibilities.

For the wider security decisions, use your event security plan. The radio sheet should tell staff how to reach the agreed roles and raise a concern. It shouldn't quietly invent a new approval process that conflicts with the venue or contractor briefing.

Arrange relief before the shift starts. The replacement needs to know which channels to monitor, open requests, current restrictions and who is available. Tell the department leads when the handover is complete. Otherwise they can keep directing an urgent question to a manager who has left the site.

Choose call signs people can understand

Use role or location names your team can recognise immediately. "Control", "Admissions", "Production" and "East entrance" are easier for a new steward to interpret than somebody's nickname. Where several people share a role, add a consistent identifier and write down who holds each one.

Keep names distinct when spoken in a noisy environment. Two entrances with similar names can cause a real mistake even if they look different on paper. Say the names aloud through the radios with the venue team, and compare them against signs and the site map.

A call sign identifies the person or position for the event's operation. It doesn't replace any station identification required under the radio service or licence. Ask the supplier how that requirement is handled rather than treating the staff call-sign list as permission to transmit.

Agree how a call sign transfers. If "Admissions" means the supervisor, the outgoing supervisor hands over that role and tells control who is now covering it. If the name means a fixed entrance, the incoming person needs the current instructions for that entrance before taking the radio.

Avoid making the list longer than the team needs. A steward should know their own call sign, their supervisor, event control and the urgent reporting route. The full list can remain available to leads. Nobody should have to memorise your complete organisation chart before opening the doors.

Teach a short call that gets an answer

A useful routine call names the recipient, identifies the caller and waits for a reply before delivering the message. That gives the other person a chance to stop their current conversation and listen. It also tells everyone else who the call is for.

For example, an admissions supervisor might say, "Control, this is Admissions." Control answers, "Admissions, go ahead." The supervisor then gives a short report: "The ticket help position needs another member of staff. Can you send the available relief person to the east entrance?"

Control should respond with the decision or the next step. "Received, I'll check relief availability" means the request is understood and being checked. "Relief is on the way" means something different. Use the wording that matches what has actually happened, especially when another team is waiting to act.

For an instruction with consequences, ask for the relevant details back. If production redirects a delivery, the receiving lead repeats the entrance and agreed arrival arrangement. The sender corrects any mistake before ending the call. You don't need a ceremonial repeat of every casual message; you need confidence that the important detail survived.

The Health and Safety Executive's communication principles emphasise matching the method and language to the people and task, with additional communication methods where a critical message needs them. For your team, that can mean a spoken instruction followed by an updated written brief and confirmation from the affected lead.

Explain the handset controls, too. People need to know how to select their assigned channel, set the volume, use the microphone and recognise a low battery. Let them practise transmitting a complete sentence. A printed instruction cannot show you that someone is pressing the wrong button.

Follow one request through to completion

Suppose the east entrance supervisor asks control for relief because a ticket support colleague needs a break. Control hears the request, but the person expected to provide cover is helping the venue elsewhere. This is where an apparently successful radio call can leave the entrance short of staff.

A useful reply tells admissions what is happening. Control checks with the relevant lead, confirms who can attend and reports back. If nobody is available yet, control says so and follows the agreed staffing arrangement. Admissions can then manage the break with accurate information rather than assuming somebody is already walking over.

When the replacement arrives, the supervisor confirms the handover. Control can close the request, while the supervisor explains the current ticket support issues to the incoming colleague. The original call, the staffing decision and the completed handover are different moments. Treating them as one leaves avoidable uncertainty.

Now imagine that production calls about a vehicle waiting at the loading entrance during that conversation. Production's internal discussion can continue on its assigned channel. Its lead brings only the decision needing another department to control, using the same location name as the delivery instructions. The two requests remain understandable because each has a named owner.

This is the sort of rehearsal worth doing with your leads. Ask control to identify the unresolved request after the second call. Ask admissions whether cover has been confirmed or merely requested. Ask production who is meeting the vehicle. If their answers disagree, fix the call wording or responsibility before adding more equipment.

You can also practise the moment a conversation becomes unclear. The listener should ask for the specific missing detail rather than agreeing to something they haven't understood. Repeating an entrance name is a small interruption. Sending the wrong person to the wrong side of the building creates a much longer one.

Keep routine traffic brief without making it cryptic

Plain language is the better default for mixed event teams. You may have venue staff, contractors, paid crew and volunteers who have never worked together. A code familiar to one employer may mean something entirely different to another.

CISA's plain-language communication resources address the problems coded language creates between organisations. The same principle is useful for an event team, though your event procedures still need agreement with the people responsible for them. Don't publish a borrowed set of emergency codes and assume responders will understand it.

Short messages can still be specific. "Need help at the gate" leaves the listener guessing which gate, what happened and who should respond. "Admissions to Control, the east entrance ticket help queue needs relief staff" gives the receiver a job they can assess and assign.

Long discussions should move to an agreed, suitable route when that can happen safely. A production lead sorting out a supplier's missing equipment may need a direct call or a face-to-face conversation. Announce the change of route and return to the required monitoring arrangement afterwards. Don't leave the coordination channel without cover.

Keep personal information off general radio traffic wherever possible. Share the location and immediate operational need, then use the appropriate agreed route for sensitive details. An earpiece stops nearby attendees hearing your loudspeaker; it doesn't establish that the radio transmission itself is confidential.

Agree urgent traffic with the safety leads

Your emergency arrangements determine how staff raise an alarm and how the event responds. The radio plan must support those arrangements. Agree the wording for interrupting routine traffic, the person who answers and what other users do while the report is handled.

Brief staff to report the location, what they can directly observe and the assistance needed, using the procedure your safety leads approve. Don't require a junior team member to diagnose a medical condition or decide whether an incident meets a technical classification before requesting help.

The HSE's event emergency guidance covers clear responsibilities, communication with the public, agreed show-stop arrangements and testing systems before the event. Use that wider preparation to decide who contacts emergency services and who can authorise consequential action. A radio conversation alone doesn't complete those tasks.

A dedicated incident channel can help where the system and staffing support it. It can also fail if the reporting person moves there and nobody follows. If you use one, specify who remains on the normal channels, who transfers and how control confirms the move. Practise the transfer with the actual radios.

Don't tell every user to retune automatically whenever they hear an urgent call. Someone still needs to receive new reports elsewhere on site. Your control arrangements should preserve that coverage while the relevant people deal with the incident.

Staff should also know how to summon help if control doesn't answer, following the event's agreed emergency procedure. The fallback must not delay an emergency call or immediate protective action within their training. Write the route clearly and rehearse it, including who maintains contact with responders.

Check coverage where people actually work

A radio working across the car park doesn't establish that it works inside the loading entrance, behind the stage or in the basement office. Test the locations and routes your people will use, with control in its intended working position and the actual accessories fitted.

Ask the supplier how the event's buildings, temporary structures and equipment affect the proposed system. A useful site test includes the awkward places, rather than avoiding them to get a clean result. Report poor audio and missed replies as failures to fix, even when a signal indicator looks healthy.

Make the test a conversation in both directions. The person at a remote entrance needs to hear control and be heard by control. Try the route while moving, then test at the fixed post. Confirm the channel, call sign and location each time so you can reproduce a problem.

If the supplier proposes a repeater, ask how it is powered, what happens if it fails and what coverage remains without it. A repeater receives and retransmits radio traffic to support coverage. Its presence doesn't remove the need for a test or for an agreed response to failure.

Sound matters as much as signal. Let staff test approved headsets or earpieces in representative noise, while preserving the awareness their job requires. Ask your safety lead and supplier about appropriate accessories. Turning a loudspeaker up until it competes with the sound system isn't a considered solution.

Record unresolved locations and the operational response. That might require different equipment, a changed control position or an additional staffed contact point. Don't accept a dead spot at a necessary post simply because everyone has been warned about it. Decide whether the arrangements can support the work before opening.

Prepare for a handset failure and a system failure

A spare battery solves one kind of problem. It doesn't solve interference, a failed repeater or a whole site losing its main communication route. Work through those failures separately with the supplier and event leads so the response matches the fault.

For an individual handset, the user should know where to get a replacement, who covers their post and how they stay in contact during the exchange. Put charged spares somewhere accessible to the people issuing them. A locked cupboard whose key holder is on a break is a poor replacement arrangement.

For a failed channel, identify the authorised alternative configuration and how users receive the instruction to change. The supplier should confirm it is usable. If your only way to announce the change is the channel that has failed, you still need another contact route.

For a wider failure, agree the workable alternatives. These may include tested telephone contact, fixed contact points and designated staff carrying messages where appropriate. Check the routes, staffing and time involved. Somebody acting as a messenger cannot simultaneously provide uninterrupted cover at an entrance.

Mobile phones can be useful, but test the actual networks and working locations rather than assuming a group chat replaces radio. Define who calls whom and how missed calls are handled. If a fallback depends on the same power or connectivity as the failed system, describe that dependency honestly.

Agree who decides whether affected work can continue safely while communications are reduced. Your operations and emergency plans should cover that decision with the relevant venue and contractor leads. The person distributing spare radios shouldn't have to invent the event's response to a wider system failure.

Include the venue's own duty staff in this exercise. They may have responsibilities outside your hired team's reporting structure, and they need a reliable way to reach your event lead. Agree what happens when their usual contact is occupied. For a recurring event, repeat the check when the layout, supplier or staffing changes. A plan that worked last month can still contain the wrong assumptions for this show, particularly when a new contractor arrives with different equipment and different working procedures.

Put the operating details on a usable sheet

Your staff sheet should explain what to do with the radio in their hand. Keep the supplier's technical configuration and any restricted information in the appropriate controlled record. The operating sheet can be brief without leaving people to guess who answers them.

Include these fields, using the event's agreed names:

• Event, date, plan version and the person responsible for current instructions.

• Your assigned call sign and normal channel, plus the lead who answers routine requests.

• Event control contact and the staffed hours, including arrangements outside those hours.

• Urgent reporting wording and route, with the approved fallback if nobody answers.

• Any authorised channel transfer procedure and who confirms the return to normal monitoring.

• Replacement equipment location, issue contact and arrangements for maintaining post cover.

• System failure contact routes and where the current site map and emergency instructions are available.

Avoid shrinking a full manual into unreadable type. People need the immediate operating details at their post and access to the fuller briefing when necessary. Check the sheet against the programmed radios before distributing it. A beautiful document with an old channel assignment is still wrong.

The site map needs the same place names people will say over the radio. If your event logistics plan calls a delivery point the service entrance, don't label it "back gate" on the radio sheet. Agree one name with the venue, update the relevant documents and brief the team.

Date revisions and withdraw obsolete copies. When an assignment changes after the briefing, tell affected users directly and confirm they have the new instruction. Changing the shared file alone won't update the person who printed it yesterday and is already standing at the entrance.

Rehearse a busy moment before doors open

Bring the leads together for a rehearsal that uses the actual reporting routes. Start with an ordinary request, then add a second conversation on another channel. You want to see whether the system supports simultaneous work and whether control can follow the requests it receives.

At our imaginary show, admissions requests relief while production coordinates a delayed delivery. Each team should reach its own lead. Only the cross-team decision belongs with control. If both full conversations end up on coordination, the rehearsal has exposed a staffing or assignment problem worth fixing now.

Then practise an urgent report using a clearly announced exercise, agreed with the relevant safety leads. Check that routine speakers stop, the designated listener answers and the report reaches the responsible person. Nobody should mistake the rehearsal for a real incident, including contractors working nearby.

Include a missed reply and an equipment fault. Ask the person at the remote post to demonstrate the fallback rather than describe it from memory. If the replacement radio is unavailable or the phone number reaches an unanswered office, you have found a specific problem to resolve.

Afterwards, ask each lead what they heard and what action they believed was required. This often reveals ambiguity that a successful transmission test misses. Correct the wording or route, update the sheet, and repeat the part that failed before treating the arrangement as ready.

Keep the plan current through the last shift

Issue radios against roles and named users so you know who has the equipment. Check the battery, assigned setting and accessory at handover. Explain where replacements go and when equipment must return. Include contractors in the agreed process rather than assuming their internal arrangements cover your whole event.

During the show, control should keep a proportionate record of significant requests, decisions and outstanding actions. A request for relief stays open until the relevant lead confirms what happened. The record also helps the next shift understand the current situation without replaying every conversation over the radio.

Include close and breakdown in your coverage hours. People still coordinate deliveries, clear equipment and manage access after attendees leave. Agree when departments can leave their channels and who remains responsible for communication. The end of the performance isn't automatically the end of the work.

Before returning the equipment, ask the leads which calls failed or needed repeating and where staff couldn't hear. Separate a coverage problem from an unclear instruction or an unanswered channel. Each needs a different fix. Use those findings with the supplier before booking the system for your next event.