Band Soundcheck Checklist: A Step-by-Step Live Sound Workflow

TL;DR — A useful band soundcheck verifies the finished signal path, sets stable input gain, builds performer monitor mixes, balances the audience mix, tests show-critical cues, and records the final state. Start from the current stage plot and input list. Check one source at a time before playing full songs, fix routing before tone, save the approved console state, and write any changed channel, position, or responsibility back into the Rider.

Table of contents

1. Prepare before the band plays
2. Use the right soundcheck order
3. Check each input
4. Build monitor mixes
5. Check the full band at FOH
6. Test show-critical moments
7. Save and hand off the result
8. FAQ

Prepare before the band plays

A soundcheck is not the first moment to discover what the show contains. Begin with the current stage plot, numbered input list, monitor mix list, and production schedule. Confirm that the documents describe the equipment actually on stage.

Before sending audio, verify:

• every performer and source is in the expected position;
• microphones, DIs, stands, playback outputs, and backline match the input list;
• input numbers, stage-box sockets, console channels, and source names agree;
• phantom power is applied only where the connected equipment requires and accepts it;
• wedges and IEM outputs reach the named performers;
• PA, fills, delays, and system processing are released for use by the responsible engineer;
• talkback works between the people who need it;
• console outputs are at a safe starting state;
• the person leading the check and the person approving each mix are known.

If this verification has not happened, run a line check first. A line check proves that sources reach the intended destinations. Soundcheck then evaluates gain, monitoring, balance, tone, dynamics, and the musical workflow.

Assign one voice to lead

Choose one person—normally the FOH engineer, monitor engineer, or production lead—to call sources and transitions. Musicians should answer briefly, play when asked, and stop when the next instruction arrives. With separate FOH and monitor consoles, agree whether the monitor engineer or FOH engineer leads the input sequence.

Avoid several people giving simultaneous instructions over the PA, talkback, and stage. A single sequence makes faults easier to isolate and preserves limited soundcheck time.

Use the right soundcheck order

There is no universal instrument order, but the sequence should follow the patch logically and let engineers build from individual sources to the ensemble.

For a conventional band, an efficient input order might be drums, percussion, bass, guitars, keyboards, playback, instruments, and vocals. Following numbered input-list order is often clearer than inventing a new sequence. Check audience or playback microphones only when they are part of the actual show.

Check each input

Ask for a realistic performance level, not a timid tap followed by a much louder show. Each musician should play a repeatable passage long enough for the engineer to set gain and listen for noise, clipping, vibration, spill, or an incorrect patch.

For every source:

1. Call the channel number and stable source name.
2. Confirm the expected microphone, DI, connector, and stage-box input.
3. Listen through the relevant console path with outputs controlled safely.
4. Set input gain from the loudest realistic performance level with usable headroom.
5. Confirm polarity or paired-channel behavior where it matters.
6. Verify the source reaches its required FOH, monitor, recording, or stream destinations.
7. Label the console channel to match the input list.
8. Mark faults or substitutions instead of relying on memory.

Solve routing and connection faults before applying corrective EQ. If a source is missing, follow the live sound signal flow from instrument to microphone or DI, cable, stage box, split, console input, bus, output, and destination. Change one part at a time so the cause remains visible.

What musicians should play

Use material that represents the show:

• drummers play each drum and cymbal separately, then a full-kit groove;
• bassists and guitarists use their normal show output and test meaningful level changes;
• keyboard and playback operators test every required output, not only one patch;
• vocalists sing at performance intensity and hold the microphone as they will onstage;
• performers test instrument swaps, mute states, pedals, or wireless packs that alter the path.

Do not spend the whole check playing complete songs. Short, repeatable sections give engineers time to listen and communicate.

Build monitor mixes

Build monitors after the relevant inputs are stable. Work performer by performer or destination by destination, using the named mix list from the Rider.

Start with the source each performer needs for pitch, timing, or cues, then add supporting sources. Ask for one change at a time using a source name and direction: “more lead vocal in mix 2” is more actionable than “my monitor is bad.”

For each wedge or IEM mix, confirm:

• output number and performer name;
• wedge position or IEM transmitter and pack assignment;
• pre-fader or other intended send behavior;
• essential sources such as vocal, instrument, click, cues, or talkback;
• stereo linking and left/right orientation when used;
• limiter, output level, and mute state under the responsible engineer's control;
• whether the mix remains usable during full-band playing.

Use the monitor mix guide to keep destinations tied to performers and stage positions. Avoid copying one mix to everyone without checking individual needs.

Check the full band at FOH

