Book a demo

Knowledge · Rostering tool requirements

48 requirements. 12 questions. ATC rostering software requirements: a neutral checklist for ANSPs, airports and military air traffic control

A rostering tool for air traffic control is bought rarely and used every hour. This list collects what it has to do, from the eight roster elements of ATS.OR.320 to the return of your data when the contract ends. Copy it into your specification, adjust the tags to your unit and send the twelve questions to every vendor.

Rostify editorial teamLast checked 15.11.2026

00 / 08

How to use this list

Free to copy. Please name the source.

Each line is written so that it can go into a specification as it stands. The tag says how much it should weigh: Must is a knock-out criterion, Should is weighted in the evaluation, Could separates offers that are otherwise close. The tags are a proposal. A single tower, an area control centre and a military unit will move lines up or down.

ATS.OR.320 of Regulation (EU) 2017/373 names eight elements that every ATC rostering system has to specify. It sets no values. The values come from your organisation, from national law and from collective agreements, and they differ widely between providers, as the EASA fatigue study of 2024 found. That is why the first block asks for a tool that holds your values rather than one that brings its own.

References point to the legal text, or to the EUROCONTROL guidelines on rostering software (Edition 1.0, April 2023), where a line is derived from them. Lines without a reference come from operational practice. The list names no product and no vendor. Rostify appears only at the end of the page.

You may copy, change and use the list in tenders without asking. Please name the source: Rostify, rostering tool requirements, as of 15 November 2026.

Requirements
48 in 7 blocks
Vendor questions
12
Use
Free, source appreciated
As of
15.11.2026

01 / 08

Rules and fatigue

The values are yours. The tool has to hold them.

  1. 01.01

    The eight elements of ATS.OR.320

    Must

    The organisation sets its own value for each element: consecutive working days with duty, hours per duty period, time providing ATC service without a break, ratio of duty to breaks, minimum rest, consecutive duties reaching into the night, rest after such a duty, and rest periods per roster cycle. The night-time window is configurable; AMC1 to ATS.OR.320 uses 00:00 to 05:59.

    ATS.OR.320(a); AMC1 ATS.OR.320(a)(6);(7)

  2. 01.02

    Checked at every entry

    Must

    Every change is checked the moment it is made: in the draft, after publication, for swaps, replacements and overtime. Rest and duty times are calculated to the minute, across month ends and daylight-saving changes. A violation names the rule and the person concerned.

    EUROCONTROL 2023, 5.10; EASA study 2024, 2.4

  3. 01.03

    Hard and soft rules

    Must

    Automatic planning never breaks a hard rule. Soft rules carry a weight that the organisation sets. The organisation decides which rule is hard and which is soft, not the vendor.

    EUROCONTROL 2023, 5.11

  4. 01.04

    Rule sets per unit and staff group

    Must

    Several rule sets apply side by side: per unit, per staff group such as ATCO, ATSEP, AIS, MET or flow management, and per contract type such as part time.

    EUROCONTROL 2023, 5.3; 5.6

  5. 01.05

    Every duty counts

    Should

    Office, simulator, training and medical-check duties count towards working-time limits like operational duties, unless the organisation decides otherwise for a duty type.

    EASA study 2024, 6.3.2

  6. 01.06

    Rule changes with a start date

    Should

    The organisation changes a value or adds a rule set with an effective date, without a new software release. A new collective agreement can be set up and tested before it applies.

    EUROCONTROL 2023, 5.6; 5.11

  7. 01.07

    Overrides on record

    Should

    Where the organisation allows a planner to override a rule, the tool asks for a reason and records who did it and when. Overrides can be listed for any period.

    ATS.OR.320(a); ATM/ANS.OR.B.030

  8. 01.08

    Interface to a fatigue model

    Could

    Draft and published rosters, including later changes, can be passed to a biomathematical fatigue model chosen by the organisation.

    EASA study 2024, 6.3.3

02 / 08

Demand and planning

