What to do when an employee does not clock in? etempus automates working time record follow-up

Having a clock-in system is not always enough. What happens when an employee forgets to record their working day, or goes several days without clocking in? It is a common situation and can turn into an administrative and legal problem. At etempus we have added a working time record compliance follow-up system to detect omissions, automate notifications and document what the company does, without spending hours reviewing clock-ins.

Who is responsible when an employee does not clock in?

Article 34.9 of the Spanish Workers' Statute requires the company to guarantee a daily record of working time, with the specific start and finish time of each employee. The obligation for that record to exist lies with the company.

Employees, in turn, must follow the orders and instructions the company gives in the regular exercise of its powers (articles 5.c and 20 of the Statute), and clocking in correctly is one of them.

In practice, this means that providing a time-tracking app is necessary, but not enough. If an employee does not record their working day, the company still needs that record. That is why it pays to have ways to detect omissions, ask for them to be regularised and later show what was done.

etempus automatically detects days without clock-ins

Every morning, etempus reviews the previous day and identifies the days on which an employee had to record their working time and there is no clock-in at all.

To decide whether there was an obligation, the system takes into account each person's contract, schedule and work calendar: public holidays, annual leave, permitted absences and sick leave do not count as days without clock-ins. Flexible schedules are checked by whole weeks.

Managers see everything on the Clock-in control page, with filters by department, employee and dates. From there they can create the corresponding incident with a reason and, where appropriate, close it with the scheduled hours. Employees also see on their clock-in screen the days of the last week with no record, so they can regularise them themselves.

Incidents with follow-up: who has to do what

An incident that nobody knows who has to resolve ends up forgotten. That is why every incident now shows its status:

  • Waiting for the employee: they need to confirm a time or explain what happened.
  • Waiting for the manager: they need to approve or reject it.
  • Resolved or rejected, with the reason.

The manager can ask the employee for a justification (the employee gets an email right away) and the employee can reply from the incident itself. The whole conversation is kept with the incident.

When the system automatically closes a working day that was left open, the employee can confirm with a single click that the time is correct, and the incident closes itself.

Notifications to reduce pending incidents

etempus lets you set up reminders for employees with incidents waiting for their reply. Instead of one email per issue, the system sends a single grouped email with everything that needs their attention, at most twice per incident.

Managers receive an incident summary daily or weekly (each one chooses the frequency) and can enable alerts when an employee has several days without clocking in or an incident has been open for too long. Each situation is notified only once.

Each company decides which notifications to enable, and each person can turn off their own in their profile.

Preventive notices to employees who do not clock in

This is the main new feature. etempus lets you set up notices to employees who accumulate days without a record, at two levels:

  • Level 1, preventive reminder: for example, when an employee has 3 consecutive working days without clocking in, or 5 days in 30 days.
  • Level 2, formal request: when new omissions keep happening after a reminder.

Each company sets its own criteria and thresholds. Only days that are still pending regularisation count, and the system avoids sending repeated notices for the same situation.

Level 1 can be sent automatically or after the manager's approval. Level 2 always requires the manager's approval: they see the exact email before it is sent and can discard it, giving a reason.

Custom emails for each company

etempus includes templates in Spanish, Catalan and English, with a professional and preventive tone, and each employee receives the email in their language. Each company can adapt the subject and the text, preview the result and send itself a test before enabling it.

The texts say that no clock-in is recorded, never that there is a breach: their aim is a complete record, not a sanction.

Notice history and acknowledgement of receipt

Every notice is recorded and cannot be modified afterwards. The company can check:

  • The employee it was sent to.
  • The dates of the days that triggered it.
  • Who approved it and when it was sent.
  • The exact content of the email.
  • When the employee read it in etempus and whether they acknowledged receipt.

Employees see their notices when they log in to etempus and can confirm they have received them. Acknowledging receipt does not mean agreeing with the content, and access to clocking in is never blocked.

More traceability for clock records

When a manager corrects or cancels a clock record, etempus stores the previous value, the new one, who changed it, when and the reason, which is mandatory. A cancelled record no longer counts, but it does not disappear from the history.

Employees can check the change history of their own clock records at any time. It is the simplest way to keep the record reliable and reviewable without losing the original data.

A report to monitor record compliance

The new compliance report, on screen and in Excel, shows per employee and period:

  • The days that had to be recorded and those with a complete record.
  • The percentage of days with a complete record.
  • Days without clock-ins and those that have been regularised.
  • Pending, resolved and rejected incidents, and the average time to resolve them.
  • Automatic clock-outs, manual changes and reminders sent.

How does etempus help with a labour inspection?

Having a computer system is not enough: records must be reliable, available and reflect the time actually worked. With these features, etempus helps to document:

  1. That the company has a working time recording system.
  2. That days without clock-ins are detected.
  3. That there is a procedure to request their regularisation.
  4. That reminders and preventive notices are sent.
  5. That the history of changes and actions is kept.

These measures improve the management and traceability of the record and provide useful information in an inspection. They do not replace the company's legal obligations and do not, on their own, guarantee that there will be no penalties, but they help to show what has been done to keep a correct record. To review the legal requirements, see our practical guide to the time-tracking law and the guide to mandatory digital time tracking.

Available now, and each company decides when to enable it

At etempus we believe time-tracking software has to do much more than record clock-ins and clock-outs: it has to help manage incidents, reduce admin work and adapt to each organisation.

These features are already available to all customers. Notifications and notices come disabled: each company sets its criteria, reviews the texts and decides when to enable them, with no unexpected changes for its employees.

Less time reviewing clock-ins, more control over the record and more traceability in an inspection.

Frequently asked questions

Are employees required to clock in?
Yes. The company must guarantee a daily record of working time (art. 34.9 of the Spanish Workers' Statute), and employees must follow the instructions the company gives in the regular exercise of its powers (arts. 5.c and 20), including using the time-tracking system correctly.
What happens if an employee does not clock in?
The day is left without a record, and the company still needs it. The best approach is to detect it early, ask the employee to regularise it and keep a record of how it was resolved. If omissions keep happening, it is worth talking to the employee to understand the cause: a slip, a technical problem or a wrongly configured schedule.
Can the company correct a clock record?
Yes, but it must be traceable. In etempus every correction or cancellation stores the previous value, the new one, who made it, when and the reason, and employees can check the history of their own clock records.
How can the company document the notices sent to employees?
etempus stores each notice with its exact content, the days that triggered it, who approved it, the date it was sent, the date it was read and the employee's acknowledgement of receipt. That history cannot be modified.
Are preventive notices a sanction?
No. They are reminders to keep the record complete and do not presume any responsibility on the employee's part. etempus does not apply sanctions: level 2 always requires a manager's approval, and acknowledging receipt does not mean agreeing with the content.

Want to improve time tracking at your company? We will show you how etempus automates the working time record, manages incidents and simplifies employee follow-up.

Contact us on WhatsApp