Quick Answer
To track employee time in field service, capture hours on a mobile app against each job or work order, split by time type — on-site labour, travel, standby, callout and overhead. Make entry offline-capable so nothing is lost without coverage, attach evidence such as location, photos, parts and a client signature, have supervisors approve daily, and drive payroll and client invoicing from the same approved record. Then review utilisation, travel share and wait time weekly.
Why field service time is harder than a workshop or an office
An office worker has one location and one pay rule. A workshop tradesperson has one location and several jobs. A field service technician has several locations, several jobs, travel between them, waiting on permits and isolations, callouts at 2am, and patchy coverage the whole way. That's why generic time clocks fail here: they can tell you a technician worked 11 hours, but not that three were travel, one was waiting on a crane, and only six were billable. The fix isn't more discipline — it's capturing time against the job with the right time type at the moment it happens.
8 steps to track field service employee time
Start from the job, not the clock
Field service time only makes sense attached to a job. A technician's day is a sequence of jobs, travel legs and waiting, not a single shift block. Capture time as entries against job or work order numbers, and let the daily total fall out of that — the reverse never reconciles.
Define your time types up front
Agree a short list before rollout: on-site labour, travel, standby or wait time, breakdown callout, workshop, yard and pre-start, training, and rework. Each one has different pay and billing treatment, and if there's no code for it, the technician puts it somewhere wrong.
Make mobile capture offline-first
Pits, underground, remote highways and camp accommodation all lose coverage. Time entry must save on the device and sync when signal returns. If the app needs live data, crews go back to writing hours on a docket at the end of the week from memory, and you lose 5 to 10 percent of billable time to rounding.
Decide how travel time is treated — once
Travel is the most disputed number in field service. Set the rule in the system: paid from depot or from home, travel billed at labour rate or a separate rate, kilometre allowance, first and last leg treatment, and whether a callout attracts a minimum charge. Write it into the award or EBA configuration so it applies without argument.
Capture time with the evidence in the same entry
The best field service time record carries its own proof: timestamp, GPS location of the entry, photos, parts used, meter readings and a client signature. That combination is what turns hours into an invoice a client pays without querying, and a WHS record you can defend.
Approve daily, by supervisor
Field techs finish at different times across a big footprint. Daily approval on the supervisor's phone — review, adjust, approve — keeps errors small and recent. Weekly batch approval under payroll pressure is how unbillable and unverified hours get waved through.
Bill from the same approved hours you pay
One approved record should feed payroll and the client invoice. Two systems means two truths, and the gap between them is your unbilled labour. Track that gap deliberately: hours paid versus hours billed, per technician, per week.
Watch utilisation, travel share and response time
Weekly: billable utilisation per tech, travel hours as a share of total, wait time by client or site, and first-time-fix rate. Those four numbers tell you whether the problem is pricing, scheduling or territory design — none of which show up in a payroll report.
Field service time types and how to treat them
Getting these categories right at entry is what makes payroll and invoicing come off the same record. Confirm pay treatment against your specific award or enterprise agreement.
| Time type | How to capture it | Pay treatment | Billing treatment |
|---|---|---|---|
| On-site labour | Start and finish per job, or a running timer on the work order | Ordinary hours or overtime per award / EBA | Billable at labour rate |
| Travel between jobs | Automatic leg or manual entry with kilometres | Usually paid; check the award and EBA | Billed at labour or travel rate, per contract |
| Standby / wait time | Own code, entered on site | Paid | Often billable if caused by the client — only if you record it |
| Breakdown callout | Callout flag on the job with response timestamps | Callout minimum plus penalties | Callout fee plus hours, plus response-time SLA evidence |
| Yard, pre-start and workshop | Overhead codes | Paid | Usually non-billable overhead |
| Rework / warranty | Rework code linked to the original job | Paid | Non-billable — but the number drives quality improvement |
Ways to capture technician time, compared
| Method | Strengths | Limitations | Best fit |
|---|---|---|---|
| Paper dockets and job cards | No rollout, works anywhere | Late, illegible, hours estimated from memory, invoices delayed by weeks | One or two techs, local work |
| Spreadsheet sent weekly | Free, flexible | No approvals, no evidence, no live visibility of where hours are going | Small teams starting out |
| Generic time tracking app | Cheap, simple clock-in and clock-out | No job or work order context, no award rules, no invoicing path | Attendance-only requirements |
| GPS fleet tracking | Accurate vehicle movement and site arrival times | Tracks the ute, not the labour type — can't tell on-site from wait time | A useful supplement, not a time system |
| Field service management software | Offline mobile entry against work orders, travel rules, evidence capture, approvals, payroll and invoicing from one record | Needs job, rate and code setup up front | Any team running multiple techs, clients or sites |
The four numbers to review every week
Billable utilisation per technician
Billable hours as a share of hours paid. The headline measure of whether your scheduling and pricing work.
Travel as a share of total hours
Rising travel share usually means territory or dispatch design, not lazy techs. It is also the easiest cost to fix.
Standby and wait hours by client or site
Shows which clients and sites cost you time, and gives you the evidence to recover or renegotiate it.
Hours paid versus hours billed
The gap is your unbilled labour. Tracked weekly it stays small; discovered at month-end it is already written off.
Mistakes that make field service time tracking fail
Best setup for a mobile crew
Offline mobile entry against the work order, time types for labour, travel and standby, evidence attached in the same entry, and daily supervisor approval on a phone.
Keep the record defensible
Seven-year retention, a logged audit trail for every adjustment, award and EBA rules applied by the system, and any location tracking disclosed to the crew up front.
Time is one part of the field service picture. For the wider system see field service software and management, and for the workshop equivalent read how to track employee time in the workshop.
Related reading: How to track employee time in the workshop · Best time tracking software · Best time tracking app for Australian crews.
