Overriding a warning, and who may
The difference between a hard block and a warning, who is allowed to override one, and why every override is recorded.
Last reviewed
Some results are hard blocks and some are warnings. A warning can be overridden by an authorised person; a hard block cannot. Either way, what happens is recorded.
Block versus warning
- A hard block is a rule that must not be broken, an expired medical, an unserviceable aircraft, a missing prerequisite. FlyerOS will not let the booking stand, and there is no override.
- A warning flags something that needs a human judgement rather than an outright refusal. It can be allowed to proceed, but only by someone whose role permits it, and only with a reason.
Who may override
Overriding is a capability attached to a role, not something everyone can do. If you do not see the option, your role does not carry it, ask whoever administers your organisation, rather than working around it.
Every override is reasoned and recorded
When a warning is overridden, FlyerOS records who did it, when, and the reason they gave. Nothing is bypassed silently. That record sits in the booking's history, so later, at a review, or an inspection, it is clear that the decision was made deliberately by a named person, not missed.
This is the point of warnings: they keep a human in the loop for the cases that need one, without pretending the exception never happened.