The go-live gate

The go-live gate is deliberately short. Most of your setup can follow once you are running. A handful of things cannot, because without them the school either cannot operate or cannot bill and forecast correctly. The gate checks those, and nothing else.

Each blocker is stated in your words, what stops you flying, not a system code.

What the gate checks

• A base location. You cannot operate without at least one location on file.
• An aircraft ready to fly. At least one aircraft must be serviceable and clear of any outstanding dispatch document, so a flight can actually be dispatched.
• Opening counters. Every aircraft you will book needs its opening hours in, because no hours projection, invoice or maintenance forecast is right until they are.
• Confirmed courses and instructor privileges. So a booking can be validated against a real syllabus and a real privilege.
• Confirmed roles. So the right people can do the right things, and no one can do what they should not.

Why the gate is coarse

The gate is a coarse, once check that you are ready to open. It is not the same as the checks that run on every booking. A specific instructor's privilege at a specific time, an aircraft's maintenance forecast against a particular flight, a document that expires next week, those are the eligibility engine's job and they run at dispatch regardless, every day, forever.

So going live does not mean everything is finished. It means the few things that must be right are right and signed off, and the rest can follow in week two. After you go live, a first-week checklist picks up the useful next steps.