The question no one can answer
You are about to walk up the spires of the Sagrada Família. Your hotel in Barcelona arranged the tour. The concierge recommended a specialist operator, made the reservation, and confirmed an English-language guide. The tour company collected a medical disclosure form when you booked: do you have a fear of heights? Are you comfortable on narrow spiral staircases? The questions were routine, but they mattered.
Now imagine something goes wrong at the top. A guest collapses. Not from a fall — from a pre-existing cardiac condition that the disclosure form mentioned, in the section nobody thought to flag to the guide.
Who is responsible? The hotel arranged the tour. The tour company operates it. The guide was standing next to the guest. The disclosure form was filed somewhere in a booking system. The emergency services arrive and ask: who was responsible for this person's welfare at the moment of the incident?
In today's travel industry, that question can take days to answer. The hotel has a booking reference. The tour company has a different booking reference. The disclosure form is in a third system. Nobody has a single, real-time record of who held Duty of Care at the moment the guest collapsed.
The gap at the heart of travel
Duty of Care is not a new concept. Every travel business carries a legal and ethical obligation to look after the people in its charge. Tour operators know it. Hotels know it. Airlines know it. The problem is not awareness — it is infrastructure.
Today, Duty of Care is handled through contracts, insurance policies, and after-the-fact legal liability. There is no real-time system that tracks who is responsible for a traveller's welfare as they move through a complex itinerary — from hotel lobby, into a taxi, through a tour operator's hands, up a spiral staircase, and back. When something goes wrong, the first task is reconstruction: who arranged what, who was present, who agreed to what. That reconstruction is slow, disputed, and expensive.
Duty of Care as a first-class runtime state
The Activity Travel Protocol makes Duty of Care a protocol-level construct, not a contractual afterthought. In a protocol-compliant booking, Duty of Care is assigned at the moment a booking is confirmed, and it transfers formally — with timestamps and confirmation requirements — every time the traveller moves from one party to another.
The Pre-Arrangement Declaration
The Pre-Arrangement Declaration between the hotel and the tour operator establishes Duty of Care assignment before any booking is made. It specifies: at which point does the hotel's responsibility end and the tour operator's begin? What are the escalation procedures if something goes wrong during the tour? These terms are agreed once and become operative in every subsequent booking that references the Pre-Arrangement Declaration.
The Pre-Activity Collection workflow
The fitness declaration, the health condition flag, the heights anxiety note — these are collected as structured data through the protocol, stored against the booking, and surfaced to the relevant party at the relevant moment. The tour guide receives a pre-activity briefing that includes the relevant flags from every participant. This is not a PDF filed in a back-office system. It is a live record attached to a live booking.
The Human Escalation Manager
If a traveller is unreachable at an expected check-in point — if the guest does not return from the spires, if no one responds to a check-in request — the protocol initiates a defined escalation chain. Who is contacted first. What the fallback procedure is. Which party is formally in charge of the response. This chain is defined in advance, in the Pre-Arrangement Declaration, not improvised in the moment of crisis.
What this means for operators and travellers
When the Duty of Care record shows the hotel's obligation ended at the lobby handoff, the liability question is answered by the record — not by a disputed reconstruction three months later.
The protocol's event log is the evidence base that insurers need to process claims efficiently. A booking with every Duty of Care transfer timestamped can be assessed in hours, not weeks.
An AI agent cannot hold Duty of Care. The protocol ensures it is always assigned to a named human party — and that the AI agent cannot make a state transition that leaves it unassigned.
For travellers, the implication is simpler: someone is always formally responsible for your welfare. Not informally. Not probably. Formally — with a timestamp, a confirmed handoff, and a defined escalation path if anything goes wrong.
That is what the Sagrada Família scenario deserves. Not a dispute about booking references. A record.