Demo access
ANSP all-in-one · One database

Staffed. Licensed. Briefed.

A good plan.

Rostify runs the roster of an ATC unit — and everything it depends on: position plan, shift patterns, daily OPS schedule, licences, e-briefings and on-the-job training.

Request demo access See the platform
NOW14:51 LCL·12:51 UTC
Ring: required positions per 15 min, position plan “Herbst 2026” · Bezel: radar headings · Disc: today’s OPS schedule

Almost eight years in daily operation at European ANSPs.

  • Safe operations
  • Audit-ready records
  • 0% lost OJT time
  • Satisfied staff
  • Fair rosters
  • Smooth shifts
  • Faster planning
  • Organisational gains
  • Financial savings
01 Platform

One chain. From demand to the controller on position.

Generic rostering starts with people. Rostify starts with positions — and carries that demand through every step. Change the position plan and the shifts, the roster and the OPS schedule follow. No spreadsheet in between.

  1. Chapter 03 Position plan Which positions must be open — per 15, 30 or 60 minutes, per season.
  2. Chapter 03 Optimal pattern The shifts that cover it — calculated against your rules.
  3. Chapter 02 Roster Monthly rosters, checked for rest, fatigue and requests.
  4. Chapter 04 OPS schedule Who works which position, slot by slot.
  5. Chapter 07 Crew app Every controller’s current roster, swaps and leave.
Check: Licensing. Every assignment is checked against ratings, endorsements and validity — issues warn admin and supervisor, the plan keeps running. 05 → Check: E-Briefing. Whoever hasn’t confirmed a mandatory briefing is flagged before the shift. 06 →
02 Roster

Rosters that check themselves.

Generate a month in one click along editable patterns. Every assignment is checked against rest periods, fatigue limits, general and single shift requests, licence validity and many more parameters — conflicts are visible before publication, not on the day. Across all watches — job sharers included.

Rostify Manage Roster for APP, October 2026, published, with rest, request and coverage states 1 2 3 4 5
FIG. 01 — Manage roster · APP · October 2026 · published Screenshot · initials anonymised
  1. 1Units APP, OJT APP, TFI, TWR, APP-SIM — one system.
  2. 2Roster, swap, sick, time, leave — one click from the grid.
  3. 3Cell states: rest, request mismatch, covered, above scheme, open.
  4. 4Actual against target hours, per week and month.
  5. 5Coverage per shift code and day.
ATS.OR.320 · Regulation (EU) 2017/373

Your rostering limits, as rules.

ATS providers have to specify these elements of their rostering system. Rostify checks each assignment against them — at generation, on every swap and on every replacement.

  1. a1Max. consecutive working days
  2. a2Max. hours per duty period
  3. a3Max. time on position without break
  4. a4Ratio of duty periods to breaks
  5. a5Min. rest periods
  6. a6Max. consecutive night duties
  7. a7Min. rest after night duty
  8. a8Min. rest periods per roster cycle
  9. …and many more. In automatic planning Rostify weighs 75 parameters — or you plan fully by hand.
Try it

05:42 — a controller calls in sick.

Record the absence, see the gap, pick a replacement. Rostify checks rest, leave and target hours before it lets you assign — and flags licence issues to the supervisor.

Published · covered
OCT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Δ h
BN
-
-
-
yb
-
b4
b4
f0
h7
-
yb
e0
-
-
21.7
DW
-
-
-
-
-
b4
b4
D4
-
F8
F8
f4
F8
F8
17.8
RJ
g8
g8
-
-
e0
F8
e0
-
-
e0
G8
f0
-
-
20.3
WQ
F8
F8
-
-
e0
F8
e0
-
-
e0
G8
-
f0
-
13.6
EE
D4
h7
F8
-
-
D4
F8
f0
-
-
u1
u1
-
h7
27.2
KX
-
-
g8
e0
-
-
F8
G8
f4
-
-
e0
e0
F8
0.3
GU
D3
-
-
-
F8
G8
f0
-
-
F8
-
F8
e0
e0
20.0
VJ
G8
-
YC
-
f4
YC
-
G8
-
f0
b4
F8
b4
-
14.0
VQ
b4
b4
G8
YC
-
b4
b4
b4
-
YC
-
U
U
U
23.6
VM
-
F8
f0
G8
-
-
v1
YC
-
h7
t1
-
u1
U
20.4
Coverage 12 Oct e02/2 f01/1 f41/1 F82/2
October is published and every position is covered. At 05:42 the phone rings.
03 Position plan

