I’m refining our radio channel map for a two-floor, 1,200-person conference next month and want to cut down crosstalk and missed handoffs. If you’ve got a day-of setup that’s worked — e.g., Ch1 all-call/hail only, Ch2 ops/FOH, Ch3 AV, Ch4 F&B, Ch5 security — plus how you manage emergency overrides and runner comms, I’d love the details or a template.
At our 1.2k two-floor shows, we make Ch1 ‘hail only’ and set every radio’s priority scan to Ch1 so emergencies/broadcasts break in, while ops is split by floor (Ch2 L1, Ch3 L2) to cut crosstalk. Runners live on Ch6 with dual watch to the nearest ops channel; AV/Sec/F&B keep their lanes, and adding CTCSS tones per team reduced venue bleed. Tiny caveat: priority scan eats battery — stash a few spares so the ‘all-call’ doesn’t clock out at lunch.
Quick tip: program the orange emergency button to revert to Security (Ch5) and open mic for about 10 seconds, and give only leads an All-Call TX interrupt so true emergencies cut through without blasting everyone. For runners, put them on a simplex talkaround channel and have them hail “Runner to FOH” then hop to the destination channel for 30 seconds; it slashed crosstalk on a two-floor, 1,200-person show. Small caveat: keypad-lock the fleet so folks can’t park on Ch1 for anything but hails.
I’ve found splitting your channels by task is key, but don’t forget to have a dedicated channel for unplanned chaos — like instant crew requests. It can be like trying to coordinate a flash mob during a power outage — for emergencies, consider using a simple color code system, makes it easier to communicate under pressure. @daniel10, what do you think about having a channel solely for general announcements?