Choose Your View: Flexible Booking Grids in Flight School Booking

Submitted by Mathew Waters on

One of the quiet frustrations of any scheduling grid is that it was designed for someone else’s operation. Most booking systems hand you a wide grid built for a busy ops desk, then expect a student to make sense of it on a phone screen.

Flight School Booking takes the opposite starting point. The default view is built for the person who books most often — the student — and the wide grid is there for the schools that genuinely need it.

The default: time down the side

By default, time runs down the left-hand column, with aircraft and instructors across the top. This makes the grid tall and narrow rather than wide and shallow — the natural shape for a phone screen, and the way most people already think about a day.

For most members, the column headers are simple: one or two aircraft they’re checked out on, one or two instructors they fly with. That’s a grid with maybe three columns. It scrolls vertically through the day, which is exactly how a phone scrolls. Finding a slot is fast.

This works well for:

  • Students booking from their phones, which is most students, most of the time.
  • Clubs where members fly one or two aircraft — the narrow grid feels spacious rather than sparse.
  • Anyone who prefers time to flow top to bottom, which maps naturally to how most people picture their day.

For the large majority of people using FSB, this is simply the better view, so it’s the one they get out of the box.

The alternative: time across the top

Flip the axes and you get the classic scheduler view. Hours run left to right along the column headers; aircraft and instructors are listed down the rows. At a glance you can see every resource across the full day.

This isn’t the default, but for some people it’s the right choice:

  • Very busy schools with many aircraft and instructors, where seeing the whole fleet in one sweep is the point. A CFI or ground staff member spotting gaps, clashes, and bottlenecks across the operation needs that breadth — and on a desktop at the ops desk, a wide grid is no problem at all.
  • People used to other booking systems. Most schedulers default to time-across-the-top, and there’s real value in familiarity. If that’s the layout someone has used for years, FSB shouldn’t force them to relearn it.
  • Instructors who work across multiple schools. Someone teaching at two clubs may use a time-across-the-top system at one of them. Matching that layout in FSB keeps their day consistent rather than asking them to switch mental models between bookings.

Each user chooses for themselves

The preference lives in your FSB account settings. Switch between orientations any time — it’s remembered for next time. Schools don’t pick one layout for everyone: a student on their phone gets the tall grid by default, while an instructor who prefers the wide view sets it once and keeps it, all within the same system.

There’s no single correct orientation. There’s a sensible default for most people, and a proper alternative for the people the default doesn’t suit.

Why it took a real layout decision to get right

A grid that just flips its axes sounds straightforward. In practice it means rethinking how headers render, how resource labels truncate at different screen widths, and how touch targets behave when time slots become rows rather than columns. We spent the time making both orientations feel native, rather than treating one as an afterthought.

The result is a booking form that works as well for a student in a muddy airfield car park as it does for an staff behind a desk in the ops room.