From traffic demand to a published roster.

  1. 02.01

    Demand per position and time

    Must

    Staffing demand is entered per position or sector configuration in a fixed time grid, for example 15, 30 or 60 minutes, with separate profiles for weekdays, seasons and special days. Planners can override the demand for single days, for instance during industrial action or a large event.

    EUROCONTROL 2023, 5.8

  2. 02.02

    Fixed and flexible shift patterns

    Must

    The tool supports fixed rotations and flexible allocation, forward and backward rotation, team and individual rosters, and the move from a team roster to individual rosters.

    EUROCONTROL 2023, 5.7; 5.9

  3. 02.03

    Automatic roster generation

    Must

    The tool fills a roster period from demand, patterns, availability, qualifications, rules and requests. A shift it cannot fill stays open and shows the reason. It is never filled by breaking a hard rule.

    EUROCONTROL 2023, 3.4 (1); 5.10

  4. 02.04

    Drafts and what-if

    Should

    Several drafts can be saved, compared on key figures such as overtime, open shifts or night duties per person, and discussed with staff representatives before one is published.

    EUROCONTROL 2023, 5.7; 5.12; ATS.OR.320(b)

  5. 02.05

    Periods, publication, changes

    Must

    Roster periods and lead times are configurable, from one month to a year. A new period continues from the published one without a gap in the rule checks. Publication notifies staff. Changes after publication follow defined rules and are logged.

    EUROCONTROL 2023, 6.5; 6.7

  6. 02.06

    Fair distribution in figures

    Should

    Nights, weekends, public holidays and short-notice changes are counted per person over any period and shown side by side.

    EUROCONTROL 2023, 5.6

  7. 02.07

    Demand from forecasts

    Could

    Demand can be imported from a traffic forecast or a sector opening scheme instead of being entered by hand.

    EUROCONTROL 2023, 5.2

03 / 08

Competence and training

Only qualified people on a position.

  1. 03.01

    Licences with validity dates

    Must

    For each person the tool holds ratings, unit endorsements, language proficiency, medical certificate and local qualifications, each with its validity. It warns before expiry, with a lead time set per qualification.

    Reg. (EU) 2015/340, ATCO.A.015(a); EUROCONTROL 2023, 5.5

  2. 03.02

    No duty without the qualification

    Must

    A person can only be planned on a duty or position if every required qualification is valid on that day. This applies to automatic planning, manual entries, swaps and replacements.

    EUROCONTROL 2023, 5.5

  3. 03.03

    Suspension takes effect at once

    Must

    If a qualification is suspended, for example after a declared provisional inability, the person drops out of all affected plans and the planner sees which duties are now open.

    Reg. (EU) 2015/340, ATCO.A.015(c)–(d); EUROCONTROL 2023, 5.2

  4. 03.04

    Training as a duty type

    Must

    Simulator, refresher, assessment and classroom days are plannable duty types. They block the person for operational duty and count as working time.

    EUROCONTROL 2023, 5.4; 6.3

  5. 03.05

    Minimum hours and longest gap

    Should

    The tool counts the hours worked per unit endorsement against the minimum in the unit competence scheme, and the longest period without exercising the privileges. It warns before a limit is reached.

    Reg. (EU) 2015/340, ATCO.B.020(i); ATCO.B.025(a)(2)–(3)

  6. 03.06

    Trainee and instructor as a pair

    Should

    On-the-job training is planned as a pair: a trainee only on a position for which the instructor holds a valid unit endorsement and an OJTI endorsement. The pair counts correctly against demand.

    Reg. (EU) 2015/340, ATCO.C.010(a); EUROCONTROL 2023, 5.2

  7. 03.07

    Qualifications for every staff group

    Should

    The organisation defines its own qualifications for ATSEP, AIS, MET, flow management, airport or military staff, without programming by the vendor.

    EUROCONTROL 2023, 5.5

04 / 08

Day of operations

