Roster planning
Create and edit planned shifts, recurring shift series, open work, assignments, staffing levels, and planned one-way travel.
Fatigue management software
Plan the work. Understand what it triggers.
Fatigue Management is a beta roster workspace for organisations managing shift-based and operational work. It connects planned duties, modelled fatigue exposure, scoped rule checks, and documented management decisions.
- Beta software
- Modelled fatigue exposure
- Human decisions remain essential
Core workflow
One operational thread from roster to decision.
The software keeps model output separate from organisational policy and human judgement. That distinction matters: a fatigue score is evidence for a decision, not the decision itself.
- 01
Plan
Build shifts, organise the roster, and assign work to the right people.
- 02
Assess
Evaluate roster-related fatigue exposure using modelled FI and RI outputs.
- 03
Check
See conditions triggered by the active, named policy profile and why they triggered.
- 04
Record
Retain evaluation snapshots and, where required, a management approval reason.
Current beta capabilities
What is available now.
Week and timeline views
Review the roster in a week overview or timeline, with model and policy context kept close to each assignment.
People and locations
Maintain workforce planning profiles, reusable locations, roles, contact details, competency labels, and recent planned-duty hours.
Modelled FI and RI
Run server-authoritative RR446-compatible Fatigue Index and Risk Index calculations after fatigue-relevant roster changes.
Triggered reasons
When a policy profile is active, see the conditions, measured values, thresholds, and duty context behind its outcome.
Governed outcomes
Routine outcomes remain one-step. Managed Level 1 requires an authorised reason; Prohibited outcomes cannot be overridden.
Roles and access
Separate owner, admin, manager, planner, and viewer capabilities inside one organisation workspace.
Evaluation records
Fatigue-relevant changes create immutable server-side snapshots. Mutation events are logged; a user-facing audit-history browser is not yet available.
Safe failure modes
Calculation failures, stale previews, overlaps, and prohibited outcomes block affected writes rather than creating an unassessed roster state.
Methodology
Three layers, kept explicit.
1. Model outputPopulation-based FI and RI estimates derived from planned roster inputs.
2. Policy resultConditions triggered by an active, named, and versioned rule profile.
3. Management decisionThe operational action, approval reason, or roster change made by an authorised person.
The calculation layer is based on a tested compatibility implementation of published HSE RR446 methods. The current optional governance profile is Rail Recommended 1.0.0: a product reference profile, not an HSE, ORR, RSSB, or Network Rail standard or approval.
Read the methodology, provenance, adaptation rules, and limitations.
Compliance and governance
Compliant with what?
The software can support a fatigue compliance process only when the applicable rule, policy, contract, or framework is identified and correctly configured. It can show triggered conditions, require management action, and retain records; it cannot certify universal or legal compliance.
Supports consistency
Apply the same named policy profile to fatigue-relevant roster changes and show why a condition triggered.
Supports action
Require a management reason where the active profile permits approval, or change the roster where it does not.
Supports records
Preserve the calculation and policy context used at the time of each current evaluation.
Important limitations
Decision support, not a fitness-for-duty test.
- Model outputs are estimates based on population-level research.
- They do not measure an individual’s actual alertness, sleep, health, or fitness for duty.
- A low score does not guarantee safety; a high score does not prove that an incident will occur.
- FI and RI thresholds are not universal legal limits.
- Missing planned travel uses the model’s documented 40-minute fallback.
- Two unequal known travel legs remain unresolved rather than being averaged into an invented score.
- Competent management judgement and workplace controls remain essential.
See limitations of fatigue models and FI versus RI for educational context.
Current scope
What the beta does not yet provide.
These boundaries are deliberate and should be understood before evaluation.
- No automatic roster generation or optimisation.
- No roster import workflow.
- No planned-versus-actual, clocking, attendance, or timesheet workflow.
- No live routing provider or actual-travel capture.
- No organisation policy editor or custom rule-pack builder.
- No audit-history browser, report export, or monitoring dashboard.
- No payment, checkout, subscription, or worker-count enforcement.
- No universal compliance certification or regulator endorsement.
Who it is for
Organisations managing fatigue-sensitive planned work.
Current positioning is internationally neutral while the available governance profile is explicitly rail-oriented and UK-scoped. The product does not claim compliance with US, Australian, Indian, or other national rules.
Rail and infrastructure
Planners, operations managers, and safety teams reviewing roster and travel-related fatigue exposure.
Engineering and field work
Organisations coordinating shift-based, mobile, maintenance, utilities, highways, or site operations.
Shift-work employers
Teams that need a consistent planned-work assessment and governance record around operational decisions.
Frequently asked questions
Before you evaluate the beta.
Is this an FRI calculator?
Section titled “Is this an FRI calculator?”It includes modelled FI and RI, but the product is broader than a standalone calculator. It connects scores to planned shifts, recent duty history, an optional rule profile, governed outcomes, and retained evaluation records.
Does it guarantee compliance or safe rosters?
Section titled “Does it guarantee compliance or safe rosters?”No. Compliance depends on the specific applicable rules and how they are implemented. Model outputs and policy checks cannot establish individual fitness for duty or guarantee that work is safe.
Can organisations configure their own policy?
Section titled “Can organisations configure their own policy?”Not in the current beta. Organisations can activate or deactivate the immutable Rail Recommended reference profile. A policy editor and organisation-owned profiles are not yet available.
Can I import a roster or compare planned with actual work?
Section titled “Can I import a roster or compare planned with actual work?”Not yet. Current roster information is created in the workspace and represents planned duty.
Is the product available outside the UK?
Section titled “Is the product available outside the UK?”The general roster and fatigue-assessment workflow is not presented as UK-only. However, the current named governance profile is specifically rail-oriented and no non-UK compliance claims are made.
Beta access
Review fatigue exposure before planned work begins.
Create an account in the current beta, or review indicative pricing and commercial scope.