ISO 45001 clause 7.4.1: design communication around people and decisions
ISO 45001:2018 clause 7.4.1 requires processes that determine what OH&S information is communicated, when, with whom and how. Audiences include internal levels and functions, contractors and visitors, and other interested parties. The organisation considers diversity, relevant external views, legal and other requirements, and the consistency and reliability of the information.
What clause 7.4.1 requires in practice
Clause 7.4.1 asks the organisation to establish, implement and maintain the processes for internal and external communication. Within them it determines what it will communicate, when, with whom and how. The audience includes people at different levels and functions inside the organisation, contractors and visitors, and other interested parties.
The organisation takes diversity into account, with gender, language, culture, literacy and disability named as examples, and considers the views of external interested parties when it sets up the process. It also takes legal and other requirements into account and makes sure the OH&S information communicated is reliable and consistent with what the system generates. It responds to relevant communications and retains documented information as evidence, as appropriate. No particular channel, template or log is prescribed.
Design for the recipient’s decision
Start with what the recipient needs to understand or do. A visitor needs relevant site information; a contractor may need coordination requirements; management may need a decision about an unresolved control issue. Those purposes call for different content, timing and methods.
Identify responsibility for preparing, checking and communicating important information. Where technical or legal interpretation is needed, use suitable competence. Avoid allowing an urgent request to produce an unsupported assurance simply because someone expects an immediate answer.
Account for diversity and external views
The process takes relevant diversity factors into account, including gender, language, culture, literacy and disability. This is a practical question about whether communication can be understood and used. Translation may help, but accessible design and confirmation of understanding may also be necessary.
Consider relevant external interested parties’ views when establishing communication arrangements. A contractor or emergency-response interface may reveal a need that an internal team has overlooked. The organisation still determines an appropriate process; it does not need to adopt every suggested channel or format.
Why designing communication around the recipient pays off
A notice that was issued but not understood protects nobody. Designing communication around what the recipient must decide or do reduces misunderstandings between shifts, between employers on a shared site and between the organisation and visitors. Considering diversity early avoids expensive rework after an incident reveals that part of the workforce could not use the information. Reliable, consistent messages also protect the organisation's credibility with authorities and clients, because statements can be traced to the system's own information. Auditors frequently test this by following one message from decision to recipient.
How to implement clause 7.4.1
The sequence below shows one practical way to design the process. Keep the design practical and test it on the least well served audience first, since gaps there usually reveal weaknesses for everyone. Document only what helps.
- Start from the decisions and actions each audience must take, such as a visitor following site rules or a contractor coordinating work.
- Describe each audience, including its languages, literacy, access to systems and working hours.
- Choose content, timing and method to suit, and test whether the recipient can use the message.
- Assign responsibility for preparing, checking and releasing important information, using competent review where interpretation is needed.
- Collect the views of relevant external parties, such as contractors or emergency services, and decide which to adopt.
- Set how incoming communications are received, answered and recorded, and how urgent matters are escalated.
- Review the design after incidents, complaints or changes of workforce, and update audiences and methods accordingly.
Two illustrative process designs
A construction contractor uses several languages across its workforce. It identifies the information workers need for a changed work interface and selects suitable explanations and checks of understanding. It does not rely solely on a written technical notice in one language. Workers have a route to challenge an unclear instruction before the affected activity.
A BPO provider receives an OH&S concern from a remote worker outside normal office hours. Its process establishes how the message reaches the appropriate responsible person and how urgent matters are escalated under the organisation’s arrangements. The response is based on the facts and suitable advice, without making a medical judgement through a generic helpdesk script.
Keep information consistent and answer relevant messages
Communication should be consistent with information generated within the system and reliable. Check important facts, versions and boundaries. Where an investigation is incomplete, make that status clear. A polished message that overstates certainty can undermine decisions and trust.
Respond to relevant OH&S communications. The response may involve clarification, investigation or referral to a competent owner. The process should connect the message with the necessary action and preserve a route for feedback, rather than simply acknowledge receipt.
Evidence and common mistakes
Retain documented information as evidence of communication as appropriate. A significant request, assessed response and resulting decision can provide a useful trail. The standard does not require a transcript of every conversation or prescribe one communication matrix.
Common weaknesses include unclear ownership, inaccessible formats, inconsistent instructions and an assumption that external parties have received information because a contract was signed. Another is collecting worker concerns through a channel whose users cannot see how to obtain a response.
Frequently asked questions
Is translation always sufficient?
Not necessarily. Consider comprehension, literacy, accessibility and the work context as well as language.
Must external parties help design every message?
No. Consider their relevant views in establishing the process and communicate appropriately for the purpose.
Can an acknowledgement count as a response?
It may be an initial step, but the relevant issue still needs appropriate handling rather than administrative closure alone.
Test a message and its response route
Ask Sterling to review an OH&S communication workflow, from information source to practical action. The ISO 45001 Awareness course develops the foundation. Effivity ISO & GRC automation software can be scoped to agreed information and audit needs. Continue through communication and the guide.