Plan the positions. Protect the people.

Model every position your unit has to staff — supervisor, executive and planner positions, standby, briefing and breaks — in a 15-, 30- or 60-minute grid, valid for a season or traffic period. Then shape shifts people can live with — rest, fatigue and fairness are part of the calculation, not an afterthought.

Rostify position plan: SUP, FEE, MEC, MPLC, BEC, BPLC, standby and briefing positions in a 30-minute grid 1 2 3 4 5
FIG. 02 — Position plan · APP · Herbst 2026, 01.09.–31.12.2026 Screenshot
  1. 1Validity per season or traffic period.
  2. 2Position types: position, SUP, standby, briefing, break.
  3. 3Draw blocks by hand or place them automatically.
  4. 415-, 30- or 60-minute grid — here 30 min, SUP 05:30–23:00.
  5. 5Occupancy profile of the day — peak 6 positions.

The engine calculates the shifts that cover it.

Economical or employee-friendly, normal or long shifts, briefing at the start or the end of duty. Rostify returns the required shifts per weekday, checks them against your rule set and marks the shift types you don’t have yet.

1,160.6 h
per week — optimal pattern
−95.2 h
per week vs. existing shifts (−7.6 %)
0
uncovered positions
0
rule violations

Example unit · pattern for December 2026 · economical, long shifts preferred, briefing at the end.

Rostify optimal pattern calculated from the position plan: 1,160.6 h per week against 1,255.8 h for the existing shifts 1 2 3 4
FIG. 03 — Optimal pattern from position plan Screenshot
  1. 1Calculation: employee-friendly or economical.
  2. 2Optimal against existing shifts, hours per week.
  3. 3Every result checked against the rule set.
  4. 4Shift types that don’t exist yet — create them in one step.
Course of the day: required positions against staff on duty, with briefing, breaks and sleep breaks on night duty 1 2 3 4
FIG. 04 — Course of the day · Mon–Sun Screenshot
  1. 1Required positions (line) against staff on duty (bars).
  2. 2Briefing time where you want it — here at the end of duty.
  3. 3Night duty with planned sleep break.
  4. 4Night shifts run on into the next day.
04 Daily OPS

Position by position. Slot by slot.

The OPS schedule turns the roster into the day. Supervisors assign positions to the controllers on duty — by hand or automatically — with the NOW line, last night’s handover, unstaffed requirements and double assignments in plain sight. In local time and UTC.

Rostify OPS schedule for APP on Saturday 26.09.2026 with NOW line, last night handover, unstaffed position and UTC view 1 2 3 4 5 6 7
FIG. 05 — OPS schedule · APP · Saturday 26.09.2026, 11:02 LCL Screenshot · initials anonymised
  1. 1NOW in local time and UTC.
  2. 2Positions staffed, open hours today, rule hits.
  3. 3Last night — handover from the night duty.
  4. 4Required but unstaffed — impossible to overlook.
  5. 5NOW line across every position.
  6. 6UTC view: who is on which position.
  7. 7Display mode and share link for the ops room.
OJT · On-the-job training

Every trainee has their trainer.

Trainee and OJTI are rostered as a pair and put on the same position in the OPS schedule. No training slot without a trainer, no gaps in the training plan — and the training time is documented per trainee.

MEC07:00–09:30OJTI AFTRN LX
P09:30–10:00OJTI AFTRN LX
MEC10:00–12:30OJTI AFTRN LX
Training time today · 5.0 h on position · documented
05 Licensing

Expiry is never a surprise.

Licences, ratings, endorsements and hour requirements live in one tree per controller. Each shift declares which of them it requires. If an assignment doesn’t match, Rostify warns the administrator and the supervisor — the plan itself keeps running. Alerts go out before anything expires.

Rostify licence management: ATCO licence, 200 hours, Supervisor (WM), RTF, TRM and unit endorsement with expiry dates 1 2 3 4 5 6
FIG. 06 — Licences per controller Screenshot · names cropped
  1. 1Expired — flagged in red.
  2. 2Dependent licences nest under their parent.
  3. 3Time to expiry at a glance.
  4. 4Warning threshold hit — highlighted.
  5. 5Licence report per controller and month, as PDF.
  6. 6Alerts for admins and controllers.
