ISO 45001 Clause 8.1.3: Manage Change Before Work Shifts

What clause 8.1.3 requires in practice

Clause 8.1.3 requires a process for putting planned changes into effect under control, whether the change is temporary or permanent, wherever it can affect OH&S performance. The standard lists what counts: new products, services and processes, and alterations to existing ones, including workplace locations and surroundings, how work is organised, working conditions, equipment and the workforce. It also lists changes in legal and other requirements, changes in what is known about hazards and risks, and developments in knowledge and technology.

A second duty applies to changes nobody planned. The organisation reviews what such changes caused and acts to reduce harmful effects where needed. A closing note reminds readers that change can bring opportunities as well as risks. The output is a decision route that people use before work shifts, plus a way to catch and correct drift afterwards.

Recognise more than major engineering projects

The clause includes new or changed products, services and processes, workplace locations and surroundings, work organisation, conditions, equipment and workforce. It also covers changes to legal and other requirements, knowledge about hazards and risks, and relevant technology. A modest-looking administrative decision can therefore affect OH&S performance.

Establish practical triggers for review. Ask whether the proposed arrangement changes how work is done, who performs it, where it occurs or which controls it relies on. The organisation can integrate that question into existing planning, procurement or approval processes. A separate form for every minor decision is not automatically necessary.

Assess before implementation and involve affected people

Clause 6 planning requires assessment of relevant risks and opportunities before planned change is implemented. Use worker participation and suitable technical input to understand consequences. Examine interfaces: a change that seems acceptable within one department may alter another team's exposure, emergency arrangements or responsibilities.

A practical change decision identifies the purpose, affected activities, necessary controls, responsibilities and information needed before introduction. The detail depends on the change. These are useful implementation considerations, not a prescribed checklist that guarantees suitability in every workplace.

Why clause 8.1.3 matters to the business

Most serious failures happen at the edges of normal operation: a new shift pattern, a replaced machine, a different contractor, a relocated team. Controls designed for the old arrangement quietly stop fitting. A business that reviews change before it happens avoids paying for rework, stoppages and injuries that were predictable. Customers who rely on stable delivery also benefit, because planned changes arrive with their consequences understood. Good change control builds trust between operations and the people doing the work, since workers see their concerns shaping decisions rather than following them. During an audit it is also one of the clearest places to see whether planning, operation and worker participation are really connected.

How to implement clause 8.1.3

Build change control into the decisions the business already makes, so it is not seen as extra paperwork. A proportionate approach follows.

1. List the kinds of change that can touch OH&S, using the categories in the clause, and add those specific to your operation such as new sites, outsourcing or new technology.
2. Place a short trigger question inside existing approval points: does this alter how, where, by whom or with what controls work is done?
3. For triggered changes, assess hazards and risks before introduction, with input from affected workers and suitable technical competence.
4. Give temporary changes an owner, a defined end condition and a review point, and treat a return to the old state as a change too.
5. Check readiness across instructions, competence, contractor information and emergency arrangements before the change goes live.
6. Provide a simple route for anyone to report an unplanned change, such as absence cover or unavailable equipment, and a named person who decides.
7. Review consequences after the change, and feed repeated unplanned changes back into planning or purchasing.

Illustrative software example: moving to extended support hours

Control temporary changes and their end point

Temporary arrangements can gradually become normal. Define an appropriate review point and ensure people understand the authorised conditions. If the arrangement continues or changes again, reassess the basis rather than repeatedly extending permission without review. Returning to the previous arrangement may also require a controlled decision.

Consider supporting information, competence and communication. An approved technical change can fail operationally if instructions, contractor information or supervisory responsibilities remain based on the old state. Check readiness across relevant processes, not only the team that proposed the change.

Illustrative manufacturing example: a temporary production location

A fictional manufacturer moves an activity to a different area while its usual space is unavailable. The move changes nearby activities, access and the working environment. Competent personnel and affected workers assess the arrangement, establish appropriate controls and communicate the conditions before use.

The organisation records the authorised basis and reviews actual operation. When the original area becomes available, it checks the return rather than assuming all conditions are unchanged. Evidence might include the assessment, decision, relevant instructions, readiness checks and follow-up. This example does not prescribe a layout, equipment setup or technical protective measure.

Review unintended changes when they become apparent

Not every change follows a proposal. Staff absence, unavailable equipment or an unexpected site condition can alter work. The organisation reviews consequences and takes necessary action to mitigate adverse effects. People need a usable route to raise changed conditions and obtain a decision instead of improvising beyond their authority.

When unintended change recurs, examine the wider cause. A repeated workaround may indicate inadequate capacity, purchasing or planning. Managing each occurrence individually without addressing the pattern can leave the system dependent on informal adaptations that nobody has fully evaluated.

Evidence and effectiveness

Common nonconformities with clause 8.1.3

Auditors tend to find the same weaknesses when they trace a recent change from proposal to operation.

• Risk assessment written after the change was already running, so it describes rather than informs the decision.
• Temporary arrangements extended repeatedly with no review, until they become the normal way of working.
• Technical approval that never reached supervisors, contractors or night shift, who kept following the old instructions.
• Change control applied to equipment projects only, while staffing, hours and work organisation changes pass unexamined.
• No evidence that consequences of an unplanned change were reviewed, even though workarounds are visible on the floor.