Worship Band Stage Plot: Inputs, IEMs, and Playback

TL;DR — A worship band stage plot should map the actual service team: leader, vocalists, drums, bass, guitars, keys, playback, speaking microphones, monitor destinations, power, and cable handoffs. Give every source a stable channel name, keep click and guide cues out of audience and broadcast mixes, and distinguish FOH, monitors, broadcast, and recording responsibilities. For rotating teams, save named configurations and update the current plot and input list before rehearsal.

Table of contents

1. Define the service team
2. Draw the platform layout
3. Build the input and output lists
4. Route playback, click, and talkback
5. Manage IEMs, broadcast, and rotating teams
6. FAQ

Define the service team

Do not begin with the venue’s largest template. List who serves in this event:

• worship leader;
• supporting vocalists;
• acoustic and electric guitars;
• bass;
• drums and percussion;
• keyboard, piano, or organ;
• playback operator;
• musical director;
• choir or additional ensemble;
• speaking positions;
• FOH, monitor, broadcast, and stream operators.

Mark sources that are not present this week. Unused channels may remain in a console file, but the current input list should make active and spare paths obvious.

Use stable role-based names where membership rotates, such as WL Vocal, Vocal 2, EG 1, and Keys 1 L/R. Add the performer name in a separate field. This keeps the console and stage position understandable without pretending every person uses identical equipment.

Draw the platform layout

Show:

• audience or congregation direction;
• each performer and instrument;
• vocal microphone stands;
• drum kit or enclosure footprint;
• amplifiers, modelers, and pedalboards;
• keyboard tiers and laptop/playback station;
• wedges, wired IEM packs, or wireless IEM assignments;
• music or confidence-monitor sightlines;
• lectern and speaking microphones when part of the same production;
• stage boxes and input splits;
• power points;
• stairs, accessibility paths, and emergency routes.

Keep cables and stands away from speaker movement, baptistry access, choir risers, camera lanes, and entrances. A permanent platform can still change when seasonal set pieces, choirs, or special events are installed.

If cameras are used, review sightlines with video production. Do not move musicians solely for the drawing if the new position breaks communication, monitoring, or safe access.

Build the input and output lists

Example source groups

Create one numbered row per console input. Put click, guide, talkback, and ambience channels in the list even when they never reach the audience.

Use one output row per monitor or production destination:

Replace the example with the actual system. The Monitor Console Tech Rider explains how to count stereo buses and physical outputs.

Route playback, click, and talkback

Playback

State:

• playback computer and operator;
• audio interface;
• track or stem count;
• balanced or unbalanced outputs;
• connector and stage input;
• power and network requirements;
• primary and tested backup.

If stems are used, name them by musical function. If FOH receives only stereo playback, the playback operator owns the internal balance.

Click and guide

Click and spoken guide cues must be assigned only to the intended IEM or monitor destinations. Label them clearly:

• Click — monitors only;
• Guide — monitors only;
• Tracks L/R — FOH + broadcast as advanced.

Verify that scenes, sends, matrices, broadcast buses, recordings, and stream feeds cannot accidentally include click or guide.

Talkback

Separate:

• production talkback from FOH or monitors;
• musical-director talkback;
• stage-manager communication;
• speaking microphones intended for the congregation.

Name the destinations and operating method. A talkback channel should not reach FOH or broadcast unless the service design explicitly requires it.

Use Playback Tracks Tech Rider for a detailed backup workflow.

Manage IEMs, broadcast, and rotating teams

IEMs and ambience

For each performer, list mono/stereo format, wired/wireless delivery, bodypack or headphone amplifier, provider, output patch, and safe-level responsibility.

IEM ambience microphones are production inputs, not generic room decoration. State their purpose, position, stand, channel, phantom power, and which mixes receive them. Keep them out of feedback-prone paths unless the engineer intentionally routes them.

Wireless IEM and microphone systems need one RF inventory and a coordination owner. Permanent licensing or frequency assumptions may change with equipment and local spectrum conditions.

Broadcast and recording

FOH and broadcast mixes have different audiences. Document:

• shared inputs or split method;
• preamp and phantom-power ownership;
• broadcast console or mix workflow;
• audience/ambience inputs;
• playback and speech feeds;
• video sync or delay responsibility when relevant;
• recording permission and storage owner.

Do not promise a broadcast mix from a spare FOH output without assigning an operator and listening environment.

Rotating teams

Save a reusable configuration for each common team size, then update:

1. active performers and names;
2. source and channel changes;
3. stage positions;
4. IEM assignments;
5. wireless devices;
6. playback outputs;
7. rehearsal and service times.

Invite the worship leader, production lead, or engineer to edit and save the same Rider and inspect its history. Export a dated PDF for volunteers who need an offline patch reference.

Pre-service checklist

• Active performers and sources match the current service.
• Plot labels and console channels use stable names.
• Stereo sources occupy paired inputs.
• Click, guide, and talkback routing is isolated.
• IEM format, output, pack, and provider are confirmed.
• Wireless inventory and batteries are current.
• FOH, monitor, broadcast, and recording ownership is clear.
• Power, music stands, cameras, and access paths are coordinated.
• Playback backup loads and passes audio.
• The current Rider is available to staff and volunteers.

Common worship-plot mistakes

Using last month’s team. Update people, sources, IEMs, and wireless devices before rehearsal.

Hiding click and guide from the input list. List them and mark their restricted destinations.

Calling every feed “broadcast.” Define source, format, operator, and destination.

Treating personal mixers as self-explanatory. Document input split, network or output path, and responsibility.

Mixing role and person names. Keep a stable channel role and record the current performer separately.

FAQ

What should a worship band stage plot include?

Include every active musician and vocalist, instruments, microphones and DIs, playback, click/guide, monitor destinations, stage boxes or splits, power, music stands, speaking positions, camera and access constraints, and equipment ownership.

How do you make an input list for a worship team?

Create one numbered row for every microphone, DI, instrument output, playback stem, click, guide, talkback, and ambience source. Use stable role names and identify which channels are active for the current service.

How should click tracks be routed for worship?

Send click only to named performer monitor or IEM mixes. Keep it out of FOH, broadcast, recording, lobby, and stream feeds, and verify routing after scene or console-file changes.

Does a worship band need IEMs?

Not necessarily. Wedges, IEMs, or a hybrid can work. Choose according to stage volume, performer needs, budget, available outputs, RF capacity, and operator support, then document every destination.

How do you document rotating worship team members?

Keep stable role-based channel names, record the current performer separately, save common configurations, and update active sources, positions, monitors, and wireless assignments before rehearsal.

Keep the service patch current

Build the worship stage plot and input list in Techrider.live, invite production leaders to edit the same Rider, and give volunteers one current source before rehearsal.

---

Last updated: 2026-07-28 · Reviewed for worship-team inputs, playback and click, IEMs, broadcast, rotating members, and service workflows.