When the day does not go to plan.

  1. 04.01

    Daily position plan

    Must

    For each day the tool shows who works on which position at what time, including breaks and briefings.

    EUROCONTROL 2023, 5.2

  2. 04.02

    Time on position and breaks checked

    Must

    The daily plan is checked against the maximum time providing ATC service without a break and against the ratio of duty to breaks.

    ATS.OR.320(a)(3)–(4)

  3. 04.03

    Sector configurations during the day

    Should

    Supervisors open and close sectors or change the configuration during the day. The position plan follows and is checked again.

    EUROCONTROL 2023, 5.2; 6.6

  4. 04.04

    Replacement at short notice

    Must

    When someone calls in sick, the tool lists the people who could take over: available, qualified and within all rules.

    EUROCONTROL 2023, 5.4; 6.6

  5. 04.05

    Call-in and overtime requests

    Should

    An open duty can be offered to all eligible staff at once by push notification or text message. Answers come back into the tool; the supervisor assigns the duty after the rule check.

    EUROCONTROL 2023, 5.2

  6. 04.06

    Live view for the supervisor

    Should

    The supervisor sees who is on duty, on a break or late, and which positions are uncovered. A read-only display for the ops room is available.

    EUROCONTROL 2023, 5.2

  7. 04.07

    Fallback when the system is down

    Must

    If the tool or the network fails, today's and tomorrow's plans remain available, for example as a regularly updated export or printout. The procedure is written down and practised.

    NIS2 Art. 21(2)(c)

05 / 08

Staff and self-service

Requests, swaps and leave without paper.

  1. 05.01

    Own roster on phone and browser

    Must

    Every person sees their own roster on iOS, Android and in a browser, and is notified when a roster is published or a duty changes.

    EUROCONTROL 2023, 5.2; 6.5

  2. 05.02

    Requests before planning

    Must

    Staff enter duty and day-off requests for the next period. Automatic planning takes them into account, and each person can see which requests were granted.

    EUROCONTROL 2023, 3.3; 6.3

  3. 05.03

    Leave with a view of coverage

    Must

    Leave is requested and approved in the tool. Before approving, the planner sees what the absence does to coverage on each affected day.

    EUROCONTROL 2023, 5.2

  4. 05.04

    Swaps with a rule check

    Must

    Staff propose swaps among themselves. The tool checks rules and qualifications for both people before the swap goes to approval. The approval steps are configurable.

    EUROCONTROL 2023, 3.3; EASA study 2024, 2.4

  5. 05.05

    Own balances and expiry dates

    Should

    Staff see their leave balance, hours worked, overtime and the expiry dates of their own qualifications.

    EUROCONTROL 2023, 3.4 (10); 5.2

  6. 05.06

    Individual arrangements

    Should

    Individual arrangements, such as part time, no night duty for medical reasons or fixed days off, are stored as personal constraints and kept by automatic planning.

    EUROCONTROL 2023, 2; 3.3

06 / 08

IT, data and interfaces

Open to your systems, closed to everyone else.

  1. 06.01

    Payroll export

    Must

    Hours, allowances and absences are exported per personnel number and cost centre, in a format agreed with payroll.

    EUROCONTROL 2023, 3.4 (10)

  2. 06.02

    Open, documented interface

    Should

    A documented programming interface (API) allows reading and writing master data, absences and duties, so that HR, training and identity systems can be connected without the vendor.

    EUROCONTROL 2023, 5.2; 5.12

  3. 06.03

    Freely configurable reports

    Should

    Users build their own reports on hours, duty types, qualifications, absences and overtime, per person, team or unit, and export them as CSV or Excel to their own analysis tools.

    EUROCONTROL 2023, 5.2

  4. 06.04

    Audit trail and evidence

    Must

    Every change is recorded with user, time, old and new value, and protected against alteration. Reports for any period show rule checks, overrides and changes after publication.

    ATM/ANS.OR.B.030; EUROCONTROL 2023, 5.2

  5. 06.05

    Sign-on and roles

    Must

    Users log in through the organisation's single sign-on with multi-factor authentication. Roles control who may see and change what, down to unit and staff group.

    NIS2 Art. 21(2)(i)–(j)

  6. 06.06

    Data location and data protection

    Must

    Data are hosted in the EU or the EEA. The vendor signs a data processing agreement, names all sub-processors and gives notice before changing them.

    GDPR Art. 28; Art. 44; EUROCONTROL 2023, 5.2

  7. 06.07

    On-premises operation

    Could

    The tool can also run in the organisation's own data centre or private cloud. Where security rules exclude public cloud services, raise this line to a must.

    EUROCONTROL 2023, 5.1; 5.2

