Technician Travel Time Tracking on Jobs
Start and stop a travel timer on a job; the time is booked as labour on that job under an automatic Travel code.
Included with your module subscription at no extra charge. An administrator switches each pack on for your business in Admin > Features.
What job travel timer is
For a dealership with a service ute, the road to the paddock is part of the job, and when it is not recorded the job looks cheaper than it was. The job travel timer puts two buttons on the Labour tab of a job: Start travel and Stop travel.
Pressing Start begins a timer for the technician. Pressing Stop ends it and books the elapsed time as labour on that job, under a Travel code that MDMS creates automatically. Because it is real labour on the job, it counts in the job's hours and flows wherever job labour flows. It builds on Generic labour codes, so that pack has to be on first.
It measures time, nothing else. There is no map, no kilometres and no per-kilometre charge; the older travel trips feature remains a separate thing. A technician can only have one timer open at a time, and the only way to end it is the Stop travel button, which keeps the number honest. If a business decides it does not want travel recorded this way, a manager deactivates the Travel code and the buttons stop doing anything.
On a phone in the cab the interaction is deliberately small: one button to begin, one to end. Because the result is ordinary job labour, a manager reviewing the job sees the drive alongside the repair time instead of in a separate list, and anything that already reads job hours picks it up without extra steps.
Part of these modules
What job travel timer covers
- Adds Start travel and Stop travel buttons on the job's Labour tab
- Books the travel time as labour on that job under an automatically created Travel code
- Counts the travel in the job's hours
- Lets a manager switch travel off by deactivating the Travel code under Operations > Labour
Where job travel timer stops
Stated as it behaves today, so you can judge the fit before you switch it on.
- Records time only: no GPS, no distance and no per-kilometre billing
- Allows one open timer per technician
- Stops only from the Stop travel button, not from the Unplanned work card
- Is separate from the older travel trips feature
Job travel timer in a working day
A technician leaves the yard for a bore pump a long drive out. She taps Start travel in the cab before pulling out and Stop travel at the gate. The drive sits on the job as Travel labour. At invoice time the service advisor sees the job's real hours rather than just the hours at the pump.
Switching on job travel timer
Included with your module subscription at no extra charge. An administrator switches each pack on for your business in Admin > Features.
Switch these on first:
More feature packs
Generic labour codes
Let technicians clock on to yard, travel or workshop admin codes with no work order, then have a manager move the time onto a job.
Work order job segments
Organise a work order by fault, each with its own Bill to, technician, parts, labour, checklist and photos.
Segmented work order invoicing
Invoice a long chargeable work order in stages, billing chosen labour, parts and travel once, with the remainder billed at completion.
Frequently asked questions
- Does it log the route or kilometres?
- No. It records elapsed time only. There is no GPS capture and no distance billing.
- What has to be on before the travel timer works?
- Generic labour codes. The travel timer books its time under a Travel code that sits on that pack.
- Can I turn travel off after trying it?
- Yes. A manager deactivates the Travel code under Operations > Labour.
Where this work shows up
Ready to try job travel timer?
Start a 14-day free trial — no credit card, no implementation fee, no sales call required. Or book a personalised demo with our team to see your workflow in MDMS.