Why Your Stage Plot Is Wrong (And How to Fix It)

I have loaded in thousands of shows. Festival fly dates, theatre runs, club tours where the monitors are older than the opener's drummer. And I can tell you with absolute certainty: the stage plot you emailed to the venue last Tuesday is wrong.

Not wrong in a malicious way. Wrong in the way that a snapshot of your band from eight months ago is wrong. The keyboard player switched to a Nord. You added a backing track rig. The bass player's DI died in Omaha and got replaced with something else entirely. But the PDF you're sending around still says "Bass: Radial J48" because nobody updated it.

This is the single most common problem in live sound, and it is almost entirely preventable.

The five mistakes I see on every tour

1. The plot is outdated

This is the big one. A stage plot is only useful if it reflects what's actually on stage today. Not what was on stage when you made it for your first tour. I've walked into venues where the plot shows a four-piece and there are seven people on stage. That's not a plot. That's historical fiction.

2. Channel counts don't match

Your plot says 24 inputs. Your input list says 28. The venue patched for 24. Now we're burning soundcheck time figuring out where to put the four channels nobody told them about. I have watched this exact scenario play out in rooms on five continents.

3. Positions are wrong

Stage left and stage right are from the performer's perspective. I know this seems basic, but I still get plots where the guitarist is drawn on the wrong side. The house engineer is looking at a mirror image of your stage and trying to figure out who's where. Every minute spent on that confusion is a minute not spent on making the show sound good.

4. Missing critical information

Phantom power requirements. Stereo pairs. Which channels need DIs versus mic inputs. Whether the keyboard rig is stereo or mono. These aren't nice-to-haves. A house engineer who doesn't know your condenser needs 48V is going to wonder why channel 12 is dead. Then they'll spend five minutes troubleshooting a problem that a single line on your input list would have prevented.

5. The plot and the input list disagree

This is the worst variant. Your stage plot shows the drummer with four mics. Your input list has seven drum channels. Which one is right? The house engineer has to guess, and guessing means patching errors, which means more soundcheck time, which means a shorter set or a worse-sounding show. Pick one.

The source-of-truth problem

The root cause of all five mistakes is the same: there is no single source of truth. Your stage plot lives in a PDF someone made in Photoshop. Your input list lives in a spreadsheet. Your actual console file has its own channel names and routing. Three documents, three versions of reality, zero guarantee that any of them match.

This is the problem I built stage·left to solve.

When you import a console file into stage·left — whether that's an X32 scene, a Yamaha CL/QL file, or a DiGiCo show — the input list comes directly from your console. Those are the real channel names, the real phantom power settings, the real stereo links. That's not a guess. That's what your console actually says.

From there, you build your stage plot around that input list. The plot and the list are the same document. Change a channel name and it updates everywhere. Add a channel and the count updates. The plot can never disagree with the input list because they aren't separate things.

How to fix your plot right now

Even if you're not using stage·left, you can fix the worst problems today:

Update it before every tour leg. Not every tour. Every leg. Personnel changes, gear changes, anything that touches the stage. Five minutes before you leave saves thirty minutes at every venue.

Put channel counts on the plot. Total input count, visible and clear. "32 inputs, 4 stereo pairs, 6 channels need 48V." A house engineer should be able to glance at your plot and know exactly what's coming.

Use the performer's perspective. Stage left is the performer's left. Label it. Remove any ambiguity.

Make the input list the authority. If the plot and the list disagree, the list wins. Always. The plot is a visual aid. The list is the contract.

Send the console file. If the venue has the same desk you carry, send them the file. Not a PDF, not a screenshot. The actual file. Let them load it and have everything patched before you walk in the door. This is the single biggest time-saver in touring audio, and almost nobody does it consistently.

The real cost of a bad plot

A bad stage plot doesn't just waste time. It erodes trust. When a house engineer gets a plot that doesn't match reality, they stop trusting your advance. They patch conservatively. They hedge. They assume they'll need to redo everything at soundcheck anyway.

A good plot does the opposite. It tells the house engineer: this artist has their act together. Patch it as drawn, and we'll be checking monitors in ten minutes.

That's the show I want to walk into every night. That's the show stage·left is designed to produce.