"An air traffic control services provider shall consult those air traffic controllers who will be subject to the rostering system, or, as applicable, their representatives, during its development and its application, to identify and mitigate risks concerning fatigue which could be due to the rostering system itself."
Regulation · ATS.OR.320(b)
Consult controllers on the rostering system.
ATS.OR.320(b) requires providers to consult controllers or their representatives during the development and application of the rostering system, to identify and mitigate fatigue risks arising from it.
Read the structure
Understand who must be consulted and when.
ATS.OR.320(a) lists eight rostering elements, including consecutive duty days, duty hours and minimum rest. Paragraph (b) adds a consultation requirement. Specifying the limits does not replace that consultation.
This is also a deliberately European feature. ICAO's Annex 11 sets the prescriptive-versus-FRMS choice and the categories of numeric limit, but its equivalent SARP text for the prescriptive track carries no standalone duty to consult controllers before the system is built. The closest ICAO comes is inside the FRMS track, where an FRMS policy must "reflect the shared responsibility of management, air traffic controllers, and other involved personnel" ICAO Annex 11 (15th ed.), Appendix 6, §1.1.2(b) · a commitment about shared responsibility inside an approved FRMS, not a duty to consult before a prescriptive rostering system goes live. ATS.OR.320(b) applies regardless of which track the ANSP is on.
What it means in practice
Consult during development and application.
Keep the conversation going
The article says "during its development and its application." A rostering system that was discussed with controllers once, before launch, and never again, does not satisfy the second half of that sentence. Every subsequent change to the values behind the eight elements is itself part of the system's "application," and the same duty applies.
Include staff representatives
The article reads "those air traffic controllers … or, as applicable, their representatives." An ANSP does not have to poll every controller individually; consulting the recognised union or staff representative body on the rostering system's design satisfies the same duty, provided that channel is genuine and not nominal.
EUROCONTROL's own fatigue-management guideline for rostering systems treats the consultation duty as inseparable from the scientific basis of the rules themselves, not a separate HR step:
"Training should be provided on scientific principles affecting fatigue and sleep science to support the development and implementation of a rostering system and staff consultation."
Its own conclusions repeat the same pairing as a design principle for any rostering system, not just a legal footnote: "Consultation with staff who will be subject to the rostering system, or, as applicable, their representatives, during its development and its application."EUROCONTROL, Guidelines on Fatigue Management in ATC Rostering Systems, NMD/SAF/2611, Edition 1.0, 26 April 2023, §7, p.31
What changes when it works
What the research found.
EASA’s 2024 study discusses reported changes in roster predictability, transparency and coordination:
"The ATCO fatigue regulatory requirements … have increased the predictability and transparency of the roster development process. This improved the motivation of the employees and allowed a better understanding of the process by the ATCO representatives and unions, thus resulting in more effective coordination."
The same study is equally direct about the failure mode: in its executive summary, ATCO representatives told the researchers that, while the formal requirements were being met, the underlying measures were "often either insufficient or ineffective in practice" EASA, Study on the Analysis, Prevention and Management of Air Traffic Controller Fatigue (D-4.C.1), May 2024, Executive Summary, p.4. The findings highlight the need to assess how fatigue-management measures work in practice.
What a rostering system has to be able to show
Use roster information to support consultation.
Bring the limits, planned duties and worked hours into the same discussion. Add the documented deviations to see how policy plays out in practice.
Accessible roster limits
Present the values chosen for all eight ATS.OR.320(a) elements in an accessible form, including their definitions, scope and effective dates.
Evidence the limits held, and where they didn't
Annex 11 requires the State to get "evidence that the limitations are not exceeded and that non-duty period requirements are met" ICAO Annex 11 (15th ed.), §2.28.3(a). In practice that means records of planned versus actual work periods Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), §4.1.1, p.50, the same record a union representative needs to check whether the numbers agreed in consultation are the numbers actually worked.
A record of every deviation, not just the rule
Where a State allows variations from the prescriptive limits, Annex 11 requires each one to carry "the reason for the need to deviate," "the extent of the deviation," "the date and time of enactment," and "a safety case" ICAO Annex 11 (15th ed.), Appendix 5, §3. Include the relevant deviation records in the consultation and review process.
Rostering software can support consultation with accessible policy settings and records of planned and worked duties. The provider remains responsible for conducting consultation with controllers or their representatives.
This page describes what the regulation requires and what makes the requirement meaningful in practice. What it looks like from a controller's or a union representative's own seat, day to day, is at the desk written for controllers and unions.