Sms Gap Analysis Checklist and Implementation Plan
Sms Gap Analysis Checklist and Implementation Plan
1.1 The initial gap analysis checklist in Table 1 can be used as a template to conduct the first step of an
SMS gap analysis. This format with its overall “Yes/No/Partial” responses will provide an initial indication of the
broad scope of gaps and hence overall workload to be expected. The questionnaire may be adjusted to suit the
needs of the organization and the nature of the product or service provided. This initial information should be
useful to senior management in anticipating the scale of the SMS implementation effort and hence the resources
to be provided. This initial checklist would need to be followed up by an appropriate implementation plan as per
Tables 2 and 3.
1.2. A “Yes” answer indicates that the organization meets or exceeds the expectation of the question
concerned. A “No” answer indicates a substantial gap in the existing system with respect to the question’s
expectation. A “Partial” answer indicates that further enhancement or development work is required to an existing
process in order to meet the question’s expectations.
3.3-3 Does the SMS audit plan include the sampling of ¨ Yes
completed/existing safety risk assessments? ¨ No
¨ Partial
3.3-4 Does the SMS audit plan include the sampling of ¨ Yes
safety performance indicators for data currency ¨ No
and their target/alert settings performance? ¨ Partial
3.3-5 Does the SMS audit plan cover the SMS ¨ Yes
interface with subcontractors or customers where ¨ No
applicable? ¨ Partial
The initial gap analysis checklist in Table 1 should then be followed up by using the detailed “SMS gap analysis
and implementation task identification plan” in Table 2. Once completed, Table 2 will provide follow-up analysis
on details of the gaps and help translate these into actual required tasks and subtasks in the specific context of
the organization’s processes and procedures. Each task will then accordingly be assigned to appropriate
individuals or groups for action. It is important that correlation of individual element/task development with their
descriptive placeholders in the SMS document be provided for in Table 2 in order to trigger progressive updating
of the draft SMS document as each element is implemented or enhanced. (Initial element write-ups in SMS
documents tend to be anticipatory rather than declaratory.)
Table 3 will show the milestones (start-end dates) scheduled for each task/action. For a phased implementation
approach, these tasks/actions will need to be sorted according to the phase allocation of their related elements.
Table 3 can be a separate consolidation of all outstanding actions/tasks or, if preferred, be a continuation of
Table 2 in the form of a spreadsheet. Where it is anticipated that the actual number of tasks/actions and their
milestones are sufficiently voluminous and complex so as to require utilizing a project management software to
manage them, this may be done by using software such as MS project/Gantt chart as appropriate. Table 4 is an
illustration of a Gantt chart.
Table 2. Example SMS gap analysis and implementation task identification plan
Status of
Answer Assigned SMS action/task
Questio (Yes/No/Partial Action/task required task document (Open/WIP/Closed
n Ref # Gap analysis question ) Description of gap to fill the gap group/person reference )
1.1-1 Is there a safety policy Partial The existing safety a) enhance the Task Chapter 1, Open
in place? policy addresses existing safety Group 1 Section 1.3.
OSHE only. policy to include
aviation SMS
objectives and
policies or develop
a separate aviation
safety policy;
- END OF DOCUMENT -