Missing time registration
Fires when an employee has left working days without any time registration in the timesheet period that is still open.
Everything this email says is already on the employee’s own timesheet, and mTime already chases an unsubmitted timesheet once the period is over. What this trigger adds is earliness: a forgotten Monday surfaces while the employee can still remember what they did, instead of five weeks later when the period is overdue.
When to use
Use it where time registration feeds payroll or invoicing, and a gap discovered at month end is expensive to reconstruct. Send it to the employee — they are the one who can fix it.
Sending it to managers or HR works, but each affected employee produces a separate email, and unlike the sickness monitors this trigger can fire for many people on the same morning.
Parameters
| Parameter | Description | Default |
|---|---|---|
| Minimum missing days | How many working days without any time registration must add up in the period before the email is sent. | 1 |
| Grace days | How many extra days to wait before a day counts as missing. A day can only be judged once it is over, so 0 already means “reported the morning after the day itself” — each further day gives the employee that much longer to catch up. | 1 |
How it works
Every night mTime looks at the working days in each employee’s open timesheet period, up to the grace-day cutoff, and counts the ones with no time registered. When the count reaches the threshold, the advisory is sent.
It is sent once per period. However many further days go missing afterwards, no second email follows — and the next period can send again.
A day is not counted when:
- it is a public holiday, or the employee has no norm hours on it
- time off covers it, whether approved, planned or registered
- the work time policy in force deliberately allows missing registrations
- it belongs to a period the employee has already submitted, where nothing can be changed anyway
Whether a check-in on its own accounts for a day is decided by the work time policy, not by this trigger: under the standard rule a check-in is enough, while a policy carrying the Mandatory Time Registration constraint reports the day even when the employee checked in.
Message
The trigger’s standard message reads:
{employee_name} has {missing_days} day(s) without time registration
{employee_name} has {missing_days} working day(s) without any time registration in {period}: {missing_dates}.
Available variables: {employee_name}, {workspace_name}, {date}, {missing_days} (the count), {missing_dates} (the dates themselves) and {period}.
Examples
Remind people about any forgotten day
- Add an advisory and select the Missing time registration trigger
- Leave Minimum missing days at 1
- Turn on Employee as the recipient
Only chase the people who are properly behind
- Set Minimum missing days to 3
- Turn on Employee , and Manager as well if someone should follow up
Troubleshooting
| Issue | Solution |
|---|---|
| Nothing is ever sent | Check that the employees have an open timesheet period covering the days in question — a period that is already submitted or approved is never reported on. |
| A day with a check-in but no registration is not reported | Under the standard rule a check-in accounts for the day. Add the Mandatory Time Registration constraint to the work time policy to require an actual registration. |
| Days the workspace deliberately excuses are reported | Check whether the work time policy still carries the marker that allows missing registrations. |
| No second email even though more days went missing | Expected: one email per period. The next period sends again. |
| Employees are told about days that get filled automatically | Raise Grace days to 1 or more so the nightly fill lands first. |