Line Check vs Soundcheck: What's the Difference?

TL;DR — A line check verifies that every input reaches the correct console channel and every output reaches the intended destination. A soundcheck goes further: the band performs so engineers can set gains, processing, monitor balances, and the room mix. Festivals often allow only a line check; headline shows may schedule both. A correct input list, stage plot, monitor plan, and current rider make either process faster, but neither replaces the other.

Table of contents

1. The difference in one table
2. What happens during a line check
3. What happens during a soundcheck
4. Who needs to be present
5. How to prepare the rider
6. A practical check sequence
7. Common mistakes
8. FAQ

The difference in one table

Line check and soundcheck are related production steps, but they answer different questions. A line check asks, “Is the system connected and routed correctly?” A soundcheck asks, “Does the show sound and feel right with the performers playing?”

A successful line check does not prove that the monitor balance works for the musicians. A successful soundcheck still depends on a correct patch underneath it.

What happens during a line check

The engineer calls sources in the order shown on the input list. Each source produces a clear signal: a drummer hits one microphone at a time, a DI-fed instrument is played, and each vocal microphone is spoken or sung into. The crew confirms that the source appears on the expected channel with a usable level.

A line check normally verifies:

• source name and input number;
• stage box, split, and console routing;
• microphone, DI, or playback output operation;
• phantom power only where the documented device requires it;
• left/right assignment for stereo sources;
• monitor and other output destinations;
• obvious faults such as silence, hum, distortion, or crossed channels.

It is not the moment to perform a full song after every channel. Keep each source isolated until the engineer confirms it, then stop. If the patch differs from the rider, record the approved change so FOH, monitors, and stage crew use the same channel identity.

For the document behind this sequence, see Input List vs Patch Sheet and the input list template guide.

What happens during a soundcheck

During soundcheck, the band plays material that represents the show. Engineers listen to sources together, establish the FOH balance, and shape monitor mixes around actual performance levels. A useful sequence may include a full-band section, the quietest passage, the loudest passage, an instrument change, and any show-critical playback or cue transition.

Soundcheck is used to:

1. set input gains at realistic performance level;
2. build and confirm each wedge or IEM mix;
3. balance the band through the PA;
4. check important solos, vocal changes, mutes, and playback cues;
5. identify acoustic problems or stage-volume conflicts;
6. confirm that performers can hear what they need;
7. save the agreed console state where the system allows it.

An empty room changes once an audience arrives, so soundcheck produces a strong starting point rather than a finished mix for every moment of the show. The FOH engineer continues adjusting during the performance.

Who needs to be present

Presence depends on the workflow and equipment.

If a performer cannot attend a scheduled line check, agree in advance who can safely operate or test that source. Do not ask unqualified crew to handle instruments, wireless packs, hearing equipment, or specialist rigs without permission.

How to prepare the rider

The production documents should let the crew predict the check before anyone arrives. Provide a current stage plot, ordered input list, monitor mix list, playback routing, power notes, and artist/venue responsibility for supplied equipment.

Before sending the rider, confirm:

• every plotted source has the same name and channel number in the input list;
• stereo pairs identify left and right consistently;
• microphone and DI provider is stated;
• phantom-power needs reflect the actual device, not a guess;
• monitor mixes have stable IDs and named performers;
• IEM systems are identified as wired or wireless and artist- or venue-supplied;
• playback outputs distinguish program, click, cues, and spare paths;
• substitutions and festival patch changes are documented;
• the production contact who can approve changes is named.

Share the current link during the advance and keep a PDF available for offline or printed use. If the plan changes, update the source Rider before distributing another export so the crew does not receive two competing versions.

A practical check sequence

Use the input list as the call sheet rather than inventing an order on stage.

1. Confirm the patch version. FOH, monitors, and stage crew identify the same rider revision.
2. Verify outputs and communication. Confirm talkback, monitor destinations, and any required cue path before loud sources begin.
3. Check inputs in order. Work through drums, bass, guitars, keys, playback, vocals, and other sources according to the submitted list.
4. Resolve faults immediately. Stop and identify crossed, missing, noisy, or distorted paths before adding more sources.
5. Check the band together. When time permits, move from isolated signals to representative performance material.
6. Build monitors systematically. Ask one performer and one requested change at a time; keep mix IDs consistent with the rider.
7. Test critical transitions. Include instrument swaps, playback starts, lead changes, and any configuration that changes routing.
8. Record the final differences. Update show notes and the Rider when the confirmed setup differs from the advance.

For a festival with short turnovers, use the festival changeover guide. For the broader production timeline, follow the show advance checklist.

Common mistakes

Treating the terms as interchangeable. Calling a five-minute patch verification a soundcheck creates the wrong expectation for musicians and crew.

Submitting an unordered channel inventory. The engineer should be able to call the list from channel 1 onward without translating nicknames or searching for stage positions.

Playing at an unrealistic level. Whispering through soundcheck and performing loudly later invalidates gain and monitor decisions. Check at representative show level while following venue direction.

Changing several monitor mixes at once. Identify the performer, mix, source, and requested direction: “More lead vocal in Maya’s Mix 2” is actionable; “The monitors are wrong” is not.

Assuming a festival includes a full soundcheck. Advance the available check type and duration. Prepare a line-check-first workflow when the schedule cannot support songs before doors.

FAQ

What is the difference between a line check and a soundcheck?

A line check verifies each signal path, channel, and output. A soundcheck has the band perform so engineers can build FOH and monitor mixes under realistic playing conditions. Line check proves connection and routing; soundcheck evaluates the combined show.

What happens during a line check?

Sources are tested one at a time in input-list order. The crew confirms that each microphone, DI, instrument output, or playback feed reaches the expected channel and that monitor or other output routing goes to the intended destination.

What happens during a soundcheck?

The band plays representative material while engineers set gains, balance sources, refine processing, build monitor mixes, and test important musical or technical transitions. Performers also confirm that they can hear what they need.

How long does a soundcheck take?

There is no universal duration. It depends on channel count, monitor complexity, changeover constraints, shared equipment, venue access, and how accurately the show was advanced. Confirm the scheduled window with production and prepare a prioritized check sequence that fits it.

Do bands always get a soundcheck?

No. Festivals, support slots, and tight schedules may provide only a line check or a brief changeover check. The advance should state what is available so the band can prepare the correct workflow instead of expecting a full rehearsal.

Make the check predictable

Build one current Rider in Techrider.live with the plot, input list, monitor plan, and technical notes the crew needs. Share the current plan before load-in and export a PDF for the day-of-show fallback.

---

Last updated: 2026-07-23 · Reviewed for practical live-production communication.