Planning to Achieve OH&S Objectives: Clause 6.2.2 of ISO 45001 Explained

Why Clause 6.2.2 Matters More Than Most People Realise

Setting OH&S objectives is only half the job. The other half is planning how you will actually achieve them. Clause 6.2.2 of ISO 45001 deals specifically with that second half, and it is where a lot of organisations fall short. They produce a list of objectives, tick the box, and move on. When an auditor arrives and asks how those objectives are being pursued, the answers become vague.

This article is a plain English walkthrough of Clause 6.2.2. It explains what the clause requires, why each requirement exists, what good planning looks like in practice, and what auditors are looking for when they examine this area. If you are a quality or HSE manager responsible for maintaining an ISO 45001 system, or an auditor preparing to assess one, this is the guidance you need.

If you want to first understand how OH&S objectives should be set before planning their achievement, the companion article on Setting OH&S Objectives: Clause 6.2.1 of ISO 45001 Explained covers that ground in detail.

What Clause 6.2.2 Actually Requires

The clause is short in word count but demanding in practice. ISO 45001 requires that when planning how to achieve its OH&S objectives, the organisation shall determine:

• What will be done
• What resources will be required
• Who will be responsible
• When it will be completed
• How the results will be evaluated, including indicators for monitoring progress
• How the actions to achieve OH&S objectives will be integrated into the organisation's business processes

That final point about integration is one that many organisations overlook entirely. It is not enough to create a standalone OH&S action plan that sits in a folder. The standard expects the work of achieving OH&S objectives to be embedded into how the business actually operates, not treated as a separate project running alongside it.

Breaking Down Each Requirement

What Will Be Done

This is the action itself. It should be specific enough that someone unfamiliar with the objective could read it and understand exactly what needs to happen. Vague statements like improve safety culture or reduce incidents are not actions. They are aspirations. The plan needs to describe the concrete steps that will be taken.

For example, if the objective is to reduce manual handling injuries in the warehouse, the actions might include conducting a manual handling risk assessment of all picking tasks, delivering manual handling training to all warehouse staff, trialling mechanical lifting aids in the high risk zones, and reviewing incident data monthly to assess whether injury rates are trending downward.

Each of those is a specific, observable action. That is the level of detail the clause is looking for.

What Resources Will Be Required

Resources in this context means people, time, money, equipment, and any external expertise needed to carry out the planned actions. Organisations that list actions without identifying resources are setting themselves up to fail. The actions look good on paper but never get funded or staffed.

An auditor reviewing an action plan will often ask how a particular action was resourced. If the answer is that it was not formally budgeted or assigned, that raises questions about whether the organisation genuinely intends to achieve the objective or whether the plan is performative.

Resources do not need to be documented in elaborate detail, but there should be enough information to show that the organisation has thought through what is needed and that those needs are being addressed.

Who Will Be Responsible

Every action needs a named owner. Not a team, not a department, a person. Shared responsibility tends to become no responsibility. The clause expects that someone is accountable for ensuring each action is completed.

This does not mean that one person does all the work. It means one person is responsible for ensuring the work gets done, tracking progress, escalating issues, and reporting outcomes. That is a meaningful distinction in practice.

Auditors will often cross check this against the broader roles and responsibilities framework under Clause 5.3. If the person named as responsible for an OH&S objective action does not appear to have the authority or capacity to carry it out, that is worth probing.

When It Will Be Completed

Every action needs a deadline. Not a vague timeframe like end of year or ongoing, but a specific date or milestone. Ongoing actions are a particular red flag. If an action never has a completion point, it can never be evaluated as achieved or not achieved.

Where an action is genuinely ongoing, such as monthly safety inspections, the plan should define what ongoing means in measurable terms. How many inspections per month? What does completion of each cycle look like? What is the review point where the overall effectiveness of the action will be assessed?

How Results Will Be Evaluated

This is the monitoring and measurement component. The clause specifically asks for indicators. Those indicators should be defined before the actions begin, not invented after the fact to demonstrate success.

Good indicators are leading and lagging. Lagging indicators measure outcomes that have already occurred, such as the number of manual handling injuries in a quarter. Leading indicators measure activities that are expected to prevent those outcomes, such as the percentage of staff who have completed manual handling training, or the number of near misses reported per month.

Relying only on lagging indicators is a common weakness. By the time a lagging indicator tells you something has gone wrong, the harm has already occurred. Leading indicators give you the opportunity to intervene before that happens.

Integration Into Business Processes

This is the requirement that separates a genuine OH&S management system from a compliance exercise. Clause 6.2.2 explicitly requires that actions to achieve OH&S objectives be integrated into the organisation's business processes.

In practice, this means the actions should be embedded into operational planning, procurement decisions, project management, contractor management, and any other processes that affect OH&S performance. If a construction company has an objective to reduce falls from height, the actions to achieve that objective should appear in how projects are planned, how scaffolding is procured, how toolbox talks are structured, and how supervisors are trained. The objective cannot live only in an OH&S spreadsheet.

When auditing this requirement, look for evidence that OH&S objectives are referenced in operational documents, meeting agendas, performance reviews, and management discussions. If the only place the objective appears is in a standalone action plan, integration is probably not happening.

What a Good Action Plan Looks Like

There is no prescribed format for the action plan. ISO 45001 does not require a specific template. What it does require is that the information described above is documented and maintained. The format is up to the organisation.

In practice, most organisations use a table or register. A well structured action plan for a single objective might look something like this:

