RF Coordination During Festival Season: A Survival Guide

Festival season is where RF coordination separates the professionals from the people who just own a Shure Axient rack. When you're managing 200+ active wireless channels across four stages with overlapping schedules, every decision you make during advance saves you 10 minutes of panic during the show.

Start with a clean scan

Do your RF scan on-site at the same time the shows will run. A scan at 9 AM on load-in day tells you nothing about the interference environment at 8 PM when 40,000 phones are streaming Instagram stories. Run Wireless Workbench or the equivalent for your ecosystem and document everything.

Frequency coordination is not optional

Every act's RF tech needs to submit their frequencies before they arrive. No exceptions. Build a shared spreadsheet with columns for: channel, frequency, transmitter type, power level, and stage. If an act shows up with uncoordinated frequencies, they get reassigned on the spot.

Intermod is the silent killer

Two clean frequencies can create a third that wipes out something else entirely. Run intermod analysis on every frequency plan before you publish it. Wireless Workbench does this automatically — use it. Third-order intermod products are the ones that get you; fifth-order usually falls below the noise floor.

Zone your antennas

Don't try to cover the entire festival with one antenna system. Zone it. Each stage gets its own antenna zone with directional paddles pointed away from adjacent stages. The goal is isolation, not coverage.

Keep a buffer

Reserve 10-15 frequencies as hot spares. When something goes sideways at 7 PM on Saturday — and it will — you need clean channels ready to deploy in under 60 seconds. Label them, program them into backup packs, and keep those packs charged.

Document everything

At the end of the festival, export your final coordination plan. Next year's RF coordinator will thank you. Or it'll be you again, and you'll thank yourself.

---

Festival RF work pays well because it's hard. The techs who get called back are the ones who plan like it's a military operation and troubleshoot like they've seen it all — because they have.