Once inputs and basic monitors work, play representative sections of one or two songs. Choose material that exposes the show's real demands: the loudest chorus, a quiet opening, dense playback, lead-vocal changes, solos, or an arrangement with many open microphones.

FOH should check:

• lead elements remain intelligible;
• low-frequency sources work together;
• vocals stay stable when the band reaches show level;
• panning and stereo sources translate across the audience area;
• buses, groups, effects, scenes, and mute logic follow the arrangement;
• required fills or zones receive the intended mix;
• monitor changes do not create feedback or distract performers;
• the mix has headroom for the actual performance.

When practical, listen from more than one audience position. The FOH position is a control point, not proof that every seat sounds identical. System coverage problems belong with the responsible system engineer; channel balance and creative mix decisions belong with the mix engineer.

Test show-critical moments

Spend remaining time on exceptions that can stop or derail the show:

• walk-on, intro, and outro playback;
• count, click, cue, or musical-director talkback paths;
• lead-vocal handoffs or guest microphones;
• instrument, cable, or wireless pack changes;
• acoustic-to-electric changes;
• solos that require scene, mute, or level changes;
• audience participation microphones where planned;
• emergency playback or spare vocal microphone;
• recording or livestream feeds that the production has approved;
• the first song and any no-pause transition.

Test only workflows the show actually uses. Avoid consuming time on speculative feeds or features while a required cue remains unchecked.

A compact full-band check

When time is short, prioritize in this order:

1. lead vocal and essential timing sources;
2. complete patch and safe gain;
3. every performer's essential monitor needs;
4. full-band balance at show level;
5. first song, playback, and critical transitions;
6. a recoverable saved state and written exceptions.

Short time does not justify guessing about an unsafe or missing path. Escalate what cannot be verified and agree on the fallback before doors.

Save and hand off the result

The check is not complete until its result can survive the gap before the performance.

Record:

• console scene or show-file name, save time, and responsible owner;
• input-list revision used during the check;
• changed channels, stage positions, patches, monitor destinations, or equipment;
• approved substitutions and who accepted them;
• muted, disconnected, or unavailable sources;
• outstanding faults and the fallback for each;
• who may change the console or stage after soundcheck;
• the line-check plan immediately before the set, if required.

Save deliberately and protect shared-console workflows from accidental recall or overwrite. A console file does not replace readable show documents.

Update the same Techrider.live Rider when the physical setup differs from the plan. Invite the bandleader, engineer, or tour manager to edit and save the Rider, then inspect history when a decision needs tracing. Give the venue the current link and keep a dated PDF available for offline handoff.

Pre-show soundcheck checklist

• Stage plot, input list, and monitor list match the installed setup.
• Every required input reaches the correct channel and destinations.
• Gains were set from realistic performance levels.
• Every performer approved an essential monitor mix.
• The band played representative loud and quiet sections.
• Playback, cues, talkback, changes, and the first song were tested.
• Faults, substitutions, and unverified paths have owners and fallbacks.
• The approved console state is named, saved, and protected.
• Rider changes were recorded and shared with the relevant crew.
• A pre-set line check is scheduled when the stage may change.

FAQ

What should a band soundcheck include?

A band soundcheck should verify every required input, establish stable gain, build and approve monitor mixes, balance representative full-band material at FOH, test critical cues and changes, and save and document the final setup.

What order should you soundcheck a band?

First confirm the system and patch, then check individual inputs in a clear order, build monitors, hear related sections, play the full band, and test show-specific exceptions. Following the numbered input list usually reduces confusion.

How long should a band soundcheck take?

The required time depends on channel count, monitor complexity, carried equipment, changeovers, and how much was verified in advance. Plan from the actual workflow rather than assuming one duration fits every show, and agree on priorities if the schedule changes.

What should musicians play during soundcheck?

Musicians should play repeatable material at realistic show intensity. Start with individual sources, then use short song sections that represent loud, quiet, dense, and cue-dependent moments. Test meaningful instrument, patch, or level changes.

What should you check after soundcheck?

Confirm the console state is saved and labeled, changes are written into the Rider, faults have owners and fallbacks, shared equipment is protected, and any pre-set line check is assigned. The crew should know which version is authoritative.

Turn the check into a repeatable handoff

Create a reusable Rider with Techrider.live, keep the stage plot, input list, and monitor destinations together, and invite your engineer or tour manager to edit and save the final soundcheck changes before sharing the current link.

---

Last updated: 2026-08-25 · Reviewed by the Techrider.live team for practical band, FOH, monitor, and production handoffs.