ADR And Regulator Escalation: Passenger Rights Workflow

Build a one-page chronology

Use short dated entries rather than a long narrative. Include only events that affect route coverage, passenger conduct, care, notice, arrival or cause. The underlying documents can then be numbered and attached behind the summary.

Minimum evidence before submission

• Booking and full itinerary
• Boarding pass or check-in proof
• Operating carrier and flight number
• Disruption notice and reason given
• Final-arrival evidence and replacement itinerary
• Reasonable expense receipts and airline correspondence

Keep originals and submit copies through the selected channel.

List each remedy separately

The remedy table should identify what was requested, what the airline provided and what remains unresolved. A later complaint can then focus on the disputed duty instead of resubmitting the entire history without structure.

Do not convert a category label into a conclusion

Do not argue cause before route and timing facts are clear. Once they are, compare the airline's explanation with contemporaneous notices. Unknown operational details should become focused questions rather than unsupported accusations.

Keep proof of exactly what was sent

Where several duties are unresolved, use separate headings and ask the airline to answer each. This creates a clear record if the response addresses one issue but ignores another.

Accepted, rejected or unanswered

Mark each requested remedy as accepted, rejected or unanswered. Classify the reason for refusal: coverage, carrier identity, notice, timing, cause, passenger conduct, documentation or another point. That classification shows whether new evidence, clarification or escalation is needed.

ADR, regulator or court are not interchangeable

Before escalating, confirm which body can handle the airline, route and remedy, whether its decision is binding, the deadline, cost and documents required. Do not assume that a regulator can award money or that one country's procedure applies everywhere.

No workflow guarantees payment

Verify the recipient before sending booking references, identity documents or bank details. Remove unnecessary sensitive information and keep a record of consent where another person is represented. ADR and regulator escalation is a structured workflow, not a guarantee of eligibility, reimbursement or compensation.

What this guide is designed to achieve

Use ADR and regulator escalation as a controlled process rather than a promise of payment. The stated objective is to choose the route that matches the airline and jurisdiction. Identify the decision that must be made, the evidence needed and the person or organisation that can make that decision.

Build the jurisdiction frame

The eligibility screen is a factual checklist, not a legal essay. Confirm travel direction, operator, disruption type, notice timing and final outcome. Unknown points should remain marked as unknown rather than filled with assumptions.