GO UP
esim background
ISO 31030

ISO 31030 Explained: Travel Risk, Duty of Care and Practical Implementation

A company approves an employee’s trip to a country experiencing political unrest. Travel is booked, insurance is confirmed and the traveller receives an emergency telephone number.

Three days later, a security incident disrupts transport and mobile communications.

The employee cannot reach the assistance provider. The security team does not know whether the traveller has received its warning. HR assumes the travel manager is coordinating the response, while the travel manager believes security has taken responsibility.

The organization has travel policies, suppliers and emergency contacts. What it lacks is a tested system connecting them.

This is the problem ISO 31030 is designed to help organizations address.

ISO 31030:2021, Travel risk management — Guidance for organizations, is an international standard providing a structured approach to identifying, assessing, managing and reviewing the risks associated with business travel.

Its purpose is not to eliminate travel risk. That is impossible. It is to help organizations make informed decisions, establish responsibilities, apply proportionate controls and evaluate whether those controls actually work.

For businesses with international employees, contractors or frequently travelling teams, ISO 31030 offers a framework for turning duty-of-care commitments into repeatable operational processes.

What Is ISO 31030:2021?

Published in September 2021, ISO 31030 belongs to the wider ISO 31000 family of risk management guidance.

The standard addresses organizational travel, including the risks travellers and their employers may face before, during and after a trip.

Its scope includes developing policies and programmes, identifying threats and hazards, assessing risk, determining mitigation strategies and reviewing outcomes.

It applies to organizations of different sizes and sectors, including businesses, governments, educational institutions and non-profit organizations.

The standard does not generally apply to private tourism or leisure travel unrelated to organizational responsibilities.

Importantly, ISO 31030 is a guidance standard, not a certification standard.

Companies can assess their programmes against it and commission independent reviews, but should be cautious about claims that a particular platform or organization is officially “ISO 31030 certified.”

The current published edition is ISO 31030:2021. As of November 2026, ISO lists it as under systematic review.

ISO 31030 and Duty of Care: What Is the Difference?

Duty of care describes responsibilities that an organization may have toward people travelling on its behalf.

These responsibilities can arise through employment law, occupational safety obligations, negligence principles, contracts and other applicable legal arrangements.

ISO 31030 guides managing travel-related risk. It does not establish a universal new legal duty, replace national legislation or guarantee that an organization has fulfilled all its obligations.

The applicable legal position depends on jurisdiction, employment relationships, travel circumstances and other factors.

READ MORE: Enterprise eSIM Intelligence & Buyer’s Guide

A company operating across the UK, European Union and United States should therefore distinguish between two questions:

Legal responsibility: What does the law require in each relevant jurisdiction?

Risk management practice: What processes and controls should the company establish to identify and manage foreseeable travel risks?

ISO 31030 helps structure the second question.

It may support evidence of an organization’s approach to the first, but legal compliance requires separate assessment.

The ISO 31030 Framework: From Policy to Action

An effective travel risk management programme connects several activities.

Programme element Practical purpose Example
Governance and policy Establish responsibilities and risk criteria Approved travel risk policy
Risk identification Understand relevant threats and vulnerabilities Destination and traveller assessment
Risk evaluation Decide which risks require treatment Risk-rated trip approval
Prevention and mitigation Reduce exposure or consequences Briefings, safeguards and assistance
Monitoring and response Detect changes and support affected travellers Alerts and escalation procedures
Evaluation and improvement Learn from incidents and exercises Post-trip and programme reviews

These elements reflect the standard’s stated scope. The table is a practical interpretation, not a reproduction of its full requirements.

1. Establish an ISO 31030 travel risk policy

The travel risk policy should clarify who is accountable for decisions.

A common weakness is distributing responsibility across departments without defining ownership.

Travel managers handle bookings. Security assesses threats. HR manages employee welfare. IT provides communications. Procurement contracts assistance suppliers.

All may perform their individual duties without anyone owning the overall travel risk process.

A useful policy identifies decision-making authority, risk tolerance, approval thresholds, escalation rules and arrangements for exceptions.

It should also address travellers whose circumstances require additional consideration, such as medical needs, challenging assignments or travel outside ordinary working arrangements.

The policy must be understood by relevant people—not merely stored in a document repository.

2. Assess risk before travel

A destination’s general security rating is only one part of a meaningful assessment.

The same location may present different risks to a conference attendee, a field engineer visiting remote infrastructure and an executive travelling with commercially sensitive information.

The assessment should consider the destination, itinerary, traveller circumstances, activity, available support and potential consequences of disruption.

