Let us be honest about how safety systems grow. Something happens, or something nearly happens, and the response is a new form, a new log, a new poster, a new rule. Each addition feels responsible, and often it is. But months later the organisation owns a thick stack of safety paperwork, and nobody is quite sure which parts are still alive. This article offers a conversational checklist for the opposite instinct: looking after your safety management system as it stands, before bolting anything onto it.
A clear caveat before we start. This is a friendly, practical walk-through of administrative housekeeping. The requirements that apply to your operation come from your aviation authority and your approved procedures, and nothing here replaces or interprets them. Where you are unsure whether something is mandatory, ask the person responsible for compliance, not a blog.
Set the scene: what you are actually doing
You are not auditing people, and you are not rewriting policy. You are checking the condition of things that already exist. Think of it as walking around an aircraft before a flight, except the aircraft is your safety paperwork and your published information. Ask the same three simple questions of everything you meet: is it holding up, is it wanted, and does it direct people sensibly.
Grab a notebook, or a shared sheet, and a mug of something warm. Set aside a couple of quiet hours. Work through the sections below in order.
Section one: the reporting route
Reporting is the heart of most safety systems, and it is the part most likely to quietly fall over.
- Find the front door. Where does a person go to raise a concern? Try it yourself, from scratch, as a newcomer would.
- Does it work? Submit a harmless test entry, if your process allows it, and confirm someone receives it.
- Is it findable? If the route is buried three pages deep, treat that as a defect.
- Does the person named still hold the role? Old names on forms are surprisingly common.
Section two: registers and logs
Hazard registers and action logs tend to grow by accumulation. Look at them with fresh eyes.
- Are old entries marked as closed, open or still being watched? An entry with no status is a mystery.
- Does every open item have an owner and a next date?
- Are there entries that describe a situation which no longer exists, such as equipment that has been replaced or a procedure that has been changed? Those can be closed with a note, not left to confuse the next reader.
- Is the register still in the format people use, or has everybody quietly moved to a different tool?
Section three: documents and templates
Old templates are like old maps. They look authoritative, and they are only useful if the roads have not moved.
- List every form and template in circulation.
- Check each for a version date and an owner.
- Look for duplicates, where two slightly different versions of the same form exist.
- Retire the ones nobody uses, and tell the people who might have used them where the current version lives.
Section four: the people list
An organisation is only as reachable as its contact list. Go through every named contact in your safety documents. Confirm that the person is still there, the role is still accurate, and the contact route still works. Pay particular attention to emergency and out-of-hours arrangements, and refer any doubts about their adequacy to the responsible manager rather than fixing them on your own.
Section five: web pages and links
Most organisations publish at least some safety information online: a page explaining how to raise a concern, links to authority guidance, reference documents for staff and students. These pages quietly accumulate broken links.
Testing each by hand is the sort of job that gets postponed forever. Some teams park their public links on URLSnow, where background checks note any link that has stopped responding, so the repair list arrives without a click-through marathon. Whichever route you take, make sure each link still opens, still lands on the page you intend, and still carries the information the surrounding text promises.
Section six: training and induction material
New joiners learn the system from whatever material is handed to them, so that material deserves a look of its own. Open the induction pack, the slides and any quick-reference cards. Do the screenshots match the tools people now use? Do the names, locations and routes mentioned still exist? A newcomer who follows an outdated instruction will assume it is current, and will not know to question it. If a slide deck has drifted far from reality, treat it as a candidate for repair or retirement, and note who owns the update.
Section seven: decide, record, schedule
When the walk-through is done, give every item one of three outcomes.
- Keep. It works, it is needed, it points correctly.
- Repair. It is needed but out of date. Fix the detail and note the date.
- Retire. It no longer serves a purpose. Remove it, and leave a pointer if people might still look for it.
Write down what you decided, and pick a date for the next walk-through. If you only do one thing from this list, do that. A review without a next date is a one-off, and a one-off does not stop slow decay.
Making it feel lighter
Auditing sounds heavy, so shrink it. Split the sections across a few short sessions rather than one long slog, and invite a colleague from a different department to shadow you. A fresh pair of eyes spots the confusing bits you have stopped seeing, and a bit of company makes the job feel less like penance. Finish each session by writing three lines: what you looked at, what you changed, what remains.
A few gentle warnings
- Do not tidy away something you do not understand. If you are unsure whether a document is required, ask first.
- Keep the audit separate from official inspection and compliance activity. This is housekeeping that supports them, not a replacement.
- Do not blame. Old forms and dead links are signs of a busy organisation, not careless people.
- Do not skip the quiet pages. The rarely visited ones decay fastest.
Why bother before adding anything new?
Because every addition inherits the condition of what it joins. A new reporting form that sits beside an abandoned one invites confusion about which to use. A new web page that links to a dead one inherits its problem. Starting with what already exists gives the new material a solid base, and it often reveals that the best improvement is not an addition at all, but a clearer version of what is already there.
Safety culture is partly made of small signals. A system that is visibly looked after, with current names, working links and tidy registers, tells people that the organisation means what it says. One that is visibly neglected tells them something else. Spending a couple of quiet hours on the first signal is a cheap way to send it.
