When Clara opened the confirmation email for Saturday's performance, she did not look first for the row or the entrance. She looked for her sister Eva's name. They had gone out together for years: Clara uses a wheelchair, knows the theatre well, and moves independently in many places, but on a long outing Eva helps carry a spare battery, find an alternative route if a lift fails, and make quick decisions when the environment becomes difficult. The system had assigned Clara the only accessible place in row twelve and Eva a standard seat in row five. On screen, both bookings were marked as correct. In real life, the evening was already asking Clara to bargain over safety, company, and the pleasure of attending.
The problem is not that every seat has been sold. It is that the mechanism treated two related tickets as two separate requests. Many ticketing platforms are designed to fill a seating plan, reduce empty seats, and finish a purchase in a few clicks. Those aims matter, but they do not fully describe what a ticket promises. A cultural reservation also arranges a shared experience: talking before the lights go down, being able to ask for help without calling across rows, and knowing that the person who understands your support needs is nearby. When design automatically separates a person with reduced mobility from their companion, it turns supposed efficiency into a barrier.
A companion is not a sentimental add-on#
One common simplification needs resisting: the idea that everyone who books an accessible space requires constant supervision. That is untrue, and the assumption can be as restricting as ignoring a need altogether. Autonomy includes deciding who accompanies you, when, and in what role. Clara does not give hers up because Eva sits beside her. Choosing a trusted person is part of how she exercises it in a building with slopes, narrow corridors, heavy doors, and evacuation times she does not control.
One common simplification needs resisting: the idea that everyone who books an accessible space requires constant supervision.
Support takes many forms. Someone may need help with a transfer or retrieving stored equipment. Another person may need communication during a pain episode, orientation when leaving through an alternative route, or simply an adjacent seat so they are not separated from a child in their care. Some support is invisible: a friend who notices fatigue, a partner who knows about an allergy, a personal assistant who makes it possible to enjoy a performance without anticipating every obstacle. The system does not need an intimate account to acknowledge this reality. It needs to accept that some functional relationships require proximity as a condition of access.
Calling that a “seating preference” diminishes what is at stake. Preferring an aisle or a particular view is legitimate, but it can be negotiated. Being next to an essential support cannot always be. If the alternative is entering alone, relying on strangers, or giving up the outing, the choices are not equivalent. The interface should represent that difference from the start, just as it distinguishes an accessible place from a conventional one.
The failure begins before payment#
On many booking sites, the accessibility option appears at the end of checkout or behind a telephone number answered only on weekdays. A buyer first selects a performance, then the number of tickets, and only afterwards discovers that an accessible place exists. By then, the algorithm has distributed the rest of the group. If the need is discovered late, the person must abandon the basket, call, explain themselves, and hope that someone can undo what the machine has already decided.
A better journey begins with a short, voluntary question: “Do you need to reserve seats linked by accessibility or essential support?” It does not have to create a medical category. Once selected, the map should show genuinely usable combinations: the accessible place and adjacent, nearby, or agreed sightline seats, rather than scattered gaps that force the buyer to calculate. Where the venue offers several arrangements, the person should be able to choose and understand the practical consequence of each.
The decisive word is linked. It is not enough for a system to store two tickets in the same order. It must preserve an operating rule: these bookings must not be separated during reassignment, a room change, or a waiting-list allocation. Otherwise the relationship disappears at the moment it matters most, such as when a performance moves to a venue with a different layout.
Design the plan for people, not boxes#
A theatre cannot create an accessible space on the day of a performance, but it can decide how to protect the area around that space. Setting aside a wheelchair position while immediately selling every seat next to it is a predictable way to create separation. The answer is not to block half an auditorium forever. It is to define small access units for each room: one accessible place with one or two linkable seats, plus clear rules for releasing that capacity when the date approaches without demand.
Those rules should be public. Audiences understand staged release better than the opaque reply, “nothing is left together.” A theatre can keep linked seats available until a reasonable date, offer them first to the person booking the accessible place, and release unused ones later, while retaining a human route for late cases. That balances the use of the room without making the person who needs support chase exceptions.
Physical detail matters too. “Near” is not always the closest seat on a map. There may be a step, a fixed armrest, a rail that prevents communication, or an exit that requires a long detour. Accessibility and front-of-house staff should walk the venue, record which combinations actually work, and translate that knowledge into the digital inventory. A beautiful map without knowledge of the building merely automates mistakes faster.
When an algorithm cannot decide, it must stop#
No automatic rule will cover every situation. There may be no adjacent seats left, a person may travel with two supports, or the production may change the stage layout. The right response is not to hide the issue behind a generic message. It is to trigger human review with real authority to act.
That review needs a visible timeframe, an accessible channel, and a person empowered to move bookings while comparing options. “Write to this inbox” is not enough if the performance is tonight and nobody can change inventory. The team should be able to offer concrete choices: relocate a small group, open an area held for contingencies, suggest another performance with compatible transport, or refund the payment without penalty if no dignified solution exists. The work of finding one should not fall entirely on the person who has already identified the barrier.
The information requested should be minimal. Asking whether an accessible place is required and how many tickets are linked to it is reasonable. Requiring diagnoses, medical letters, or explanations that do not change the decision is not. The more intimate data a venue accumulates, the more people will avoid asking for support and the greater the risk of mishandling it. Accessibility works better through service rules than through files about private lives.
The test comes with changes and at the door#
A booking can appear sound until something changes. If a theatre moves a performance, closes a row, or substitutes a room, the system must retrieve links before reassigning anything. The notice should say whether proximity is retained, what is offered if it cannot be retained, and how to request correction without starting again. A unilateral change that sends each ticket to a different end of the building breaks a promise the original confirmation made implicitly.
The work continues at the entrance. Front-of-house staff need to see discreetly that seats are linked and know whom to call if the area is occupied or an access route fails. They do not need to know Clara's condition. They need a practical instruction: keep these people together, admit them through the agreed route, and escalate an incident without debating it in front of a queue. Good reservation software does not replace that preparation; it enables it.
Theatre teams can test whether their rule works with straightforward questions. How many linked-seat requests were resolved automatically? How many went to review, and how long did it take? How many separations did a relocation produce? What did affected people say after the performance? These figures should not become a race to reduce requests. They are for finding badly configured plans, inadequate service hours, and decisions that look efficient only on a spreadsheet.
The next time Clara buys tickets, the goal should not be to prove why Eva deserves a seat beside her. She should be able to state the link, see a viable option, and receive a prompt answer when the map cannot offer one. Culture often speaks of encounter and shared experience. That commitment begins with a small decision before the curtain rises: do not separate someone from the person who makes it possible for them to be there calmly and on equal terms.
