Setup is sequencing, not software work
Onboarding is the work of putting your existing operation into the system: the instructors who teach, the members who fly, the aircraft they share, and the rules everyone has already agreed to. There is no data migration project and no consultant. Each step below is something one administrator can do, and the steps build on each other in order.
A small club can finish in an afternoon. A school with many instructors and aircraft usually spreads it over a week, mostly waiting on instructors to submit credentials and members to accept invitations.
From new account to live operation
- 1Create the school account
One person creates the account, names the school, and becomes the owner. Ownership can be shared with additional staff later; nothing else can happen until this anchor exists.
- 2Add instructors and verify CFI credentials
Invite each instructor by email. Every CFI submits credentials for review, and instructor capabilities unlock only after that review. A school never operates on unverified instructor accounts.
- 3Bring in members and students
Invite members individually or in batches. Each person gets their own account and their own training record; the school sees what its relationship to that person allows, nothing more.
- 4Choose scheduling
Enable native scheduling and configure aircraft, instructors, and locations as resources. Schools already on an external provider connect it instead, and that provider's schedule displays read-only inside the platform.
- 5Set billing and booking policies
Write the advance booking limits, cancellation notice, and daily maximums members will see in plain language, and set how charges are billed. Policy and enforcement come from the same source, so they cannot drift apart.
- 6Publish the first schedule and go live
Build the first schedule in draft, resolve conflicts, and publish. From that point members book against posted rules and the school operates from the platform day to day.
Member records and training history belong to the school, not to the platform. What your operation puts in, your operation can take out. Adopting the platform is an operating decision, not a lock-in decision.