Festival Stage Plot and Changeover Guide for Bands

TL;DR — A festival stage plot must show not only the final performance layout but how the band gets there during a short changeover. Mark carried versus shared gear, rolling risers, sub-snake or patch groups, monitor destinations, power drops, wireless systems, offstage prep positions, and line-check priorities. Send it with a numbered input list and a one-page changeover sequence; confirm every deviation from your normal rider during advance.

Table of contents

1. Why a festival plot is different
2. The festival stage plot checklist
3. Build a changeover-ready input list
4. Plan the changeover sequence
5. Shared backline and rolling risers
6. Line check and monitor priorities
7. What to confirm in advance
8. FAQ

Why a festival plot is different

A normal stage plot describes the desired setup. A festival stage plot must also help the local team move from the previous act to that setup safely and quickly. The final positions still matter, but so do preparation, ownership, patch continuity, and the order of work.

Festival production often introduces:

• a fixed house or festival patch;
• shared drum shells, amplifiers, stands, or DJ equipment;
• limited soundcheck or line-check time;
• rolling risers and offstage build areas;
• consecutive acts using the same stage boxes and monitor system;
• coordinated wireless frequency plans;
• tight rules for cases and personnel on deck.

Do not shrink a club rider and call it festival-ready. Add the information that makes the transition executable.

The festival stage plot checklist

Start with the standard anatomy in How to Make a Stage Plot, then add changeover fields.

Final performance layout

• performer names or roles and positions;
• instruments, amplifiers, keyboards, DJ tables, and drum setup;
• vocal and instrument microphones, DIs, and stand types;
• wedge or IEM destination with mix number;
• power-drop IDs;
• riser size, height, orientation, wheels, and rail/stair needs;
• stage dimensions or minimum footprint where relevant.

Changeover information

• CARRY: equipment arriving with the artist;
• SHARED: festival equipment staying in position;
• SWAP: personal items replacing parts of shared equipment;
• PRE-BUILD: rig assembled offstage before the changeover;
• ROLL: riser or package moved as one prepared unit;
• STRIKE: equipment that must leave immediately after the set.

Use a small legend and consistent labels. Color alone is insufficient because printouts, low light, and color-vision differences can remove the distinction.

Build a changeover-ready input list

Keep the artist's logical channel order, but add the information needed to map it to the festival patch.

The festival owns the physical socket assignments; the artist owns the source meaning and priority. Reconcile the two without silently renumbering the reusable input list. Input List vs Patch Sheet explains this distinction.

Flag channels that are:

• essential for the first song;
• artist-supplied and pre-patchable;
• stereo pairs;
• phantom-powered;
• playback, click, cue, or timecode;
• spare or conditional;
• safe to omit only with artist approval.

Plan the changeover sequence

A sequence assigns parallel work instead of giving everyone the same vague instruction to “set the band.”

Only the stage manager or assigned lead should call the transition ready. Side conversations should not replace the agreed command structure.

Shared backline and rolling risers

For shared backline, publish an ownership matrix before the event.

List exact included hardware. “Shared drums” does not say whether the throne, hi-hat stand, cymbal stands, snare stand, or rug is included. The Backline Rider Requirements guide provides the full template.

Rolling risers work only when the route has enough width, correct height transitions, cable slack, brakes, and a safe offstage preparation area. Confirm the riser orientation and final mark on the plot. Do not assume a riser can roll through a cable ramp, narrow wing, or audience path.

Line check and monitor priorities

When there is no full soundcheck, agree on a short verification order:

1. show-critical playback, clock, click, and cues;
2. lead vocal and communication microphone;
3. kick, snare, bass, and core rhythmic sources;
4. featured instruments and remaining vocals;
5. stereo pairs, ambience, spares, and conditional channels.

This is not a universal artistic priority—it is a starting pattern. Put the actual order in the advance notes.

For monitors, verify destination before content: the correct performer must receive the correct mix through the correct wedge or IEM pack. Then confirm essential sources and talkback. A short changeover is the worst time to discover that “Mix 3” means keys in one document and drums in another.

What to confirm in advance

• stage, wing, and pre-build dimensions;
• changeover duration and who controls the clock;
• festival patch and artist input-list mapping;
• console/show-file policy;
• provided microphones, DIs, stands, backline, and risers;
• monitor mix/output availability and IEM integration;
• wireless inventory and frequency-coordination deadline;
• power positions and carried-system requirements;
• load-in path, storage, cases, and after-set strike;
• local crew assignments and artist crew access;
• fallback for late arrival, missing equipment, or shortened transition;
• current live Rider link and dated offline PDF.

Close disagreements as written decisions with an owner and deadline. Use the complete Show Advance Checklist for the wider event handoff.

Pre-send checklist

• Plot shows the final setup and changeover legend
• Carried, shared, swapped, and pre-built gear is distinguished
• Every input has a source, mic/DI, stand, 48V, and patch group
• Monitor destinations use stable mix IDs
• Rolling risers include dimensions and confirmed travel path
• Shared backline includes all small hardware
• Wireless equipment is submitted for coordination
• Power-drop locations match the carried equipment inventory
• The changeover sequence names work owners
• Line-check priorities are agreed
• Current version and production contact are visible

FAQ

What should be on a festival stage plot?

Show performers, equipment, mics/DIs, monitors, power, risers, and directions, plus which gear is carried, shared, swapped, pre-built, rolled, or struck during changeover.

How do bands change over at festivals?

Teams pre-build what they can offstage, clear the previous act, place rolling or labeled packages, connect agreed patch groups, line-check priority channels, verify monitors, clear the deck, and hand readiness to the stage manager.

Should a festival stage plot include backline?

Yes. Show its final position and mark whether each item is festival-provided, artist-carried, shared, or swapped. Put detailed models, accessories, and substitutions in the backline section.

What is a festival patch?

It is the festival's planned mapping of stage sources to its physical inputs and console channels. An artist input list describes the artist's sources; production reconciles that list with the festival patch.

How do you prepare a tech rider for a festival?

Keep the core Rider current, then add festival-specific patch mapping, shared-backline decisions, monitor integration, RF details, power positions, rolling-riser information, changeover sequence, and line-check priorities.

Give the festival one current technical source

Build a reusable Rider in Techrider.live, invite the appropriate editors, and deliver both a current view-only link and a dated PDF for offline festival use.

---

Last updated: 2026-07-16 · Reviewed by the Techrider.live team for multi-act festival advances and fast production changeovers.