Travel-time stamping: recording the drive between two sites

A third answer when clocking out

With the function switched on, your staff can pick “site change” when clocking out – alongside “end of work” and, if active, “break”.

Tipp: The question only appears at clock-out. Jobilino never asks when clocking in.

The gap becomes an entry of its own

When the person clocks in at the next site, Jobilino creates a time entry for the time in between – marked as travel time and without a project.

Tipp: The difference to a break: a break stays a pure gap, while travel time becomes a real entry. It is working time, after all.

Working time yes, customer time no

Travel time counts as hours worked and feeds into overtime. It deliberately belongs to no project and no contingent, though – a site change belongs to no customer.

Tipp: So the drive appears in your hours but does not distort any costing or any invoice to the client.

The stamp at the destination stays real

The clock-in time at the next site is not shifted. The travel time is placed before it instead of overwriting the actual start of work.

Activate the switch

Administration → Time tracking → “Travel-time stamping (‘site change’)”. From then on the extra answer appears at clock-out – in the app, in the web app and with NFC.

Tipp: The function is independent of break stamping. You can switch on both, one, or neither.

Set the limit per drive

Define how long a drive may be to count automatically as travel time: between 5 and 240 minutes, 60 by default. The limit applies per individual drive, not per day.

Tipp: Take your realistic longest drive between two of your sites as the guide, not the exceptional case. Anything above that deserves review, not an automatic credit.

Tell the team

One sentence is enough: anyone driving to the next site picks “site change” – not “end of work”. Anyone finishing for the day still picks “end of work”.

Tipp: If “end of work” is picked by mistake, no travel time is created. It can be marked afterwards by editing the entry.

Nothing is credited automatically

If the gap exceeds your limit, Jobilino creates no travel time. The real stamp at the destination counts unchanged, and the entry's history records that a travel time was not counted.

Tipp: That is deliberate: a three-hour gap may be a long drive – or a forgotten clock-in. Jobilino does not guess.

The intended route: add it manually

Enter the actual driving time as a manual entry. In the form, pick “travel time” as the entry kind and give the start and the end.

Tipp: A manually recorded site change is deliberately NOT subject to the limit – it is precisely the route for capturing an over-long case properly. In return it goes through the usual approval.

Exactly on the limit

A drive matching the limit exactly is still credited. The rule only bites above it.

When no further job follows

Sometimes the drive ends without any work afterwards – returning to the depot, for instance. While you are travelling, the app shows that state and offers a button to end the travel time explicitly.

Tipp: Without ending it and without a next stamp, no travel time is created – an open drive with nothing after it counts nothing.

The first minute is locked

The button cannot be pressed during the first sixty seconds. That prevents travel times of a few seconds through an accidental double tap – the same lock as when stopping working time.

The limit applies here too

If the drive is already above your limit when you end it, Jobilino refuses and points to the manual entry.

In the entry list

Travel-time entries are marked as such and recognisable by having no project. After clocking in at the destination, the app also shows a brief note that the drive was recorded.

Monthly view, PDF and Excel

The monthly overview carries travel time as a total of its own, per day and per month. The PDF and the Excel export show the same figures.

Tipp: So for the first time you can see, with evidence, how much working time actually sits in driving – a figure that disappears inside flat rates.

A closed month

At the month-end close travel time stays visibly reported. Its minutes are already inside the hours worked – the separate line shows which share of them was driving.

The commute does not count

The first stamp of a day never creates travel time – there is no earlier site to have changed from. The journey from home is therefore left out.

Only between real stamps

Travel time arises exclusively between two stamped times on the same day. Manually recorded and full-day entries do not trigger it.

Nothing is counted across midnight

A drive crossing midnight creates no travel time, because the closing stamp falls on the next day. On night shifts, add it manually.

How it interacts with breaks

Travel time is not a break: it earns no paid-break credit and does not start the rest period either – only a real end of work does that.

Tipp: Anyone who both drives and takes lunch between two sites stamps them separately: first “site change”, then clock in at the destination, and after arriving pick “break”.

After the last job

The drive after the last clock-out of the day is not recorded automatically. If you pay for the return journey, use the button to end travel time or add it manually.