For higher-risk trips, approval may depend on additional measures or a decision not to travel.

The organization should record the rationale rather than simply mark the journey as approved.

ISO 31030
3. Prepare travellers and support teams

Risk information must reach the people who need it.

Appropriate preparation may include destination briefings, health guidance, secure working procedures, emergency contacts and instructions for reporting incidents.

Travellers should understand what assistance is available and when to seek it.

Support teams need compatible information about the itinerary, approved controls and escalation arrangements.

A policy that employees cannot follow under pressure is not an effective operational control.

4. Monitor and respond during travel

Travel risk can change after departure.

Weather, political events, health emergencies, security incidents or transport disruption may require the organization to reassess a trip.

An effective programme establishes how relevant information is monitored, who evaluates it and what actions follow.

This may include contacting travellers, changing itineraries, authorizing accommodation or activating emergency assistance.

The organization should define what happens when a traveller cannot be contacted.

That possibility deserves explicit planning rather than an assumption that every employee will always be reachable.

5. Review performance after travel

Travel risk management should improve through experience.

Not every trip needs an extensive review, but significant incidents, near misses and control failures should generate learning.

Useful questions include whether warnings arrived in time, whether decisions were appropriately authorized and whether suppliers delivered the expected support.

The results should lead to documented improvements where necessary.

The Missing Link: ISO 31030, Connectivity and Traveller Reachability

Many modern travel risk processes depend on digital communication.

Employees receive alerts through mobile applications. They access medical or security assistance online. Support teams use messaging systems, travel itineraries and location information to understand changing circumstances.

But those systems depend on the traveller having an appropriate communications path.

READ MORE: The IT Channel’s Next eSIM Opportunity

An employee may lose mobile coverage, encounter a roaming restriction, exhaust a data allowance or become unable to use their primary device.

This creates a dependency that risk teams should assess.

Mobile connectivity is not the whole of travel risk management. It is one of the enabling controls that can determine whether other controls remain usable.

Connectivity as a risk control

Consider three practical situations:

A traveller needs to receive an updated security advisory.

An employee must contact an assistance provider after a medical incident.

A security team needs to establish whether a person has received and acknowledged emergency instructions.

Reliable communications support all three processes.

However, an enterprise eSIM, roaming plan or multi-network subscription should not be described as an ISO 31030 compliance solution in its own right.

Different services have different coverage, administration, monitoring and resilience capabilities.

A SIM with access to several networks does not guarantee instantaneous switching or continuous availability.

For higher-risk travel, organizations may require alternative communication arrangements, offline information, predetermined meeting procedures or satellite communications where justified.

The right approach is to identify the communications risk, choose proportionate safeguards and test them.

Location awareness versus employee surveillance

Connectivity data may help an organization understand service status or support traveller assistance.

It should not be assumed that SIM activity provides precise real-time employee location.

Network registration information, billing location, GPS data and active location sharing are different sources with different accuracy, consent and privacy implications.

Any traveller location-processing arrangement should have a legitimate, clearly documented purpose and appropriate access and retention controls.

ISO 31030 should not become a justification for indiscriminate employee tracking.

The ISO 31030 Audit Trail: What Should Organizations Document?

One of the standard’s most useful applications is helping organizations demonstrate how decisions were made and reviewed.

An ISO 31030 audit trail is not a mandatory software product or a prescribed single document.

It is the collection of appropriate records showing how the travel risk programme operates.

A practical evidence model might look like this:

Stage Useful evidence What it demonstrates
Before travel Risk assessment and approval record Risks considered and decisions authorized
Preparation Briefing and training records Relevant information communicated
During travel Material alerts, contacts and decisions Controls operated when needed
Incident response Escalations and assistance actions Response responsibilities exercised
After travel Incident review and corrective actions Learning and improvement
Programme review Policy updates, exercises and assurance findings Ongoing governance

Organizations should retain evidence proportionately and according to applicable legal and privacy requirements.

Collecting every available location or connectivity event is not automatically better governance.

The relevant question is whether records support meaningful review without exposing unnecessary personal information.

A Practical ISO 31030 Scenario

Consider a hypothetical engineering company sending two technicians to inspect infrastructure in a remote region.

The trip is business-critical, but the destination presents uncertain mobile coverage, limited local transport and potential health and security risks.

A weak process approves travel once insurance and accommodation are confirmed.

A more mature programme asks additional questions.

Who has approved the residual risk?

What communications will the technicians use?

Are there reliable local assistance options?

How frequently should they check in?

What happens if they miss a scheduled check-in?

Who can authorize a change in transport or evacuation?

