What duty of care means in corporate travel

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. Practical checklists are in duty of care and when plans change. We do not invent incident counts, response-time figures or certifications.

What has to be visible

A duty-of-care posture fails when the latest itinerary lives in a traveller’s inbox and nowhere else. The organisation then cannot answer a basic question: who is in this city, on this date, and how do we reach them? The trip record is the honest place for that answer. Flights, stays, transfers, contact details, and copies of documents and visa status that the company is entitled to hold should sit on that file. A traveller map is a view of the same record, not a separate tracker with its own version of the truth.

Travel readiness and the passport and visa guide — belongs next to this. A passport that will not be valid on the departure date is a pre-trip duty-of-care issue as well as an operations issue. What remains with the authorities, such as a visa decision, should be recorded as status, not pretended to be an outcome the software can issue.

When plans change

The obligation is tested in motion, not at booking. A missed connection, a civil disruption, a medical issue, or a hotel that can no longer take the guest all require a current file and a desk that can work it. After-hours coverage is part of that test. If the night desk cannot open the same trip the traveller already sees, care becomes a scavenger hunt. In GTOS, duty of care and Control Tower are designed so a change is an update to the record, and after-hours support works that file rather than a parallel mailbox.

A duty-of-care programme also has a limit that should be stated. Software can keep the itinerary, the contacts and the documents together, and it can put them in front of the people who have to act. It cannot replace local emergency services, a security consultant, or a medical evacuation provider. Those remain specialist roles. The system of record should make it faster to brief them, not claim to be them.

Policy, unofficial travel and care

People who book outside the programme are harder to see, and therefore harder to look after. That is one reason out-of-policy leakage is not only a cost issue. A managed travel model, with a path people will use and a desk for the rest, is a duty-of-care design as well as a commercial one. The duty-of-care programme page sets out that operating view.

What not to claim

Do not treat a map pin as proof that someone is safe. Location views are only as current as the itinerary and any status the traveller or desk has recorded. Do not treat a completed booking as completed care. And do not hide unofficial travel by reporting only what was booked in the official tool. A serious posture reports what the organisation can actually see, and it works to bring more travel onto the record so that more of it can be seen.