Case Study: A Flight School Counts Its Forms Before New Software

Think of the account below as a made-up scenario that carries a practical lesson about safety paperwork in aviation training. A small flight training team, which we will call the school, decided its reporting and record-keeping had become messy and that a new software package would fix it. A week later it had done something far less expensive: it had listed everything it already used. The story below follows what happened, what the list revealed and what the team changed, with no names and no invented numbers, just the sequence of decisions.

The situation: a feeling that something was missing

The school had a small team: a head of training, a few instructors, a part-time administrator and a safety contact who handled reports on top of regular duties. Over the years, the paperwork had grown in layers. There were paper forms in a cabinet, a shared spreadsheet, a few email threads where incidents had been discussed and a folder on a computer where some documents lived.

At a team meeting, someone observed that finding past reports took too long and that follow-up actions sometimes slipped. The immediate suggestion was to buy a dedicated platform. It looked sensible. The administrator, however, asked for one thing first: a list of everything the school already used for safety records and communication. The head of training agreed, with a deadline of one week.

The method: a plain inventory, built by the people who use the tools

The administrator set up a simple table with five columns: item, location, user, purpose and the date of the last change. Every instructor was asked to add rows for the things they personally touched, and the safety contact added the forms used for reports.

Three rules kept the exercise honest.

  1. List first, judge later. No item could be marked as useless during the count.
  2. Record how things are really used, not how they were meant to be used.
  3. Include documents, not just software: forms, checklists, briefing sheets and logs.

The team spent a few short sessions on it. By the end of the week the table was far longer than anyone had guessed, which surprised everyone.

What the list showed

Overlap hiding in plain sight

Two separate forms existed for reporting the same kind of event, one on paper and one in the spreadsheet. Neither was complete, and instructors tended to choose whichever was nearest. Follow-up actions were recorded in a third place, an email folder, which explained why they slipped.

Features nobody knew about

The spreadsheet already had a status column and a date column that hardly anyone used. An existing shared calendar had reminders that could have prompted action reviews. The team’s email system supported shared folders that would have made a central archive easy.

Missing links, not missing tools

The real problem turned out to be that nothing connected the pieces. Reports were taken in one place, actions tracked in another and reviews held without a standing agenda. A new platform might have helped, but it would also have added a fourth place to check until the old ones were retired.

One genuine gap

The list did show one true shortfall: there was no simple way for students to submit a report without handing over a paper form in person. That was a specific, describable need, quite different from the vague sense that something was missing.

The decision: fix the connections and fill the one gap

With the inventory in hand, the head of training set a short plan.

  • Choose one reporting form and retire the duplicate, keeping the better layout.
  • Use the spreadsheet status and date columns for every follow-up action.
  • Set a recurring calendar reminder for a monthly review meeting, with the open actions as the agenda.
  • Create a shared email folder as the central archive for reports and responses.
  • Add a simple online form for student submissions, which was the one real gap.

The cost was small, mostly the administrator’s time. Because no one had to learn a new platform, adoption was quick. Instructors were already familiar with every part of the new routine.

A passing glance at how other operations teams think

The school’s approach is not unusual among operations-minded groups in other industries. If you are curious, the blog-format site RobotsOps writes about robotics operations and offers a side read on how a very different field talks about running things. It is only background; the case study stays with the flight school.

Pushback inside the team

Some colleagues were lukewarm at the outset. One instructor worried that the list would turn into extra paperwork. The administrator answered that the table replaced searching, so the net time was lower. Another team member feared the inventory would expose untidy habits. The head of training made clear that the purpose was to understand how work happens, not to assign blame, and that every row was a fact and not a verdict.

A third concern was that a spreadsheet looked too modest for something as serious as safety records. The reply was that the seriousness lies in what the team does with the information, such as reviewing it, acting on it and closing the loop. A modest tool used consistently beats an impressive one used rarely. If the volume of reports ever outgrows the spreadsheet, the inventory will show exactly what a larger system must do, which makes any later purchase easier to scope.

What changed after a quarter

After three months the team held a short review. Reports were being found in seconds, since there was one archive. Follow-up items were visible and the monthly meeting had a clear agenda. Students used the online form, and some of them reported minor observations that would previously have gone unmentioned. The head of training noted that the school had not bought anything beyond a form, and that the question about a larger platform could be revisited later with a clear picture of what it would need to do.

Lessons from the case

The inventory is faster than the purchase

A week of listing took less time than evaluating vendors would have, and it cost nothing. It also gave the team a precise brief, so a later purchase, if needed, would be targeted.

Ask the people who use the tools

Instructors knew exactly which form they preferred and why. A list built from the top down would have missed those habits. Bring the whole team into the count.

Distinguish between a missing tool and a missing process

Most of the pain came from absent routines, such as a regular review, not from absent software. A tool cannot fix a routine nobody follows, and an inventory is a fast way to see the difference.

Keep the list alive

The administrator kept the table and added a line for each change. When the school considered something new, the first step was always to check the table.

A short template you can borrow

If your own team wants to repeat the exercise, copy these steps.

  1. Create a table with item, location, user, purpose and last update.
  2. Have each team member add what they use, including paper.
  3. Highlight duplicates and unused features.
  4. List the connections that are missing between items.
  5. Name the single biggest genuine gap and address it first.
  6. Review the table every quarter.

The school never existed, yet the pattern is common enough to test in your own team. Count first, then decide, and keep the decision as small as the evidence allows.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top