Keep duty of care on the current trip when plans change mid-journey

It is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. The duty of care checklist covers the wider programme. This page is the mid-trip slice. In GTOS, the traveller map, documents, and after-hours work in Control Tower sit on the same live file as the booking. We do not invent response-time guarantees, medical-evacuation credentials, or headcount figures for a crisis team.

1. Treat the current itinerary as the duty-of-care source

If the desk is looking at yesterday's ticket and the traveller is already on a new sector, you do not have a duty-of-care view. You have two guesses. Changes, including after hours, should update the same confirmations the traveller can open on a phone, and the same map and document set the company uses. After-hours support only works on that condition.

2. Reach the person from the file, not from a reconstructed contact list

When plans break, someone has to know who is travelling, where they were meant to be, and how to reach them. That information should already be on the trip, with access by role, inside the company's data boundary. A side spreadsheet of mobile numbers, disconnected from the itinerary, will be out of date at the moment it is needed.

3. Do not let a mid-trip change become unofficial travel

A new hotel or a reissued flight booked outside the record is a duty-of-care hole as well as a finance hole. The expert desk should take the change on the same file, with policy context still visible. Duty of care is not an excuse to switch policy off; it is a reason to keep the official path usable under pressure.

4. Review the change afterwards

A mid-trip incident or disruption is also a later review: what was on the file, who was reached, what was issued. The audit trail of the change is part of the duty-of-care programme, not only of finance. We do not claim to be a security or medical-response company. We describe the travel record those teams would need if they are ever called.

USD is the main currency on this site. Pricing for GTOS is in USD and available on request. Each company sees only its own data. A demo can work a change on an existing trip and then show what the traveller and the map would display afterwards, which is the test this guide argues for.