Help by role
Help for a Head of Training
The training programme, records that stand up, and who is assigned to whom.
- Getting your school set upHow onboarding works in FlyerOS: a set of areas, each prepared by us and signed off by the right person, with readiness measured by what you can do rather than a progress bar.
- Confirming what we preparedFlyerOS pre-fills your setup from templates and your data, but a prefill is our reading until you sign it. What to check before you confirm each area.
- Setting up a courseHow to create a course, add its exercises, and publish a version students can enrol on.
- Authoring a syllabusHow to build your course as exercises, lessons and competencies in the syllabus editor, with grading scales, so a lesson is graded against the real syllabus you teach.
- How courses, versions and enrolments fit togetherThe three ideas at the heart of training records, a course, a published version of it, and a student enrolled on that version.
- Comparing syllabus versionsHow to see exactly what changed between two versions of a syllabus, which exercises were added, removed or moved, before you decide who moves across.
- Adding your first studentHow to add a student to your organisation so you can enrol and schedule them.
- Enrolling a student on a courseHow to place a student on a published version of a course so their training record starts tracking.
- Grouping students into a cohortHow to create a cohort, add students to it, and what a cohort makes easier.
- Assigning instructors to studentsHow to assign an instructor to a student, what the assignment changes, and how to manage load and cover.
- Instructor load and continuityHow FlyerOS shows how many students each instructor carries, the hours they fly, and how much of a student's training stays with one instructor.
- The difference between an exercise and a lessonAn exercise is a fixed item in the syllabus; a lesson is a flight you actually flew. Here is how they relate.
- Tracking qualifications and expiryHow the compliance view shows every licence, rating and medical across your people, and warns before they lapse.
- Working under two authoritiesFor schools holding both a UK CAA and an EASA approval: FlyerOS tracks which authority each licence, rating and medical belongs to, and never crosses the two.
- Understanding roles and permissionsWhat a role is, why access is granted by capability rather than by job title, and how to decide what each person sees.
- Generating a document from a templateHow templates and merge fields work, how a document is generated, and how sensitive documents are handled.
- Document templates and merge fieldsHow FlyerOS generates a document from a template and a merge-field registry, with a sensitivity level and a versioned record of every document produced.
- Signing a documentHow to request signatures on a document, record or decline each one with tamper-evident evidence, and how minors get a guardian co-signer automatically.
- Course agreements and training liabilityHow money paid up front for a course is held against training not yet delivered, recognised as it is flown, settled fairly on withdrawal, and reported as a liability.
- Reports and analyticsHow the analytics in FlyerOS are built from the day you actually flew, with drill-through to the underlying records and exports for a board or an auditor.
- The analytics dashboardsThe Fleet, Instructors, Finance, Training and Eligibility dashboards, how each number resolves through one metric definition, and how to drill through to the records behind it.