Skip to content

Constraint plugins

Constraint plugins are the rules a work time policy checks an employee’s time against — for example the daily rest between two working days, or how far back time may be registered.

What a constraint does

Most constraints check each day of the timesheet, from the first day of the period up to and including today. Future days are not checked. When a day breaks a rule, the timesheet marks that day, and the period overview lists the breach with the day and the figures behind it.

A few constraints work differently: they are checked at the moment time is registered, and refuse the registration outright instead of flagging the day afterwards. These are Allow future registration , Limit backdating and Check in/out not used .

Work time policies stack: every policy that applies to an employee contributes its constraints, and each one is checked on its own.

Blocking and non-blocking constraints

When you add a constraint to a policy, you choose the section you add it to:

SectionWhat happens on a breach
Blocking constraintsThe employee cannot submit the timesheet until the breach is resolved.
Non-blocking constraintsThe breach is shown as a warning, but the timesheet can still be submitted.

The same plugin can be blocking on one policy and non-blocking on another. The rule itself is identical — only the consequence changes.

The three constraints that refuse registrations (Allow future registration , Limit backdating , Check in/out not used ) are always blocking, so they are only offered under Blocking constraints .

Rules that apply without a constraint

Two checks apply to every employee, whether or not a policy configures anything:

  • Open check-in — a day with a check-in but no check-out blocks submission until the check-out is added.
  • Nothing registered — a working day with no time registration and no check-in, and not covered by time off, blocks submission. Add Allow missing registration to a policy to turn this check off for the employees it applies to.

Available constraints

ConstraintWhat it checks
Maximum Daily HoursMaximum worked time per day — not enforced yet
Maximum Weekly HoursMaximum worked time per week — not enforced yet
Mandatory BreakA break after a period of continuous work — not enforced yet
Daily Rest (Hviletid)The rest between the last check-out and the next day’s first check-in
Weekly Free Day (Fridøgn)One long continuous rest within a rolling number of days
Daily Flex LimitsHow far worked time may go above or below the day’s norm
Balance CapA ceiling on the flex balance — not enforced; use the settlement policy’s balance cap
No work beyond norm during time offWork on a day with time off, beyond what the time off leaves
Mandatory Check-inAt least one check-in on every working day
Mandatory Time RegistrationAt least one time registration on every working day
Allow missing registrationTurns off the check that every working day has something registered
Attendance Matches RegistrationsRegistered time matches checked-in time on every working day
Allow future registrationHow many working days ahead time may be registered
Limit backdatingHow many working days back time may be created or edited
Check in/out not usedTurns check in/out off for everyone on the policy