Eligibility rules and the rulebook
How the checks the schedule enforces are configured as data in the rulebook, each rule with its source and effective date, so you can see and adjust what blocks a booking.
Last reviewed
The checks that decide whether a booking can go ahead are not buried in code. They are configured as data in the rulebook, so you can see what is enforced and adjust it to how your school operates.
Rules are data, with a source
Each rule, an instructor privilege, a document validity, a recency window, a duty limit, carries its regulatory or procedural basis and the date that basis took effect. So a rule is not a mystery: it says where it comes from and since when.
Tighten, do not weaken silently
Rules can be tightened to your own procedures where you are stricter than the baseline. The layering resolves so a rule cannot be quietly weakened below what the regulation requires. See Regional settings and jurisdiction for how the baseline itself is set.
What you change here shows up there
Because the schedule reads the rulebook directly, a change you make here is what the board enforces at the next booking. The plain-English reason a booking gives when it blocks is the rule from here, stated back to you. See What the schedule checks.