Skip to main content

Sense Automate: Return to Work with custom screens now configurable

Released: 3 June 2026 · A new configurable Return to Work workflow for organisations using custom screens.

Released: 3 June 2026

Product: Sense Automate / Sense HR

Who it affects: Administrators and HR teams

Available on: Elite and Enterprise plans


Overview

A new configurable Return to Work with custom screens workflow is now available.

This workflow replaces previous custom Return to Work workflow variations that relied on fixed, predefined steps. Administrators can now configure one workflow to better match their organisation’s return-to-work process.


What’s new

Configurable Return to Work workflow with custom screens

Administrators can now configure a custom-screen Return to Work workflow with between 1 and 6 steps.

Each step can be assigned to the relevant participant, such as an Employee, Manager or Administrator. The questions shown at each step can also be customised.

What this means for you:

You can build a Return to Work process that better reflects how your organisation manages sickness follow-up, without maintaining multiple fixed workflow versions.


Flexible trigger options

The workflow can also be configured to trigger at the point that best suits your process.

Trigger options include:

  • Immediately when a sickness absence is recorded.

  • On the next working day following the absence.

  • Automatically when the employee first clocks back in to work.

What this means for you:

Return to Work forms can be assigned at a more appropriate time, depending on how your organisation manages absence and return-to-work conversations.


Learn more

For full setup steps and configuration guidance, see:


Summary

This release gives administrators more flexibility when managing Return to Work workflows that use custom screens.

Instead of relying on fixed workflow variations, organisations can now configure the number of steps, participants, questions and trigger timing from one configurable workflow.

Did this answer your question?