Zone Control in PA Systems: How to Design Audio Zones for a Large Office, Hospital or Campus

The difference between a PA system that works and a PA system that works well is almost always zone design. Getting zones right — defining them correctly, sizing them appropriately, and programming the routing logic for both routine and emergency use — is where experienced PA system designers earn their value. Get it wrong and you end up with a system that broadcasts announcements to the wrong areas, cannot deliver emergency messages to the right zones, or delivers so much audio to so few zones that the system is practically useless.

This guide explains the principles of audio zone design for three of the most demanding PA environments: large offices, hospitals, and campuses. It covers what zones are, how to define them, and how to design the zone matrix logic that routes the right audio to the right place at the right time.

What an Audio Zone Is

An audio zone is an independently controllable group of loudspeakers. "Independently controllable" is the key phrase — it means the zone can receive a different audio source, at a different volume level, and under different routing rules than any other zone in the system.

In a traditional analog PA, zones are defined by speaker line wiring — each zone is a physical cable run from the amplifier to a set of speakers. In an IP PA system, zones are software-defined — any speaker or amplifier connected to the IP network can be assigned to any zone without any wiring changes.

The number of zones in a PA system should be determined by the audio control granularity needed — not by budget minimisation. A 10-zone PA for a 50-floor building is a false economy. When emergencies occur, you need to address specific floors, specific areas, and specific occupancy groups independently. When background music is running, you may want different content in different areas. Each distinct use case is an argument for more zones, not fewer.

Zone Planning Principles

Three principles guide good zone planning: functional differentiation, privacy requirements, and emergency routing.

Functional Differentiation

Different areas of a building have different PA requirements. A hospital's ICU requires calm, factual announcements at controlled volumes. The hospital's public corridors and waiting areas need clear, audible announcements at higher volumes. The cafeteria may run background music during meal times. The helipad and ambulance bay need outdoor-rated weatherproof speakers with high output levels.

Grouping all of these areas into a single zone makes it impossible to serve any of them well. Assigning each distinct functional area its own zone — or its own set of zones — enables appropriate audio management for each context.

Privacy Requirements

Some areas must be excluded from certain announcements. Patient ward areas in hospitals should not receive public paging calls that use patient names or clinical information — privacy regulations (and basic dignity) require that such calls go only to the nursing station. Executive floors in corporate offices may be excluded from general building paging to avoid disruption to senior management during meetings. Server rooms and equipment rooms have no occupants and need no routine PA coverage (though emergency coverage is still required).

Zone design must map these privacy exclusions explicitly. A zone routing rule that says "general paging excludes wards 4A, 4B, ICU, and executive floor" must be programmed into the zone matrix and verified during commissioning.

Emergency Routing

Emergency routing — how the PA system responds to fire alarm, security alarm, or other emergency triggers — must be designed with care because it is the most consequential use of the PA system. Emergency zones should be more granular, not less. When a fire alarm triggers on floor 7, you want to address floors 6, 7, and 8 separately from floors 1–5 and 9 upward. This requires that each floor is at minimum one independently addressable emergency zone.

Emergency zone routing also includes evacuation sequencing logic — the rules that determine which zones receive which messages in what order. This logic should be documented in a zone routing matrix (a spreadsheet showing every trigger event mapped to every target zone and the message/priority assigned) and then programmed into the PA system controller. The zone matrix becomes a design document, a commissioning test document, and an ongoing reference for system maintenance.

Hospital Zone Design

Hospitals are the most demanding PA zone design environment. They combine the requirements of a life safety system (fire evacuation for hundreds of floors of occupied building) with the sensitivity of a healthcare environment (patient privacy, clinical staff communication protocols, noise management for patient recovery) and the complexity of a 24/7 operation (the building never empties, so there is no "unoccupied" state that simplifies zone routing).

Functional Zones in a Hospital

A medium-sized hospital (300 beds, 8 floors) requires at minimum the following zone groupings:

Public zones: Main lobby, outpatient waiting areas, corridors on public floors, cafeteria, and chapel. These zones receive general public paging, visiting hour announcements, and emergency evacuation messages for public areas.

Ward zones (per ward): Each inpatient ward is a distinct zone. Routine paging is not broadcast to wards — only specific calls directed to that ward and emergency messages are received. Volume levels are lower (45–55 dB SPL) to support patient rest.

Nursing station zones: Each nursing station has its own speaker or sub-zone, allowing calls specifically to nursing staff to be targeted without broadcasting to the adjacent ward.

ICU and critical care zones: These are treated separately from general ward zones. Access is restricted. Announcements are limited to direct nursing staff communication and emergency alerts. Volume is controlled tightly.

Clinical staff zones: Operating theatres, procedure rooms, and clinical offices may require paging for urgent calls but must be carefully designed — sudden loud announcements in an operating theatre are dangerous. Some clinical zones use low-volume speakers with simultaneous indicator lights rather than audible-only PA.

Technical and support zones: Pharmacy, pharmacy dispensary, sterilisation units, kitchen, laundry, and maintenance workshops have standard PA coverage for general paging and emergency announcements but not for routine patient-related calls.

External and transition zones: Ambulance bay, main entrance canopy, car park, helipad. These require outdoor-rated high-output speakers and receive emergency announcements relevant to external operations.

Code Call Routing

Hospitals use coded emergency announcements — "code blue," "code red," "code grey" — to communicate emergencies to clinical staff without creating public alarm. The PA zone design must map each code call to the correct zones. A "code blue" (medical emergency) call is broadcast to all clinical staff zones (including wards, nursing stations, and staff corridors) but not to public waiting areas. A "code red" (fire) activates the full life safety PA protocol with evacuation messages to appropriate zones.

Bangladesh Hospital Context

