Chapter 03 · Service workflows

SERVICE THAT CONNECTS

Information only improves a lounge when it reaches someone who can act. This chapter follows a signal from sensor or request to a finished task, and treats service recovery as a workflow in its own right.

From signal to task

A lounge produces a steady stream of signals: a zone emptied after a boarding call, a buffet tray running low, a washroom check overdue, a guest requesting assistance, a delay pushing dozens of passengers into a longer stay. Each one is information. It becomes service only when it turns into a task with five parts: what needs doing, where, by when, who owns it, and what "done" looks like.

Platforms differ in how they generate tasks — from rules, from schedules, from staff input — but the five parts are the test. A task that lacks an owner is a notification; a task without a done-state never closes.

Partly stocked buffet counter in a dim lounge with soft reflections on metal trays

Common triggers and their owners

Example mapping. Owners and response targets should reflect the operator's own staffing model.

TriggerSourceTypical ownerDone-state
Zone vacated after boardingOccupancy drop + flight feedFloor attendantTables cleared and reset
Buffet item lowStaff report or scale sensorFood and beverageItem replenished, time logged
Washroom check dueScheduleHousekeepingCheck recorded with time
Assistance requestDesk, app or airline messageDuty supervisorHandoff to assistance provider confirmed
Delay over 60 minutesFlight feedShift leadAffected guests informed; service adjusted

Service recovery as a workflow

Recovery is what the team does after something has gone wrong. In lounges, three situations recur: a guest refused at entry who believes they are entitled, a guest who missed or nearly missed a boarding call, and a physical incident such as a spill or a broken seat. Each deserves a defined trigger, a first response, a follow-up and a record.

Disputed entry. Log the reason code from the entry decision, offer the guest a clear explanation and, where the rule allows, a paid alternative. Feed disputes back to whoever owns the entitlement rules; repeated disputes on the same credential type usually signal a data problem, not a guest problem.

Missed boarding call. Many lounges do not announce flights aloud, so guests rely on screens and apps. When a gate change or early boarding is not shown in time, the failure is in the flight-information handoff. Record which flight, what the lounge displayed and when, and pass it to the integration owner.

Physical incidents. Treat them like any other task with an owner and done-state, plus a note of whether a guest was affected and what was offered.

Airports Council International's Airport Service Quality (ASQ) programme, running since 2006, surveys departing passengers on many aspects of the airport experience. Lounge operators often design their own feedback alongside it; linking feedback to the recovery record shows whether interventions actually changed the outcome.

Assistance and accessibility

Passengers with disabilities and reduced mobility have rights to assistance under Regulation (EC) No 1107/2006, with airport managing bodies responsible for assistance within the airport. A lounge is one stop in that chain. The practical requirement is a reliable handoff: the lounge knows the guest is waiting, the assistance provider knows the guest is in the lounge, and the time to collect is agreed. Missed handoffs here have serious consequences and should be reviewed every time.

Protecting staff attention

More alerts do not mean better service. Staff who receive constant low-priority notifications learn to ignore them. Useful practice: group routine tasks into rounds, reserve interrupting alerts for time-critical events, and allow staff to reject or reassign a task with a reason. Choose devices for the job — a handheld for detailed tasks, a wearable for short alerts — and make the language of tasks match the language of the floor.

Quiet lounge corridor with a wheelchair-accessible doorway lit by a soft ceiling light

Shift-lead checklist

  • Every automated task has an owner role, a target time and a done-state.
  • Interrupting alerts are limited to time-critical events.
  • Assistance handoffs are confirmed with the provider, not assumed.
  • Entry disputes and missed calls are logged with reason codes.
  • Recovery records are reviewed weekly against guest feedback.
  • Staff can reassign or reject a task with a reason.

Sources and dates

  1. Regulation (EC) No 1107/2006 concerning the rights of disabled persons and persons with reduced mobility when travelling by air, adopted 5 July 2006.
  2. Airports Council International, Airport Service Quality (ASQ) programme, established 2006.
  3. Directive (EU) 2019/882 (European Accessibility Act), applicable from 28 June 2025.

Next: Systems that exchange