A consultant flies to a client workshop on Monday, visits a second site on Wednesday, and extends the trip after the project scope changes. A lawyer travels for a negotiation whose time and location are deliberately restricted. An auditor works inside a facility controlled by another organisation. A technical specialist is sent at short notice because a client has suffered an operational failure.
Each traveller may have a valid flight, hotel, and travel approval. Yet none of those records, by itself, describes the risk the firm is actually managing.
The booking says where a person was expected to travel when the reservation was made. The assignment explains why the person is travelling, whose work they are undertaking, which locations and organisations shape their exposure, who can change the plan, and who must act if circumstances deteriorate. That distinction is especially important in professional services, where work is organised through clients, engagements, projects, and matrix management rather than through a single, stable line of operational control.
Travel risk management becomes materially stronger when the client assignment is treated as its basic unit. The point is not to replace itineraries. It is to connect them to the business purpose, changing conditions, decision rights, and assistance arrangements that make an itinerary operationally meaningful.
Travel risk management is a management system, not a travel desk
ISO 31030 describes travel risk management as a structured approach covering policy, programme development, threat and hazard identification, risk assessment, prevention, mitigation, evaluation, and review. It applies to organisations of every size and sector, and it concerns risks both to the traveller and to the organisation.1 That scope is much broader than booking administration.
This matters because travel operations and travel risk operations answer different questions. The travel function may be able to show the booked flight, hotel, and ground transport. The engagement leader may know why a consultant is needed at the client site and whether attendance can be postponed. The security team may understand a developing threat. Human resources may know of an adjustment the traveller requires. A local office may understand what an apparently small change in a district or route means in practice. The traveller may be the only person who knows that the meeting has moved.
No single source is necessarily defective. The weakness lies in leaving the sources unconnected. When the firm manages a trip as a transaction, changes to the work can detach the person’s real exposure from the record on which monitoring and assistance depend.
The assignment provides the connecting structure. It associates a named business purpose with a traveller or team, an accountable engagement leader, one or more client locations, planned movements, relevant risk information, communications arrangements, and agreed escalation decisions. It also gives the firm a reason to close the record when the work ends, rather than retaining a vague assumption that a traveller is still exposed because an old booking remains visible.
An itinerary is evidence of intention, not evidence of location or safety
Travel programmes often begin with passenger-name records and itinerary feeds because they are structured, available, and useful. They can identify who was expected to arrive in a country and when. They may also support alerts when disruption affects a booked route.
Their limitation is temporal. A booking is a statement made before travel. Risk is experienced in the present.
Professional-services work changes quickly. Meetings move from a client headquarters to a project site. A traveller adds a day, uses a different hotel, joins a colleague’s vehicle, or crosses an internal boundary that was not apparent when the trip was approved. Some changes are entirely ordinary. Others alter the available transport, communications, medical support, political exposure, or time needed for assistance.
The practical response is not to demand surveillance of every movement. It is to define which changes are material to the assignment. A move to another office in the same low-risk city may require no intervention. An overnight extension, journey to a remote site, change to a higher-risk district, or separation from the rest of the team may require the traveller or engagement leader to update the plan. The threshold should reflect the work and environment, not the convenience of the technology.
This turns itinerary management into exposure management. The organisation stops asking only, “Who has a booking in this country?” and can ask, “Which active assignments may be affected, what do we know about the people involved, and which decision now falls to whom?”
Country risk information must change a decision to become a control
Government travel advice, threat intelligence, health information, and local reporting are essential inputs. The FCDO’s Overseas Business Risk service expressly directs organisations to continue checking country travel advice, while its crisis guidance warns that consular help may be limited, particularly where official advice already recommends against travel.2 3 An employer cannot therefore treat access to public advice as an outsourced response plan.
The managerial question is what new information changes. If a security update does not affect authorisation, route, accommodation, timing, communications, protective measures, or the decision to continue, its role is merely informative. That may sometimes be appropriate, but it should be conscious.
A useful assignment model links risk information to pre-agreed decision points. Before departure, the decision may concern whether the work justifies travel and whether the proposed controls are adequate. During the assignment, it may concern a route change, a temporary pause, relocation, remote delivery, or withdrawal. In an incident, the decision may concern who should check in, who needs direct assistance, who is authorised to contact the client, and when the firm moves from monitoring to active intervention.
This avoids two common extremes. The first is a static country rating that produces the same generic briefing for every traveller, regardless of the assignment. The second is an improvised response in which senior people debate authority only after an incident has started. Neither demonstrates that information was converted into proportionate action.
Client sites create shared responsibility, not transferred responsibility
A professional-services employee working at a client location sits inside two operational systems. The client controls the premises, local emergency arrangements, access, and many site-specific hazards. The professional-services firm remains the person’s employer and controls matters such as whether the assignment proceeds, how its employee is prepared, and what assistance the firm will provide.
HSE guidance on shared workplaces states that employers sharing a workplace, temporarily or permanently, need to co-operate, co-ordinate their measures, and exchange information about risks that their activities may present.4 The significance for professional services is not that every client visit requires an elaborate joint command structure. It is that “the client is responsible on site” is not a complete control.
Before higher-risk work, the parties should understand how local alerts reach visiting personnel, where visitors assemble or shelter, how the client accounts for them, who informs the employer, and which organisation leads if the person is away from the premises when an incident occurs. Those are interface questions. They are easy to omit because each organisation has a competent internal procedure, but neither procedure necessarily explains the handover between them.
The client assignment is the natural place to record that interface. It can identify the client contact and internal engagement owner, distinguish site emergency arrangements from employer assistance, and show the point at which an operational problem becomes a duty-of-care escalation. This is more robust than expecting a traveller to reconcile two organisations’ procedures under pressure.
Matrix management needs explicit decision rights
Professional-services firms frequently distribute authority across service lines, geographies, client teams, and corporate functions. That structure helps firms deploy expertise, but it can blur ownership during disruption.
Consider a traveller whose home-office manager approves development and leave, whose engagement leader directs the work, whose regional leader owns the client relationship, and whose security team sets travel controls. If conditions worsen, several people may have legitimate interests but no one may have a clearly defined decision.
An effective assignment record should therefore identify decision rights, not merely contacts. Who can approve travel to proceed? Who can require a traveller to pause or leave? Who can accept the residual business risk? Who may speak to the client? Who owns welfare contact with the traveller’s family if the event becomes serious? Who can authorise extraordinary assistance costs?
These decisions need not all belong to one person. They do need to be allocated before the organisation relies on them. Escalation based only on seniority can be slow and misleading: the most senior person available may not know the assignment, the location, or the traveller’s circumstances. A sound model assigns authority to roles and establishes alternates for out-of-hours operation.
Driving risk shows why the assignment matters
Travel risk is often imagined as aviation, geopolitical disruption, or a crisis abroad. Much of the practical exposure may arise between the airport, hotel, client office, and project site.
HSE guidance treats driving on the road for work as a work activity and advises employers to assess the journey, driver or rider, and vehicle. It highlights factors including fatigue, time pressure, weather, traffic, and vehicle condition.5 These factors are shaped by the assignment. A late-running client meeting can create pressure to complete a long transfer. A last-minute site visit can introduce an unfamiliar road or unsuitable vehicle. A demanding programme can leave insufficient recovery time between travel and work.
The lesson is wider than road safety. Risk controls must follow the way work is actually commissioned and changed. A perfectly compliant booking policy cannot compensate for an engagement plan that makes safe execution unrealistic.
Privacy must be designed into travel support
Location can be extremely useful during a fast-moving incident. It can also become intrusive if it is collected continuously, retained indefinitely, or reused for unrelated management purposes.
The Information Commissioner’s Office says worker monitoring must be lawful and fair, have a clear purpose, and use the least intrusive means capable of achieving that purpose. It warns that excessive monitoring can intrude into private life and damage trust. Importantly, the ICO also cautions that consent is not usually an appropriate lawful basis in employment because the imbalance of power may prevent it from being freely given.6
That last point is often missed. A travel programme cannot solve privacy simply by adding a consent button. It must identify the lawful basis for processing, define the safety purpose, minimise the data collected, set retention and access rules, explain the arrangement clearly, and assess whether the same outcome can be achieved less intrusively.
The assignment model supports proportionality. Location sharing can be limited to an active journey, defined work period, higher-risk movement, or live incident. Different assignments can use different controls. A consultant making a routine journey between major offices need not be treated like an engineer travelling alone to an isolated client facility. Clear activation and closure points also reduce the risk that work-related visibility extends silently into private time.
Trust is not a soft addition to the control. It determines whether people keep information current, acknowledge messages, and ask for help early. A system that appears to conceal its monitoring purpose may produce apparently comprehensive data while encouraging avoidance and workarounds.
An acknowledgement is not a welfare assessment
During disruption, a mass message can quickly ask travellers to confirm that they are safe. That is useful triage, but it should not be confused with resolution.
A person who presses “safe” may still be stranded, without medication, under pressure from a client, or uncertain whether to continue. A person who does not respond may be in danger, asleep, in a meeting, without coverage, or no longer in the affected area. The response team needs a disciplined way to separate communications status from welfare status and assistance need.
The assignment provides context for that judgement. It shows why the person is present, what they were expected to be doing, who else is involved, which client contact may help, and what alternatives have already been agreed. This allows follow-up to be prioritised instead of treating every non-response identically.
It also supports continuity. If a response extends across shifts, the incoming team should not have to reconstruct the traveller’s situation from messages, spreadsheets, and personal recollection. The record should distinguish verified facts, reported information, assessments, decisions, assigned actions, and unresolved questions. That distinction improves both immediate control and later review.
The post-incident review should examine the assignment, not just the alarm
Weak reviews ask whether the alert was sent. Strong reviews ask whether the organisation made sound decisions with the information reasonably available at the time.
That requires examining the full assignment lifecycle. Was the business purpose clear enough to support the original risk decision? Did material itinerary changes reach the people responsible for monitoring? Was client-site information exchanged? Did the traveller understand the communications and escalation process? Were decision rights usable out of hours? Did location collection remain within its stated purpose? Was assistance closed only when the traveller’s situation, rather than the notification, was resolved?
HSE’s general management guidance describes health and safety as an ongoing process of planning, implementation, checking, and action, supported by monitoring and review rather than a one-off assessment.7 Applied to travel, this means the organisation should use incidents, exercises, near misses, and ordinary changes of plan to improve the programme. The best evidence is not an immaculate policy. It is a traceable relationship between the assignment, the risk decision, the actions taken, and the learning adopted.
Where technology fits
Technology can help professional-services firms create this operational connection, but only if governance comes first.
AtlasNXT can support this way of working by bringing relevant people, locations, communications, and incident activity into a shared operational view. The AtlasNXT app can give travellers an everyday route for safety communications, agreed location sharing, and requests for assistance. Targeted notifications and acknowledgements can help a response team identify where direct follow-up is required, while an incident history can preserve actions and decisions for handover and review.
That does not make a software platform the owner of risk. The firm must still define material changes, decision authority, privacy rules, client interfaces, and the point at which an assignment is closed. The platform’s role is to make those arrangements usable when work departs from the itinerary.
The central principle is simple: professional-services travel exists because an assignment exists. If the firm manages the booking but not the assignment context, it can know that somebody travelled without being able to explain their current exposure or its own next decision. Treating the assignment as the unit of control closes that gap and turns travel risk management into part of how the work is governed.
Book an AtlasNXT demonstration to explore how an assignment-centred approach could support your travelling and client-facing teams.
References
2. Foreign, Commonwealth & Development Office, Overseas business risk
3. Foreign, Commonwealth & Development Office, If you’re affected by a crisis abroad
4. Health and Safety Executive, Shared workplaces
5. Health and Safety Executive, Employers — driving and riding safely for work
6. Information Commissioner’s Office, Data protection and monitoring workers
7. Health and Safety Executive, Introduction to managing health and safety
