Airport and Station PA System Guide: Halls, Platforms, and Journeys

Follow the passenger journey

Airport and station PA briefs should follow passengers: entrances, check-in or ticket areas, concourses, waiting areas, gates or platforms, and exits, with the sound wanted at each step. Each step hears announcements differently, and the brief should follow the journey rather than listing rooms.

Check-in and ticket areas need announcements that reach people queuing and moving at once. The brief should name queue shapes and movement patterns, because a queue hears differently from a seated waiting area.

Concourses are journey places on a large scale: passengers walking, reading signs, and listening for their gate or platform. Concourse announcements must carry along the walk, not just fill the space, and the brief should mark concourses as journey places.

Gates and platforms are journey ends where passengers wait and board. Their announcements must reach waiting passengers clearly and boarding passengers urgently, and the brief should name both moments separately.

Message types across a journey

Journey sites carry several message types: general notices, gate or platform calls, delay and change notices, and safety messages. The brief should name each type with its zones and its senders, before naming any equipment.

Gate and platform calls deserve their own lines because they are time-critical: passengers must hear them before boarding ends. The brief should name boarding sequences and call timings in plain terms, so the reply can address the time pressure.

Delay and change notices form another type: messages that redirect passengers already on their journey. The brief should name how redirections work — which zones hear them, and how passengers are guided to new gates or platforms.

Safety messages must be briefed apart from routine and journey messages, with their own zones and control rules. Journey briefs that mix routine and safety traffic bury safety, however busy the journey gets.

Noise, crowds, and languages of the journey

Journey sites are noisy: crowds, vehicles, announcements from neighbouring zones, and building systems all compete. The brief should name noise sources per step of the journey, because a design without noise facts will be too quiet where noise is high.

Crowds change through the day: peak departures, quiet nights, holiday surges, and disrupted days each bring different crowds. The brief should name peak patterns and disruption patterns, so the reply addresses the hardest times, not just average ones.

Passengers speak many languages, and the brief should name the language question honestly: which announcements need which languages, and how language versions share zones and time. The brief should ask how multilingual announcements are sequenced, rather than assuming one language fits all.

Accessibility belongs in journey briefs: passengers who need sound most — older travellers, travellers with hearing needs, and unaccompanied children — should be named in plain terms, so seating and placement consider those who need sound most.

Zones that move with passengers

Journey zones move with passengers rather than sitting still. A gate zone grows as boarding nears, a concourse zone shifts as crowds move, and a platform zone empties and fills with each arrival. The brief should describe zones as moving patterns, not fixed rooms.

Zone handover matters on journeys: announcements that start in the concourse and continue at the gate, or start at check-in and continue at the platform. The brief should name handover points — doors, escalators, and corridors — where one zone hands over to the next.

Temporary zones appear during disruption: delayed flights, changed platforms, and crowded halls each create zones that did not exist in the normal plan. The brief should name disruption zones as a pattern, so the reply can address them rather than treating disruption as an exception.

Finally, the brief should name what success sounds like per journey step, in plain terms: check-in calls understood in queues, concourse calls followed along the walk, gate calls heard before boarding ends, and safety messages understood everywhere. Put a post-installation journey check in the brief, so the reply is judged by a walked journey, not by promises.

Writing the airport and station brief

Write the brief as a passenger journey with steps, message types, noise sources, crowd patterns, language questions, and moving zones. End with quantity and target date, and ask for MOQ and lead time for the order.

Ask what to measure in each step and what to check on a sample, and confirm the specification sheet before ordering. Before payment, confirm every term that applies to your order, and confirm that the reply matches the journey and message types in the brief.

Check the reply against disruption: a changed platform and a delayed departure, each with its own messages and zones. A reply that handles only normal journeys has not answered a journey brief. Disruption messages should be written before disruption happens: templates for changed platforms, delayed departures, and crowded halls, each with zones and senders already named. A journey brief that works only on normal days will fail on the first disrupted day; test it against disruption before ordering. Disruption is not an exception for journey briefs; it is the test.

Night operations and quiet hours

Late arrivals, early departures, overnight staff, and cleaning crews all use airports and stations when passengers are few. Night work needs its own roster: late arrivals, early departures, cleaning crews, each with zones and hours. Attach that roster to the brief.

Night zones differ from day zones. A concourse busy by day may be nearly empty at night, while staff areas busy at night may be quiet by day, and the brief should name the night zone pattern separately from the day pattern.

Ask how the site handles the last departure and the first arrival: which areas sleep between them, and which messages wake them. A reply without a between-services plan leaves night staff without guidance.

Night messages form their own type: staff messages, cleaning notices, and the few passenger messages that night travel still needs. A night message sent with day rules will reach the wrong zones; write night rules separately.

Review night operations after every timetable change and every major night disruption, with night staff present. Review questions keep night sound working alongside day sound, rather than forgotten after dark.

Rehearsing the journey plan

Ask for a disruption-day listening report: one delayed departure, every affected zone, with failures written down.

Rehearsal also tests disruption: a changed platform, a delayed departure, and a crowded hall, each practiced with the messages and zone handovers that disruption needs. Name the disruption pattern most likely to fail, and rehearse that pattern first.

Seasonal peaks and disruption seasons

Passenger numbers and disruption frequency move with holiday peaks, festival travel, and storm seasons. Have the reply start from the worst disruption week on record — which messages ran, which zones failed, what changed since — and build the plan from that week.

Related guides

• Wireless PA Systems for Business: A Selection Guide
• Background Music System Design: Zones, Feel, and Rooms