Skip to content
Open application
Site menu

Law, guidance, standards and policy

Fatigue management draws on several layers of information — from statute to internal roster rules. Treating them as the same thing causes confusion, weak governance, and unsafe assumptions.

This page explains the difference between law, guidance, standards, policy and model rules in plain English. It is not legal advice and is not a complete compliance guide.

Legislation is law made by Parliament (or devolved legislatures). It creates legal duties that organisations and individuals must meet.

Relevant examples for UK fatigue management include:

Legislation sets general duties. It does not usually prescribe detailed roster rules for every sector. How duties apply depends on the activity, the foreseeable risks, and what is reasonably practicable in context.

Regulator guidance is published by bodies such as HSE or ORR to help dutyholders understand how to meet their duties. It is not statute, though courts may consider whether guidance was followed when assessing whether duties were met.

Examples:

Guidance can be influential and practical, but it should not be quoted as if it were law. HSE research reports such as RR446 are research, not mandatory thresholds.

Industry standards are often developed by sector bodies or infrastructure owners for use within a particular industry or supply chain. They may be contractually required for organisations working under those arrangements — but they are not automatically UK law for all employers.

An example is the Network Rail standard NR/L2/OHS/003 (Fatigue Management), issued through the Network Rail standards arrangements. Organisations subject to Network Rail contracts may need to meet its requirements. That does not mean NR standards are universal UK law, and this site does not reproduce standard text or numeric thresholds.

Contracts between clients, principal contractors, and suppliers can impose fatigue-related requirements beyond general law — for example specific roster review processes, reporting, or standards compliance on a project.

Contractual requirements apply to parties to that contract. They should not be presented as applying to all UK workers.

Organisational policies are rules an employer sets for its own operation — for example maximum shift length, minimum rest between duties, overtime approval, or fatigue reporting routes.

Policies should be proportionate, documented, and reviewed. They may be stricter than minimum legal requirements but cannot lawfully reduce statutory protections.

Model outputs — such as a Fatigue Index or Risk Index from HSE RR446-based methods — are modelled estimates of relative exposure. They are decision-support, not law.

Many organisations apply colour bands or trigger levels to model outputs. These are organisational policy thresholds that may vary — configured to context and reviewed by competent persons. They are not universal legal limits. RR446 does not itself establish universal mandatory FI/RI pass/fail values. Historic rail indicative values discussed in ORR Appendix D are not satisfactory/unsatisfactory verdicts.

Software may also enforce rule sets (for example flagging gaps between duties). These reflect how the tool is configured — not statute.

LayerWhat it isCommon mistake
LawStatutory dutiesAssuming law sets detailed roster numbers for every job
GuidancePractical help from regulatorsTreating guidance as mandatory in every detail
Industry standardSector/contractual requirementsPresenting a rail or infrastructure standard as universal UK law
ContractAgreed obligations between partiesAssuming contract terms apply outside that arrangement
PolicyInternal employer rulesTreating internal FI/RI bands as legal limits
Model outputModelled estimateTreating a score as proof of safety or fitness for duty

Confusing these layers can lead to weak fatigue risk assessment, misplaced confidence in model scores, or failure to meet actual legal and contractual duties.