ISO 45001 documentation requirements cause more audit findings than unsafe work does. The site is often in decent shape; the evidence of it sits in someone’s email instead of the management system, and the auditor never sees it.
This guide covers four steps we use to meet ISO 45001 documentation requirements before certification: build the mandatory core, add what auditors expect in practice, record the climate change decision, and put everything under control. It reflects ISO 45001:2018 as amended in 2024.
What the ISO 45001 Documentation Requirements Actually Cover
ISO 45001 replaced the old split between “documents” and “records” with one term: documented information (Clause 7.5). Two kinds matter in practice.
Maintained information is what you used to call documents: the policy, scope, plans and procedures. It says what you do. Retained information is what you used to call records: minutes, training evidence, audit results, calibration certificates. It proves you did it.
The standard sets no document count. Clause 7.5.1 also lets you add whatever your system needs to work effectively, and beginners read that as a licence to write forty procedures. Resist it. Meeting the ISO 45001 documentation requirements means the right set for your risks, not the biggest one.
Step 1: Build the Mandatory Core of ISO 45001 Documentation Requirements
Start with the ISO 45001 documentation requirements the standard names outright. Everything else is judgement; these items are not.
Maintained: what you keep current
- OH&S management system scope (Clause 4.3), specific enough to name sites and activities. “All operations” invites a challenge.
- OH&S policy (Clause 5.2), available to interested parties.
- Roles, responsibilities and authorities (Clause 5.3). An org chart alone does not show who owns incident investigation or legal compliance.
- Risks and opportunities, and the processes behind hazard identification, legal requirements and planning (Clause 6.1.1). Our step-by-step risk assessment guide covers the method, and the legal register guide covers the register.
- OH&S objectives and the plans to achieve them (Clause 6.2.2).
- Emergency preparedness and response processes and plans (Clause 8.2).
Retained: what you must prove
- Evidence of competence (Clause 7.2), such as certificates for scaffolders, riggers and first aiders.
- Evidence of communication, as appropriate (Clause 7.4.1): toolbox talk sheets and meeting minutes.
- Monitoring and measurement results, plus calibration records for gas detectors, noise meters and similar equipment (Clause 9.1.1).
- Compliance evaluation results (Clause 9.1.2).
- The internal audit programme and its results (Clause 9.2.2).
- Management review results (Clause 9.3).
- Incidents, nonconformities, actions taken and whether they worked (Clause 10.2).
Clause 8.1.1 adds a “to the extent necessary” test for operational controls. That is where SOPs, permits and work instructions for high-risk tasks belong.
Step 2: Add the Documents Auditors Expect Anyway
Several items sit outside the formal ISO 45001 documentation requirements, yet auditors ask for them because the clause cannot be demonstrated any other way. Plan for these:
- An OH&S manual. Optional under the standard, but it gives the auditor a map and saves the first audit day from becoming a verbal tour.
- Worker consultation and participation evidence (Clause 5.4): safety committee minutes, worker input on risk assessments, hazard reporting logs. “We tell the workers” is not participation.
- Management of change records (Clause 8.1.3) for new equipment, chemicals and contractors. Often missing.
- Contractor evaluation records (Clause 8.1.4). Where most high-risk work is subcontracted, as it is across the GCC, this is closely examined. See our guide to contractor safety under ISO 45001.
- Training matrix, permit-to-work register and drill records. A plan without drill evidence rarely survives an audit.

Step 3: Record the Climate Change Decision
ISO 45001:2018/Amd 1:2024, published in February 2024 as part of a joint change to management system standards, added climate change to the context clauses. Clause 4.1 now says the organisation shall determine whether climate change is a relevant issue, and a note to Clause 4.2 says relevant interested parties can have climate-related requirements. The CQI and IRCA summary of the change and the ISO catalogue entry for the amendment give the detail.
It adds a decision to your ISO 45001 documentation requirements, not a new procedure. But if your context analysis never mentions climate, it is an easy finding. In the Gulf the answer is rarely “no”: summer heat and humidity, sandstorms and flash flooding all reach the workforce. Write the decision down with its reasoning, then carry the hazards into your risk assessments. Our heat stress guide for GCC employers shows how.
Step 4: Control Your ISO 45001 Documentation Requirements Before the Auditor Does
Clause 7.5 asks for control of ISO 45001 documentation requirements, not a procedure, but a short document control procedure is the quickest way to show it is done consistently. Our document control guide goes further. At minimum:
- One controlled location, such as SharePoint or HSE software, not personal laptops.
- Version number, approver and date on every maintained document.
- Review dates scheduled in advance. “Reviewed when we remember” will not pass.
- Retention periods for records, so incident files do not vanish when the HSE officer resigns.
Practical tip: before writing anything new, build a one-page master list of every document and record above. Add columns for owner, location and next review date. Gaps show up in an afternoon, and the list becomes your audit index.
GCC Example: An Abu Dhabi Contractor Before Stage 2
This is an illustrative scenario drawn from patterns we see often. A mid-size MEP contractor with about 300 workers across three sites, mostly on subcontracted labour, completes its Stage 1 audit. The auditor notes four gaps against the ISO 45001 documentation requirements: an English-only policy, no climate change decision, drills held but not recorded, and a legal register that lists laws but records no compliance evaluation.
Over six weeks the team translates the policy into the languages its crews actually read, typically Arabic, Hindi and Urdu. They add the climate decision to the context analysis, citing summer heat and the midday work break. They start a drill log, and they evaluate compliance against the register. Because the company works in Abu Dhabi, they also map ADOSH-SF requirements to ISO 45001 clauses, as set out in our ADOSH-SF and ISO 45001 article. Nothing new was invented for the ISO 45001 documentation requirements. The evidence that already existed was simply written down and filed.
Common Mistakes with ISO 45001 Documentation Requirements
- Copy-paste manuals. Another company’s name in the footer is spotted within minutes.
- Procedures nobody follows. A procedure that contradicts site practice is worse than none, because it shows the system is on paper only.
- Empty registers. A legal register with no evaluations is decoration.
- No consultation evidence. Committees that meet but keep no minutes.
- One language only. Procedures workers cannot read fail the communication and awareness tests.
- Several versions of one assessment. Nobody can say which is current.
Consultant Tip: Trace One Incident End to End
Pick a single incident or near miss from the last six months and follow it through the paper: report, investigation, corrective action, effectiveness check, management review. Wherever the trail breaks is a gap in your ISO 45001 documentation requirements, and it is exactly the sample an auditor will pull. Fixing one real trail teaches the team more than rewriting ten procedures.
Conclusion: Make ISO 45001 Documentation Requirements a Habit
Certification is decided in the months before audit day. Work through the ISO 45001 documentation requirements in order: the mandatory core, the expected extras, the climate decision, then control. Check your progress against our ISO 45001 compliance checklist.
If you would rather adapt than draft from a blank page, the ISO 45001 Documentation Package helps you meet ISO 45001 documentation requirements with an editable Word manual, 15+ procedures, 20+ SOPs and work instructions, 50+ forms and records, an internal audit toolkit and a risk assessment toolkit. It is a starting point; you still tailor it to your sites and keep the evidence honest.
