Working context
Reliable sound begins with an understandable signal path. Every source should have a known route through input, processing, mixing, distribution, amplification, and destination. Monitoring and communication paths deserve the same attention because the production team must be able to hear problems, coordinate decisions, and confirm what the audience is actually receiving.
System design should respond to the room, programme, audience, noise limits, equipment, staffing, and safety requirements. A technically impressive component cannot compensate for unclear routing or incomplete testing. Documentation gives specialists a shared reference while preserving room for responsible adjustment during setup.
SECTION 01Map every source and destination
Create an input list with source, connection, channel, required power, stand or mount, performer position, and destination. Document playback, announcements, communications, recording, streaming, assistive listening, lobby, and backstage feeds where applicable. Label physical and digital paths consistently. Confirm who supplies each component and which conversions, adapters, networks, or clock relationships are required.
SECTION 02Build gain and coverage deliberately
Set gain structure so useful level is achieved without unnecessary noise or clipping at any stage. Coverage should be evaluated across the occupied audience area, including front, rear, sides, balconies, and accessibility positions. System processing and level choices must respect equipment capability, local limits, hearing safety, the programme, and the venue. Measurements support judgment; they do not replace listening in the room.
SECTION 03Test the complete operational chain
Line checks confirm connectivity; sound checks confirm musical and programme needs; show checks confirm cues, playback, communications, transitions, recording, and fallback. Test mute states, power-up and shutdown order, emergency communication, and the response to a missing source or failed path. Changes should be documented so the final operating state remains understandable to the responsible team.
Checks to carry into the decision
- Document every source, connection, channel, and destination.
- Confirm ownership of equipment, power, networking, and conversion needs.
- Evaluate gain, noise, headroom, coverage, and applicable level limits.
- Test monitoring, communications, recording, and playback paths.
- Prepare and label the minimum safe fallback for critical signals.
How to get the most from it
Use the guides as a shared reference for the whole production team, and adapt every checklist to the venue's own rules, the artist's technical rider and the local licence conditions.
Common questions
Questions readers ask
Is a line check the same as a sound check?
No. A line check proves that expected paths pass signal. A sound check evaluates level, tone, balance, monitoring, coverage, programme needs, and operating workflow.
How much redundancy is appropriate?
Prioritise paths whose loss would stop safe communication or the essential programme. Redundancy should be understandable, tested, and operable by the available team.
Who decides acceptable sound level?
The responsible production and venue teams must work within applicable rules, safety requirements, programme needs, and audience context. A single meter reading is only one part of that decision.
Bringing it together
A reliable audio system is one that the team can explain, test, operate, and recover. Clear signal documentation turns isolated technical choices into a coherent production system.
These field notes are general live-production education; rigging, electrical, crowd-safety and licensing decisions rest with the venue, competent persons and the relevant local authority.
