ISO 45001 clause 6.2: connect OH&S objectives with practical plans
ISO 45001:2018 clause 6.2 requires OH&S objectives and plans to achieve them. The objectives support maintenance and continual improvement of the system and OH&S performance. They should connect policy, applicable requirements, risk and opportunity assessment, and worker consultation with practical action and evaluation.
What clause 6.2 requires in practice
Clause 6.2 has two connected parts. Subclause 6.2.1 requires OH&S objectives at the functions and levels where they are relevant, set to maintain and improve the management system and OH&S performance. Subclause 6.2.2 requires planning of how each objective will be achieved.
Objectives need to be consistent with the policy, measurable where practicable or otherwise capable of performance evaluation, and based on applicable requirements, the assessment of risks and opportunities, and the results of worker consultation. They are monitored, communicated and updated when appropriate. The plan then settles what will be done, with what resources, who is responsible, when it will finish, how results will be evaluated including indicators, and how the work joins ordinary business processes. Documented information on objectives and plans is maintained and retained. Clause 6.2 does not oblige the organisation to set an objective for every hazard.
Choose a result that matters to the work
Clause 6.2.1 requires objectives at relevant functions and levels, consistent with policy and measurable where practicable or capable of performance evaluation. They take relevant requirements, assessment results and worker consultation into account. Objectives are monitored, communicated and updated as appropriate.
A useful objective focuses attention on an outcome that needs coordinated improvement. It should not simply restate every duty or create a target for every hazard. Ongoing controls and fulfilment of requirements remain necessary whether or not a separate objective is selected.
Plan how the result will be achieved
Clause 6.2.2 requires decisions about actions, resources, responsibility, completion timing, evaluation and integration with business processes. The organisation maintains and retains documented information on objectives and the plans to achieve them.
Separate milestones from the intended result. Completing a training session, issuing a procedure or installing equipment may be necessary steps. Evaluation should examine whether those steps changed the relevant work condition or system performance. A high completion percentage can coexist with ineffective controls.
Why objectives give prevention direction
Day-to-day controls keep known risks in check; objectives are how an organisation decides where to get better. Well-chosen objectives focus management attention and budget on a few improvements that workers recognise as real, rather than on a scorecard nobody believes. They also give leaders and auditors a fair way to judge whether the system is improving or merely being maintained. Badly chosen objectives, for example a target for fewer reported incidents, can push problems out of sight. Treating objectives and their delivery plans as one connected idea keeps ambition and resources aligned.
How to implement clause 6.2
One way to apply the whole clause is to run objective selection and delivery planning as a single short cycle. Keep it light enough to run alongside existing planning. Involve workers from the first step so that the measures reflect real conditions and the results are believed. Treat the first pass as a trial: a few objectives delivered well are worth more than a long list that nobody can resource or explain.
- Collect evidence on performance: assessment results, incidents, audit findings, worker consultation and applicable requirements.
- Pick a small number of priorities where coordinated improvement is needed, and state each result and its boundary.
- Choose measures that support accurate reporting and show both control effectiveness and outcome.
- Plan the actions, resources, owners, timing and evaluation for each objective, using clause 6.2.2 as the checklist.
- Build the actions into existing business processes and name the contributing functions.
- Communicate each objective to the people who must contribute, including affected workers.
- Review progress at set points and record why any objective is changed.
Two illustrative objective-and-plan pairs
A manufacturer wants to improve control reliability during contractor maintenance. Its objective focuses on a defined coordination weakness identified through worker feedback and audits. The plan assigns purchasing, operations and contractor interfaces and tests the revised arrangement during relevant work. It does not use an absence of reported injuries as the sole measure of success.
A software support business aims to improve predictability of workload during releases. Workers contribute to the choice of measures and the planned changes in scheduling and escalation. Evaluation considers the actual pattern of work and relevant feedback. Counting attendance at a wellbeing session would not demonstrate achievement of the work-organisation objective.
Keep measures from distorting behaviour
Choose indicators that support accurate reporting. A target framed only around reducing incident reports can discourage the information needed for prevention. Consider measures of control effectiveness and system performance alongside outcomes, with clear definitions and context.
Where numerical measurement is impracticable, use a credible performance-evaluation method. The standard permits this; it does not require an artificial number for every objective. The organisation should still be able to explain what achievement means and how it will be judged.
Evidence and common weaknesses
Documented objectives and plans are required. A combined record can be suitable if it preserves the required planning decisions, current progress and results. No particular dashboard, target-setting acronym or project template is prescribed.
Common weaknesses include selecting objectives without worker input, assigning targets without resources and changing definitions to make performance look better. Another is allowing an objective to distract from an existing duty that still needs fulfilment. Management review should examine achievement and decide on necessary responses.
Explore each numbered part
6.2.1 · select meaningful OH&S objectives
An OH&S objective should make a useful improvement priority clear without encouraging under-reporting or distracting from basic duties. Clause 6.2.1 defines how objectives relate to policy, requirements, assessment and worker consultation. This guide explains proportionate measures, communication and updating, with examples that focus on control reliability and work organisation.
6.2.2 · turn OH&S objectives into delivery plans
Objectives need a plan that connects the intended result with real authority, resources and work processes. Clause 6.2.2 specifies the planning decisions and requires documented objectives and plans. This guide explains dependencies, evaluation indicators and business integration, using examples that distinguish completion of an initiative from evidence that it improved OH&S performance.
Frequently asked questions
Must every objective be numerical?
It must be measurable where practicable or capable of performance evaluation. Use a method that can credibly establish progress and achievement.
Are objectives and plans documented?
Yes. The organisation maintains and retains documented information on both.
Is fewer incident reports always a good objective?
Not necessarily. A target must not undermine reporting or hide risk. Consider what the measure actually indicates.
Develop an objective with a useful evaluation
Discuss OH&S objectives and delivery plans with Sterling, including worker input and audit evidence. The KPIs, Objectives and Management Review course develops relevant skills. Effivity ISO & GRC automation software can be scoped to agreed performance processes. See planning and the complete guide.