Two ways to record
Declarative: the employee fills in their grid from their workspace. Clock-in: they punch arrivals, breaks and departures in real time. The mode is set per company, with nothing else to change.
Module · Time & activities
hours get declared, overtime gets computed.
Monthly grid or online clock-in, your choice. The manager approves the week, eachr computes the premiums according to the agreement, and turns overtime into rest if you decide so. Schedules, projects and annualization included.
what changes when time is kept in one place.
Overtime without a spreadsheet
25% and 50% tiers and the weekly threshold set according to the collective agreement, legal values by default. Days and weeks that run too long are flagged as anomalies before approval.
Planned versus actual
A published weekly schedule, projects to allocate time to, and stats that compare planned shifts with hours actually recorded, per employee and per project.
from the week to the rest earned.
The schedule is published
Shifts, breaks and project per employee, prepared as a draft then published for the week. The employee sees "My schedule" in their workspace, the previous week copies in one click.
The employee records or punches
In declarative mode they fill in their hours per day. In clock-in mode they punch and can report a missed punch. Without a password, from their phone.
The manager approves the week
Declared, planned, gap: everything side by side. Anomalies (a day over 10 hours, a week over 48, inconsistent punches) are flagged before approval.
Overtime finds its way out
Paid with its premium in the export, or converted into compensatory rest added to the employee's balance. The annualization counter follows the reference period.
everything the module can do.
- Declarative timesheets, week or month view
- Online clock-in: arrivals, breaks, departures, missed-punch report
- No geolocation or biometrics, punches purged after the set period (60 months by default)
- Privacy notice shown to the employee, employer commitment on activation
- Weekly approval by the manager, declared vs planned and gap
- Anomalies: daily max 10h, weekly max 48h, inconsistent punches
- Overtime at 25% and 50% with an adjustable threshold per agreement
- Overtime converted into compensatory rest, in days or hours
- Weekly schedule: draft, publish, copy the previous week
- Clients and projects, time allocation, planned vs actual stats
- Annualization: reference period, 1607h target adjusted for part-time
- Day-rate contracts: monthly attendance declaration and dedicated counter
Included with the core
The contract drives the math.
Weekly hours, part-time, day-rate or annualized contract live on the core's employee record. The module reads them to compute overtime, targets and counters.
- Employee record: weekly hours, contract type, working time
- Line manager and org chart
- Employee workspace with no password
- Sites and per-company settings
- CSV and XLSX exports
- Module setup assistant
questions about time and activities.
what we get asked before switching the module on.
Declarative or clock-in, how do I choose?
The mode is set per company in the settings. In declarative mode, the employee fills in their monthly grid from their workspace. In clock-in mode, they punch arrivals, breaks and departures in real time from the online clock. Both feed the same timesheets, the same approval and the same exports.
Is the clock-in compliant with privacy rules?
It only collects arrival, break and departure times, with no geolocation or biometric data. On activation, the employer confirms they have informed employees of the purpose and their rights. A notice is shown to the employee, who can view their punches and request a correction. Punches are deleted automatically after the set period, 60 months by default.
How is overtime computed?
Beyond the contract's weekly hours, the first hours carry a 25% premium, then 50% past the threshold (8h by default). These values follow the collective agreement. Once the timesheet is approved, you choose: pay them with their premium in the export, or convert them into compensatory rest added to the employee's balance.
Is the schedule mandatory?
No. It serves teams working in shifts: you prepare the week as a draft, with breaks and project, then publish it. The employee sees their shifts and rest days in their workspace. The schedule's planned hours are then compared with the actual timesheets.
What about annualized contracts?
You set the first month of the reference period and the annual target (1607h by default, pro rata for part-time). The annualization counter follows each employee concerned over the period, with no effect on other contracts.
What about day-rate employees?
They declare their days of attendance every month from their workspace, and a dedicated counter tracks the number of days worked. They are excluded from hour-based computations and from the schedule, since their contract is not measured in hours.
switch on time and activities in one click.
14-day full trial, no card. The module is included in the price, with the six others.