I've been at festivals where the main stage lost power for 18 minutes. Not because the generator failed—because someone plugged a coffee maker into the same circuit as the lighting console. That's the kind of dumb mistake that advanced techniques are supposed to prevent. But most of the advice out there is either too basic ("bring extra batteries") or too abstract ("design for resilience").
So here's the real stuff: what actually goes wrong when you're running a 10,000-person event, and how to stop it before it happens. No theory. Just the mess of cables, people, and deadlines that's advanced festival tech.
Who Actually Needs This Stuff
Volunteer coordinators who get dumped with tech duties
You volunteered to wrangle people, not patch Wi-Fi dead zones at 3 a.m. Yet here you're—laptop balanced on a cooler, hotspot dropping every third request, and a stage manager screaming about a missing timesheet. I have been that person. The one who inherits a half-broken tablet, a Google Sheet with conflicting permissions, and a stack of walkie-talkies that only work if you hold them at a specific angle. The default move is to limp through with duct-tape solutions. That works for exactly one festival. By year two, your volunteers ghost you because the sign-in process takes twenty minutes, and data from Thursday’s shift somehow overwrites Saturday’s roster. The cost of skipping real planning is not a minor headache—it's losing your crew mid-season. The trade-off is simple: invest a few hours upfront, or spend a full day of the festival firefighting credential errors. Most coordinators learn this the hard way, right when the headliner’s guest list vanishes from the app.
Site managers who learned on the job
You're the person who knows where the porta-potties go, where the generator hum doesn’t bother the main stage, and which field turns into a mud pit after one hour of rain. Congratulations—that makes you the default tech lead, too. Site managers get handed a clipboard, a radio, and a password for the scheduling platform they have never opened. The catch? Everyone assumes you can make the system bend. It won't bend. It will quietly corrupt your staff assignments when you plug in a CSV with mismatched columns. I watched a site manager lose three hundred volunteer shifts because he renamed a column header and the sync tool treated it as a new field. The pitfall here is assuming that because you can handle the physical chaos, digital tools will behave. They don't. What usually breaks first is the data handoff between your walkie-talkie check-in and the central schedule. You fix that by building a single source of truth—one spreadsheet, one tool, one person who owns the key file. Everything else is a mirror.
‘The worst failures I have seen were not from bad gear. They were from assuming that if nobody screamed, everything worked fine.’
— Festival ops lead, eight years running
Tech leads who want fewer mid-festival fires
Maybe you already know the tech stack. You have deployed the check-in kiosks, tested the wristband readers, stress-tested the server. Good. Now ask yourself: does your system survive a volunteer calling in sick thirty minutes before her shift? Does it handle a rain delay that pushes all meal breaks by two hours? The fires that actually burn you're not the big ones—they're the small, cumulative failures that cascade into a mess by Sunday. The mistake I see tech leads make is optimizing for the happy path. They test the login flow but not the password-reset chain. They verify the schedule export but not the rollback logic when someone fat-fingers a deletion. The hard truth is that your festival won't follow your workflow. It will follow entropy. Your job is not to prevent every break—it's to make sure each break takes five minutes to fix instead of two hours. That means building friction points where humans can override the automation, adding audit logs that a site manager can actually read, and accepting that some features will remain unused while one weird edge case eats your Saturday. Invest in those edge cases. They're the ones that turn a good festival into one where people say ‘we will never work with that system again.’
The Basics You Better Have Nailed First
Power: Your First and Last Word
You can have the slickest livestream rig on the continent, but if your generator hiccups at 9:17 PM, you’re done. I have watched a perfectly good three-stage setup die because someone used a 50-amp extension cord for a 100-amp draw. The math is not optional. Total load—add every amp, every phantom-powered DI, every LED wall brick—then add 30% headroom. Cable gauge follows the same brutal logic: too thin and the voltage drop turns your console into a dim, glitching paperweight. Most teams skip this step until the seam blows out. That hurts.
‘Power is not romantic. But a dead PA in front of 2,000 people is a very specific kind of silence.’
— sound engineer, after a generator swap at 2 AM
The catch is that rental generators are often rated at ‘peak’ wattage, not continuous. A 5,000-watt unit might deliver 3,800 steady. Check the data plate. And never daisy-chain extension cords from three different vendors—the impedance mismatch will cook something. We fixed a recurring drop-out on a folk stage by simply replacing all the 16-gauge homeowner cords with 12-gauge rubber SJOOW. One swap, zero issues. That said, budget for a spare generator cable. You will lose one in the mud.
Comms: Frequencies, Boosters, and the Dead Zone
Radio frequencies are a minefield. Most festival grounds are crammed with wireless mics, in-ear monitors, Wi-Fi hotspots, and the occasional trucker blasting through on CB. Your walkie-talkie system needs to be licensed and frequency-coordinated, or you will step on the headliner’s guitar pack. I have seen a stage manager lose contact with front-of-house for seventeen minutes because they bought blister-pack radios from a big-box store. Seventeen minutes of silent panic. Don't be that person.
The fix is threefold. First, use UHF business-band radios with programmable channels—not the consumer FRS stuff. Second, rent a cell booster if your site has marginal coverage; a Wilson weBoost unit can turn a one-bar parking lot into usable signal. Third (and this one stings the budget), carry at least two satellite phones for the core team. Not for everyone—just the people who make go/no-go calls. Because when a storm rolls in and the cell tower goes dark, your only link to emergency services is a brick of plastic pointed at the sky. Wrong order there means no order at all.
Layout: Crowd Density and the Unseen Path
Stage orientation seems like a creative choice until a medical team can't reach the front row. Crowd density is not about comfort—it's about evacuation time. You need a minimum 12-foot-wide clear path from the front barrier to the nearest exit, and every gate must swing outward. I have stood in a field where the only way out of the pit was a 4-foot gap between two beer tents. Not yet a disaster. Close enough to taste one. The rule: walk every evacuation route at dusk, when lighting is worst. What looks obvious on a map disappears in the dark.
Your sound and lighting positions must not block those paths. That means running feeder cables in overhead trays or armored ramps—never loose across grass. And check your load-in access: a 40-foot trailer needs a turning radius that a sedan doesn't. We once had to unload a full lighting rig by hand because the generator truck blocked the only gate. That wasted four hours and a lot of goodwill. Layout is forgiveness in advance—spend the time now so you don't apologize later.
Core Workflow: Three Steps That Actually Matter
Step 1: Map your power budget to the last watt
Most failures happen before the first beat drops. Not on stage — at the generator. I have watched a festival lose its entire main stage because someone plugged a mobile catering truck into the wrong circuit. That hurts. The catch is that power looks simple until you add a fog machine, a video wall, and three phone-charging tents running simultaneously. Map every device, its draw, and its location. Test the breaker load at 80% capacity — not when the site is empty at noon, but during soundcheck when everything is hot and hungry. Quick reality check: a standard 15-amp circuit handles about 1,800 watts. A single subwoofer rig can eat half that on bass hits. Wrong order? You lose a stage. Or worse, you lose the medical tent.
Most teams skip this: calculating peak-draw overlap. A DJ drops a riser effect, lights spike, the sub kicks — that three-second burst can trip a breaker that held steady for hours. We fixed this by staggering high-draw gear across different phases and labeling every distro box with its max safe load in permanent marker. Not tape. Marker. Tape falls off in rain. — first-person, field experience
Step 2: Scan RF spectrum for interference sources
The second step is invisible until it ruins your headliner. Wireless microphones, in-ear monitors, walkie-talkies, even the parking lot attendant’s Bluetooth speaker — they all compete for airspace. You can't fix interference with a better antenna after the fact. You have to scan the spectrum before load-in. Rent a spectrum analyzer or use the one built into your digital wireless system. Walk the entire site. Note where cell towers sit, where WiFi routers are mounted, and where the press compound plans to stream live. That sounds fine until you realize the green room sits directly under a cellular tower; we had to move an entire wireless rack twenty feet to clear the dropout zone.
The pitfall here is assuming RF is static. It isn’t. A TV news van rolls in at 4 PM, fires up its transmitter, and suddenly your lead vocalist’s mic cuts out mid-song. Build RF redundancy — two frequencies per mic, auto-scan fallback, and a crew member with a handheld scanner. One concrete anecdote: at a lake-side festival, boat radios from the marina next door stomped all over channel 7. We didn’t catch it until soundcheck. Cost us forty-five minutes of re-coordination.
Step 3: Model crowd flow to prevent bottlenecks
By the time the crowd arrives, it's too late to fix the layout. Model flow before you stake a single tent. Think about where people enter, where they buy drinks, where the bathrooms are, and where the emergency exits sit. That sounds like common sense. Most teams still place the main bar directly between the entrance and the main stage. You create a human dam. I have seen a line back up two hundred meters because three food trucks were all on the same side of a narrow path. One reroute — swap the trucks with the merch tent — cut wait times by half.
The trade-off is between convenience and safety. Wide paths kill the cozy festival vibe but save lives in a crush. A rule of thumb: every major point (stage exit, bar, first aid) needs a secondary route that doesn't intersect the main flow. That means two exits from every field, no dead-end vendor alleys, and gates that swing outward for evacuation. Test it with a dry walk — not with the crowd, but with staff holding flags to simulate bottlenecks. Fifteen minutes of walking saves hours of crowd-control drama.
“We had one exit for 8,000 people. It took three ambulances to convince the organizer that was a problem.”
— site manager, regional music festival, 2024
Gear and Software You'll Lean On
Load Calculators: Spreadsheets vs. Dedicated Apps
Most teams start with a spreadsheet. Google Sheets, LibreOffice Calc, a napkin taped to a Pelican case—whatever works. And for a single stage with four subs? A well-built spreadsheet is plenty. You type in amp draw per device, sum the column, multiply by 1.25 for headroom, and you're done. Simple. Cheap. Reliable.
The catch arrives when you have three stages, a silent disco tent, a charging station for vendors, and someone plugs a pizza oven into the wrong circuit. Now your spreadsheet needs cross-referenced phase balancing, voltage drop over 200 feet of feeder, and a way to flag when the generator's third leg is already at 85%. Spreadsheets can do all that—if you build the formulas right. Most people don't. I have pulled more festival electricians out of fires caused by a single misplaced decimal than I care to count.
Dedicated apps like Load Calc Pro or EasyPower force you into structure. They prompt for wire gauge, distance, ambient temperature, even power factor. The trade-off: cost. A decent license runs $200–$500, and the learning curve is real. Quick reality check—you don't need a $500 app for a 200-person private festival. A spreadsheet plus a second set of eyes on the math will hold. But once you exceed four service panels or 50 amps per circuit, the app pays for itself in the first blown breaker you avoid.
Spectrum Analyzers: Pro Units vs. Cheap RTL-SDR
Wireless microphones, IEMs, talkback systems, even the DMX control link—everything fights for airspace. A pro spectrum analyzer like the RF Explorer costs around $300 and will show you a clean waterfall of noise across 2.4 GHz and 5 GHz bands. It's the tool I see veteran A2s reach for before soundcheck. They sweep the stage area, find the open channel, lock it in. Done in three minutes. That feels like wizardry when you're standing in a field with 30,000 phones all searching for a signal.
The affordable alternative is an RTL-SDR dongle. Twenty-five bucks. Pair it with a laptop running Gqrx or SDR#, and you get surprisingly usable data. The limitation? No calibrated antenna, so you can't trust the amplitude numbers. You can see where the noise floor spikes, but you can't tell exactly how strong a signal is. That matters when you're trying to find a hole for a low-power IEM pack. But for a simple scan to avoid the obvious Wi-Fi conflict on channel 11? The cheap dongle works. I once watched a stage manager fix a drop-out issue by taping an RTL-SDR to a PVC pipe and walking the perimeter. Not elegant. Functional. That's the trade-off: precision versus cost.
'The RTL-SDR won't replace a $2,000 Tektronix. But it will keep your main vocal mic from cutting out during the headliner's first chorus.'
— Field note from a 2023 outdoor festival build
GIS Software: QGIS for Site Planning (Free)
Site plans drawn by hand on graph paper work for stages under 40 feet wide. Beyond that, you need spatial awareness—where does the sun hit during the afternoon set? How far is the generator from the FOH position? What is the actual slope of the ground where you want to place the main tent? GIS software answers those questions with precision a tape measure can't touch.
QGIS is free, open-source, and brutally capable. You drop in a geo-referenced aerial photo of your festival field—Google Earth export works—then draw polygons for every structure, route, and power run. The software calculates distances and areas, overlays wind direction data from the nearest weather station, and even exports a KMZ file you can load onto a phone for walking the site. The downside: QGIS has a steep initial climb. The interface was not designed for a sound engineer under time pressure. I have taught it to volunteers who gave up after twenty minutes. But for the person willing to spend two hours learning layers, symbology, and coordinate systems, the payoff is massive. One concrete example: we used QGIS to plan crowd-flow fencing for a 5,000-person event and discovered the designated exit route dead-ended into a drainage ditch. Caught it in planning, not during the evacuation.
When Your Festival Is Tiny (or Huge)
Small Festivals: When Everything Rides on a Walkie
I once watched a sixty-person micro-fest die because the stage manager couldn't hear the gate. Not a power failure—the cheap two-way radios had a four-mile range and the site was five miles end to end. That hurts. For tiny events your single most fragile point is communication, not electricity. You can run a full sound system off a borrowed Honda generator; you can't fix a lost volunteer who doesn't know where the medical tent moved. Prioritize a proper handheld radio system—Motorola CP200s or similar, not blister-pack toys—and test them at site extremes before load-in. One charged spare battery per unit. Write channel assignments on laminated cards and duct-tape them to the radios. The catch? You'll still have dead spots. Have a designated runner with a mountain bike and a loud whistle for the gap. Overkill? Not when the artist's mother is trying to find the quiet room.
What about power redundancy for a show with three thousand people? You don't need it. One quality inverter generator, a spare five-gallon fuel can, and a clear fuel-line filter—that covers ninety percent of failures. I have seen organizers drop thousands on dual-supply UPS systems for a site that ran perfectly on a single camping generator for ten years. That money buys better signage, more porta-potties, happier staff. Avoid the temptation to over-engineer. Scale your paranoia to the audience count. For a tiny festival the real disaster isn't a dead PA—it's a lost child nobody can radio about.
Large Festivals: Redundancy Is a Religion
Flip the script for thirty thousand people. Here the failure modes compound fast—one blown mains transformer can strand fifteen stages if you didn't tier your power distribution. Invest in a proper three-tier electrical plan: utility feed to main distribution panels for critical loads (medical, comms, FOH), then sub-panels for stages and vendor zones, and finally isolated UPS units for networking and ticketing systems. That sounds boring until a drunk driver hits a pole at 2 AM and your medical tent still has lights and your gate crew can still scan wristbands. The pitfall is assuming the rental company tested everything—they didn't. We fixed this by spending Friday afternoon walking every cable run with a circuit tester and tagging each tie-in with a zip-tie color code. Does it take five hours? Absolutely. Worth it when you don't have to cancel day two.
Fiber backbone, not copper. At scale, Ethernet runs beyond three hundred feet drop packets under tent-fabric EMI. We pulled single-mode fiber from the production office to each stage hub—terminated in weatherproof boxes, not dangling SFP modules. One lightning-near miss at Electric Forest turned a copper network into a dead tangle. Fiber took the same hit with zero reboots. — veteran site tech, post-incident debrief
— production manager, 12-year large-festival veteran
Large events also need a dedicated fuel logistics plan for generators—not the "someone will grab diesel in the morning" approach. Assign one person with a clipboard, a fuel log, and a reserved contact at the local supplier. I have seen a 50kW generator starve at 4 PM on Saturday because the volunteer forgot the lock combination on the fuel cage. That person is no longer a volunteer.
Remote Sites: Solar, Satellite, and the Fuel Math Nobody Does
Deserts. Mountain meadows. The beach at low tide. Remote sites punish small and large festivals equally—just with different tools. The trick is admitting that grid power is not coming and cellular data will fail around sunset when everyone posts stories. Start with solar generators—not panels alone, but a proper battery-plus-inverter unit like a Bluetti AC300 or EcoFlow Delta Pro. Pair it with a quiet gas generator for backup charging when clouds roll in for three days straight. Do the math: a small stage running digital mixing and LED uplighting draws roughly 800Wh per hour. A 2kWh battery gives you two hours of runtime with no recharge. That math kills festivals. Most teams skip this: calculate your worst-case load (all gear on, no solar input) and multiply by four. Then add a generator.
Satellite internet is no longer a luxury. A Starlink unit with a clear view of the northern sky will handle ticketing validation and social posts for a 500-person crowd. The catch is fuel logistics for the generator that backs it up—remote sites mean every gallon of diesel was driven two hours on a dirt road. Pre-position fuel drums with a hand pump, label them "STAGE C - NOT FOR VEHICLES," and lock the caps. I saw a well-intentioned volunteer drain a drum meant for the sound system into a festival truck. The show ran a day behind because of that kindness. One rhetorical question—worth asking before load-in: is your satellite dish anchored against wind or will a gust at 3 AM send your internet budget flying into a ravine? Answer that before you arrive.
Five Things That'll Bite You (and How to Spot Them)
Generator ground loops — 60-cycle hum that kills your kick drum
You rented a 20 kW diesel because the power distro quote looked too fancy. Soundcheck goes fine. Then the food trucks plug in — and your subs start humming like a trapped hornet. That low-frequency grumble isn't coming from the music.
Quick reality check: ground loops happen when your audio gear and the generator share two different earth paths. The voltage difference finds your signal cables. Pin it fast. Bring a three-prong tester — plug it into the generator outlet before you connect anything. If the 'open ground' light glows, you need a bonded neutral plug or a proper ground rod. I have watched a headliner's engineer spend forty-five minutes chasing this while the crowd grew restless. Don't be that team.
The fix is not guessing. Use a ground lift switch on one amp only — never lift safety grounds on multiple devices unless you understand the code. Or run everything off the same distro with star-grounding. Test with a voltmeter between chassis and ground: anything above 1 VAC spells trouble.
Cell tower overload — your ticketing app dies at 9 PM
Headliner hits the stage. 18,000 people pull out phones simultaneously. Your QR scanner spins. Then it crashes. Cell towers in festival fields handle about 200 simultaneous voice calls — not 10,000 Instagram uploads.
Most teams skip this: run a speed test at the site during load-in, then again at the same time the show will run. The numbers drop 90% when the crowd mass arrives. We fixed this by caching admission data locally on tablets — offline-first ticketing that syncs when the network breathes. Carry a portable WiFi hotspot on a different carrier. One event I worked lost forty minutes of entry revenue because nobody tested the backup provider. That hurts.
Crowd crush at narrow exits — the bottleneck you didn't measure
Your site map shows a 12-foot gap between two vendor tents. Fine for idle walking. Not fine when 3,000 people try to leave after the closer. Crowd movement follows fluid dynamics: flow rate drops catastrophically below 0.8 meters per person per second. You don't need a PhD to spot this — walk that path yourself during the busiest hour. Does your shoulder brush the tent wall? Then you have a problem.
'Every gate should handle half the total attendance per hour. If yours doesn't, you have already failed the crowd — you just haven't seen it yet.'
— security director on a regional EDM festival, after we widened three gates mid-show
Measure your largest exit. Check it at peak load. Add secondary lanes with crash barriers — they force single-file and prevent the lateral shove that turns a slow exit into a crush.
RF interference from LED walls — the silent show-killer
The video team rolls in a 10×10 LED wall. Looks gorgeous. Your wireless microphones start crackling on channel E7. That's not a coincidence — LED walls radiate broadband noise from their power supplies and data drivers. The interference sits between 500 MHz and 700 MHz, right where many UHF wireless systems operate.
Catch it during load-in: turn on every LED surface before soundcheck. Walk the stage area with a spectrum analyzer or a cheap software-defined radio dongle. I have seen a festival lose four Sennheiser channels because nobody ran this test. The workaround: reposition antennas above and behind the wall, or switch to a frequency block that your analyzer shows as clean. Some walls emit less noise when dimmed to 80% — that hack saved a mainstage once.
Waterlogged cable runs — the failure that smells like ozone
Rain starts at 3 PM. By 5, your snake cables lie in a puddle. Water seeps through connectors you thought were sealed. One short later, your front-of-house desk reboots. The smell of burning PVC tells you exactly what happened.
Spot it before it finds you: check every stage box and sub-snake connection for loose gaskets. Use cable ramps that elevate runs off wet ground — those cheap rubber ones work fine. For critical paths like monitor returns, double-wrap the connectors with self-amalgamating tape. Then cover that with electrical tape. That combo held for twelve hours of continuous rain at a mountain festival last summer. Test your waterproofing with a garden hose before the show. It sounds ridiculous. Then you hear the ozone smell at 11 PM and wish you had.
FAQs from the Trenches
How many watts per person do I need?
None. Stop asking for watts per person. That question means someone sold you a rule of thumb that doesn’t exist. I’ve been on site where a 15,000-watt system drowned a field of 8,000 because the array was stacked wrong—then watched a 4,000-watt rig on sticks cover 12,000 people cleanly. The real number is coverage geometry and headroom. Figure your seating depth and throw distance first. Then add 6 dB of headroom for the moment a kick drum hits and you need transient impact without distortion. Most techs undershoot that reserve. That hurts. You push into limiting, the vocal snaps, and the crowd feels tired an hour before curfew.
The catch is wattage ratings lie. A speaker rated 1,000 watts continuous might handle 2,000 peak—but only if your amplifier clips clean and your DSP doesn’t fold. I once watched a crew swap a “5,000-watt” sub stack for a pair of used 18-inch drivers on half the power. Coverage improved. Why? The first rig had phase cancellation from bad placement. The second was flown correctly. Watts per person is a sales metric. Angle, delay, and rigging are engineering.
“We spec’d 2 watts per person. By noon Saturday the mix was mush. We had to pull the top boxes down and re-angle by hand.”
— FOH engineer, 12,000-capacity outdoor festival, Pacific Northwest
What’s the best radio frequency for a 5k crowd?
There isn’t one. Not a single frequency you can pencil in and trust. With 5,000 phones, two wireless IEM racks, six lavs, and a comms beltpack system, the RF floor is a battlefield. The best frequency is whatever clears local TV towers, your own intermod products, and the unlicensed gear some busker is running off a battery pack near the beer tent.
Most teams skip this: you need a coordinated scan on site, morning of day one, not a spreadsheet from Tuesday. I’ve seen a tech load a “clean” show file from last year’s same field—only to find a new cellular booster had been bolted onto a light pole 200 feet away. That booster flatlined an entire bank of wireless mics during the headliner’s first song. Fixing it on the fly meant dropping to a spare channel that had static. Crowd noticed. The fix was ugly.
Trade-off time: scanning takes 20 minutes. Not scanning costs you a show. You also need a second scanner for your comms—because UHF intercom links and audio wireless don’t share nicely. If you leave comms on a single frequency that drifts into a TV white space… well, you lose director-to-camera talk. That’s a fire you can't put out with a gain knob. The practical move? Rent a spectrum analyzer or use Wireless Workbench with a live RF feed. Do it before load-in, right after you park the trucks. And keep a paper list of backup frequencies taped to your rack door—because when the screen freezes, paper still works.
How do I test comms coverage before the event?
Walk it. Not a stroll—a stress walk. Take a beltpack tuned to the master channel and walk every corner of your site while someone talks constant low-level chatter. Dead spots show up fast. Most crews test coverage from stage to FOH and call it done. Wrong order. You need coverage at the back of the medical tent, behind the generator bank, inside the portable toilet row, and under the metal-roofed merch booth. Those are where radios fail.
I once had a comms dropout at the furthest water station—150 yards past where my walk test stopped. The runner couldn’t call for a medical ice refill. We fixed it by adding a wireless repeater hung on a lighting truss. That repeater cost $400 and saved two hours of foot-runners per day. The lesson: don’t trust line-of-sight on paper. Trees, crowd density, and metal scaffolding eat signal unpredictably. If your festival is larger than two football fields, you probably need a distributed antenna system or a second base station. Test first. Then test again when the crowd fills in—because 5,000 bodies absorb RF like a sponge. Your Sunday morning test may not hold for Saturday night sweat.
What usually breaks first is the intercom between stage manager and FOH. If that link crackles, the whole show slows down. Run a backup channel on a different frequency band—VHF for long range, UHF for clarity. And label your beltpacks with channel and zone. One last thing: nobody talks about the batteries. Test with the battery type you’ll use show day. Rechargeables sag voltage differently than alkalines. I saw a full crew comms system go silent 40 minutes into a set because every pack used old NiMH cells. That’s a pitfall you spot only by testing with show-spec gear. Do it.
Your next weekend project: grab a friend, a beltpack, and a map of your site. Walk the perimeter with a clipboard. Mark every dropout. Then fix them before the gates open—not during the headliner.
Your Next Weekend Project
Run a load test on your mains distribution
Rent a dummy load bank for a Saturday. That sounds like overkill until you watch a breaker trip at soundcheck because the toaster cart and the subs share a phase. I have fixed this exact mess—twice. Plug your distro into the load bank, pull 80% of its rated current for ten minutes, then check every connection with a thermal camera or a gloved hand. Hot spots don't lie. The catch: most rental houses charge for a full day, so find another tech to split cost and time. Wrong order? You will discover the loose lug mid-set, not during load-in.
“Thermal imaging caught a lug that was 40°C hotter than its neighbor. Tightening it took ninety seconds; the fire risk had been there for years.”
— stage electrician, festival season 2022
That's your Saturday morning. Saturday afternoon? Walk the site with a spectrum analyzer. Dead zones in the wireless coverage are guaranteed—usually where shipping containers or the main stage truss sits. Scan the 2.4 GHz band near every food stall; those microwave ovens bleed RF like crazy. Mark the bad spots on a paper map. Then build a backup radio plan with two fallback channels. Channel one for primary talk, channel two for emergencies, a third for the quiet team. Most crews rely on the one-button-scan feature. That fails exactly when the headliner's monitor engineer needs to call a power drop. Quick reality check—a printed channel card in every radio pouch beats a PDF that nobody opens.
Block your Sunday for a dry run of failure scenarios
Gather three volunteers. Hand each a radio and a list of cues: “Simulate a lost generator at 15:00.” “Mimic an RF hit on channel 4.” “Pretend the production manager vanished for twenty minutes.” Run the drill without stopping to fix things—note who froze, who swapped frequencies, who walked to the dead zone and stood there swearing. That hurts to watch. But you learn exactly which part of your plan is paper-thin. I once watched a stage manager yell into a dead microphone for forty seconds because the spare channel was listed on a sheet taped to the distro panel a hundred meters away. Fix that before the gates open. Your next weekend project turns three likely disasters into boring checklists.
Comments (0)
Please sign in to post a comment.
Don't have an account? Create one
No comments yet. Be the first to comment!