Remote and hybrid working models have brought real flexibility, but also an uncomfortable question: how do we record working hours without turning the relationship into a 'Big Brother' situation? The good news is that it is possible: the key is to separate time tracking (a legal obligation and guarantee of rights) from performance monitoring (objectives and results).
1) The obligation to record working hours does not disappear when working remotely
Working from home does not eliminate the obligation to record the start and end times of the working day. In fact, in hybrid teams, there is often a greater risk of 'invisible hours': people who connect earlier, respond to messages outside working hours, or extend their day to 'compensate' for breaks. Without records, these excesses are left unprotected for the worker and without defence for the company.
In practice, good time tracking in remote work helps set clear boundaries. If the system shows that an employee is consistently accumulating overtime, the conversation stops being subjective ('it seems like you work a lot') and becomes objective ('you have 6 overtime hours this week — what is happening with your workload?').
2) Design a simple and consistent clock-in method
Remotely, friction kills adoption. If clocking in requires opening three screens or requesting a VPN, people will skip it 'just for today'... until it stops being an exception. Ideally, a web or mobile clock-in with a couple of clear actions: start the day, end the day, and record breaks if your policy requires it.
A simple example: a hybrid support team clocks in from the employee portal. When they start, they click 'Clock in'. If they take a break, they record 'Break'. When they finish, 'Clock out'. If they forget one day, they request a correction with a reason ('forgot to clock out') and the supervisor approves it with traceability. It is quick, auditable, and reduces disputes.
3) Geolocation: use it only when it adds real value
Geolocation should not be the norm for remote working. In most roles, it adds nothing to recording compliance and does add privacy risks and distrust. Where it may make sense is in mobile teams (delivery, maintenance, sales) to confirm presence at a location or to facilitate the operational management of routes.
If you decide to use it, define clear rules: only at the moment of clocking in (not continuous tracking), with an explicit purpose, minimising data collection, and with alternatives when there are justified situations (for example, indoor work without GPS). And above all, communicate it: the 'why' matters as much as the 'how'.
4) Breaks, flexibility, and disconnection: record them without penalising work-life balance
Remotely, micro-breaks are normal: taking a child to school, receiving a parcel, or stopping for 10 minutes. If the record is interpreted as 'surveillance', people will hide breaks and end up extending the day without control. On the other hand, if it is understood as a transparency tool, it helps people work better.
A good practice is to define a simple policy: which breaks are recorded, which are assumed within the organisation of work, and how compensation is made if applicable. For example, allowing flexibility in a time band (8:00–10:00) and only requiring registration of start/end times, avoiding demanding that every micro-break be 'clocked'.
5) Win-win approach: protect the person and the company with the same data
For the worker, a clear record prevents unacknowledged overtime and sets limits on availability. For the company, it provides defence against inspections and reduces the risk of labour disputes, because the data is traceable and managed with rules known to everyone.
The winning combination is: simple recording + clear policy + incident traceability + periodic review of metrics (overtime, forgotten clock-ins, workload patterns). That turns remote working into a sustainable model, not a 'always connected' one.