Wedding Band Stage Plot: Ceremony, Reception, and Sound Handoffs

TL;DR — A wedding band stage plot should show the exact reception lineup, performer positions, instruments, inputs, monitors, power, PA boundaries, and access space. If the band also covers the ceremony or cocktail hour, document each location as a separate configuration with its own sources, playback, wireless, power, operator, setup window, and fallback. Send the plot with a matching input list and timeline so the venue, planner, and audio provider can coordinate every move.

Table of contents

1. Define every performance location
2. Draw the reception stage plot
3. Build the matching input list
4. Plan ceremony and cocktail audio
5. Advance PA, power, wireless, and access
6. Schedule setup and transitions
7. FAQ

Define every performance location

List the actual event scope before drawing:

• ceremony speech, readers, musicians, and playback;
• cocktail-hour solo, duo, playlist, or ensemble;
• reception band performance;
• speeches, announcements, formalities, and walk-on music;
• DJ or playlist coverage during band breaks;
• recording, video, or stream feeds if separately agreed.

Do not compress these into one diagram when the room, lineup, equipment, or operator changes. Use one named configuration per location and connect them with a production schedule.

Replace generic labels with venue room names. Record indoor/outdoor status, audience layout, usable area, access route, stairs or lifts, weather plan, power availability, curfew, and venue-provided sound restrictions.

Use the show-advance checklist to coordinate contacts, authority, access, timing, and final documents.

Draw the reception stage plot

Draw from the performers’ view and label stage left and right. If there is no raised stage, title the drawing Reception performance area and show its orientation to the audience, dance floor, walls, doors, and service routes.

Place the fixed footprint first

Begin with items that control the layout:

• drum kit and any riser;
• keyboards, amplifiers, and instrument stands;
• lead and backing vocal positions;
• wedges or IEM rack;
• stage boxes, band mixer, or split rack;
• PA loudspeakers only when the band provides or positions them;
• power drops, cable paths, and performer access.

Do not draw décor or venue equipment as if the band controls it. Mark the boundary and identify the team responsible for final placement.

Use measured dimensions when the setup depends on them. Distinguish total platform size from the usable area after stairs, railings, décor, loudspeakers, and access. Follow the stage-dimensions guide instead of claiming one minimum size fits every band.

Keep source names stable

Use labels such as Lead Vocal — Maya, Keys L/R — Devon, and Bass DI — Alex. Repeat those names on the plot, input list, monitor list, console file, and cable labels.

Every source needs a visible destination or input-list reference. Every monitor needs a mix label. Show the IEM rack or wedge position, plus ambience and cue inputs when used. Keep monitors and stands out of guest and performer routes.

For the drawing sequence, see How to Make a Stage Plot.

Build the matching input list

The plot explains position; the input list explains the channel. Include:

• channel and stable source name;
• source connector and signal type;
• microphone or DI and provider;
• stand or mounting requirement;
• stage-box destination where known;
• phantom-power note where relevant;
• monitor destination;
• band and production responsibility;
• concise notes for changes, talkback, or playback.

Example reception-band input list

This is a structure example, not a standard channel count. Expand it for the real lineup and delete unused sources.

Keep ceremony microphones and speech channels in a separate table when a different system handles them. That prevents a reception console number being mistaken for a ceremony receiver or portable mixer input.

Plan ceremony and cocktail audio

Ceremony configuration

Identify:

• officiant, couple, reader, and musician microphone needs;
• wired or wireless ownership and RF coordination;
• playback device, operator, cues, connection, and backup;
• loudspeaker coverage responsibility;
• weather and shelter limits supplied by the provider;
• power and protected cable routes;
• test time before guests enter;
• a simple speech and playback fallback.

Do not promise that one microphone covers every position or that wireless works everywhere. Confirm speaking locations, microphone method, RF environment, weather protection, and operator workflow.

Keep cue titles and file versions in an operator run sheet. The rider should say who supplies the file, who loads it, where it plays, who calls it, and what happens if the primary device fails.

Cocktail configuration

If musicians move, document what travels and what remains set:

Include travel time, stairs, weather exposure, security, repatching, and a new line check. One item cannot serve two rooms at the same time.

Advance PA, power, wireless, and access

Define the PA boundary

State whether the venue, audio company, DJ, planner, or band provides:

• main loudspeakers and processing;
• subwoofers where agreed;
• wedges or IEM infrastructure;
• FOH console and stage I/O;
• microphones, DIs, stands, and cables;
• ceremony and speech systems;
• operators for ceremony, reception, and breaks.

Avoid venue provides suitable PA. Describe audience areas, program, control position, I/O, provider boundary, and confirmation. Use PA System Tech Rider Requirements for detail.

Document power by equipment

Mark every requested drop beside the equipment it serves. Build an inventory from manufacturer labels or documentation and separate band loads from PA, lighting, catering, and venue loads.

Never defeat protective earth, use unsuitable adapters, or run unprotected power across guest routes. The venue or qualified provider controls supply and distribution. See Stage Power Requirements.

Coordinate wireless systems

Inventory band, ceremony, DJ, venue, and video wireless microphones and IEMs. Include system type, channel count, tuning capability from device documentation, provider, antenna location, battery plan, and coordination owner.

Do not publish fixed frequencies before coordination unless requested by the RF lead. Confirm permitted operation for the location and re-coordinate after changes. Use the wireless microphone tech rider for the full checklist.

Protect access routes

Coordinate the plot with the room layout. Keep exits and required egress clear, service doors usable, stands away from traffic, cables protected, drinks away from equipment, and performer entrances open.

The venue and safety team approve the final layout. A stage plot supports coordination; it is not safety approval.

Schedule setup and transitions

Work backward from guest access and performance time:

1. venue access and load-in;
2. room or stage released to production;
3. PA and power ready;
4. backline and patch complete;
5. line check and soundcheck;
6. room reset or décor handback;
7. ceremony and cocktail moves;
8. speeches, formalities, sets, breaks, and DJ transitions;
9. curfew and load-out.

Do not schedule soundcheck while catering, décor, photography, or venue staff need exclusive use of the same area. Name who approves layout changes and who accepts the ready-room handoff.

Transition checklist

• Band and DJ agree on console, PA, and playback boundaries.
• Speech microphones have an operator during band breaks.
• Walk-on and formal-moment cues have an owner and backup.
• Moving equipment has transport, repatch, and test time.
• Unattended instruments have secure storage.
• Planner, venue, and audio provider hold the same schedule.

Pre-send checklist

• Each location has a named configuration.
• Reception positions, inputs, monitors, power, and access are shown.
• Input-list source names match the plot.
• Ceremony speech, playback, wireless, operator, and fallback are assigned.
• PA, console, microphones, DIs, stands, cables, and power ownership is explicit.
• Every vendor’s wireless systems are included in coordination.
• Weather, access, sound, curfew, and venue limits are confirmed.
• Equipment moves fit the schedule.
• Guest, service, performer, and emergency routes remain available.
• The link or file shows the latest revision and contact.

FAQ

What should a wedding band stage plot include?

Show the reception area, audience orientation, performers, instruments, microphones and DIs, monitor destinations, stage I/O, power drops, PA responsibility, dimensions that affect fit, and access. Use separate configurations for ceremony or cocktail locations.

Does a wedding band need a tech rider?

Yes when the event requires coordination between the band, planner, venue, DJ, and audio provider. It can be concise, but should connect the plot, input list, equipment responsibilities, wireless inventory, power, access, schedule, and contacts.

How do you make an input list for a wedding band?

Number each source and record its stable name, connector, microphone or DI, stand, provider, stage input, phantom-power note where relevant, and monitor destination. Match the plot and separate ceremony channels when another system handles them.

How do you plan sound for a wedding ceremony and reception?

Treat them as separate configurations. Define sources, microphones, playback, loudspeakers, wireless, power, operator, weather plan, test time, equipment moves, and fallback for each, then join them with one production schedule.

When should a wedding band send its stage plot?

Send it early enough for the venue, planner, and audio provider to resolve space, access, equipment, power, wireless, and timing. Update it whenever the lineup, room, provider, schedule, or technical scope changes.

Give every location one current plan

Create the wedding band stage plot and input list in Techrider.live, save the confirmed configurations, and share the current Rider with the venue, planner, and audio provider before load-in.

---

Last updated: 2026-08-11 · Reviewed for ceremony, cocktail, and reception configurations, band inputs, PA and power ownership, wireless coordination, venue access, and production transitions.