Confirming what we prepared

FlyerOS prepares as much of your setup as it safely can, from templates and from the data you bring across. That saves you the typing. It does not make the result yours. A prefill is our reading of your school, and it becomes your responsibility only when the right person confirms it.

The areas that carry the most risk show a caution at the point you sign, so the check is in front of you when it matters.

The prefills worth reading carefully

• Opening counters. These readings set every hours projection, invoice and maintenance forecast. Confirm them against the aircraft, not against a spreadsheet.
• Maintenance programmes. Intervals and tolerances are pre-filled from sensible defaults. They are not your approved programme until you confirm every interval and tolerance against it.
• AD and SB position. Confirm the applicable directive and service-bulletin position against your own records.
• Courses and syllabi. Adopted from a template, they are our reading and your responsibility until you confirm them.
• Eligibility rule bindings. Where a binding is stricter than the regulation, it is marked "stricter than required", so it is clear you are choosing that, not that the rule requires it.

Why we make you sign

The point of confirmation is that the record then says a named person in a named role checked this and stood behind it. That is worth having when a CAA standardisation visit asks how your programme intervals or your solo policy came to be what they are. "FlyerOS filled it in" is not an answer. "Our Head of Training confirmed it on this date" is.

Nothing you confirm is locked forever, you can change it later like anything else. Confirmation is about who is accountable for it now, not about freezing it.