Depping In: How to Read a Stage Plot You've Never Seen

Depping is its own discipline. You're not writing the parts, you're not choosing the gear, and most of the time you didn't build the paperwork you're about to read. The stage plot the bandleader or contractor forwards you, often the night before, is usually the only real information you get about the gig before you're standing on the stage itself. Learning to read it fast and correctly, and knowing exactly what to ask when it's missing or incomplete, is a skill worth building on purpose rather than picking up the hard way.

What does it mean to dep into a band you've never played with?

Depping means filling in for a regular member of a band, often for a single show, sometimes for a short run of dates, usually on one rehearsal or none. You're hired for your ear, your sight-reading, and your ability to sound like you've held the chair for a year by the time the downbeat hits. The stage plot is frequently the only real information you get before load in, so reading it cold is part of the job, not an extra skill you bolt on.

How do you read someone else's stage plot before you've met the band?

Read a borrowed stage plot the way an engineer reads it: for position, signal path, and quantity, not for style. Find your marked spot first, note whether the plot places it stage left, stage right, or centre using the performer's own point of view, then look at what surrounds that position, an amp, a DI, a shared riser, a wedge, or an in-ear symbol.

Cross-check the plot against the input list if the band sent one along with it. A plot might show a keyboard rig without indicating it needs a stereo pair of DI channels, information that usually only shows up on the list. When the two documents disagree, trust the input list over the drawing, since it's typically built or revised closer to the actual show.

What should you ask before you say yes to the gig?

Ask exactly what changes your preparation: what instrument or amp is expected of you, whether it's provided or you're bringing your own, what monitor format the band runs, and what the material actually is. A contractor calling with a last-minute offer rarely volunteers all of this up front, so it falls on you to ask before you sink rehearsal time into the wrong chart or the wrong rig.

Some quick questions worth sending back the same day you're offered the gig:

• Is there a current stage plot and input list, or just a set list and charts?
• Am I bringing my own amp, or is there house backline I should expect to use?
• Wedges or in ears, and do I need my own pack and cable?
• Is there a click or a guide track running, and does it affect my monitor mix?
• How many songs, in what order, and is there a real rehearsal or just a line check?

A short reply like stage right, house bass amp, wedges, no click, forty-minute line check at four answers most of what matters in a single line and tells the bandleader you already know how to think about a stage. What you're doing here is a scaled-down version of what a full band sends a venue in a band advance email; you're just aiming the same due diligence at the bandleader instead of a production office.

What do you do when there's no stage plot at all?

Build a rough one yourself and send it back for confirmation rather than guessing on the day. A short text description works fine: name your instrument, your expected position based on what the bandleader tells you, and any space or electrical requirement, an extra amp, a second DI, or floor room for a pedalboard. Ask the bandleader to confirm or correct it before you show up holding it as fact.

This matters more than it sounds like it should. A dep who arrives with a clear, even informal, sense of where they'll stand and what they'll plug into reads as prepared, even on a gig where nobody else brought paperwork. It also protects you: if the house engineer expected two guitar amps and there's only room on stage for one, you find that out before load in, not while cases are already coming off the truck.

How do you translate someone else's channel list into your own gear?

Match your rig to what's already patched instead of expecting the band to reshape their plan around you. If the regular player runs a stereo keyboard rig through two DI channels and you're subbing on guitar with a single mono amp, don't assume the engineer has a spare channel waiting; confirm the actual input number and type you're being handed.

Pay attention to phantom power specifically. If you're bringing a condenser mic, an active DI, or a wireless system with its own power draw, check whether the house snake supplies 48 volts on your channel, or whether you need a separate power source of your own. This is the kind of detail a regular member never has to think about, because it got solved once, months earlier, and never came up again.

If the band runs in-ear monitors from a personal mixing station such as an Aviom or a Behringer P16, ask whether there's a spare port and headphone amp waiting for you, or whether you're expected to bring your own beltpack. Showing up with a quarter-inch cable and no idea what the house system expects burns soundcheck minutes a touring act, unlike a relaxed club night, usually can't spare.

What should you bring regardless of what the paperwork says?

Bring redundancy for anything a missing cable or a dead battery could take down. A spare instrument cable, a fresh nine-volt for your tuner or pedal, backup in-ear tips, and a basic DI box cover most of the small failures that would otherwise stop a set. A dep who quietly solves their own problem earns more trust in five minutes than one who plays flawlessly but needs the whole crew to help find a battery.

Bring your own tuning reference and confirm the band's pitch standard before the gig, especially on cover circuits and theatre pits where a fixed reference for horns or a backing track matters. A guitar tuned to a plain 440 against a band running slightly sharp for a track will be audible the second you're both holding the same chord.

What happens differently at soundcheck when you're the sub?

Expect less time and less patience for open-ended exploration than a regular member would get, and spend the minutes you have confirming rather than experimenting. State what you need in language the engineer already uses: more of your own instrument, a specific reference such as bass or click, or a level change, rather than a vague request for more of yourself in the mix.

If something is genuinely wrong, a dead channel, no signal reaching your DI, say so immediately and plainly instead of quietly working around it. Most engineers would rather stop for thirty seconds during line check than discover a missing channel two songs into a set they can't restart. This single habit, being direct instead of politely vague, is often what separates a dep who gets called back from one who doesn't.

Confirm your monitor mix is actually usable before the room fills, not just technically present. A wedge that's on but buried under drum spill isn't a working mix; ask for a specific change while there's still time left to make it.