Drafts, and publishing a roster
How to plan a roster privately in a draft and publish it when it is ready, so students never see an unfinished schedule.
Last reviewed
Plan a roster in a draft, then publish it when it is ready. A draft is private to the people planning it, so students and instructors never see a half-finished schedule or a booking that gets moved twice before the week starts.
Working in a draft
Build the week in a draft: add bookings, move them around, try an aircraft here and an instructor there. The eligibility checks still run, so a draft cannot quietly contain an invalid booking, but nothing in it is visible to members yet.
Publishing
When the draft is right, publish it. Publishing shows you exactly what will change against what is currently live, the new bookings, the moved ones, the cancellations, so you approve the difference rather than guessing. Once published, the roster is live and the people it affects can see their flights.
Why plan this way
A schedule that changes in front of members erodes trust in it. Keeping the planning private until it is settled means the published roster is one people can rely on. When you do need to change a published booking, that change is checked and communicated like any other. See The auto-scheduler for building a draft from your demand automatically.