The show schedule looks simple until you’re managing transitions underpressure. What makes a schedule operationally valid?

Specific on-stage times — not approximate ranges. Duration for each act.Special instructions covering air starts, formation builds, and holdsequences. A performer identifier for every slot. And it must be readableunder stress. If the schedule requires interpretation during a transition, it’snot ready.

The sequencing math is where a lot of schedules break down.

Because taxi time and positioning time don’t always get built in. You needto know how long it takes each aircraft to reach the runway, and how longfrom runway hold to FDA entry. Air starts require cueing the outbound actand the inbound act so they don’t conflict in the box. Ground starts needmore lead time — factor that into every transition, not just the ones youthink will be tight.

And for a BAB, the one-act-at-a-time rule shapes the whole schedulestructure.

No overlapping act windows. The schedule must reflect that explicitly —not as an assumption, but as a visible gap between acts. If the scheduleshows back-to-back acts with no transition margin, it violates the BABoperating constraint.

Who needs a copy of the schedule?

The FAA IIC, ARFF, ATC, narrators, performers, and the event director.Every one of them. If a revision is issued, label it Revision 1, Revision 2 —never reuse the same filename. When a revision goes out, confirm allparties have replaced the prior version. One person working from thewrong version during the show creates coordination failures.

Revision management sounds straightforward until you’re issuing Revision3 at 0700 on show morning.

That’s when discipline on version labeling matters most. Build the habitbefore you need it under time pressure.