The Frequent Traveller

The least considered population in this section. Not posted, not on assignment, not remote — simply travelling a great deal for work, in a way that has grown gradually and been noticed by nobody.

The workflow in “The Frequent Traveller” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring task switching cost, the product page can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.

They are usually senior, usually in sales or engineering or project delivery, and their travel is a cost line rather than a compliance fact. The organisation knows exactly where they went, because it paid for the flights.

For an independent reference relevant to “The Frequent Traveller”, consult the FBI counterintelligence resources. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

Why the pattern matters

Several of the frameworks in this subject use duration or frequency thresholds: days in a country, consecutive days, proportion of working time. A person travelling constantly may cross one without anything that looks like a relocation.

The working time question is secondary to the tax and immigration ones and it is the same shape: which rules applied while they were there, and does the organisation's record of their hours reflect it.

The data already exists

Travel bookings and expense claims record where people were, by date, because finance needs that. For most organisations this is the most complete location dataset they hold and it is used for nothing else.

A count — nights per person per country per year — takes an hour from that data. It is the cheapest possible first step and it tells you whether this population exists in your organisation at a scale worth looking at.

What the count usually shows

A small number of people with very high totals, a longer tail of moderate travellers, and a concentration in particular country pairs.

The high totals are the ones to look at, and they are frequently people nobody thought of as travellers — a regional manager, a technical lead on a long project, somebody covering a market without a local presence.

The concentration is useful too: where many people spend substantial time in one country, the organisation may be approaching a question about presence rather than about individuals.

Hours, which are genuinely hard here

A frequent traveller's hours are among the least well recorded in any organisation. They are usually salaried, frequently excluded from time recording, and their working day includes travel that may or may not count depending on where they are.

The honest position is that the organisation does not know their hours and that the limits apply to them in most regimes regardless.

Where that is the case, the useful first step is not a measurement system but a conversation about the pattern: a person doing four countries in five days is working a long week whatever the records say.

The threshold to set internally

An internal trigger — more than this many nights outside the home country in a rolling year, or more than this many in any one country — that routes the person to a review.

The numbers should come from advice, because they are trying to sit below the lowest relevant external threshold. Once set, the check runs against the travel data automatically and nobody has to remember.

What a review actually covers

Whether any threshold has been crossed in any country. Whether the travel pattern is sustainable in working time terms. And whether the organisation's records for that person are adequate.

Three questions, most of which will come back clear for most people. The value is in the small number where they do not, and in having asked.

The conversation that is overdue anyway

Running this count usually produces a second finding that has nothing to do with compliance: somebody has been travelling at a rate nobody has looked at, for years, and nobody has asked whether it is reasonable.

That conversation is worth having on its own terms. It is also, in practice, the thing that gets the count taken seriously, because a compliance threshold is abstract and a person spending a hundred and forty nights a year in hotels is not.

Counting nights rather than trips

A trip count understates the exposure, because thresholds are generally expressed in days or nights present rather than in journeys.

Two long trips can exceed what twenty short ones do, and a report of trips per person will rank the wrong people at the top.

Pull nights by country from the accommodation data rather than trips from the booking data. It is the same source and a different query, and it is the figure that corresponds to how the thresholds are actually written.

The traveller who is also remote

The two populations overlap more than the categories suggest: somebody working remotely from one country and travelling frequently to others has no clean base at all.

For them the question of place of work has no single answer, and the register should say so rather than forcing one.

These are a small group and they are the ones where the register earns its keep, because the alternative is that each system holds a different answer and nobody has ever compared them.