Travel Time, and Which Journeys Are Work
Which journeys are work and which are not, why the first and last journey of the day is the hard case, and how to record travel without a tracker.
Travel between two places of work during the day is almost always work; the ordinary commute from home to a fixed workplace usually is not. The difficult cases sit between those two, and they are the ones most organisations have never decided: the engineer who goes straight from home to the first customer, the carer who drives between four visits, the person sent to another site for a week.
The time question in “Travel Time, and Which Journeys Are Work” is easier to resolve when actual work, scheduled time and later corrections remain distinguishable. A team assessing read the official overview for employee monitoring data security can use its project and time records as operational evidence, while local rules, employee explanations and accountable review still determine what must be paid.
Travel is also the category where the minutes are largest and the records are thinnest. Nobody clocks in for a drive.
For an independent reference relevant to “Travel Time, and Which Journeys Are Work”, consult the OWASP logging guidance. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.
The journeys, grouped
| Journey | Usually | Why |
|---|---|---|
| Home to a fixed workplace | Not work | The ordinary commute |
| Between two workplaces in the day | Work | Travelling at the employer's direction |
| Home to the first job, no fixed workplace | Contested | Often work, and the rules differ sharply |
| Last job back home, no fixed workplace | Contested | Usually treated the same as the first |
| To a different site at the employer's request | Often work, at least in part | Not the ordinary commute |
| Overnight travel for work | Varies a great deal | Depends on when and how it is done |
The middle two rows are where the money is, and they are exactly the rows that differ most between jurisdictions. Both are a question for somebody qualified in the place concerned, and the answer tends to be worth getting once and applying to a whole workforce.
No fixed workplace is a category, not an exception
An employee who starts at a different address every day does not have a commute in the ordinary sense, and several systems treat their first and last journeys differently from a commute to a fixed site.
The practical consequence is large. A carer with six visits a day may spend ninety minutes travelling, of which the first and last are substantial. Getting that wrong across a workforce is not a rounding error; it is a proportion of every day.
Recording it without a tracker
Organisations assume this needs vehicle telematics and it usually does not. The schedule already contains the addresses and the appointment times, and a routing calculation between consecutive addresses gives a defensible estimate.
Where travel is paid on an estimate rather than a measurement, publish the basis — which addresses, which routing, what allowance for traffic — and let people say when it is wrong. An estimate nobody can check is an estimate people assume is against them.
That approach is cheaper than tracking, less intrusive, and produces a record that can be explained to somebody later, which a stream of GPS points generally cannot.
Travel that is also waiting
A passenger on a long journey, somebody waiting at an airport, a driver delayed at a depot — these are the cases where the categories blur, and where the answer often turns on whether the person is free to do as they please.
The operational question is narrower than the legal one: is anybody recording this time at all? In most organisations the answer is no, which means the legal question has not been reached.
The rate travel is paid at
Paying travel at a lower rate than work is common and in many places permissible, provided the arrangement is agreed and clear. What catches organisations out is the knock-on effect: hours paid at two different rates in one week usually have to be combined for the premium, on a weighted basis.
So a decision to pay travel at a lower rate quietly creates a multi-rate employee, and multi-rate premium calculations are the ones most systems get wrong by default.
Deciding it before somebody asks
The reason this sits undecided is that deciding costs money and leaving it costs nothing until it does. That calculation is wrong once the aggregate is computed and wrong twice if the question ever arrives from outside.
Write down, for each group of employees, which journeys are treated as work, what rate applies, and on what basis the time is measured. One page per group.
Travel that replaces work
A journey made instead of work is different from one made in addition to it. Somebody sent across the city mid-shift is travelling on paid time whatever anybody decides about commutes, because the alternative to the journey was working.
That distinction resolves a good proportion of the awkward cases without reaching the harder question at all. Before asking whether a journey is work in principle, ask what the person would have been doing instead — and if the answer is their job, the question is already settled.
Checking what the schedule implies
A useful test: take one employee's week, map the addresses in order, and add up the travel the schedule actually requires. Compare it with what was paid.
Where the two differ, the schedule is prescribing unpaid travel — not as a policy anybody wrote, but as an arithmetic consequence of how the visits were sequenced. That is a planning problem with a pay consequence, and it is fixed in the planning rather than in payroll.