Release notes: 1 September 2022 | Roubler v9.2

Roubler 9.2 was released on 1 September 2022 with the following new features, improvements and fixes.

What’s new?

Hours remaining on an employees contract

This feature allows rostering staff to be as efficient as possible, giving them more visibility around how well they’re utilising the hours for staff members on fixed contracts. For example, if you have a staff member contracted to work 25 hours per week, and they’re rostered for one 8-hour shift so far, you’ll be able to see how many more of their hours are available.

Cost centres on timesheets

The cost centre feature which is currently available within the shift structure has been carried over to timesheets, allowing timesheets to be optionally broken down by their cost centre. Note, if a shift is in a cost centre it will automatically map to the corresponding timesheet.

User-defined fields reporting

Authorised users have long been able to create custom fields in user profiles, which has been a popular feature. In this release, we’ve made that information more accessible by providing flexible reporting that can list user-defined fields by the employee, across employees or by the type of data.

New alerts on timesheets

Four new alerts have been added to the time and attendance page, which allow users to drill further into which timesheets they should be paying attention to. These include:

• Shift vs timesheet: This alert will trigger when the timesheet start/end differs from the shift start/end by more than the grace period. This allows managers to look at scenarios where employees started or finished a shift at unexpected times (and why).

• Clock vs timesheet: Triggers when the timesheet start/end differs from the clock-in/clock-out times by more than the grace period. Typically, these scenarios occur when the manager has manually edited a timesheet and it’s significantly different from the clocking times, improving compliance.

Notes when dismissing alerts

Authorised managers have long been able to dismiss alerts, but this change means that individual alerts can be configured to require notes. This further improves compliance and can make note-taking mandatory. E.g. if an alert is dismissed for a legitimate reason these details can be stored directly against the timesheet (“Alan forgot to clock out, but returned to the store 30-minutes later to do so. I’ve adjusted his timesheet accordingly.”).