Consecutive sick days
Fires while an employee is still off sick and their absence has lasted a set number of calendar days.
This is the trigger behind sygedagpengerefusion: after the employer period (arbejdsgiverperiode) of 30 calendar days you may claim reimbursement, and nobody in mTime tells you the day arrives unless you set this up. The same trigger at 14 days covers the sygesamtale obligation.
When to use
Use it when someone needs to act at a fixed point in a long absence — claim reimbursement, book the return-to-work conversation, involve occupational health. Send it to the manager, to a shared HR address, or both.
For repeated short absences, which never reach a long run, use Sick days in period instead.
Parameters
| Parameter | Description | Default |
|---|---|---|
| Days | Calendar days the ongoing absence must reach before the advisory is sent. | 30 |
How it works
Every night mTime looks at everyone in the advisory’s Employees section who is off sick that day, works out when their current absence began, and sends the message once the absence has reached the configured number of days.
A few rules decide what “the absence began” means:
- Days are calendar days, not working days. An absence that starts on a Monday reaches 5 days on the Friday. This is what the agreements count, and it means a part-time employee reaches the same milestone at the same time as a full-time one.
- Weekends, holidays and other non-working days do not break the absence. Sick on Friday and sick again on Monday is one four-day absence, not two one-day ones.
- Any working day not covered by sickness ends it — including a day taken as vacation or time off in lieu. This matters for reimbursement: other leave interrupts the employer period rather than extending it. The next sick day starts a new absence, counting from 1.
- Only an absence that is still running triggers the advisory. A finished absence is never reported, and an absence booked in advance does not trigger anything until it has actually run for the configured number of days.
Each absence produces one email. A longer absence does not send a second one, but a genuinely new absence later does.
Message
Leaving the subject and text empty sends:
{employee_name} has been off sick for {days} days
{employee_name} has been absent due to sickness since {since} — {days} calendar days so far.
Available variables: {employee_name}, {workspace_name}, {date}, {days} (calendar days so far) and {since} (the first day of the absence).
Examples
Reimbursement after the employer period
- Add an advisory and select the Consecutive sick days trigger
- Leave Days at 30
- Under Recipients, add your payroll or HR address
Payroll hears about every absence that has reached the employer period, once each, on the day it gets there.
The return-to-work conversation
- Add a second advisory with the same trigger
- Set Days to 14
- Turn on Manager as the recipient
Two advisories on the same trigger with different thresholds is the normal setup — each sends its own message at its own point.