This is advance notice of a change being deployed to Fatigue360 on 22nd April 2026 between 10:00 - 11:00 BST. Update: 22/04 This is now live!

The update overhauls how Shift overrides are handled, moving from a single blanket override to individual overrides per issue (with the option to apply the note to multiple issues at once) and removing the current field.

We know that many of you will be planning ahead and have managed your shifts adding overrides for issues and we've tried our best to accommodate that without deploying something that impacts immediate shifts. To that end, following deployment the situation will be as follows:

• Shifts prior to 5th May 2026 will have their blanket override transferred across to all existing issues, as the system would have applied it before the change.
• Shifts from 5th May 2026 onwards that have overrides will only have the override applied where the issue started before the time the override was set.

After deployment, any shifts that is updated will follow the new individual override logic, for example, a shift with overrides (e.g. insufficient rest before) from March that is modified to now exceed the on-site time, will be flagged where previously it would not have been. Another example of this will when actuals are captured, that effect the amount of rest had before the next shift

What has changed for individual Shift Overrides?

As already mentioned the existing override field has been removed and replaced with a button that opens a popup window:

Within this popup you will see the issues exist for the shift, and select those you want to override and than provide the reason as you did before:

Once applied, the sidebar and shift are updated to reflect this, in this example both issues (on-site rule and the rest after) were overridden. The shift on timeline shows that overrides have been applied (as now).

When overrides are added this continue to be shown within the Audit History:

Later on there is now a new issue with a competency that either expired or has been added and the individual does not hold it.  This may now need a new override to be applied. You can see that that the shift is red because of the issue - but shows that some overrides have already been applied.

Reopening the override popup, shows the original overrides applied, and provides the option to add a new override for the new issue. Of course if the situation is managed differently, in this case their competency record is updated, then the issue is cleared and the override isn't required.

This popup also allows you update the individual overrides or delete them as required.

Applying Overrides to Multiple Shifts

This has also been updated, to provide an option to override the same common issues on multiple shifts in one go, select multiple shifts (press CTRL and then click on the shifts), and the multiple shifts sidebar is shown: 

As before, a popup window is shown and you can select which issues to override and provide a reason (and upload media e.g. assessment form): 

Once applied, the sidebar and shift are updated to reflect this, in this example there remains a issue unique to one shift (rest before) so the shift remains in the red state on the timeline:

There remains the option to override everything for multiple shifts as well, this will require a reason (and option to upload media), and will then create add reason to each issue that the shifts have.

If you have questions about this update, please do reach out and ask!