Duty of care without turning it into travel red tape
What the organisation needs to know before someone travels, who decides when things get complicated and what can be left out without losing diligence.
Marta installs equipment for a company of sixty people and travels two or three times a month. One Saturday afternoon she calls her manager from a city where the airport has closed because of a protest nobody expected. The hotel has asked her not to go out and her return flight has disappeared from the app. Her manager tells her not to worry, that he will look into it right now, and hangs up to discover that he does not know which hotel she is in, that the insurer's assistance number is in an email from two years ago and that the travel agency does not open until Monday. Nothing serious has happened yet. But the company is already running late.
That scene is the duty of care seen from the inside. Almost every organisation settles it with a written policy and an insurance policy, and both are needed. What neither of them does is answer the phone. Insurance pays after the incident, but it does not evidence what the company did before, and that is exactly the question a client, an insurer or a judge will ask when something goes wrong: what did the company know about that trip, who approved it and on what criteria, and what did it have ready for the first hour. In Spain the employer's duty of protection sits in the Occupational Risk Prevention Act, which brings the European framework directive on health and safety at work into Spanish law. Neither of them distinguishes by company size or stops at the office door, and ISO 31030 is the voluntary guidance that explains how to meet that duty when people travel. How it applies in each case is for Legal to say. That it exists is not up for discussion.
What you hear most often in SMEs is that this is a matter for multinationals, with their control room, their tracking platform and their assistance provider, and that they will get to it later. The mistake is to measure the risk by headcount. A twelve-person engineering firm that sends two technicians to site every month has more to manage than a four-hundred-employee company that only visits client offices in European capitals. What shapes the programme is the travel profile: how many people travel, where, to do what and how often. And that is where contractors, domestic trips and the business trip with a few days of holiday added on come in, which tend to fall outside the policy and inside the responsibility.
A proportionate programme fits in a few pages. A named person who runs it and a senior executive who signs the policy and owns the level of risk the company accepts. A two-page policy that people actually read. A register of who is travelling, when and where they are sleeping, filled in before booking. And three categories of trip, so that attention goes where the risk is. Most trips only need booking through the agreed channel, a destination brief and the assistance number saved on the phone. A few need a one-page assessment, a short briefing and check-ins at fixed times. And destinations the Government itself advises against need a written decision from management, specialist support and, often, the honest answer that the trip does not go ahead. The country's risk level is the starting point, not the end. It is adjusted by city, by dates and by who is travelling, because going in a group is not the same as going alone, nor does everyone face the same risk under every legal system.
Then comes what almost nobody rehearses. A one-page response plan that says who decides, who can spend money without asking permission, who gets called and what is done in the first hour. A ninety-minute tabletop exercise with a realistic case, which usually ends with a list of things that were not where everyone thought they were. And an annual review of the insurance, actually reading the policy: how far it covers a medical evacuation, what it excludes, whether it extends to contractors and domestic trips, and what precautions it requires you to have taken before it pays. The one thing a small company should buy rather than build is assistance with real evacuation capability, because an international medical transfer can cost more than the whole programme put together.
The mistakes repeat themselves so often that they can almost be recited from memory. Contracting a tracking platform before deciding who watches it and what they do when an alert comes in, which is the most expensive way to have a nice dashboard and no response. Writing a long policy that travellers do not read and managers do not apply. Sending the briefing as an attachment without asking for confirmation, so that later there is no way to show it arrived. Leaving the programme with Finance or Human Resources with nobody bringing security judgement. And never testing the response plan until a real incident tests it.
In the end, the programme is evidenced by a folder. The signed policy, the travel register, the assessments carried out, the briefing confirmations, the insurance policy with its review, the response plan, the record of the exercise with its actions closed, and the annual review. Boxes ticked and saved to the server, to be able to show, in-house or to a labour inspection, that everything has been done.
What we care about is people. Being there when help is needed and resolving the situations that, seen from the office, do not look critical, but for the person living them they are. A flight cancelled at midnight in an unfamiliar city, a lost suitcase with the medication inside, a call that nobody returns. The folder evidences what was done before the trip. But if someone in your company called on a Saturday from a closed airport, who would pick up the phone, and what would they know about that person in the first ten minutes? The answer to that question is the real state of your duty of care.
If this resonates with something you are seeing in your organisation, let's talk.
Let's talk