Rostify shift management: licences required for a shift, start in local time, duration, radar or non-radar 1 2 3 4 5
FIG. 07 — Shift definition with required licences Screenshot
  1. 1Move licences from available to required.
  2. 2Required licences for this shift.
  3. 3Start in local time, duration in hours.
  4. 4Radar or non-radar shift.
  5. 5Selectable by staff for requests; active or archived.
06 E-Briefing

Every briefing read — provably.

Mandatory or informative, addressed to departments, groups or single controllers, with up to five attachments — plus daily briefings, e.g. from the supervisor. Every read is confirmed per person; whoever is unbriefed shows up on the supervisor dashboard before taking position.

MANDATORY · READ & CONFIRM Example record
Procedure change — effective AIRAC 2611
APP · 42 controllers · 2 attachments (PDF)
Confirmed38 / 42
Unbriefed HS TE EP BL → on the supervisor dashboard
07 Crew

The roster in every controller’s pocket.

My Roster in the app and the browser: current roster, hours, swap requests with rule check, leave requests and briefings. The same database as the ops room — no printed roster on the wall, no stale PDF.

My Roster in the browser: target, scheduled and actual hours, overtime and the September roster 1 2 3
FIG. 09 — My Roster · browser · September 2026 1 Hours · 2 Overtime, time account · 3 ICS, clock, leave
Rostify My Roster app on a phone
Shift exchange for October 2026: own shifts, possible swap partners and shifts not available for the swap
FIG. 10 — Exchange · October 2026 Screenshot
Shift Trading
Only rule-compliant partners are offered. Greyed shifts show why they can’t be swapped.
Leave
Requests go straight into leave planning and the annual view.
Requests
Shift wishes feed the next generation — mismatches are marked, not hidden.
Calendar
ICS export into the controller’s own calendar.
08 Beyond ANSP

Same problem. Other control rooms.

Wherever qualified people hold positions around the clock and must prove they were briefed, the model is identical. Only the names change.

08.1Military ATCController ratings, unit endorsements, mission briefings.→ 08.2AIM · AIS24/7 AIS and NOTAM desks with documented competence.→ 08.3Airport operationsApron control, ARFF and security posts that require certification.→ 08.4Rail traffic controlSignallers and dispatchers with route knowledge and licences.→ 08.5Grid controlSystem operators with switching authorisations, 24/7.→ 08.6Emergency dispatchMinimum staffing per console, certified call-takers and dispatchers.→ 08.7Vessel traffic servicesVTS operators and supervisors on certified watch positions.→ 08.8Your control roomShow us your positions and qualifications — we map them for your demo.Request demo access →
09 Specification

Technical data.

Deployment
Cloud, in the browser — no installation
Development, hosting
Vienna, Austria and Germany (EU)
Organisation
Units and departments — e.g. ACC, APP, TWR, OJT, SIM — with their own settings
Scale
2 to 2,000 staff
Time base
Local time and UTC
Rostering
1-click generation along editable patterns, or fully manual · across watches, incl. job sharers
Position planning
15-, 30- or 60-minute grid, validity per season or traffic period
Pattern engine
Economical or employee-friendly · normal or long shifts · briefing at start or end · or fully manual design
Rule checks
Rest, fatigue and duty limits, shift and general requests · automatic planning (optional) weighs 75 parameters
Licensing
Licence tree per person, warning thresholds, PDF report · issues warn admin and supervisor, never block the plan
Training (OJT)
Trainer–trainee pairing, OJT unit roster, training documentation
E-Briefing
Mandatory or informative, daily briefings (e.g. from the supervisor), up to 5 attachments, read confirmation per user
Absence
Sick leave, replacement proposals, overtime requests by SMS, overtime volunteering via the app
Ops room
Display mode and share link for the OPS schedule
Exports
PDF, CSV, XLS, ICS · actual, target and leave prints
Audit
Access log
Languages
English, German · easy-read font option
Unit-specific permissions: admin, planner, supervisor, staff, observer, trainer, trainee
FIG. 11 — Roles per unit Screenshot

Seven roles — admin, planner, supervisor, staff, observer, trainer, trainee — combined per person and set per unit. An instructor can be trainer in APP and staff in TWR.

Next step

Bring one month of your roster.

Show us your shift logic and we’ll rebuild it in Rostify shortly — with your shift codes, your roster, your licences, your requirements. No complex installation. You get limited demo access and see for yourself.

Request demo access Log in
+43 1 4120052office[at]rostify.app