A safety management system depends on one humble event: someone notices something and tells someone else. Everything downstream, the review, the risk assessment, the corrective action and the feedback, rests on that first report reaching the right person in a usable form. If it stalls, the system looks healthy on paper and is quiet in practice.
The most reliable way to find out whether your reporting workflow works is to use it, deliberately, with a harmless mock report. This article gives an audit checklist for that dry run. It is written for safety managers, accountable executives and anyone in an aviation organisation who owns part of the reporting chain.
What this audit is, and what it is not
The audit is a controlled rehearsal. You invent a plausible, low-severity event, submit it through the normal channel and track it from receipt to closure. The goal is to find out how the process behaves when nobody is under pressure.
It is not a test of the staff, and it should not be presented that way. People who feel tested stop reporting, which is the opposite of the purpose. Brief the people who will handle the mock report in advance that an exercise is coming, or at least debrief them warmly afterwards. The thing under examination is the workflow.
It is also not a replacement for your regulator’s requirements or your organisation’s own manuals. Treat it as an internal check that complements them.
Before you start: preparation checklist
- Define the scope: one reporting channel, one report type, one cycle from submission to closure.
- Write the mock report, keeping it realistic but clearly low in consequence, and label it internally as an exercise.
- Identify every person who should touch it, and confirm who is on leave.
- Decide what you will record at each step: time received, person, action taken, time passed on.
- Agree who observes and who debriefs.
- Set a date for the debrief before you begin, so the findings are not left to drift.
Stage 1: submission
Submit the report as an ordinary employee would, using the ordinary form or tool. Do not use a back channel or a personal contact.
- Could the submitter find the reporting method without asking?
- Did the form ask for what the reviewer needs, and nothing the submitter cannot know?
- Was it possible to report anonymously or confidentially if the policy says so?
- Did the submitter receive an acknowledgement, and how quickly?
If the acknowledgement is slow or absent, record it. Silence after reporting is among the most common reasons people stop reporting.
Stage 2: triage
Watch how the report is received and sorted.
- Was it logged in the right place on the same day?
- Did the person triaging know who owns this type of report?
- Was a preliminary risk view recorded, and by whom?
- Did anyone attempt to identify the submitter when the policy says they should not?
Triage is where ambiguity hides. If two people each assume the other is handling the report, the dry run will show it within a day.
Stage 3: investigation and assessment
Even a mock event needs a plausible look at causes and contributing factors.
- Was an investigator assigned, and did they have the access they needed?
- Were the relevant records, procedures and people reachable within a reasonable time?
- Did the assessment use the organisation’s own risk matrix, and did the result make sense?
- Were findings written in neutral language that focuses on conditions, not individuals?
Stage 4: corrective action
Pick a simple, invented corrective action and follow it.
- Was an owner named, with a due date?
- Did the action reach the people who would implement it?
- Was there a way to confirm that it was done, not merely agreed?
- Was the effect of the action reviewed after an interval?
Stage 5: feedback to the reporter
This stage is the one most often skipped, and the one that most affects whether people keep reporting.
- Did the submitter learn what happened to the report?
- Was the message clear, timely and free of jargon?
- Was there a route for the submitter to ask follow-up questions?
- Were lessons shared more widely, in a form that protects identities?
Common findings to expect
Teams attempting this for the first time usually run into the same handful of surprises. The reporting form lives on a page nobody links to. A shared mailbox is checked by one person who is on holiday. A risk matrix is applied differently by two reviewers. Closure is recorded as soon as an action is assigned, not when it is finished. None of these is a scandal. Each is a normal gap in a process that has never been walked from end to end, and each is a cheap fix once seen.
It is worth recording how long each stage took in plain working hours. Elapsed time is easy to understand and hard to argue with, and it gives you something concrete to compare against on the next exercise.
It also pays to repeat the exercise with a different report type. A mock event raised by a maintenance technician may travel a different path from one raised by a pilot or a ground handler, and the second path may have its own stalls.
Scoring the dry run
Avoid inventing elaborate scores. A simple record works better: for each stage, note the time taken, the observed problem and the suggested fix. Then sort the findings into three piles.
1. Stalls: places where the report stopped moving and nobody noticed. 2. Ambiguities: places where people were unsure who should act. 3. Frictions: places where the process worked but needed more effort than it should.
Stalls come first, because they directly threaten the usefulness of the system. Ambiguities come next and are usually solved by writing down a name. Frictions can wait for the next improvement cycle.
A quick note on shared knowledge
Many organisations discover that the best procedures live in people’s heads. The same is true of cooking traditions, which is why Blendz, an archive that collects heritage recipes, ingredients and food stories from different cultures and accepts submissions from visitors exists. An aviation safety team can learn from the idea: if a method matters, write it down while the person who knows it is still around.
Debrief: turning findings into changes
Hold the debrief within a week. Review each finding without blame, assign an owner and a date, and record the decisions. Share a short summary with everyone who took part, including the person who submitted the mock report.
Then schedule the next dry run. A reporting process changes as people, tools and structures change, so one exercise is a snapshot, not a certificate.
Checklist for closing the audit
- Every stage has recorded times and observations.
- Every finding has an owner and a due date.
- The debrief has taken place and the notes have been filed.
- Participants have been thanked and told what will change.
- The date of the next exercise is in the calendar.
A reporting workflow that has been rehearsed is one you can trust a little more on the day a real report arrives. That trust is built from small, unremarkable exercises, done on quiet days, by people who would rather find the stall now than later.
