We're pleased to announce the release of Humanforce Workforce Management (Cloud) version 6.0.75. This release delivers targeted reliability improvements across timesheets, award interpretation, rostering compliance, and employee management — reducing manual workarounds, improving confidence in bulk operations, and ensuring payroll outcomes are accurate and consistent.

Release Schedule

• Staging environments were updated on Thursday, April 23, 2026.
• All Humanforce WFM (Cloud) accounts and UAT environments will be automatically updated overnight on Wednesday, May 6, 2026.

Clocking, Timesheets & Breaks

Timesheets with no rostered break - more reliable auto-authorisation

Management > Timesheets > Timesheets

Timesheets for shifts imported from Template Manager, with no break defined, now auto-authorise accurately when an employee clocks in and out. Previously, these timesheets could receive a "Break requirement(s) are not met" status even when no break was required as per the configuration , preventing auto-authorisation and potentially leading to unnecessary manual review. 

Saving timesheets that have an open confirmation check

Management > Timesheets > Timesheets

When an admin edits a timesheet for an employee who has an active/open timesheet confirmation check, clicking "Yes" on the invalidation warning now updates the timesheet and resets the confirmation. Previously, the override response wasn't being evaluated fully, causing the warning to reappear. Now admins can apply the change and reset the confirmation check, rather than waiting for the employee’s response.

Bulk Edit Timesheets - Department & Role validation improvement 

Management > Timesheets > Timesheets

When using Timesheet Bulk Edit and changing the Department field, the auto-populated Role value is now correctly recognised when saving. Previously, the form may have returned a "Role is required" validation message even though the field was already populated — requiring the user to manually re-select the role before the save would proceed.

Bulk Generate Timesheets handles long roster comments text

Management > Timesheets > Timesheets

Bulk timesheet generation now handles situations where the Comments field contains more than 255 characters, by limiting the input to 255 characters when copying from the roster to the timesheet. Previously, this scenario could result in the bulk generation operation to stall, requiring admins to shorten comments or generate timesheets individually to work around the limit.

Improved “Select All” Timesheets behaviour during filtering

Management > Timesheets > Timesheets

Using Select All checkbox in the Timesheet Admin only applies to timesheets within the current scope. However, we’ve resolved a case where filtering by Shift Type, Reason, or Award Profile was not working in conjunction with the Select All option - meaning more timesheets than intended could be included when initiating a bulk action. 

New Timesheet from Roster for individually selected items

Management > Timesheets > Timesheets

When using New > Timesheet from Roster and selecting specific roster items, clicking Save All Timesheets now generates timesheets only for those selected items. Previously, all roster items in the list were included regardless of which ones you had selected - potentially generating timesheets before you were ready to.

Employee Management

Access level changes work across equivalent authorisation levels

Management > Employees > Employee Profile

Admins with the "Change access level of others above current access level" permission can now update the access level on any employee profile, including cases where the admin and the employee being edited are on different access levels that share the same authorisation level. Previously, this scenario could prevent the change from being made despite the admin holding the appropriate permission.

Employee API – PATCH response reflects updated data

API – PATCH /api/1.0/employees/{guidKey}

The Employee PATCH endpoint now returns the updated employee data in the response body immediately after a change is saved. Previously, the response could reflect the employee's state prior to the update — meaning integrations relying on the PATCH response to confirm changes may have been working from stale data. The underlying record was always saved correctly; the response now accurately reflects it.

Reporting & Analytics

Employee Codes now more visible in Workforce Analytics

Management > Advanced > Workforce Analytics

Employee Code values in the Employee Basic built-in dashboard are now visible to all users with appropriate view access, regardless of whether they have the "Edit Employee Code" field permission enabled. Previously, visibility of Employee Codes could be incorrectly tied to the edit permission, causing them to appear blank for users who were able to view but not edit the field.