Staff scheduling rules

Make the rule visible where the assignment happens.

A policy document cannot check Thursday’s replacement by itself. Configure the working rules that apply, keep the relevant worker records current and inspect warnings before approving the roster.

Check a sample roster See it in the console

Runs in your browser on demonstration data. No account, and nothing you try is saved.

Two workers in hi-vis on a building site reading the day’s jobs from one tablet between them.

The short answer

Fivexer checks the working rules you configure — rest, rolling hours, qualifications, availability — against every assignment in the roster, and shows the arithmetic behind each warning before a planner publishes.

What it checks: Rest intervals, rolling hours, required qualifications, site permission and availability.
What it does not supply: Any country's legal limits as defaults. A blank rule is not checked; a configured rule is enforced and explained.
Who decides: Your planner. Fivexer explains the conflict and records it; it never publishes on its own.

Check the boundary of the week

Monday’s first shift can depend on Sunday’s last shift. Include relevant history when checking rest and rolling hours. A clean-looking week is not enough if the previous period has been omitted.

Keep required rules distinct from preferences

Availability, required qualifications and configured limits determine whether an assignment is allowed. Preferences help choose between eligible alternatives. Review which conditions are mandatory before assuming a generated plan reflects your working agreement.

Explain a warning before changing the setting

A warning may mean that the worker record is wrong, the shift is wrong or demand cannot be met. Check the underlying facts with the responsible planner. Changing a limit just to remove the warning changes the policy the system enforces.

Read the arithmetic behind a rest conflict

Illustrative rule, not a statement of Irish legal requirements: the organisation has configured 12 hours of minimum rest.

Input	Value
Previous shift ends	Monday 22:00
Next shift starts	Tuesday 07:00
Gap	9 hours
Configured minimum	12 hours
Decision	Does not meet the configured rule

The screen this happens on

Not a mock-up. The console below runs on demonstration data; open the simulator to inspect the same week and change something yourself.

The Fivexer console's Rules tab: working-time rules written as sentences with their agreed figures set into them, under a banner naming the instrument the starting point came from. — Actual Fivexer console. Each rule is a sentence with your own figure set into it, and an edited figure keeps a Reset beside it. The banner names the instrument the starting point came from and the date it was checked.

Actual Fivexer console. Each rule is a sentence with your own figure set into it, and an edited figure keeps a Reset beside it. The banner names the instrument the starting point came from and the date it was checked.

What to account for

Fivexer ships no country’s legal limits as defaults. Rules vary by jurisdiction, sector, agreement and person. A blank rule is not checked; a configured rule is enforced and explained.

Read the rostering documentation for setup detail, or return to workforce scheduling software for the whole workflow.