What Is a Line Check?

Check the Connection Before the Performance

A line check asks whether the source being checked is present where the audio team expects it. A named channel is not proof that the connected microphone or playback output is the intended source.

It is a focused verification step within the wider live-sound workflow. The aim is to find connection and identity problems before they consume the time intended for performers and programme checks.

Start With the Current Input List

Use the current input list and the agreed patch information. Confirm the source identity rather than assuming an input number always equals a physical socket number. Console routing and stage connections may use different mappings.

When the working patch differs from the document, clarify which is correct and update the relevant records. A handwritten change that only one person knows about can create another problem at the next handover.

Check One Source at a Time

The audio team needs an identifiable signal from the source under test and a way to confirm where it arrives. Use a suitable agreed test for the particular source. Simply seeing activity on a meter does not establish that the channel contains the right source.

Check stereo or multi-output sources according to their intended identities. A signal arriving on one input does not prove every required output has been connected. The details depend on the system and programme.

Inputs and Destinations

Agree the scope of the check. Confirming console input identity is not necessarily the same as confirming every output, monitor feed, recording feed or remote connection. Relevant destinations may need their own checks.

Keep test activity under the audio team's control. Do not introduce unexpected signals into live audience or performer outputs. Equipment settings and connection methods should follow the responsible engineer's plan and manufacturer guidance.

Line Check vs Soundcheck

A line check focuses on signal presence, identity and the intended connection path. Soundcheck checks the working performance with performers, monitoring, programme and venue. A successful connection check does not establish a usable performer mix or an appropriate audience balance.

Line check, soundcheck and rehearsal answer different questions. Rehearsal tests programme delivery, timing and cues. The activities may overlap on a small event, but one should not silently stand in for all three.

What a Line Check Can Reveal

The team may find an absent source, a connection assigned to the wrong input, an unexpected channel identity or a signal that needs further investigation. Communicate the observed problem and the affected source rather than assuming the cause.

This article does not prescribe a troubleshooting sequence or technical settings. The responsible audio team should investigate according to the equipment and system involved.

Record What Is Still Unresolved

Keep unresolved inputs visible, including who will investigate them and which later check depends on their resolution. A channel should not be marked ready simply because the problem was mentioned.

If equipment is repatched or replaced, review the affected checks. An earlier result applies to the connection and configuration that were actually tested, not to every later variation.

A Connection Check Is Not Show Readiness

A line check is useful because it separates basic connection verification from broader performance preparation. It can make soundcheck more productive, but it cannot remove the need to test the requirements the show actually has.

Signal present is a useful result. It is not, by itself, a ready production.