Dhaka's major private hospitals — such as Square Hospital, United Hospital, Labaid, and Ibn Sina — and public hospitals like Dhaka Medical College Hospital present the full complexity of hospital PA design. The largest private hospitals have 400–800 beds across multiple tower buildings, requiring 150–300+ independent PA zones for effective management. SSAL has designed and implemented PA systems for healthcare facilities across Bangladesh, with zone architectures tailored to local clinical communication protocols.

Office Zone Design

A large commercial office PA zone design is simpler than a hospital but still requires careful planning. The key variables are floor plate size, tenancy mix (single-tenant vs. multi-tenant), and the balance between routine paging and emergency function.

Typical Office Zone Structure

Per-floor zones: At minimum, each floor should be one addressable zone. For large floor plates (over 1,500 m² per floor), divide each floor into at least 2–3 zones — typically east wing, west wing, and core (lift lobbies, meeting rooms, reception). This granularity is required for phased fire evacuation (evacuating specific floor sections in sequence) and for multi-tenant buildings where tenants require independent PA control.

Lobby and reception zones: The main lobby, reception, and ground floor common areas are typically higher-volume zones receiving all general paging, visitor announcements, and emergency messages. Background music may run in these areas during business hours.

Meeting room zones: Individual large meeting rooms (boardrooms, training rooms) may be separate zones, receiving scheduled room announcement (e.g., "your meeting in Conference Room A starts in 5 minutes") and allowing privacy mode when confidential discussions are in progress.

Car park zones: Basement and multi-storey car parks require separate zones with higher-output speakers to overcome vehicle noise. Routine PA may include parking guidance announcements. Emergency evacuation of car parks follows a different sequence from the office floors above.

Plant room and service areas: Fire and emergency coverage only — no routine paging.

Multi-Tenant Zone Isolation

In multi-tenant buildings, each tenancy typically requires PA zone isolation — meaning one tenant's paging announcements are not audible to other tenants. This is achieved by defining tenant zones that include only that tenant's floor areas. The building management retains the ability to broadcast emergency messages to all zones regardless of tenancy boundaries — this override capability is a non-negotiable life safety requirement.

Campus Zone Design

University campuses, industrial zones, hospital campuses, and commercial mixed-use developments present zone design challenges that differ from single-building scenarios.

The primary challenge is coordinating multiple independent buildings — each potentially with its own building PA system — into a unified campus communication network. IP PA technology makes this achievable: each building has local IP PA amplifiers and speakers, but all buildings connect over the campus IP network and are managed from a central controller. Zone groups can be defined at the campus level, spanning multiple buildings.

Campus Zone Hierarchy

Building-level zones: Each building is a master zone that can be addressed as a complete unit. "All announcements to Building A" routes to every speaker in Building A.

Floor-level zones within each building: Within each building, floor-level zones enable per-floor addressing — essential for multi-floor emergency evacuation sequencing.

Outdoor zones: Campus walkways, plazas, sports facilities, and external assembly points require weather-rated outdoor columns or horn speakers. Outdoor zones typically require significantly higher output (90–100 dB SPL at 1 metre) to overcome ambient noise from traffic, wind, and large outdoor crowds.

Emergency assembly point zones: Pre-designated emergency assembly points should each have at least one outdoor speaker capable of broadcasting instructions to assembled evacuees — confirming "all clear" or providing guidance on alternative assembly points.

Bangladesh Campus Examples

BUET's main campus in Dhaka spans multiple academic buildings, workshops, and residential halls. A campus PA design for BUET would require 40–60 zones spanning all buildings and outdoor areas. North South University (NSU) in Bashundhara has a concentrated multi-block campus design requiring inter-building IP PA backbone with 80–120 zones across academic, administrative, and student facility buildings.

For Bangladesh EPZ factories and industrial parks — such as those in Ashulia, Gazipur, and Chittagong EPZ — campus PA systems serve both routine production management communication and emergency mass notification requirements under BGMEA and RSC compliance obligations.

The Zone Matrix: Documenting Routing Logic

Every PA system with more than 20 zones should have a formal zone matrix — a structured document that maps every input source and every trigger event to every target zone, with priority levels and message assignments.

The zone matrix takes the form of a two-dimensional table. Rows represent audio sources and trigger events (fire alarm zone 1, fire alarm zone 2, paging microphone 1, background music source 1, code blue call, etc.). Columns represent output zones (floor 1 zone A, floor 1 zone B, floor 2 zone A, etc.). Each cell in the table specifies whether the source is routed to that zone for that trigger event, and at what priority level.

For a hospital with 200 zones and 30 trigger events, this matrix has 6,000 cells. Designing it correctly — reviewing every cell for accuracy — is time-consuming but essential. The zone matrix is submitted to the client for approval before programming begins. It becomes the test document for commissioning (every zone-trigger combination is tested against the matrix). It is retained as part of the as-built documentation for ongoing system management.

SSAL produces zone matrices for every PA system we install. This document-first approach prevents the most common PA system problems — wrong-zone announcements, missed emergency broadcasts, and routing errors that only surface during actual emergencies.

Conclusion

Zone design is the discipline that transforms a collection of speakers and amplifiers into an effective communication system. Whether you are designing a hospital PA serving 400 beds across 8 floors, a multi-tenant office tower requiring phased fire evacuation, or a university campus needing coordinated mass notification across 20 buildings, the zone architecture determines whether the system actually performs when needed.

SSAL's PA system engineers have designed zone architectures for some of Bangladesh's most complex facilities. We bring that experience to every project — from initial zone planning through matrix design, programming, commissioning, and ongoing AMC support.

Talk to Our Expert — Contact SSAL to discuss your PA zone design requirements. We will review your building plans, ask the right questions about your communication requirements, and propose a zone architecture that serves both routine and emergency needs effectively.