Before departure, the company records its assessment, confirms suitable controls and briefs the technicians.

During the assignment, a scheduled check-in is missed.

The support team follows a predetermined escalation process rather than improvising. It checks relevant information, attempts the agreed contact methods and escalates according to the documented thresholds.

Afterward, the organization reviews whether the communications arrangements and response process were effective.

This hypothetical example shows the practical value of ISO 31030: the organization has established who acts, when they act and how outcomes are assessed.

It does not depend on buying a particular technology.

How to Implement ISO 31030: A 90-Day Starting Plan

The implementation effort depends on organizational size, travel exposure and existing processes.

A practical starting programme can be organized into three stages.

ISO 31030: A Practical 90-Day Roadmap

DAYS 01–30
Understand the current position

Identify who travels, where, why and under which existing policies.

Review incident arrangements, assistance suppliers, employee communications and current approval procedures.

Compare the existing approach with relevant ISO 31030 guidance.

Document gaps and assign responsibility for addressing them.

DAYS 31–60
Strengthen controls

Update the travel risk policy and clarify governance.

Introduce proportionate risk assessments, approval rules, traveller briefings and escalation processes.

Confirm responsibilities between travel, security, HR, IT and external assistance providers.

Ensure communications arrangements are suitable for the risk profile.

DAYS 61–90
Exercise and improve

Test representative scenarios, including an unreachable traveller, a changed destination risk and an incident requiring coordination across departments.

Document what happened, how decisions were made and which controls failed or worked.

Assign corrective actions and schedule the next programme review.

IMPORTANT:
Ninety days is a suggested initial improvement period, not an ISO requirement or a promise of full programme maturity.

How to Evaluate ISO 31030 Solutions and Service Providers

Travel risk technology can support a programme, but no single software platform replaces organizational governance.

Suppliers may offer destination intelligence, medical and security assistance, traveller communications, incident management, itinerary monitoring, connectivity or programme assessments.

The relevant capabilities depend on the identified risks.

Procurement teams should ask:

  • What specific operational problem does the service solve?
  • Which parts of the risk programme remain the organization’s responsibility?
  • How are alerts delivered and acknowledged?
  • What happens if the employee has no mobile or internet connectivity?
  • Can the provider demonstrate incident escalation and recovery procedures?
  • What evidence and reporting are available for programme reviews?
  • How are personal information, access rights and data retention managed?
  • What support is available across the actual destinations and working hours?

For connectivity suppliers specifically, test network access, device compatibility, escalation arrangements and coverage limitations.

For assistance providers, assess incident handling, relevant expertise and coordination procedures.

For risk platforms, determine whether the information they provide can support timely decisions rather than merely populate dashboards.

More on Alertify
Follow the latest eSIM news
Stay updated with breaking headlines, mobile connectivity updates, travel technology, eSIM carrier deals, and global telecom trends.

Explore news→

Is ISO 31030 Mandatory or Certifiable?

ISO 31030:2021 is voluntary international guidance unless its use is required through a particular contract, procurement condition or other applicable arrangement.

It does not automatically replace local legal obligations.

The standard is not intended as a conventional organizational certification scheme.

Companies can undertake self-assessments, gap analyses and independent audits against its guidance. Individual training providers may issue completion certificates, but these should not be confused with certification of an organization’s travel risk management programme to ISO 31030.

READ MORE: When Travellers Go Dark: The Connectivity Risk TRM Misses

Businesses should be cautious about vendors claiming that purchasing their software makes an organization “ISO 31030 compliant.”

Alignment depends on the overall risk management arrangements, not simply a product feature.

Conclusion: ISO 31030 Is About Making Duty of Care Operational

A company does not demonstrate effective travel risk management by publishing a lengthy policy or purchasing an emergency assistance platform.

It demonstrates it through proportionate decisions, clear responsibilities, appropriate controls and the ability to respond when circumstances change.

ISO 31030 provides an internationally recognized framework for organizing those activities.

For travel, security and HR teams, its value lies in bringing otherwise fragmented responsibilities into one coordinated programme.

For IT and telecom teams, it creates a reason to examine the communications infrastructure supporting traveller assistance.

For procurement, it offers a stronger way to assess whether suppliers genuinely support the organization’s needs.

The important question is not whether the company has an ISO 31030 policy. It is whether the organization can show what happens when a traveller needs help—and whether that process has actually been tested.

Driven by wanderlust and a passion for tech, Sandra is the creative force behind Alertify. Love for exploration and discovery is what sparked the idea for Alertify, a product that likely combines Sandra’s technological expertise with the desire to simplify or enhance travel experiences in some way.