Attendance issues are automatically detected for you by analysing your attendance events and your shifts. Some are just warnings and can be dismissed, but others need to be resolved.

✅ Issues in the last 21 days are flagged by default, but you're free to choose a different date range when viewing your attendance issues. Rotaready can also adjust this default value for you.

❗️ It's important to keep on top of your attendance issues. Rotaready notifies you if you have any when you log-in. You must resolve them before you sign-off. If left unresolved, some kinds of issues can cause worked hours to be excluded from sign-off, reports and payroll.

Seeing all your issues

The dedicated attendance issues page consolidates all your issues in one place.

  1. Click Attendance then Issues

  2. Optionally adjust the date range or site/department and filter by issue type, job role or person.

On a daily or weekly basis, the attendance viewer also highlights any unmatched attendance. They can be resolved in-line.

Types of attendance issues

Unmatched attendance

There's no shift to match with the attendance. Learn more about matched and unmatched attendance.

No clock-in

A clock-in can't be found to match with the start of someone's shift. It might exist but could have fallen into the unmatched attendance section. Learn more about matched and unmatched attendance.

This can also occur if someone didn't turn up or was sick. Resolving the issue will guide you through the steps of adding an absence record in lieu of attendance.

No clock-out

A clock-out can't be found to match with the end of someone's shift. It might exist but could have fallen into the unmatched attendance section. Learn more about matched and unmatched attendance.

Suspect clock-out

This can occur if a clock-out is significantly later than a shift's scheduled finish time. It could be that someone forgot to clock-out on the day and did so the following day instead. You should adjust the attendance if it's incorrect, or otherwise dismiss the issue.

Suspect attendance

This can occur if the time from a clock-in to a clock-out is very short, or doesn't correlate with the length of the corresponding shift. It could be that someone forgot to clock-in at the start of their shift and only did so just before they clocked-out. You should adjust the attendance if it's incorrect, or otherwise dismiss the issue.

Unapproved early clock-in, or unapproved late clock-out

Some pay rules have overtime approval enabled, which means manual approval is required whenever some works hours over and above the scheduled duration of an associated shift.

If a shift is associated with such a pay rule, and someone clocks in early or clocks out late, an attendance issue is triggered to notify you that manual approval is required. Giving approval will cause the overtime to be paid according to the pay rule. You can also reject, which will prevent the overtime from being paid.

Break not taken*

A shift had a rest break but the employee failed to break-on at the start of their break and break-off at the end, indicating that they didn't take their break. You can add the break manually on their behalf, or dismiss the issue.

Invalid break(s)*

This can happen if an employee went on break but failed to break-off at the end. You should amend their break records manually on their behalf.

Suspect break*

If an employee takes a significantly shorter or longer break than expected, you'll see a suspect break issue. You can amend the break if it's incorrect, or otherwise dismiss the issue.

*The break-related issues only appear if employees are required to break-on and break-off. This is a setting controlled by Rotaready. It's disabled by default.

👀 Find out more about resolving attendance issues on our Spotlight Session 'Everything attendance'.

Did this answer your question?