Book a demo

02 · ROSTERLeave planning Leave requests, decided with staffing in view.

Staff apply in My Roster, in the app or the browser, and follow the status. Planners see what each request does to staffing, day by day, before they decide.

Apply

Three fields and a button.

Reason, first day, last day, Apply. Your unit decides which reasons exist – leave, special leave, a business trip – and every application shows its status: pending, approved or not approved.

Leave dialog in My Roster: reason, first and last day, Apply; leave total per year; requests with status pending, approved and not approved
FIG. 01 — Leave in My Roster · status per requestScreenshot

Check

Against the medium-term resource plan.

Capability Prediction shows heads left, OPS demand, other demand and leave for every day. Open requests already count as absence, so you see whether one more would leave you short.

Capability Prediction September 2026: heads left, OPS demand, other demand and leave per day, with hours per ATCO predicted (illustrative figures)
FIG. 02 — Capability Prediction · September 2026Screenshot · illustrative

Decide

Approve, decline or keep pending.

One click per request. The applicant gets the decision as a notification, in the app or in the browser.

  • Approve
  • Decline
  • Keep pending
Manage Roster, Approve Leave: list of leave requests with first and last day, days, applied date and the actions decline and accept
FIG. 03 — Approve Leave · decline or accept per requestScreenshot

Then

Approved days land in the roster on their own. Try it with your own absence codes.