Sofema Online (SOL) considers best practices for the Management of Change (MoC), Change Management, Documentation, and Control Processes.
Introduction
Objectives of MoC Documentation
The primary objective of documenting the Management of Change (MoC) process is to create a traceable safety narrative that bridges the gap between a business decision and operational safety.
• Systematic Management: The documentation ensures that all changes - whether structural, facility-related, or procedural - are managed through a standard, repeatable process rather than ad hoc decisions.
• The "Circuit Breaker" Function: A formal record acts as a safety "circuit breaker." By requiring specific fields to be completed (such as the "Why" statement and risk mitigation), the documentation forces the organization to pause and assess hazards before implementation, preventing the introduction of unmanaged risks.
• Formal Verification: The record serves as the legal and operational authority to proceed. It documents the explicit agreement by business owners to provide the necessary resources (such as budget or time) for safety mitigations, ensuring these are not just theoretical promises.
Challenges in Documentation
Creating effective MoC records is often hindered by cultural and structural barriers that turn the process into a bureaucratic exercise.
• The "Tick the Box" Trap: This is the most dangerous failure mode where the form is filled out perfectly to satisfy an auditor, but the content is generic (e.g., listing "None" for risks). This creates an "illusion of safety" in which the organization appears compliant on paper while latent hazards remain active.
• Retrospective Justification: In many ineffective systems, the documentation is created after the change has already been implemented. This renders the record useless as a risk management tool, turning it into a mere compliance exercise.
• Vague Definitions: A common challenge is poor documentation of the change itself. Using vague terms like "Efficiency Improvement" instead of specific descriptions (e.g., "Replacing Legacy Tool Control with Digital Scanning") makes it impossible to accurately assess the impact on resources.
Best Practices for Effective Record-Keeping
To ensure documentation adds operational value, organizations should adopt specific strategies that align with the SOP's risk-based approach.
• Scalable Documentation (Tiered Approach): Effective record-keeping adapts to the complexity of the change. "Level 1" records for simple changes (like form updates) should be concise, focusing only on immediate impacts. "Level 2" records for complex changes (like new software) require a full Safety Case. This prevents the "sledgehammer to crack a nut" syndrome and reduces resistance to the process.
• Documenting the "Transition Period": A critical best practice is explicitly recording the start and end dates of the "Transition Period"- the gap between the old and new states. This is often the period of highest risk due to hybrid procedures (e.g., parallel system operation). Documenting this forces the team to acknowledge and mitigate the specific risks of the handover phase.
• The "Three Pillars" Assessment: Documentation should capture the impact on three specific areas: Resources, Management Direction, and Management Control. This ensures that less obvious risks, such as the impact on supervision levels or training requirements, are not overlooked during the initial assessment.
• Traceable Verification (PIR): The record must include a Post-Implementation Review (PIR), typically scheduled three months after implementation. This section documents whether the mitigations actually worked and if any unexpected hazards arose, closing the loop between the theoretical plan and operational reality.
Required Content for Record-Keeping
A compliant and effective MoC record serves as a comprehensive history of the change. It must include specific narrative elements to ensure traceability.
Initiation and Definition: The record must begin by clearly defining the scope of the change and the "Why" statement. If the driver is financial (e.g., cost-cutting), this must be documented honestly so that resource impacts can be accurately assessed. Crucially, it must define the Transition Period to highlight when "parallel running" or hybrid operations will occur.
Impact and Risk Assessment: The documentation must demonstrate a structured impact assessment. For complex changes, this involves a "Safety Case" that drills down into specific hazards, particularly Human Factors (e.g., cognitive load or fatigue). It must explicitly list the mitigation controls that will be active before the change goes live, along with the owner of those actions.
Approval and Resource Commitment: The approval section is not just a signature; it is a record of the commitment of resources. The Business Area Owner's signature serves as formal documentation that they agree to provide the budget, time, and personnel required for the agreed mitigations.
Verification and Closure: The final part of the record is the PIR. This section must document the answers to critical questions: Did the mitigations work? Did we actually hire the planned staff? If unexpected hazards appeared, the record must reference the new Safety Reports raised. The MoC is only formally closed once the process is deemed stable.
Storage and Retention
To ensure historical traceability and audit compliance, the completed MoC form and all supporting evidence (such as risk registers and meeting minutes) must be centrally stored. The standard location is the Safety Management System (SMS) Drive or Quality Database. These records must be retained for a minimum of 5 years, or as defined by specific company policy, to allow for long-term trend analysis and regulatory oversight.
Next Steps
Sofema Aviation Services (SAS) and Sofema Online (SOL) Provide Classroom, Webinar and Online Training – Offering almost 1000 Courses, Packages and Diploma’s compliant with EASA, FAA, UAE GCAA, Saudi GACA, UK CAA, UK OTAR.
