The Safety Reporting Baseline Almost Nobody Records First

Safety management has been moving, slowly and steadily, from a world of paperwork kept in a drawer to one where organisations ask what their own data says about them. The shift sounds technical, but its first step is humble: write down how things work today. Before a flight department launches a new reporting tool, rewrites a hazard form or changes who reviews incidents, someone has to record what the current process looks like. That record, a safety management baseline, is the thing everybody agrees is a good idea and almost nobody actually makes.

Below we ask where the practice stands today, why it keeps being skipped and what a sensible starting record holds. It is general information for readers interested in the subject; your regulator’s requirements and your organisation’s approved manuals are what govern real operations.

A familiar story

Picture a small operator that decides its reporting system is clunky. Crews say forms take too long, so the safety officer swaps the paper form for a shorter digital one. Within a couple of months, reports go up. Everyone is delighted, and the new form gets the credit.

But did it? Nobody noted, beforehand, how many reports arrived in a typical month, how long they sat before anyone read them, or how many were closed with a documented action. So when numbers rise, there are at least three explanations: the form is easier, crews are more willing to speak up for unrelated reasons, or an unusual month produced more events. Without a starting picture, none of those can be ruled in or out. The operator’s excitement is real; its evidence is thin.

What the trend looks like now

Across aviation, the direction of travel is towards measuring the reporting process itself, not only the events reported. Organisations increasingly ask how easy it is to report, how quickly someone responds and whether the person who raised a concern hears back. Those are administrative qualities, and they are exactly what a baseline can capture before an initiative begins.

The trend is welcome, but it carries a risk. When measurement becomes fashionable, people measure after the change rather than before it. They then compare the new number with a remembered or reconstructed old one. Reconstructions are tidy and unreliable.

What a starting record contains

None of the following is exotic. A safety team can gather most of it from existing files in an afternoon.

  • Volume and rhythm of reports: how many arrive in a typical period and whether they cluster around certain days or seasons.
  • Time to acknowledgement: the gap between submission and the first human response.
  • Time to closure: how long a report stays open and how often it closes with an action rather than a note.
  • Effort to report: number of fields, number of steps, where the form is accessed and whether crews describe it as quick or irritating.
  • Feedback loop: whether reporters are told what happened and in what form.
  • Common themes in comments: the recurring words crews use when asked about the process.

Notice that none of this judges anyone’s safety performance. It describes a process. Keeping it that way matters, because the moment a baseline feels like an accusation, people stop supplying honest inputs.

Why the practice keeps getting skipped

There are human reasons, and they are not discreditable. The pressure to fix something visibly broken is strong, and recording the broken state feels like delay. There is also a quiet fear that the baseline will look bad. A third reason is plain forgetfulness: by the time a team has agreed to change something, the old process is already half dismantled.

The remedy is cultural rather than technical. Make the baseline the first agenda item of any improvement project, with a named person and a date, and treat an unflattering baseline as a gift. It will make the eventual improvement look as large as it truly is.

The same discipline in other planning work

Many readers of an aviation academy site plan journeys, courses or even treatment abroad, and the logic carries across. If you are organising eye care in another country, you might note first how long each enquiry reply takes and how many forms each step needs. BestEyeHospitals is one example of a planning site for that audience, offering country directories and a free-quote request. Its stated disclaimer describes its pages as broad background that cannot substitute for seeing a clinician, which makes it a tool for orientation rather than for decisions.

Small operators, large payoff

It is easy to assume that baselines belong to big airlines with dedicated analysts. In reality, small flight departments and training organisations benefit most, because their processes are simple enough that a single change really can be isolated. A tiny team can sit down with a month of reports, count them, note the delays and write three sentences about how crews talk about the form. That is a complete baseline. It costs one meeting and it will still be useful years later.

Reading before and after honestly

After a change has bedded in, repeat the same measures over a comparable period. Check three things before celebrating. First, were conditions similar? A quiet season and a busy one cannot be compared directly. Second, did the number you hoped to move actually move, and by enough to notice? Third, did anything get worse? Faster closure times mean little if the quality of the actions behind them fell.

It also helps to write the verdict next to the data, along with the reasoning. In a year’s time, when someone proposes yet another change, that note will show how the last one was judged.

Where it is heading

Over the coming seasons we can expect more automatic collection of process data and more pressure to show improvement. Both make the baseline more valuable, not less. Tools can record what happens after a change with great precision, yet they can only compare it with a before that somebody had the foresight to capture. The organisations that do best are likely to be the ones that treat the starting record as ordinary housekeeping rather than a special exercise.

The story of the operator and its shorter form is not a cautionary tale about bad decisions; shortening a clumsy form was probably right. It is a tale about missed evidence. A single page written before the switch would have turned a pleasant guess into a finding. That page is what we should all be writing first.

Leave a Comment

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

Scroll to Top