30% of ISO 45001:2018 you already have
ISO 27018 already covers about 30% of ISO 45001:2018, leaving
31 of 44 controls as genuinely new work.
Already covered 0
Likely covered 13
New work 31
No control in ISO 27018
maps directly to one in ISO 45001:2018. Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in ISO 27018 reaches these. This is the list to scope.
5.4Establishing Audit Programme
6.1.2.2Assessment of OH&S risks and other risks to the OH&S MS
6.1.2.3Assessment of OH&S opportunities and other opportunities for the OH&S MS
8.1.2Eliminating hazards and reducing OH&S risks
8.1.4.1Procurement, general
10.2Incident, nonconformity and corrective action
10.3Continual improvement
4.2Understanding the needs and expectations of workers and other interested parties
4.4OH&S management system
5.1Leadership and commitment
5.3Organizational roles, responsibilities and authorities
5.4Consultation and participation of workers
6.2.1OH&S objectives ISO 45001:2018
6.2.2Planning to achieve OH&S
7.4.2Internal communication
7.5Documented information
7.5.2Creating and updating
7.5.3Control of documented information
8.1.2Eliminating hazards and reducing OH&S risks
9.1Monitoring, measurement, analysis and performance evaluation
9.1.2Evaluation of compliance
9.2.2Internal audit programme
Show the 13 you already have
6.1.2.1Hazard identification
8.1.1Operational planning and control, general
8.1.3Management of change
4.1Understanding the organization and its context
4.3Determining the scope of the OH&S management system
6.1Actions to address risks and opportunities
6.2OH&S objectives and planning to achieve them
7.4.3External communication
8.1Operational planning and control
8.1.3Management of change
8.2Emergency preparedness and response
How this is calculated
Already covered means a mapping runs from a control in ISO 27018 to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition