Work time policies
Work time policies define working time rules and constraints for your employees, such as maximum daily hours and mandatory breaks.
Overview
A work time policy combines two types of rules:
- Constraints — Validate time registrations against working time limits (e.g., maximum hours per day or week, mandatory breaks)
- Auto-registrations — Automatically adjust worked time (e.g., deducting unpaid lunch breaks)
Each work time policy decides in its Availability section which employments it applies to — by work country, org unit and employment terms.
Getting started
To create a work time policy:
- Go to
- Click Add Policy and select Work Time Policy
- Enter a name and optional description
- Add constraint plugins to enforce working time rules
- Under Availability , choose who the policy applies to
- Click Save
Turning check in/out off
Some organisations register work time by entering hours and never use check in/out at all. Add the Check in/out not used constraint to a work time policy, and for everyone it applies to:
- the Check in/out row disappears from the timesheet
- the check-in buttons and the running clock disappear from the dashboard and the top bar
- new check-in registrations are refused
Existing registrations are kept. They stay visible in the check in/out report, and an administrator can still correct or delete them.
Someone who is checked in at the moment you add the constraint can still check out — their session is not left running.
Turn it off for one client without touching the others
Work time policies stack: every policy that applies to an employee contributes its rules. So the tidiest way to switch check in/out off for one group is a policy of its own, rather than editing a policy other people share:
- Go to , click Add Policy and select Work Time Policy
- Name it something like No check in/out and leave the work time norm, the other constraints and the auto-registrations empty
- Under Blocking constraints , click Add Plugin and choose Check in/out not used
- Under Availability , choose the org units or employment terms it applies to
- Click Save
A policy like this does nothing except switch check in/out off — it has no norm of its own, so it never competes with the norm the employee already gets, and it adds no other rules.
Do not combine it with the Mandatory Check-in constraint: that rule requires a check-in on every working day, which nobody on this policy can make.
Constraint plugins
Constraint plugins validate time registrations and flag warnings or errors when limits are exceeded.
| Plugin | Description | Configuration |
|---|---|---|
| Maximum Daily Hours | Limits the total worked time per day (e.g., 10 hours for German labor law compliance) | Maximum minutes per day |
| Maximum Weekly Hours | Limits the total worked time per week (e.g., 48 hours for EU Working Time Directive) | Maximum minutes per week |
| Mandatory Break | Requires a minimum break after a period of continuous work (e.g., 30 minutes after 6 hours) | Work threshold, break duration |
| Daily Rest (Hviletid) | Requires a continuous rest period before a working day may begin (the EU Working Time Directive sets 11 hours) | Minimum rest minutes |
| Weekly Free Day (Fridøgn) | Requires one continuous rest period within a rolling reference period (35 hours in the directive) | Minimum rest minutes, reference period days |
| Daily Flex Limits | Limits how far an employee can deviate from the daily norm | Maximum overtime and/or deficit in minutes |
| Mandatory Check-in | Requires at least one check-in on every working day | None |
| Mandatory Time Registration | Requires at least one time registration on every working day | None |
| Allow missing registration | Turns off the default error that requires every working day to have time registered or be covered by time off | None |
| Attendance Matches Registrations | Requires the time registered on a working day to match its check-in/out time exactly | None |
| Allow future registration | Allows check-in/out and time registrations ahead of time, up to a number of the employee’s working days; without it, time can only be registered up to today | Days ahead, separately for check-in/out and registrations |
| Limit back-dating | Restricts how far back, in the employee’s working days, time data may be created or edited; without it, back-dating is only stopped by locked periods | Days back for registrations and check-in/out, whether a manager can override |
| Check in/out not used | Employees on this policy do not check in and out: the check in/out row on the timesheet and the check-in buttons on the dashboard are hidden, and new check-in registrations are refused | None |
| No work beyond norm during time off | Flags work recorded on a day that carries time off, once it goes past the working time the time off leaves. A full day off leaves none; a half day leaves the other half | None |
No work beyond norm during time off
This rule also changes what employees see when they check in on a day they have time off.
Checking in during time off always asks the employee to confirm. With this rule on and a full day off, the dialog additionally warns that the day will be reported on their timesheet. It does not stop them registering the work — the breach is reported where breaches belong, on the timesheet, rather than leaving someone at work with no way to record it. A partial day is unaffected: the rest of the day is still working time, and only the minutes past it are flagged.
The dialog never offers to end a vacation, with or without this rule; only sick leave can be ended from there. Everything else is changed on the employee’s own time off page.
As with any constraint, whether a breach blocks timesheet submission or only warns depends on whether you add it as a blocking or a non-blocking constraint.
Auto-registration plugins
Auto-registration plugins automatically adjust worked time based on predefined rules — for example, deducting an unpaid lunch break or filling unregistered attendance onto a default activity. Each plugin has its own behaviour and configuration options, and several can be combined on a single policy.
See Auto-registration plugins for the full list and how each one works.
Settlement
What happens to the flex balance at the end of a period — crediting the delta, premiums, balance caps and payouts — is configured in a separate settlement policy. The flex-balance ceiling that used to be a Balance cap constraint here is now a cap step on the settlement policy.
A flex account with no settlement policy still carries its balance forward automatically, so simple flex setups need no settlement policy at all.
Troubleshooting
| Issue | Solution |
|---|---|
| Flex balance or caps not applying | Flex crediting, caps and payouts live on a settlement policy and the flex account on the employment term — not on the work time policy |
| Check in/out is still showing | The setting applies per work time policy — make sure the policy carrying it applies to that employee, and that no other policy applying to them leaves check in/out on |
| Constraint warnings not appearing | Check that the constraint plugin is configured with the correct values and that the policy’s availability covers the employee |