Act on fatigue warnings

When your organization has published fatigue rules and fatigue checks are on, the board checks every worker's shifts against them and flags the ones that break a rule. Fatigue warnings are advice: they never stop you placing a worker.

See which shifts break a fatigue rule

A shift that breaks a fatigue rule with Warning severity gets the same red marker as a double booking or a lapsed competency (see Allocate workers and assets). On the Workers axis, hovering the shift's bar reads Fatigue rule breached. Select the marker to open Signals for the worker and read the Fatigue section: which rule the shift breaks, the measured value against the limit, and whether the breach is Measured (everything behind it was actually worked) or Forecasted (some of it is still on the roster).

Each breach also reads Pushes over when this shift is the one that takes the worker over the limit, or Still over when they were already over before it.

A forecasted breach is the one to act on — the roster would take the worker over a limit before the shift is worked, so you can change it now.

Breaches and "approaching" findings

Any fatigue finding puts the usual signals marker on the shift. Open the signals to see what it is. In the Fatigue section:

• Findings from Warning rules show in red. The shift breaks a limit.
• Findings from Information rules show in amber, labelled Approaching limit. The worker is close to a limit but hasn't broken one, for example rest between 10 and 11 hours under the Approaching minimum rest recommended rule.

Breaches are listed first. To be told about short rest before it becomes a breach, add the Approaching minimum rest rule from Recommended rules in Fatigue Rules. It's added as an information rule, so it's never shown as a breach.

Suggested start time

When a shift breaks a rest rule (too little rest before or after another shift), its finding in the signals includes a suggested start time. This is the earliest the later of the two shifts could start to give the worker the rest the rule needs, shown with the calculation. The shift keeps its length, so its end moves by the same amount. For example: Rest 8 h, rule needs 10 h → start at 09:00 on Tue 6 Oct, ending 17:00 (+2 h). Times are in your fatigue policy's time zone and allow for overnight shifts and daylight-saving changes.

The suggestion is advice only. Nothing moves until you change the shift's time yourself. Each suggestion is re-checked against all your rules before it's shown. If it would still break a rule, or the check couldn't run, the suggestion says so; it's never presented as clear. No time is suggested when it can't be: the shift has already started, the later start would go past the shift's end or run into the worker's next shift, or the rule isn't a rest rule.

Fatigue checks when you place a worker

Placing, moving or replacing a worker, deploying a crew and changing shift times never wait for a fatigue check. The board checks ahead instead, so the answer is usually ready by the time you place someone:

• Picking from a list. When you pick a worker for a shift, a chip appears next to each candidate once their check is back: Fatigue: rule day (placing them would break that rule, on this shift or a later one), Fatigue: already over (they already break a rule and this shift adds nothing new) or Couldn't fully check. No chip means the placement is clear. The list is usable while chips load, and a chip never stops you picking someone. Select a chip to see which rules it affects and by how much.
• Dragging onto a shift. While you hold a worker over a shift, the board checks that placement.

If the check has already come back and the placement would create a new breach or make one worse, the board asks first: This placement would breach fatigue rules. For each rule it shows whether the breach is new, worse or already there, whether it lands on this shift or a later one, and the measured value against the limit. Add a Reason (optional) and select Place anyway, or cancel to leave the board as it was. The shift's signals then read "Placed despite fatigue warning by name on date".

If the check hasn't come back yet, the worker is placed straight away. When the check finishes, a warning appears if the placement breaks a rule, for example "Sam Carter now breaches Minimum rest (Fri 25 Sep)", with Undo to take the placement back. Changing a shift's times works the same way, but that warning has no Undo. Change the times back yourself.

Once a change is saved, the board re-checks the workers it affects. Moving a shift from one worker to another re-checks both. Warnings update as each check finishes, including breaches the change causes on the worker's other shifts.

While a check is running, the board reads Checking fatigue for N workers, and an older warning may stay visible with a note that it's being re-checked. A missing, running or failed check is never a clear result. A failed check doesn't undo the shift you saved.

Only Place anyway adds the "Placed despite fatigue warning" note. A placement whose warning arrived after it was saved doesn't get one, because nobody was asked.

When the board says fatigue isn't checked

A status line above the board explains anything that stops fatigue results from being complete. Until your organization has published rules and turned checks on, it reads "Fatigue checks are off: no fatigue policy is published and switched on."

On a single shift you may also see:

• This worker has changes since this result; it is being re-checked. — the warning shown is from before the latest change.
• Fatigue hasn't been checked for this shift. — the shift is outside the checked range or is missing data. It isn't clear; it just hasn't been checked.