Time tracking for technicians: methods, rules and practice

Time tracking for technicians means recording when, where and on what your field staff work: start and finish times, breaks, the job and the type of hours. Companies with field technicians do this in one of three ways: clocking in with an app, badging in at a terminal or filling in hours themselves. Accurate records are the basis for correct pay and undisputed invoices, and in the EU, member states must require employers to record each worker's daily working time.

Why accurate hours matter

For technicians working at changing locations, hours drive four things at once.

• Pay. Overtime, premiums, on-call allowances and paid travel time all come from the record. A quarter of an hour a day adds up to 55 hours a year over 220 working days.
• Invoicing. On a time-and-materials contract, the hours are the invoice; on a fixed price, they show, when you cost the job afterwards, whether it earned what you budgeted.
• Law and safety. Working time rules cap shift length and require rest. A technician who works through a night-time breakdown and then does the day shift is working tired on plant under pressure or voltage.
• Knowing who is on site. Anyone who badges in on arrival or clocks in on site is recorded as present. In an evacuation you want to know who is inside, including the crews of contractors working on your site.

Keep two kinds of hours apart. Attendance hours show when someone was working; they count for pay and the law. Hours booked on a work order show what was worked on; they count for cost per asset and maintenance history. The two don't have to match, but they must be consistent: someone who was present for 9 hours and booked 11 hours to work orders has made a mistake somewhere.

Three time tracking methods for technicians

The three common methods differ mainly in when the time is captured: the later, the more the record relies on the technician's memory and the more work the office has afterwards. The diagram below sets them side by side.

Clocking in with an app suits technicians who visit several addresses a day, such as service engineers in energy and building services. You pick the job when you clock in, so the hours land on the right project straight away. Boiler houses, basements and remote substations don't always have a signal, so choose an app that stores clock events until it reconnects.

Badging at a terminal works well where many people come in at one point: the gate of a production site, the site cabin on a project or the entrance of a waste-to-energy plant during an outage. Badging is quick and needs no phone, but the terminal doesn't know what someone is working on: the job and hour type are added later. And one colleague can use another's badge; a fingerprint reader looks like the fix, but as a rule it isn't allowed for this purpose (more on that below).

Filling in hours asks the least: no equipment, just a form or an app. It suits short jobs, small teams and regular working days, but the record is made after the fact. Whoever fills in the whole week on Friday is estimating, and estimates get rounded. So have hours filled in daily.

You don't need one method for the whole company: service technicians clock in with the app, the crew on a long-running process plant project badges in at the site cabin and the seconded technician fills in hours and has them signed off. As long as everything ends up in one timesheet per employee per week, you keep the overview.

What the law requires from time tracking

Across the EU, the Working Time Directive sets the floor: average weekly working time of no more than 48 hours including overtime, 11 consecutive hours of rest in every 24 hours, and a minimum weekly rest period. In 2019 the Court of Justice ruled that member states must require employers to set up "an objective, reliable and accessible system enabling the duration of time worked each day by each worker to be measured" (case C-55/18). Member states decide the precise form and may take account of the sector and the size of businesses. In practice that means: record times as they happen, make every change visible and let employees see their own records.

In the Netherlands, Article 4:3 of the Working Hours Act (Arbeidstijdenwet) requires employers to keep a "proper record" of working and rest times that allows compliance to be checked. For most sectors the law does not prescribe the means. Records must be kept for at least 52 weeks from the date they relate to. The recording duty and the limits below do not apply to employees earning at least three times the minimum wage, except for offshore work, regular night work or work involving serious hazards to safety or health.

Offshore, on a manned mining installation or wind farm, the record must be kept on site, with a copy at the Dutch head office within six weeks. And the Dutch Minimum Wage Act also expects you to show on request how many hours someone has worked. Who exactly the duty applies to, how long to keep what and which fines apply is covered in our article on whether time tracking is mandatory.

The record has to show whether the statutory limits are being met. For employees aged 18 and over, the basic Dutch limits are:

A breakdown that runs through the night, or a shutdown with weeks of long days, brings these limits into view quickly. A record that flags shifts over 12 hours and short rest periods helps you adjust before it becomes a pattern.

Privacy: biometrics, location and the works council

Time tracking processes personal data, so the GDPR applies. The Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) sets out the conditions for monitoring staff: a legal basis, necessity, and telling employees in advance what you record, why and how. Consent is a weak basis in employment, because employees find it hard to refuse a request from their employer.

Fingerprints and face scans: generally not

Biometric data such as fingerprints and face scans are special category data when used to identify someone. Processing them is prohibited unless an exception applies, and for employers two come into play: explicit consent, which employees can rarely give freely, and necessity for authentication or security. Since 1 September 2026 the second exception has been narrower in the Netherlands: it only applies where a substantial public interest in lawful access to certain places, buildings, services, products or systems requires it (Article 29 of the Dutch GDPR Implementation Act). In December 2019 the AP fined a company €725,000 for scanning employees' fingerprints for time and attendance registration, and announced the fine in April 2020. The company could rely on neither exception. After an objection, the AP itself reduced the fine to €50,000 because of the company's limited financial capacity during the coronavirus crisis. A badge or a personal app login is the obvious alternative.

