Define a zone by its purpose
A sound zone is an area with a stated listening requirement. It might receive the main-stage programme, independent background music or a local demonstration. Two areas using the same playlist can still need separate level control. Two different playlists do not automatically create two acoustically separate spaces.
Start with activities and draw boundaries on the venue plan. Then ask the sound supplier how to provide the sources, control and physical coverage each area requires. Q-SYS describes systems with zone source selection and output-level controls, illustrating that these are separate decisions. Its music and paging overview shows these functions.
Build a source-to-zone matrix
List sound sources down one side and destination areas across the top. Mark when each source is heard, who can change it and whether it replaces another source. Keep ordinary programme announcements distinct from the venue's emergency arrangements, which must be coordinated separately.
| Source | Stage audience | Lounge | Demonstration area |
|---|---|---|---|
| Main-stage microphones | During stage sessions | Only if a relay is agreed | Off during local demonstrations |
| Background playlist | Arrival and breaks | During agreed lounge periods | Off while the demonstrator speaks |
| Local demonstration microphone | Off | Off | During demonstrations |
| Programme announcement | As scheduled | As scheduled | As scheduled, with local session coordination |
The matrix prevents vague instructions such as “everything everywhere”. It also reveals the number of independent source and control paths the technical design needs, without prescribing a particular mixer.
Worked example: conference, networking and demonstration
Imagine a hypothetical event with a main room, an adjoining lounge and a product area along an open corridor. The lounge should support conversation. Demonstrations last ten minutes and begin during conference breaks. The same background music is wanted in all three areas before opening.
At arrival, all areas receive the playlist with separately agreed levels. At the start of a presentation, stage music stops; lounge music remains according to the programme, and the product microphone stays off. During the break, the product demonstration starts, so its local music stops while the lounge continues independently.
Now check the open corridor. If the demonstration makes lounge conversations difficult, separate mixer channels alone will not fix the physical overlap. Ask whether the demonstration area can be turned, moved or scheduled differently. Test the boundary with both activities running. Record the resulting arrangement as part of the event plan.
Do not confuse relay speakers with independent content zones
Additional speakers serving distant listeners may carry the same live programme as the main system. Their timing needs technical attention where listeners hear more than one source. Q-SYS documents delay processing used to compensate for loudspeaker placement. Its delay reference describes the function. The technician should determine settings for the actual layout; the organiser should identify the overlap areas and request a listening check.
An independent lounge playlist is a different requirement. It needs the intended source routing, operating rules and boundary review. Describe which of these jobs each speaker group performs so a quotation does not assume that every extra speaker is merely a duplicate of the stage feed.
Give control a clear owner
Decide whether one operator manages all zones or local staff receive limited controls. List what local staff may change: source, level, start/stop or a named scene. Avoid several people adjusting the same area without a shared reference.
Agree how the stage manager requests a programme announcement and what happens in each zone when it starts. If a zone is temporarily closed, name the person who disables its programme audio and restores it. These are small operational decisions with visible consequences for the guest experience.
Check boundaries and simultaneous use
Test each zone alone with its real microphone or playback source.
Run the busiest combination of activities together.
Listen at entrances, shared corridors and conversation tables.
Confirm planned transitions and the return to local sources.
Show each authorised operator the controls they will use.
Record the final routing matrix, zone names and responsibilities.
Common mistakes are drawing boundaries that sound does not respect, specifying independent levels without independent content, and testing zones only one at a time. Discuss the complete design through AV rental and include technical support for the required changes and monitoring.