Privacy and preparation
Travel accessibility request handling data: when a person must decide
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Route an accessibility or special-assistance request to a person when it falls under a rule with its own notice terms, depends on another booking or company, rests on an unverified reservation state, or is disputed. Only repeats of a service already confirmed on an unchanged segment or stay should close automatically. Record the rule, timing, dependencies and reason for each route so the history can train or test an agent.
Redaction
Travel accessibility request
Key takeaways
- Air and lodging accessibility rules limit when a business may demand notice, so a late request is a trigger for human review, not a refusal.
- Most hard cases come from dependencies: a new operating carrier, a smaller aircraft, a lost hotel night or a moved transfer.
- Store service codes such as WCHR, WCHS and WCHC or room feature categories, never the medical reason.
- A usable record carries booking scope, timestamps, the rule reference, dependencies, verified state, authority, route with reason and outcome.
- Automation should close only repeats of confirmed services with nothing upstream changed.
How should hospitality tasks route accessibility and special requests for human review?
Route a request to a person whenever one of four tests fails: the request falls under a rule with its own notice or timing terms, it depends on another booking or another company, the current reservation state has not been confirmed in the system of record, or the traveler disputes an answer. Only a request that passes all four, and repeats a service already confirmed on an unchanged segment or stay, should close without a reviewer.
That rule matters for data as much as for operations. A history of accessibility requests is only useful for training or evaluating an AI agent if each record shows which test decided the route, which rule version applied and what the reservation looked like when the decision was made. A pile of free-text notes saying "wheelchair requested" teaches a model nothing about when to stop and hand off.
This guide sets out the task brief a travel agency, tour operator, hotel group or airline servicing team can use to label those decisions, a worked disruption case and the fields that should never leave the record.
Why a late accessibility request is not a reason to decline
Accessibility requests sit under rules that limit when a business may demand notice, so an agent that applies an ordinary cutoff will get them wrong. Under the U.S. Air Carrier Access Act rules, a carrier generally may not require a passenger with a disability to give advance notice to obtain required services. Section 382.27 lists the exceptions where up to 48 hours of notice and a check-in one hour before the general public may be required, such as hooking up a ventilator or CPAP machine to aircraft power, transport on a stretcher, an electric wheelchair on an aircraft with fewer than 60 seats, and groups of ten or more passengers with disabilities.
Even when notice was required and missed, the same section says the carrier must still provide the service if it can do so with reasonable efforts and without delaying the flight. In the EU, Regulation 1107/2006 ties full airport assistance to notification at least 48 hours before the published departure time, requires the carrier or tour operator that receives it to pass it on at least 36 hours before departure, and still requires the airport to make all reasonable efforts when notice is late, as the Commission's 2024 interpretive guidelines explain.
Hotels have a different rule set. The Justice Department's ADA Title III regulation at 28 CFR 36.302(e) covers reservations made by any means, including through a third party, and requires a place of lodging to describe accessible features in enough detail for a guest to judge whether a room meets their needs, hold accessible rooms until other rooms of that type are rented, and block a reserved accessible room so it is removed from all reservation systems.
The practical consequence for a task design: "too late" and "not available" are never final answers the model may give on its own for these requests. They are triggers for a person with authority to decide what reasonable effort looks like.
Which parts of a request can be coded, and which must stay in the traveler's words?
Code the service the traveler needs and keep the reason out of the record. Airlines already do this through special service request codes: IATA's best practices document on SSR codes and assistance services describes WCHR for a passenger who can manage steps and walk to the seat but needs a wheelchair for distance, WCHS for one who cannot manage steps but can reach the seat, and WCHC for one who is immobile and must be carried to the cabin seat, with the approved list set out in IATA Resolution 700.
Hotels have no single industry code list, so the brief uses the categories the ADA guidance names for describing a room: room type, number of beds, type of bathing facility and communication features. Anything outside those categories stays as the traveler wrote it and goes to a person, because it is exactly the kind of request a model will misread.
| Request family | How to record it | Rule anchor to store | Automation ceiling |
|---|---|---|---|
| Airport wheelchair assistance | SSR code (WCHR, WCHS or WCHC) per segment | Part 382 or Regulation 1107/2006, by itinerary | May confirm on an unchanged segment; changes go to a person |
| Battery-powered mobility aid | SSR code plus device type and battery type, no diagnosis | 382.27 notice list; carrier dangerous goods procedure | Always a person, because aircraft size and battery rules decide carriage |
| Respiratory device in the cabin | Device type and need for aircraft power | 382.27 notice and check-in terms | Always a person |
| Accessible hotel room | Room type, bed count, bathing type (roll-in shower or tub), communication features | 28 CFR 36.302(e) hold and block duties | May confirm a held room; a substitution goes to a person |
| Service animal | Animal present, carrier form status | Carrier forms under Part 382 where used | Form check may be automated; any refusal goes to a person |
| Free-text need outside a code | Traveler's words, minimized before storage | None until a person classifies it | Always a person |
The request handling task brief: ten fields that decide the route
The brief below is the asset. Each row is a field a labeled record must carry before a routing decision can be checked; the example values are illustrative. A record missing any of the first eight fields cannot be scored, because the correct route depends on it.
- Reason code AUTO-REPEAT: same code, same operating company, unchanged segment or stay, already confirmed.
- Reason code HUMAN-RULE: the request is on a notice list or inside a notice window.
- Reason code HUMAN-DEPENDENCY: a linked booking, partner or room block changed or is unconfirmed.
- Reason code HUMAN-STATE: the system of record could not be read or disagrees with the itinerary shown to the traveler.
- Reason code HUMAN-DISPUTE: the traveler objects to an answer or asks for a supervisor.
- Reason code HUMAN-FREETEXT: the need does not map to a code or feature category.
| Field | What it holds | Why it decides the route | Illustrative value |
|---|---|---|---|
| booking_scope | Every segment, stay and transfer the request touches, with marketing and operating company | A request on a codeshare or packaged trip must reach the company that delivers the service | 2 air segments, 1 hotel stay, 1 transfer |
| request_code | SSR code or hotel feature category, never a diagnosis | Determines which rule and which handler apply | WCHC on both air segments |
| received_at | Timestamp the request first reached any party in the chain | Notice windows run from first receipt, not from when the request reached the right desk | Illustrative: 70 hours before departure |
| service_time | Published departure, check-in or arrival time | Needed to compute the notice window | Departure 09:40 local |
| rule_ref | Jurisdiction, regulation section and the version in force | U.S. and EU air rules and hotel rules use different windows and duties | 14 CFR 382.27; Reg. 1107/2006 Art. 6 and 7 |
| dependencies | Linked bookings, partner carriers, room blocks, ground handlers | A change to one item can void a confirmation on another | Hotel night 1 depends on arrival segment |
| state_verified | System of record checked and time of check | An agent must not act on a cached itinerary | Reservation system read 10:05, ticketed |
| authority | Who may approve the change: traveler, named delegate, travel manager | A delegate may change dates but not disclose new health details | Traveler self-booked |
| route_and_reason | Auto-confirm or human review, with one reason code | The label a model is trained or scored on | HUMAN: operating carrier changed |
| outcome | What was confirmed, by whom, and the message sent | Lets an evaluator check the decision against what happened | Re-sent to operating carrier, confirmed |
Which dependent booking or purchase-time condition limits the change?
The dependency, not the request itself, is usually what makes a case hard. In the EU rule the duty to transmit assistance information runs from whoever received the notification to the airports and the operating carrier, so a rebooking onto a partner-operated flight creates a new transmission duty even though the traveler never asked for anything new.
Aircraft changes matter in the same way. Part 382 puts an electric wheelchair on an aircraft with fewer than 60 seats on the advance-notice list, so a disruption that swaps a mainline aircraft for a regional one can turn a routine request into one that needs a person and the carrier's equipment rules.
On the hotel side, the ADA rule requires a reserved accessible room to be blocked and removed from all reservation systems. When an arrival slips past midnight and a night is lost, or a property relocates guests because it is overbooked, the record has to show whether the accessible room was held, released or substituted, and who decided.
Fare and rate rules also travel with the booking. A non-refundable rate or a fare that forbids a carrier change does not remove an accessibility duty, but it does limit what an agent may offer, so the purchase-time rule belongs in the dependency field rather than in the agent's head.
Worked example (illustrative): one canceled flight, three dependent requests
This case is invented to show how the brief labels a disruption; it does not describe a real traveler or company. A traveler booked through an agency has WCHC on two connecting flights, a hotel room with a roll-in shower for the first night and an accessible transfer. The first flight is canceled about 30 hours before departure and the traveler is rebooked onto a partner-operated regional flight that arrives five hours later.
- Notice timing: the rebooking happened inside a 48 hour window, which under the EU rule does not end the airport's duty to make reasonable efforts; the record stores the received_at of the original request, not the rebooking time.
- Outcome to record: four human-reviewed items, one automatic check, each with who confirmed and when. Counts here are illustrative.
- What a model should learn: a disruption fans out into separate dependency checks, and copying a code into a new segment is not the same as the operating company confirming it.
| Step | What the record shows | Test that fails | Route and reason |
|---|---|---|---|
| Rebooked first segment | Operating carrier changed; WCHC copied by the system but not confirmed by the partner | Dependency and state | HUMAN-DEPENDENCY: re-send to operating carrier and confirm |
| Connecting segment | Same carrier and flight, connection time shortened | Dependency on the new arrival time | HUMAN-DEPENDENCY: confirm the connection assistance still fits |
| Hotel night 1 | Arrival now after the property's late-arrival cutoff; accessible room at risk of release | Dependency on the hotel's hold of the reserved room | HUMAN-DEPENDENCY: ask the property to keep the specific room |
| Accessible transfer | Pickup time no longer matches arrival | Dependency on the new arrival | HUMAN-DEPENDENCY: rebook transfer with the vehicle type |
| Return flights | Unchanged, same carrier, WCHC already confirmed | None | AUTO-REPEAT: no action, log the check |
When can automation close a request without a person?
Only when the request repeats something already confirmed and nothing it depends on has changed. A returning guest whose profile asks for an accessible room type at a property that has already confirmed a held room for these dates is a fair automatic close; so is a return flight on the same operating carrier with the same code already acknowledged.
The exception runs the other way too. A request that looks routine but arrives with medical detail the service does not need, such as a diagnosis in a message about a room, should go to a person even though the service is standard, because someone has to minimize the record before it is stored or reused. Treat the content of the message, not just the code, as a routing input.
What the request record should leave out
Keep the service need and drop the reason for it. Disability information is health information: under Article 9 of the EU General Data Protection Regulation, processing data concerning health is prohibited unless one of the listed exceptions applies, and U.S. state privacy laws and company policies impose their own limits. A record that says WCHC on segment 2 supports the routing decision; a record that names a condition adds risk and no training value.
Before any history is reused for AI work, remove traveler names, contact details, record locators, loyalty numbers, payment data and free text that describes health, then check what remains. Reservation exports often carry passenger names inside remarks fields and old messages, so search those fields rather than relying on column names.
Separate the questions a reviewer must answer. Access to a reservation system is not permission to reuse the data; privacy permission for the traveler's information is a different question from who owns the records, and both differ from whether contracts with carriers, global distribution systems and hotel partners allow licensing. De-identification does not by itself create a right to license.
What this brief cannot decide, and who should
The brief labels routing; it does not decide what reasonable effort means for a given airport, aircraft or property. Those calls belong to the carrier's or property's own accessibility specialists. For U.S. carriers, Part 382 requires a complaints resolution official to be available at each airport the carrier serves during all times it operates there, with authority to overrule other personnel except that a pilot-in-command's safety decision need not be countermanded; a dispute in the record should show whether that official was reached.
Battery and dangerous goods questions for mobility aids need the carrier's own procedures. Questions about whether a particular agreement allows reuse of reservation or guest data need counsel. A travel or hospitality operations expert and a privacy reviewer should check any labeled set built from this brief before it is used.
Licensing accessibility request histories
Well-labeled request histories, with the route, the rule reference and the dependency recorded for each decision, are the kind of operational records AI developers use to test whether a servicing agent knows when to hand off. A travel or hospitality business can license such histories through SourceX, which takes them through rights review, contracting, preparation, delivery and payment and has the records de-identified by SourceX through approved processing routes.
Request records move only after the operator approves the scope and signs, and a short company assessment with no uploads tells it first whether it qualifies.
Frequently asked questions
Can an airline refuse a wheelchair request because it arrived late?
Generally not. U.S. rules bar carriers from requiring advance notice for most disability services, and even where 48 hours of notice may be required, the carrier must still provide the service if it can with reasonable efforts and without delaying the flight. A late request should go to a person, not to an automatic refusal.
What are WCHR, WCHS and WCHC?
They are IATA special service request codes for wheelchair assistance. WCHR covers a passenger who can manage steps and walk to the seat, WCHS one who cannot manage steps but can reach the seat, and WCHC one who must be carried to the cabin seat. Storing the code instead of a medical reason keeps the record useful and smaller.
Does a hotel have to hold an accessible room booked through a third party?
The ADA Title III rule covers reservations made by any means, including through a third party, and requires a reserved accessible room to be blocked and removed from all reservation systems. Whether a specific third-party channel met its own duties is a question for the property and its counsel.
Should a disruption rebooking reuse the original assistance request?
It should carry the original request forward with its original timestamp, but it should not be treated as confirmed. A new operating carrier, aircraft or arrival time is a new dependency that someone has to confirm with the company that delivers the service.
What should be removed before request histories are used to train an AI agent?
Traveler identity, contact and payment details, record locators, loyalty numbers and any free text describing health. Keep the service code, the timing fields, the rule reference and the routing decision, and have a privacy reviewer check remarks fields, which often hide names.
Sources
- Carriers generally may not require advance notice for disability services; 382.27 lists exceptions allowing up to 48 hours of notice and one hour earlier check-in, and requires the service to be provided with reasonable efforts if notice is missed. Source
- U.S. carriers must make a complaints resolution official available at each airport they serve during all times they operate there, with authority to overrule other personnel except a pilot-in-command's safety decision. Source
- 28 CFR 36.302(e) requires places of lodging, for reservations made by any means including third parties, to describe accessible features, hold accessible rooms and block reserved accessible rooms from all reservation systems. Source
- The Justice Department's ADA Title III regulation and guidance describe accessible room information such as room type, beds, bathing facility type and communication features, and reasonable efforts by hotels using third-party reservation services. Source
- Regulation (EC) No 1107/2006 links airport assistance to notification at least 48 hours before published departure and requires the receiving party to transmit it at least 36 hours before departure to airports and the operating carrier. Source
- The Commission's 2024 interpretive guidelines on Regulation 1107/2006 say the airport must still make all reasonable efforts to assist when notification is late or missing. Source
- IATA's best practices on SSR codes define WCHR, WCHS and WCHC wheelchair assistance codes and refer to IATA Resolution 700 for the approved list. Source
- Article 9 of the GDPR prohibits processing data concerning health unless one of its listed exceptions applies. Source
See if your company qualifies
A short company assessment. No data uploads are needed.