SMS That Works: Revisiting the 6 Components for Real-World Performance
Part 2: Documentation - The Backbone of a Functioning System
Last week, we started with the Safety Management Plan - the foundation of your SMS.
This week, we move to something that is often misunderstood, underestimated, or reduced to paperwork:
Documentation.
Because documentation is not the system.
But without it, you don’t have one.
Documentation: More Than a Requirement
In Advisory Circular 107-001, documentation is presented as a core component of SMS.
But in practice, documentation is often treated as:
A compliance exercise
A manual to maintain
A box to check
That’s where systems begin to break down.
Because documentation is not about having information.
It’s about:
Making your system visible, repeatable, and verifiable.
If your processes are not documented:
They are not consistently followed
They are dependent on individuals
They cannot be audited
And they cannot improve
1. Identification and Maintenance of Applicable Regulations
Most organizations can list the regulations that apply to them.
Far fewer can demonstrate how they stay current.
This is where documentation becomes a process - not a list.
The Real Questions:
How do you know when a regulation changes?
Who is responsible for monitoring those changes?
How are those changes assessed for impact?
How are they implemented?
Who needs to know - and how are they informed?
What documentation is updated as a result?
If those questions don’t have clear answers, compliance becomes reactive.
And It Doesn’t Stop There
As an airport operator, you also have obligations related to aeronautical publications:
Canada Flight Supplement (CFS)
Canada Air Pilot (CAP)
You are expected to:
Review them for accuracy
Identify discrepancies
Inform the Minister of Transport
That requires a process.
And more importantly:
It requires records that show it’s being done.
What Good Looks Like
A defined process for monitoring regulatory changes
Assigned responsibility and accountability
Clear linkage between changes and operational impact
Document updates tracked and verified
Communication built into the process
Periodic review of regulatory and corporate documentation
What Bad Looks Like
A static list of regulations
Changes identified informally - or too late
No clear ownership
Updates made inconsistently
No record that reviews are happening
2. SMS Documentation - Making the System Work
Last week, we said a system is made up of interconnected processes.
Documentation is what makes those processes:
Understandable
Repeatable
Auditable
And every process should clearly define:
Inputs (what triggers it)
Outputs (what it produces)
Not Everything Needs to Live in One Manual
One of the best approaches we’ve seen:
An organization responsible for multiple airports had:
A short, clear Safety Management Plan (~20 pages)
Supported by a network of documented processes
It worked because:
The SMP showed how the system connected
The processes showed how the system operated
The entire structure could be followed - and audited
That’s the goal.
The Real Challenge
Do you have a documentation strategy?
Not just documents - but a structure that answers:
Where do processes live?
How are they maintained?
How are they updated?
How are they integrated into operations?
Because at the end of the day:
If documentation is not used in daily operations, it is not part of your system.
What Good Looks Like
Clear, process-based documentation
Defined inputs and outputs
Integration with operational procedures
Documentation that reflects reality - not intention
Regular use and reference by staff
What Bad Looks Like
Overly complex manuals that no one uses
Processes implied, not defined
Disconnect between documentation and operations
Documentation created for audits - not for use
3. Records Management - Where the System Proves Itself
Documentation defines the system.
Records prove it’s working.
Certificate holders must have systems that support:
Generation of data
Maintenance of records
Analysis of information
But here’s the real question:
Is your records system working for you - or are you working for it?
What Records Must Do
Your records must be:
Identifiable
Legible
Properly stored
Retained for required periods
Protected
Accessible to those who need them
Disposed of appropriately
That’s the baseline.
But effective systems go further.
“In God We Trust. All Others Must Bring Data.”
This quote - often attributed to W. Edwards Deming - captures something essential:
Decisions should be based on evidence - not assumption.
In an SMS context, this means:
You don’t assume hazards are being managed - you see it in the data
You don’t assume corrective actions are effective - you verify them
You don’t assume your system is working - you measure it
Without reliable records:
You cannot demonstrate compliance
You cannot validate performance
You cannot support decisions
And ultimately:
You cannot manage safety effectively.
What Good Looks Like
Records tied directly to processes
Data used to support decisions
Systems that allow analysis - not just storage
Clear traceability from input to outcome
What Bad Looks Like
Data scattered across systems
Records difficult to retrieve
Information collected - but never analyzed
Systems that create administrative burden without insight
Bringing It Together
Documentation is not paperwork.
It is:
How your system is defined
How your system is followed
And how your system is proven
Without it:
Processes break down
Accountability weakens
Improvement stalls
And your SMS becomes something that exists on paper - but not in practice.
A Challenge for Leaders
Take 15 minutes this week and ask:
Do we have a clear process for monitoring regulatory changes?
Is our documentation structured around processes - or documents?
Are our processes clearly defined with inputs and outputs?
Are our records helping us make decisions - or just being stored?
Could we demonstrate how our system is working - using evidence?
If the answers aren’t clear, your system may not be as strong as it appears.
What Comes Next
Next week, we move into Safety Oversight - the engine of the system.
Because documentation defines what should happen.
Oversight determines whether it actually is.
Work With Us
At Acclivix, we help aviation organizations move beyond documentation and build SMS that function in the real world.
Whether it’s:
Developing a practical documentation strategy
Mapping processes and defining inputs/outputs
Improving records management and data visibility
Or implementing tools like Wombat Safety Software to support your system
—we help you turn documentation into something that drives performance.
If your documentation feels heavy - but not helpful - it’s worth a conversation.