Change your turnaround rules. Without a vendor ticket.

When boarding opens, when the gate closes, when to hold for connections and when to tow to a remote stand, kept in tables your operations team can edit. Before a change goes live, you see every departure situation it affects.

Checked
Every departure case
Edited by
Ops managers
Tracked
Versions and audit
Runs
Cloud or on-prem
Change preview Close the gate 15 minutes before departure.
Rule 10 Minutes to departure ≤ 10Minutes to departure ≤ 15 Load the last bags

Departures

SD 2318 · 15 min to go · on time · 0 connecting

Board
Final call Gate closed
Ground handler
Final call Load the last bags

This change also touches 7 other departures out of 40 checked.

Your operating rules sit in the vendor's system. Or in a manual.

Gate times, connection holds and disruption steps are set inside the ground handling suite, or written in a station manual and applied by hand. Changing one for a new airline contract or a new station means a vendor ticket or a briefing.

Nobody can say up front which departures a new rule changes.

Turnaround
Timings configured by the software vendor
Disruption
Steps in the station manual
Airlines
Contract exceptions in emails and briefings
Where the rules usually live today.

A rules engine for ground handling operations.

An evening of departures, decided live

At an airport's disruption desk there are minutes to decide what each late flight gets: hold for connections, swap the aircraft, call a reserve crew or cancel before the 23:30 curfew. Two tables make those calls for 24 departures, every few minutes of the evening, and work out the meal vouchers, hotel rooms and EU261 compensation that follow. Press play, then add fog or a technical fault.

Local time 17:00 Curfew 23:30
Add a disruption
Time Flight Destination Gate Expected Remarks Handler action Passenger care EU261 / pax
17:25 WG 112 Vienna A3 Boarding Board passengers
17:40 WG 431 London B4 18:05 Delayed Announce the new time
17:50 WG 205 Istanbul A1 Go to gate Turnaround on schedule
18:05 WG 318 Munich A5 Go to gate Turnaround on schedule
18:20 WG 640 Madrid B7 On time Turnaround on schedule
18:35 WG 902 New York B12 On time Turnaround on schedule
18:45 WG 227 Rome A2 19:05 Delayed Announce the new time
19:00 WG 455 Paris B3 On time Turnaround on schedule
19:10 WG 133 Budapest A4 On time Turnaround on schedule
19:25 WG 718 Dubai B9 On time Turnaround on schedule
Round trip
–
Meal vouchers
0
Hotel guests
0
EU261 owed
€0

See every case that changes. Before you save.

Every case, compared

Before you save, every combination of the table's inputs is answered by the old and the new version. You see each departure situation whose answer changes, and every other answer stays as it was.

Expected answers stay put

Save the answers you rely on as tests. An edit that changes one is flagged before you save.

Live systems never break

A change that would break what a calling system sends or reads makes a new version. Systems keep the old one until you switch.

Every change on the record

The audit log keeps who changed which rule and when, next to the tests that say what it should answer.

Your systems ask over one API call, in our cloud or on your own server. API docs

Try it on your own rules.

Try it in our cloud for 14 days with no card needed, or run it on your own server. Either way, we help you move your first rules.

Also built for other teams: checkout, insurance, retail, lending and aviation.