Safety Management System Development
A Safety Management System is what stops your safety programs going stale. It is the closed loop that catches drift, change and complacency before they turn into incidents. I develop, implement and maintain Safety Management Systems for Canadian organizations under the Canadian Aviation Regulations, ISO 45001 and the Occupational Health and Safety legislation that applies to your operation.
What a Safety Management System actually is
Safety is an outcome of well-defined work policies, supported processes and disciplined procedures. It is the result of doing the work correctly, every time. An SMS is not a separate department bolted onto the side of the business; it is the framework that keeps the way you work accurate and current.
A cohesive management framework rests on four pillars working in tandem:
- Policy provides the "why", establishing a leadership-driven mandate that safety is inseparable from production.
- Risk Management is the "where", using task inventories to identify exactly where operations could go wrong.
- Safety Assurance is the "is it working?" mechanism, monitoring that procedures are followed and remain effective.
- Safety Promotion carries the culture through the training and communication that ensure everyone understands their role.
These principles are not industry specific. Whether the work is aircraft operations, a construction site, a manufacturing floor or a clinical team, the move from scattered safety activity to a managed system follows the same blueprint. I have written about this at greater length in Moving to Long-Term Success: Integrating SMS into Operations.
Where we start: the needs assessment
Every engagement begins with a needs assessment. It is important to identify what the organization already does to manage safety, because rarely does an organization have nothing in place. If you have a way to report a broken tool, a method for training a new hire, or a schedule for vehicle maintenance, you already have the skeleton of a management system.
The purpose of the assessment is to find what is missing and what needs improving, while keeping changes to how the work is done to a minimum. That constraint matters. A system that fights the operation gets worked around; a system built on how the job already runs gets used.
What implementation involves
Once the gaps are clear, the work runs in a deliberate sequence:
- A granular task inventory. Not "operates forklift" but "performs pre-shift hydraulic leak check". Vague job descriptions cannot be measured; granular tasks can. See Mastering the Granular Task Inventory.
- Hazards, resources and training defined per task. What could go wrong, what tooling and PPE the task requires, and what a worker must know to do it safely.
- Competence validated by performance, not attendance. Completing a course does not demonstrate that someone can do the work.
- Procedures that get used. Documented so they are a tool on the floor rather than a binder on a shelf. See The Anatomy of an SOP.
- Accountabilities defined at every level, from executive leadership through supervisors to the front line. See Defining Accountabilities in Safety Policy Implementation.
- Reporting and assurance, including a reporting culture where deviations get raised rather than hidden.
Which standards this maps to
- Canadian Aviation Regulations, for aviation operators subject to a regulated SMS.
- ISO 45001, where you want an internationally recognised occupational health and safety management system standard.
- Applicable Occupational Health and Safety legislation, federal or provincial, depending on how your operation is regulated.
Most engagements touch more than one of these. The point of the needs assessment is to establish which obligations actually apply to you before anything gets built.
What you end up with
A management system your people can operate without me: documented procedures that reflect how the work is really performed, clear accountabilities, a functioning reporting loop, and the evidence to demonstrate all of it to a regulator, a client or an auditor.
Frequently asked questions
Do we have to start from scratch?
Almost never. Most organizations already have much of what a management system requires, even if they do not call it that. The needs assessment identifies what exists, what is missing and what needs improvement, so the work is targeted rather than wholesale.
How long does an SMS implementation take?
It depends on the size and complexity of the operation, how much is already in place, and how much of the work your own people carry. The needs assessment is what scopes this honestly, which is why it comes first rather than a quoted timeline up front.
Is this only for aviation operators?
No. The Canadian Aviation Regulations are where a formal SMS is most often mandated, and that is where much of my experience sits, but the four pillars apply to any operation. Construction, manufacturing, logistics and healthcare all follow the same blueprint.
Will this disrupt how we currently operate?
The approach is built to avoid that. Changes to established ways of working are kept to the minimum needed to close a real gap, because a system that conflicts with the operation gets worked around rather than followed.
Who in our organization needs to be involved?
Leadership, because policy and resourcing are decisions only they can make. Supervisors, because they verify competence and escalate what they cannot fix. And the people doing the work, because they are the subject matter experts on their own tasks and a procedure written without them tends not to survive contact with the floor.
Start with a conversation
Every engagement begins with a needs assessment, and that starts with a conversation about what your operation actually does and what you already have in place. Get in touch and we can work out whether this is the right fit.