ISO 45001 clause 7.5.2: create information people can trust and use
ISO 45001:2018 clause 7.5.2 requires suitable identification and description, format and media, and review and approval for suitability and adequacy when documented information is created or updated. These controls help ensure that people can recognise the information and use it for the intended purpose.
What clause 7.5.2 requires in practice
Clause 7.5.2 applies whenever documented information is created or updated. The organisation makes sure of three things. Each item is suitably identified and described, for example through a title, date, author or reference number. The format and the medium suit the use, covering matters such as language, software version, graphics, paper or electronic form. And each item is reviewed and approved for suitability and adequacy.
The examples in brackets in the standard are illustrations, so the clause does not demand one numbering scheme or identical fields on every item. The expectation is that a user can recognise what an item is, can use it in the setting where it is needed, and can rely on someone competent having judged it fit for purpose. How approval is recorded depends on the information and its consequences.
Identify the information clearly
Choose identification that distinguishes the document or record and supports retrieval. Depending on the information, a title, date, author or reference number may help. The standard does not prescribe one numbering convention or require every item to carry identical fields.
For a work instruction, users may need to identify the current version and applicable activity. For a completed record, identification may concern the task, location, date and responsible person. The method should preserve meaning rather than add codes that only a document administrator understands.
Make format and media suitable
Consider language, technical detail, diagrams, software versions and the setting in which the information is used. A dense document may be unsuitable for a quick operational reference. A digital form may fail if workers cannot access it at the point where the information is needed.
Test whether the format captures essential context. Missing units, unclear choices or ambiguous fields can produce unreliable records. Worker input can reveal practical problems before the document becomes an approved but unusable part of the system.
Review and approve the content
Review checks suitability and adequacy; approval confirms the information through an appropriate authorised arrangement. A signature does not demonstrate that the technical content was assessed by someone competent to judge it. The method should match the information and potential consequences.
Routine records created within a controlled workflow can have appropriate review and approval arrangements built into that process. The standard does not universally require a separate wet signature on every entry. It does require a defensible arrangement for the information being created or changed.
Why careful creation avoids unusable documents
A document that is hard to identify, written in the wrong language or format, or approved by someone who could not judge its content will either be ignored or cause harm when followed. Careful creation saves time later: an instruction that workers helped shape is more likely to be followed, and a record with clear context can be relied on in an investigation. For regulators and clients, evidence that content was reviewed by competent people carries more weight than a signature alone. Auditors regularly test whether the approved version matches what the work needs.
How to implement clause 7.5.2
The following steps are one way to set up creation and update arrangements without adding bureaucracy. Involve the people who will use the item, since they are best placed to spot unclear wording, missing context or an unsuitable format before it is approved.
- Decide what identification each type of item needs to be found and understood, such as a title, date, owner or task reference.
- Choose format and media with the users, considering language, detail, diagrams and access at the point of work.
- Pilot new instructions or forms with a few workers and fix ambiguous fields before release.
- Set who reviews content for technical suitability and who approves it, matching the level of competence to the consequence.
- Build review and approval into controlled workflows for routine records, so entries are not signed separately.
- Check a sample of items to confirm that they are identifiable and in the form people actually use.
- Review the arrangements after incidents or audit findings, as unclear items are a frequent contributor to errors at the point of work.
Two illustrative creation decisions
A manufacturer revises a maintenance coordination instruction. Competent reviewers check the responsibilities and control interfaces, while relevant workers test whether the sequence is understandable. Approval occurs before issue, and the subsequent control process ensures the new version reaches users. A formatting check alone would not establish adequacy.
A BPO company creates a form for work-related concern reports. It checks that the form allows workers to describe the issue without forcing an inaccurate category or unnecessary personal detail. The response owners review whether the information supports appropriate assessment. A trial reveals an unclear question, which is corrected before rollout.
Evidence and common mistakes
Suitable evidence can include authorised approvals, review records, version history and the information itself. No particular approval software or document template is prescribed. The organisation should be able to explain who assessed the content and how changes become authorised.
Common weaknesses include approving an inherited template without checking its relevance, allowing informal edits to operational instructions and treating visual presentation as a substitute for technical review. Another is applying such a burdensome approval process that workers rely on uncontrolled notes instead.
Frequently asked questions
Must documents have reference numbers?
No specific coding system is required. Identification and description must be suitable for the information’s purpose.
Can approval be electronic?
Yes, where the arrangement provides appropriate authorised review and approval with suitable evidence.
Do updates need the same consideration as new documents?
Yes. Changes need suitable identification, format, review and approval for their intended use.
Test a form before it becomes routine
Discuss an OH&S document or form review with Sterling, including usability and audit evidence. The Documented Information Management course develops the relevant skills. Effivity ISO & GRC automation software can be scoped to agreed information controls. See clause 7.5 and the full guide.