A well-written safety report is one of the most useful training documents an aviation team can hold. It is also one of the least studied, because most people read it once for the facts and file it away. This checklist turns a finished, anonymised safety report into a teardown exercise: a structured way to ask how it was built, so your own reports get clearer and your reviews get faster.
The list is general and educational. Follow your organisation’s safety management procedures and the rules of your national authority first; nothing here replaces them.
Before you start: pick and prepare the specimen
- Choose a completed report that went through review without major rework.
- Remove names, registrations, dates and any detail that identifies a person or an aircraft.
- Print it single-sided, with room in the margins, and have three coloured pens ready.
- Set aside forty-five minutes with one or two colleagues, and agree that the aim is learning, not fault-finding.
Part 1: structure audit
Tick each item as you find it. For anything missing, write a question mark instead and discuss it at the end.
- Is there a plain-language summary at the top? A reader in a hurry should understand the event in a few lines.
- Is the sequence of events laid out in order? Check that timing is clear without needing to read the entire document.
- Are facts separated from interpretation? What was observed should sit apart from what is concluded.
- Is the contributing context named? Look for conditions, workload or environment recorded without blame.
- Does every finding map to an action or a decision not to act? Draw an arrow from each one.
- Is ownership of each action clear? A role, not a person’s name, should be attached.
- Is there a follow-up point? A date or a review step should show when the action will be checked.
Part 2: language audit
Use a second pen colour. Underline anything that falls into the categories below, then count how many you found.
- Sentences that blame an individual rather than describe a condition.
- Vague words such as “somewhat”, “a while” or “often” where a plain description would do.
- Abbreviations that are not explained on first use.
- Paragraphs that mix more than one idea.
A strong report will have very few underlines. If your specimen has many, note that even reports that passed review can be improved, and treat the exercise as practice in noticing.
Part 3: usability audit
Give the report to a colleague with no connection to the event. Allow a few minutes and request three short answers: the event in a sentence, the decision reached, and the next owner. Keep the timing loose. If your reader hesitates, mark the spot, because that is where the structure let them down.
This test is the most revealing part of the checklist. A report can pass every structural item and still be hard to use, and only a fresh pair of eyes will find that out.
Worked illustration: one finding under the microscope
To see the checklist at work, imagine a finding in the specimen that says a checklist step was skipped during a busy turnaround. Run it through the audits. Under the structure audit, does the report say what the step was, where in the sequence it fell and what the reviewer decided? Under the language audit, does the sentence describe the condition, such as time pressure and an unusual interruption, or does it simply say someone forgot? Under the usability audit, can a stranger tell in seconds what was changed afterwards?
A strong report answers all three in a few lines. It might note that the step sat at an awkward point in the workflow, that a second interruption occurred at the same moment, and that the team moved the step to a more natural position and added a visible prompt. Nothing in that account is about a person. Everything in it is about a process, which is exactly the framing a safety culture depends on.
Practise on one finding at a time. A forty-five-minute session can comfortably cover three or four, and the repetition builds an instinct for what a well-formed entry looks like.
Adapting the checklist to different report types
Safety reports come in several shapes: short occurrence notes, longer investigations and periodic summaries. The same checklist works across them with small adjustments. For a short note, concentrate on the summary line and the action mapping. For a long investigation, give more weight to the sequence of events and the separation of fact from interpretation. For a periodic summary, check that trends are described in words a busy manager can use, and that each trend points to a decision.
Whatever the type, keep the original three questions for the usability test. If a reader cannot say what happened, what was decided and who does what next, the report has more work to do, however polished it looks.
Part 4: borrow the structure, not the content
Once the audits are done, write a one-page outline from what you learned. Use short section names, one line on the purpose of each, and a note on the typical length. This outline becomes your working guide for future reports. Do not copy sentences from the specimen: its content belongs to one event, and the value lies only in the shape.
Pin the outline where reporters can see it, and invite them to suggest changes after a month of use. A guide that is revised from real experience stays honest.
A note from the software world
Engineering teams outside aviation read finished incident write-ups for the same reason. If you are curious how a software business presents itself, the Cotocus website provides a sample. Its own description is of an India-based company working in software and digital products, and the site’s sections for services, training, solutions and its blog show one way a company can arrange its public pages. We include it as a reference for structure only.
Common problems when running the exercise
- The discussion turns into a debate about the event. Steer it back to the document’s construction.
- Participants hunt for someone to blame. Remind the group that the specimen is anonymised and the aim is clearer writing.
- The specimen is too long. Choose a shorter one; three pages is plenty.
- Nothing changes afterward. Agree on one concrete improvement to your own template before the session ends.
Keeping the habit alive
One session is useful, but the benefit grows with repetition. Rotate who chooses the specimen so that different styles of writing come under review. Keep a shared folder of outlines from earlier sessions, and glance at them before drafting a new report. Over a year, the folder becomes a small library of structures the whole team has examined together, and new joiners can learn the house style by reading it in an afternoon.
After the session: three quick follow-ups
- Update your report template with any section you found missing.
- Share the one-page outline with everyone who writes or reviews reports.
- Book the next teardown, using a different report, for a few weeks ahead.
Why this works
People learn the shape of good work much faster from a complete example than from a list of rules. Rules say what to include. A finished report shows how it feels when it is all included and nothing is wasted. The checklist above simply gives that feeling a structure you can repeat, so every new report is a little clearer than the last.
