When the First Job Is the Commute

For a mobile worker the boundary has no physical form. There is no gate, no changing room, no terminal. There is a home, a vehicle, and a first appointment, and the question is where in that sequence the paid day begins.

The practical lesson in “When the First Job Is the Commute” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring dual n back training, the Monitask website can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

It is the most legally developed corner of this subject and the least settled operationally, because the arrangements vary enormously and the systems record almost none of what matters.

For a separate benchmark relevant to “When the First Job Is the Commute”, consult the Singapore Ministry of Manpower working-hours guidance. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

The patterns, and how they differ

Depot start. The worker attends a base, draws work and a vehicle, and travels out. Travel from home to the depot is ordinarily the commute; travel from the depot onwards is ordinarily working time. Relatively clear.

Home start with a company vehicle. The vehicle is at home, the work is allocated electronically, and the first destination is a customer. Here the position in many jurisdictions has moved: where there is no fixed place of work, travel from home to the first assignment and from the last back may be working time, because the employer determines the destinations.

Home start, own vehicle, fixed first site. Closest to an ordinary commute and usually treated as one.

Variable sites with long travel. Construction and installation work where the site changes weekly and the distance is substantial. Frequently governed by an agreement with a travel-time rule rather than by the general position.

What the systems record

Almost nothing useful. A punch on arrival at the first job. A vehicle telematics ignition event. An app login. A job status change.

The loading, the vehicle check, the paperwork and the route planning leave no trace at all, and they are the part that is clearly required.

The practical consequence is that a dispute about a mobile worker's hours is argued from telematics and phone records rather than from the time system, which is a weak position for whoever has to produce the evidence.

What to record instead

A start event that the worker triggers when the required activity begins, separate from arrival at the first job. Most field service applications support it and most deployments do not use it.

The vehicle check, which should be recorded anyway for compliance and which stamps the start of required activity with a timestamp nobody can dispute.

And the allocation time: when the day's work was made available. A worker given their schedule at 07:30 for an 08:00 first appointment has a different case from one who had it the previous evening.

Arrangements that hold up

Pay from the start of the first required activity — the load, the check, the briefing call — rather than from arrival at a customer. It is simple to state, it matches what is actually happening, and it removes the argument about the drive by making the drive part of an already-started day.

Where that is too expensive, a travel allowance for the first and last journeys, agreed and written, which is the route most sectors with a collective agreement have taken.

What does not work is a position that the day starts on arrival at the customer while also requiring a vehicle check, a load and a route at home beforehand.

The hours limits, which bite harder here

Working-time maxima and rest requirements are computed on working time, so where the travel counts, the day is much longer than the job record shows.

A worker with eight hours of appointments and two hours of travel either side has a twelve-hour day. Rotas built from appointment durations alone routinely breach rest requirements without anybody noticing, because the system that holds the appointments does not hold the travel.

The number worth producing

For one week, for one team: the gap between the first required activity and the first paid minute, and the gap at the other end.

It is obtainable from telematics and job records with a day's work, it is usually between forty minutes and two hours a day, and it is the largest single edge figure anywhere in this collection.

Where the first job is chosen

The allocation decides the length of the edge, and it is usually optimised for the working day rather than for the journeys at either end of it. A scheduler that fills the first slot from the top of the list sends somebody across the county at seven in the morning.

Scheduling the first and last jobs by proximity to home, where the work allows it, shortens the contested journey without changing anything else. It is a constraint added to the optimiser, not a new system, and on a mobile workforce it is the single cheapest reduction available.