Stage Plot Examples for Bands, Duos, DJs, and Solo Artists

TL;DR — A useful stage plot is a top-down map showing where every performer, instrument, microphone, DI, monitor, backline item, and power drop belongs. The best example is not the most detailed one; it is the smallest diagram that lets a venue set the stage before the artist arrives. Use the five layouts below as patterns, then match every audio source to an input list.

Table of contents

1. What every stage plot example should show
2. Five common stage plot examples
3. How stage plots change by venue
4. Common mistakes
5. Pre-send checklist
6. FAQ

What every stage plot example should show

A stage plot is a top-down stage setup diagram. It answers where people and equipment go; the input list answers how each source connects to the sound system. A venue should be able to read the two documents together without guessing.

Every stage plot should identify:

• the downstage edge and audience direction;
• stage left and stage right from the performer's perspective;
• each performer's position and role;
• instruments, amplifiers, keyboards, DJ tables, risers, and other backline;
• vocal and instrument microphones, DIs, and stands;
• wedges or IEM positions and their mix numbers;
• requested power drops;
• a title, artist name, version date, and production contact.

Keep channel details in the input list. A small channel number beside a mic or DI is useful; a paragraph of technical notes on top of the drawing is not. If stage directions still feel ambiguous, read Stage Left vs Stage Right.

Five common stage plot examples

1. Solo singer-songwriter

A solo setup often needs more information than its size suggests. The venue still needs to know whether the guitar uses a DI, whether the artist sits or stands, and whether one wedge is enough.

Put the performer downstage center, place the wedge directly in front but behind the vocal microphone's rejection axis where practical, and mark the DI near the guitar position. If the artist carries a pickup preamp, name it in the notes. If the venue must provide a stool, guitar stand, or DI, say so explicitly.

2. Acoustic duo

The most readable acoustic duo plot uses two distinct performer lanes rather than stacking both names in the middle.

Show whether the pair shares one mix or needs separate mixes. Label stereo keys as two channels, and note any shared talk microphone. A dedicated walkthrough is available in How to Make an Acoustic Duo Stage Plot.

3. Four-piece rock band

For a typical vocal, guitar, bass, and drums lineup, build the plot around the drum position and sightlines.

Do not draw a generic drum icon and leave the engineer to infer the channel count. The accompanying input list should state the exact drum package. Keep loud amplifiers behind their players when possible, but treat the plot as a communication plan rather than an acoustic law: venue geometry may require a different position. For a channel-by-channel example, see the drum kit stage plot guide.

4. Five-piece band with keyboards and IEMs

This setup adds two coordination risks: stereo sources and wireless monitoring. Place the keyboard station where cable paths remain short and where the player can see the musical director.

Do not replace IEM information with five bodypack icons and no mix labels. The monitor engineer needs destinations and ownership: “Mix 3 — Keys — stereo IEM” is actionable. Monitor Mixes and IEMs explains the full relationship.

5. DJ or electronic live act

A DJ plot should describe the handoff between the artist's rig and the house system. Put the table dimensions, output connector, monitor position, and power requirement on the page.

If the performance includes live vocals, instruments, or timecode, show them separately instead of calling the whole setup “DJ.” See How to Write a DJ Tech Rider and Stage Plot for a complete example.

How stage plots change by venue

The core configuration should remain stable: performer relationships, inputs, monitor ownership, and essential backline. Venue-specific constraints belong in show notes or an agreed revision.

For a club, reduce optional equipment and keep the plot readable on one page. For a festival, make changeover-critical information obvious: riser requirements, rolling backline, shared drum hardware, wireless coordination contact, and sub-snake locations. For a theatre, include larger scenic footprints, playback, talkback, and lighting or video positions when they affect the stage.

Do not silently maintain several conflicting files. Keep one reusable Rider, attach it to each show, and record local exceptions without overwriting the touring baseline. The workflow is explained in Reusing One Rider Across Multiple Shows.

Common mistakes

Using audience left and right. Stage directions are defined from the performer's perspective facing the audience. Add an audience arrow so the convention is unmistakable.

Showing icons without labels. A rectangle could be a guitar amp, bass cabinet, road case, or riser. Name the item and who uses it.

Forgetting monitor ownership. “4 wedges” describes inventory, not routing. Label Mix 1 through Mix 4 and associate each with a performer.

Putting all technical detail on the map. The plot should remain visual. Put channel names, connector types, phantom power, stands, and patch notes in a structured input list.

Sending an undated file. Add a revision date and production contact. A clear old version is safer than an anonymous old version, and a live link can point recipients to the current one.

Pre-send checklist

• Artist and production contact are visible.
• Audience direction, stage left, and stage right are unambiguous.
• Every performer and major equipment item is labeled.
• Every microphone and DI maps to the input list.
• Monitor mixes show both a number and a destination.
• Power locations and unusual connector needs are marked.
• “We carry” and “venue provides” responsibilities are explicit.
• The version date is current.
• The plot remains legible when exported or printed.
• A PDF and current live link are sent from the same source of truth.

FAQ

What does a stage plot look like?

A stage plot looks like a simplified floor plan viewed from above. It shows the stage boundary, audience direction, performers, instruments, microphones, DIs, monitors, backline, and power locations. Labels matter more than realistic artwork.

What should a stage plot include?

Include positions, names, equipment, inputs, monitor mix numbers, power, stage directions, artist contact, and a revision date. Pair it with an input list for channel-level details.

Do solo artists need a stage plot?

Yes. A simple solo plot can prevent wrong assumptions about DI requirements, seating, microphone stands, monitor position, and power. It may contain only a few objects, but it still gives the venue an advanceable plan.

Should the input list be on the stage plot?

Use small channel references on the plot, but keep the complete input list as a structured table. The two should share names and numbers so a technician can move between the spatial and signal views.

Can I copy one of these examples exactly?

Use the layout pattern, not the equipment blindly. Replace every position, input, monitor, and provider responsibility with what your act actually uses. An inaccurate polished plot is worse than a plain accurate one.

Build the version your venue can use

Create a stage plot with Techrider.live and keep its input list, monitor mixes, PDF, and live link connected. If this is your first plot, follow the five-minute stage plot guide before you export.

---

Last updated: 2026-07-14 · Reviewed by the Techrider.live team for practical club, festival, and touring workflows.