Travel That Is Work

For anybody whose work moves, travel is the largest component of the gap between recorded hours and hours that count. It is also the best-recorded: dispatch systems, job management tools and vehicle telematics hold journeys to the minute, because the business needs them for other purposes.

The workflow in “Travel That Is Work” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring task switching cost, explore the software can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.

The data exists in high quality and does not reach the working time figure. That is the whole of the problem and it makes this the easiest of the uncounted categories to fix.

For an independent reference relevant to “Travel That Is Work”, consult the FTC data-security guidance. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.

Which journeys count

Travel between assignments during the working day is working time in most regimes, and this is the least contested part.

Travel from home to the first assignment and from the last back home is the contested part, and in several jurisdictions it counts for workers with no fixed place of work. The reasoning is that a mobile worker's working day begins when they set off, because the employer determines where they are going.

Travel to a place that is not the usual workplace — a training venue, another site, a client — occupies a middle ground that varies.

Why organisations assume it does not count

Because the intuition from fixed-site work is that commuting is the worker's own time, and that intuition is correct for fixed-site work.

It does not transfer. A person with no fixed workplace is not commuting in the relevant sense, and treating their first and last journeys as commuting is the single most common error in this area. It is also the most expensive one, because for a field workforce it is several hours a week per person.

Sizing it from data you already have

Export a month of journeys from the job or vehicle system for a sample of people. Sum them by category: between jobs, first and last, other.

An afternoon's work produces the number. It is usually between six and twelve hours a week per person for a field workforce, which against a forty-eight hour limit is the difference between a comfortable figure and an uncomfortable one.

The integration that closes most of it

Travel between jobs is the least contested category and frequently the largest. Bringing that one into the working time calculation closes most of the gap and avoids the argument about first and last journeys entirely.

It is usually a scheduled export from one system and an import into another, which is a small piece of work. Where the organisation wants to go further, first and last journeys are the next step and the one that needs advice first.

The scheduling consequence

Once travel counts, the schedule looks different. A day with four jobs spread across a county is a longer working day than one with four jobs in a town, even though the job time is identical.

That is a real constraint and it is also an opportunity: scheduling by geography reduces both the travel and the working time, and the second has never been a factor in the optimisation. Adding it tends to produce tighter routes, which the business wanted anyway.

What not to do

Do not start counting travel and leave the rota unchanged. The result is a workforce that is immediately in breach on paper, a report full of red, and a strong institutional temptation to switch the counting off again.

Decide what the figure is first, adjust the patterns, then turn on the measurement. The sequence matters because the first version of the report is the one that determines whether anybody believes it.

The on-call driver case

Where somebody is called out at night and drives to site, the journey is unambiguously working time in most regimes, and it also sits inside what should have been a rest period.

That combination makes call-out travel the highest-value thing to capture: it affects both the hours figure and the rest figure, and it is recorded, because the vehicle was moving and the job was logged.

What to put in the limits page

One line: for mobile workers here, these categories of travel count towards working time, on this basis, and are captured from this system.

Where the organisation has taken advice and concluded that first and last journeys do not count in its circumstances, that belongs on the same line with the date and the reason. The failure to document is what turns a defensible position into an assumption nobody can source.

The person with no fixed workplace, defined

Whether somebody has a fixed place of work is a question of fact rather than of what their contract says, and it decides whether the first and last journeys of the day count.

A contract naming a depot as the place of work, for somebody who attends it once a month, is unlikely to settle it. Where a workforce is genuinely mobile, the honest course is to take advice on that specific question and record the answer, rather than relying on a contractual designation that was written for a different purpose.