07 / 08

Contract, operation and exit

What counts after the signature.

  1. 07.01

    Full cost over the term

    Must

    The offer shows every cost over the whole term: licences per user, configuration, data migration, interfaces, training, updates and support.

    EUROCONTROL 2023, 5.2

  2. 07.02

    Implementation and data migration

    Should

    The vendor proposes a plan: migration of staff, qualifications and opening balances, a parallel run, and a go-live date per unit.

    EUROCONTROL 2023, 6.1–6.2

  3. 07.03

    Service levels for 24/7 operations

    Must

    The contract fixes availability, support hours that match round-the-clock operations, response times by severity, and backups with tested recovery times.

    NIS2 Art. 21(2)(c)

  4. 07.04

    Security at the vendor

    Must

    The vendor describes its security measures, how it handles vulnerabilities and how quickly it reports a security incident to the customer.

    NIS2 Art. 21(2)(d)–(e)

  5. 07.05

    Releases and test environment

    Should

    New versions are announced in advance with release notes. A separate test environment allows versions and rule changes to be checked before they go live.

  6. 07.06

    Exit and return of data

    Must

    At contract end the customer receives all data in a documented, machine-readable format, with support during the switch, followed by a confirmation of deletion. Notice periods and switching terms are written into the contract.

    Data Act Art. 25; GDPR Art. 28(3)(g)

08 / 08

12 questions for every vendor

Ask them in the demo, not after the award.

  1. 08.01

    Where is your tool in daily use at an air navigation service provider?

    Ask for a unit of similar size and a contact you may call. A reference from another industry tells you little about ATC rules.

  2. 08.02

    What happens when I enter a duty that breaks a rule?

    Have it shown live, not on slides: in the roster, in a swap and in a sick-leave replacement.

  3. 08.03

    How does a new collective agreement get into the system?

    Who changes the rules, you or the vendor? How long does it take, and what does it cost? Ask for a recent example.

  4. 08.04

    Why did automatic planning leave this shift open?

    A good tool gives a reason for every open shift. Planners do not trust a tool that cannot explain itself.

  5. 08.05

    Who in your company knows how an ops room works?

    Ask who will configure your rules and who you talk to about a roster problem. Product knowledge alone is not enough.

  6. 08.06

    Who answers at three in the morning?

    Support hours, channels and response times at night, at weekends and on public holidays. Check the answer against the draft contract.

  7. 08.07

    Where are our data, and who else processes them?

    Data centre location, every sub-processor, the applicable law, and how you are told about changes.

  8. 08.08

    What do we get back when the contract ends?

    Format, scope, time frame and cost. Ask for a sample export before you sign.

  9. 08.09

    What will year five cost?

    Every cost over the term, including price adjustment, extra users, interfaces and rule changes.

  10. 08.10

    How do we work if your system fails during a shift?

    Ask for the fallback procedure and when it was last tested.

  11. 08.11

    How do updates reach us?

    Notice period, release notes, test environment, and what happens if a new version breaks something.

  12. 08.12

    May our authority and auditors see how the tool works?

    Access for audits and oversight, and how a security incident at the vendor is reported to you.

    cf. ATM/ANS.OR.B.015

Rostify

Take the list to a demo.

Bring your version of the list, with your own tags. We go through it line by line on the live system, and you see each answer instead of reading it.