Regional settings and jurisdiction
How FlyerOS layers ICAO, national and school rules to fit your jurisdiction, with currency, locale and week-start set for where you operate.
Last reviewed
FlyerOS is built around UK regulation, and it is structured so the rules can fit the jurisdiction you actually operate in rather than assuming one country.
Three layers, resolved together
Rules resolve in three layers: an ICAO baseline, your national rules on top, and your own school's procedures on top of that. Each layer can tighten what the one below allows, and the layering is resolved so your school never ends up below what your national authority requires.
The jurisdiction settings page
Your active jurisdiction is set on its own page in Settings. It shows the pack that is in force, so what your school is being held to is visible rather than buried in code, and a change to it is recorded in the activity trail. The active jurisdiction acts as an enforcement floor: it is one of the layers a booking is checked against, not just a label.
When a booking is blocked, it says which layer
When the rules stop a booking, the refusal states which layer required the rule, the ICAO baseline, your national authority, or your own school's procedure. That means you can see whether a block is regulation you cannot move or a policy your school chose, and act accordingly. See why a booking was blocked.
Locale, currency and the week
Beyond the rules, regional settings cover the everyday things that differ by place: the currency you bill in, the date and number format, and which day your week starts on. Set once, they apply across the system so the product reads correctly for where you are.
Why it is separate from the rulebook
The jurisdiction layer sets the baseline; the rulebook is where your school tightens on top of it. Keeping them separate means a national rule change updates the baseline without disturbing the choices you made for your own operation.