What We're Working On | WFM UK | 18 Jun 2026

• Absence in Hours
• Multiple Session Conflict Resolution

Absence in Hours (Part Day)

The Absence in Hours feature introduces the ability to record hours and designate ‘Part Day’ status for individual absence days, supporting more accurate reporting and scheduling. It also ensures that SSP and full-day CSP are calculated correctly when ‘Part Day’ is not selected, removing the need to create separate records.

An additional setting will support half-day CSP for part-day absences (until a full 'CSP in Hours' capability is introduced). Part-day absences will still feed into Scheduling and Rotas, with relaxed restrictions enabling combinations such as a half-day holiday alongside a part-day absence.

Two new data imports will also be available. 

• Absence Record Import - a general-purpose import for absence records, supporting both the existing 'Absence in Days' functionality and the new 'Absence in Hours', with hours and 'Part Day' status applied
• Absence in Hours Update Import - specific to Absence in Hours absences and provides a way to adjust existing absence in hours records where needed, updating the number of hours and 'Part Day' status at an individual date level.

Please note: Similar to the Configurable Evidence Seen Required feature, which asked customers to create new absence types to preserve historical data, Absence in Hours will require the same approach. This does mean some additional one-off setup effort, but it is necessary to ensure that historical absence data remains intact.

Preview:

Multiple Session Conflict Resolution

We recognise that users often work across multiple browser tabs and that current session handling can force them to close their entire browser, risking the loss of other work in the process. Our upcoming Multiple Session Conflict Resolution feature is designed to address this.

When a user navigates to the login page, a session check will run automatically. This typically completes quickly, though may take up to a minute (see Fig. 4). Based on the outcome of that check, one of two things will happen:

• If another tab with an active WFM session is found and that tab is genuinely still open, the user will be presented with a notification confirming a live session is already in use. They will be asked to return to that tab to continue, or close it properly before proceeding.
• If no active session is found, such as the tab was closed but not properly logged out, the lingering session will be ended automatically and the user will be returned to the login page to continue without disruption.

Existing security and timeout rules remain in effect. If a user logs out properly, re-entry will not be affected. If a session times out via the existing timeout countdown on a still open tab, the session will return to the login page, however if a user opens a new tab to log in then the system may still consider the former an active session, in which case the session check will handle this on their next login attempt.