The Weekly Safety Review: A Beginner’s Primer With a Mini-Glossary

If you have just joined an aviation organisation and heard people mention the SMS, the safety management system, you may have nodded politely while wondering what actually happens inside it. One of the plainest, most useful routines inside any such system is the weekly safety review. This primer explains what that review is, what goes into it, and gives you a mini-glossary so the vocabulary stops sounding like a foreign language.

First, what a safety management system is

Put simply, it is an organised way of spotting problems early and dealing with them before they grow. Staff report hazards and concerns, the organisation looks at the risks, decides what to do, does it and then checks whether the fix worked. The whole thing is a loop rather than a one-off project, and loops need regular attention to keep turning. That attention is where the weekly review comes in.

What a weekly safety review is

It is a short, fixed meeting or desk session, held on the same day each week, where the people responsible look at three things. First, what was reported or observed in the last seven days. Second, which earlier actions are still open and who owns them. Third, what needs doing in the coming week. It is not an investigation and not a blame session. It is a housekeeping rhythm that keeps small concerns from being forgotten.

Mini-glossary for beginners

  • Hazard: anything that could cause harm or damage, such as a slippery apron surface or an unclear procedure.
  • Risk: the chance that a hazard leads to harm, weighed against how bad that harm could be. Two hazards of similar size may carry very different risk.
  • Report: a note from any staff member describing something they saw or experienced that might matter for safety.
  • Corrective action: a specific step taken to remove or reduce a hazard, with an owner and a due date.
  • Open item: a report or action that has not yet been closed.
  • Follow-up: checking after a fix whether the problem really went away.
  • Safety culture: the shared attitude within a team about reporting honestly and learning from mistakes without fear.

You will meet these words constantly. Keep the list on a card at your desk until they become second nature.

How to run the review, step by step

Step one: look at the past week

Read through everything that came in: staff reports, observations from walk-arounds, equipment concerns, and anything that went differently from plan. Group similar items together. Three separate comments about the same door or the same paperwork step usually signal one real issue.

Step two: check what is still open

Go through the open items list. For each, ask whether it has an owner, whether it has a date and whether it has moved. Anything that has not moved for several weeks gets discussed directly. Either someone commits to finishing it or the team agrees to close it with a written reason.

Step three: choose the few priorities for next week

Select a small number of actions, ideally three, that will be pushed hardest in the coming days. Write each as a sentence with a name and a day. Smaller lists get finished; long ones turn into wallpaper.

Step four: record it briefly

Keep a one-page note of who attended, what was decided and which items were closed. This record is invaluable later, because it shows the system working in practice rather than only on paper.

A tiny worked example

Imagine a small training organisation. During the week, two people mention that a door to the hangar sticks in wet weather, one person notes that a briefing sheet is out of date, and a student asks about a procedure that was explained differently by two instructors. In the review, the door is a hazard with an obvious fix, so someone is asked to arrange a repair by Thursday. The briefing sheet is quick, so it is assigned for the next day. The conflicting explanation is more subtle; it becomes an agenda item for the instructors’ next meeting, with an owner to bring a proposal. Next week’s three priorities are the repair, the sheet and the proposal. Nobody has been blamed, and everything has an owner.

Where the idea shows up outside aviation

The pattern of looking back, closing loose ends and setting a few next steps is used well beyond safety work. In human resources, for instance, the period between an accepted job offer and a confirmed employee is managed in stages, and DayOneFlow is a web application designed for HR teams to guide that sequence. The common thread is simple: any process that runs over weeks benefits from a recurring check that every step has an owner.

What to bring to your first session

If you are attending as a newcomer, a little preparation makes the meeting far more useful. Bring any observations you noted during the week, even minor ones, and write them in a sentence or two rather than a paragraph. Bring a question about one glossary term that is still unclear. And bring a willingness to listen: the first few reviews are mostly about learning how your organisation phrases things and what its usual priorities look like. After a month you will likely find that you can predict the discussion and even spot the item that will take the longest to close.

Common beginner mistakes

  • Treating it as paperwork. If the review becomes a box-ticking exercise, people stop reporting. Show that reports lead to visible action.
  • Letting it run long. Aim for thirty to forty minutes. Longer sessions drift into debate that belongs elsewhere.
  • Skipping quiet weeks. A week with few reports is still worth reviewing. Ask whether people are reporting less, which may itself be worth a conversation.
  • Forgetting follow-up. Closing an action is not the same as confirming it worked. Add a quick check a few weeks later.
  • Making it about individuals. Keep the focus on processes and conditions, not on who made a mistake.

A few habits that make it easier

Share the agenda in advance, so people come prepared with their reports and open items. Use the same format each week; consistency makes the review faster and allows the group to notice patterns. Rotate who leads the session, so that more people understand how the loop works. Finally, thank people who raise concerns. That small courtesy does more for a healthy reporting culture than any poster.

Where to go from here

Start small. If you are a newcomer, ask your safety manager or supervisor how the weekly review is run in your organisation, and sit in on one. If there is no regular review at all, suggest a trial: three weeks, thirty minutes, one page of notes. Treat it as an experiment and judge it on whether things stopped slipping through the cracks.

The weekly safety review will not be the most dramatic part of any aviation career, but it is among the most dependable. It turns the abstract idea of a safety management system into something you can see, attend and improve every single week.

Leave a Comment

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

Scroll to Top