Location at clock-in: measuring is not tracking

An app can record the location at clock-in and clock-out, so you can see whether someone clocked in at the project site. That is different from following a technician all day. Keep it to one reading at the moment of clocking, with a clear purpose, and tell employees what you record. If you record locations systematically, you will normally have to carry out a data protection impact assessment (DPIA) first: the AP names systematic monitoring of employees, for instance with GPS trackers, as a situation where one is mandatory.

The works council has a right of consent

In the Netherlands, the works council must consent to any arrangement for "facilities aimed at or suitable for observing or monitoring the attendance, behaviour or performance" of staff (Article 27(1)(l) of the Works Councils Act). A time tracking system records attendance, so it falls within that scope. A works council is mandatory from 50 people. If you go ahead without consent, the decision is void if the works council invokes that in writing within a month; if a collective agreement already covers the matter in substance, consent is not required.

Handling exceptions without losing the audit trail

No record is flawless. Four exceptions keep coming back:

• Forgotten clock-out. The record runs on until the next morning, for instance because the technician drove straight home from the client.
• Clock-out without clock-in. There is a finish time but no start, because there was no signal in the morning or the badge was left at home.
• Long shift. More than 12 hours in a row. If it is genuine, for example after a breakdown that overran, the shift is over the 12-hour limit in the table above: record the reason and protect the rest period that follows. If not, someone probably forgot to clock out.
• Overlap. Two records at the same time, for instance on two projects, or via both app and terminal.

Put exceptions on a separate list and go through it weekly: after a week the technician still remembers what time it was, after a month they won't. Someone who forgot to clock out after a callout that ended at 23:40 gets the right hours with a single correction ("finished 23:40 per job sheet, forgot to clock out").

If you work in shifts, watch the overlap at shift handover. The minutes in which one crew briefs the next are working time and belong in the record, not in a grey zone between two shifts.

From time records to timesheet and payroll

Clock events are raw data. For pay and invoicing you turn them into a timesheet per employee per week, showing for each day the times or hours, break, project, hour type and kilometres. How clock entries and manually entered hours come together in one weekly timesheet is shown on the time tracking page. Three parts deserve attention:

• Hour types. Normal hours, overtime, on-call and travel each carry their own premium or allowance under the collective agreement or contract. Map hour types one-to-one to pay elements, or payroll will still be piecing things together. How to record overtime and turn it into payable hours is covered in recording overtime.
• Breaks. An automatic break rule saves typing, but is only right if the break was actually taken. If the technician had to stay with the plant, it was not a break in the legal sense (see the questions below), so allow exceptions with a reason.
• Travel time and mileage. Agree where you count from (home, branch or first client) and which travel hours are paid. For working time limits, travel can count even when you pay for it differently.

Then the client signs off the hours on their own project and the manager approves the week; how to set that up so it stands up to scrutiny is covered in timesheet sign-off.

Rolling out time tracking in seven steps

A new way of recording hours stands or falls with the technicians who use it. This sequence helps:

1. 1Set the purpose and rules. What do you record, what for (pay, invoicing, the law) and what do you deliberately leave out? Less data means fewer arguments.
2. 2Choose a method per team. Start from where and how the team works, not from everything a system can do. What to look for in an app is covered in choosing a time tracking app; for a small team, a spreadsheet template can be enough.
3. 3Involve the works council. Ask for consent in good time, discuss location data and retention periods, and check whether a DPIA is needed.
4. 4Set up hour types and rules. Premiums, break rules, travel arrangements and client-specific agreements.
5. 5Pilot with one team. Four weeks with a crew that dares to be critical teaches you more than a polished presentation.
6. 6Explain it and keep it simple. One action at the start and one at the finish, and show technicians what is in it for them: overtime that adds up.
7. 7Agree a fixed rhythm. Who reviews exceptions each week, who corrects them, and when does the week go to the office?

Many lessons from implementing maintenance software apply here too: start small, bring the shop floor in and steer on use rather than on go-live.

Common mistakes in time tracking

• Biometrics because you can. A fingerprint reader looks fraud-proof, but for time recording it is generally not allowed.
• Tracking instead of measuring. Logging locations continuously where one reading at clock-in would do.
• Overwriting instead of correcting. Deleting the original makes the record unreliable, even if the new time is right.
• Hours entered at month end. Anything filled in afterwards is an estimate.
• A break that never happened. Deducting it automatically while the technician worked through a breakdown.
• Rolling out without the works council. It costs more time afterwards than it would have beforehand.