The auto-scheduler
How FlyerOS builds a draft schedule from your demand and rules, and why you still approve it before it goes live.
Last reviewed
The auto-scheduler builds a draft schedule from your demand and your rules. It proposes a plan; you review it and commit it to a draft. It never publishes on its own, so a person always sees the roster before members do.
How it works
- Set the rulebook. The rules the scheduler plans within, how you weigh aircraft use, instructor load, student progress and your own constraints.
- Generate a plan. FlyerOS works through the demand and produces a proposed schedule that respects eligibility, so every booking it suggests is one that could actually happen.
- Commit to a draft. You commit the plan into a draft, where you can adjust it before publishing.
What it will and will not do
It will fill a week from your demand far faster than doing it by hand, and it will not suggest an invalid booking, because the same eligibility engine that checks a manual booking checks each one it proposes. It will not publish anything: the plan lands in a draft for you to review and change.
After generating
Treat the generated draft as a strong starting point, not a final answer. Adjust what local knowledge tells you to, then publish it like any other roster. See Drafts, and publishing a roster.