• Objective: Reduce manual handling injuries in the warehouse by 30% within 12 months
• Action 1: Complete manual handling risk assessment for all picking tasks by 31 March
• Responsible: Warehouse Operations Manager
• Resources: External ergonomics consultant, 2 days of operational downtime for assessment
• Indicator: Risk assessment completed and signed off
• Action 2: Deliver manual handling training to all warehouse staff by 30 April
• Responsible: HSE Manager
• Resources: Internal trainer, 4 hours per staff member, training room
• Indicator: Percentage of staff trained, training records completed
• Action 3: Trial mechanical lifting aids in zones A and B from May to July
• Responsible: Warehouse Operations Manager
• Resources: Capital budget approval for 3 units, maintenance support
• Indicator: Number of manual handling tasks assisted by equipment, staff feedback
• Review point: Monthly incident data review, quarterly progress report to management

That level of detail gives an auditor confidence that the organisation has genuinely thought through how to achieve its objective, not just written one down.

Common Weaknesses Auditors Find in This Area

Actions That Are Not Really Actions

The most frequent problem is action plans that list activities that are already happening rather than new actions designed to achieve the objective. If an organisation lists conduct monthly safety inspections as an action to achieve a new objective, but monthly safety inspections were already happening before the objective was set, that is not a meaningful action. It is a description of business as usual.

The actions in a Clause 6.2.2 plan should describe what the organisation will do differently or additionally in order to achieve the objective.

No Named Owner

Action plans that assign responsibility to a department or role without naming an individual are a common weakness. The HSE team or management are not accountable owners. Someone specific needs to own each action.

No Deadlines or Vague Timeframes

Deadlines that say ongoing or as required give an auditor nothing to evaluate. Every action needs a specific completion date or a defined review cycle with measurable milestones.

No Monitoring Indicators

Some action plans describe what will be done and who will do it but say nothing about how progress will be measured. Without indicators, there is no way to know whether the actions are working or whether the objective is being achieved.

No Evidence of Integration

As noted above, an action plan that exists only in an OH&S register and is not referenced anywhere in operational processes is a sign that integration is not happening. Auditors should look for cross references in other documents, meeting minutes, project plans, and procurement records.

How This Clause Links to the Rest of ISO 45001

Clause 6.2.2 does not operate in isolation. It connects directly to several other parts of the standard.

The objectives themselves come from Clause 6.2.1. If you want to understand the criteria that objectives must meet before you can plan their achievement, the article on Auditing OH&S Objectives Against Clause 6.2.1 of ISO 45001 is a useful reference for auditors working through this area.

The resources identified in the action plan connect to Clause 7.1, which deals with resources more broadly. If the plan identifies a need for additional personnel or equipment, there should be evidence that those resource needs have been escalated and addressed.

The monitoring and measurement requirements in the action plan connect to Clause 9.1, which covers performance evaluation. The indicators defined under Clause 6.2.2 should feed into the broader performance monitoring framework, not sit in a separate document that no one looks at.

Management review under Clause 9.3 is also relevant. The standard requires that management review includes a consideration of the extent to which OH&S objectives have been achieved. If the action plan monitoring indicators are not being fed into management review, there is a gap in the system.

Auditing Clause 6.2.2 in Practice

When auditing this clause, the approach should be to start with the objectives themselves and then trace each one through to its action plan. For each objective, ask the following questions:

• What specific actions have been planned to achieve this objective?
• Who is responsible for each action?
• What resources have been allocated?
• What is the deadline for each action?
• How is progress being monitored and what indicators are being used?
• Where does this objective appear in operational documents or processes outside the OH&S register?

Then go looking for evidence. Ask to see the action plan, the monitoring records, and the management review minutes. Interview the person named as responsible for an action and ask them to describe what they have done, what is still to be done, and how they are tracking progress. Check whether the indicators being used match what was documented in the plan.

If the person named as responsible cannot describe the action or is unaware that they are the owner, that is a finding. If the indicators in the plan have never been measured, that is a finding. If the objective appears nowhere outside the OH&S action plan, the integration requirement is likely not being met.

For a broader view of what good OH&S planning looks like across the whole of Clause 6, the article on Planning Action in ISO 45001: Making Sense of Clause 6.1.4 provides useful context on how planning actions for risks and opportunities relates to planning for objectives.

Documented Information Requirements

ISO 45001 requires that documented information be maintained on OH&S objectives and on the plans to achieve them. This means the action plan needs to exist in some recorded form, whether that is a spreadsheet, a register in a management system platform, or a formal document. It cannot exist only in someone's head or in informal email chains.

The documented information should be kept up to date. If an action has been completed, that should be recorded. If a deadline has been revised, the plan should reflect the current position. An action plan that was created at the start of the year and never updated is not a functioning planning tool. It is a historical artefact.

Auditors should check when the action plan was last reviewed and updated. If the last update was six months ago and several actions were due in that period, ask what happened to those actions and why the records do not reflect current status.

Practical Tips for Managers Building These Plans

If you are responsible for building and maintaining the OH&S objective action plan for your organisation, a few practical points are worth keeping in mind.

First, involve the people who will be doing the work in building the plan. Action plans built entirely by the HSE manager without input from operational managers tend to be disconnected from reality. The people closest to the work often know what resources are actually needed and what timelines are realistic.

Second, keep the plan visible. If it lives in a shared drive folder that nobody opens between audits, it is not functioning as a management tool. Consider including a standing agenda item in team meetings to review progress against objectives.

Third, be honest about what is achievable. An ambitious objective with an unrealistic action plan is worse than a modest objective with a credible plan. Auditors and certification bodies can tell the difference between a plan that reflects genuine commitment and one that was written to satisfy a requirement.

Fourth, review the plan regularly. Circumstances change. Resources get redirected. New hazards emerge. The plan should be a living document that reflects the current state of the organisation's efforts, not a static record of good intentions.