ISO 45001 clause 7.5.1: determine the documentation the system needs

What clause 7.5.1 requires in practice

Clause 7.5.1 defines the documented information the management system must contain. There are two sources. The first is the documented information that the standard itself requires, for example in the scope, the policy, roles, planning decisions, objectives, competence and evaluation results. The second is whatever the organisation itself judges necessary for the system to be effective.

A note to the clause lists the factors that explain why organisations differ: size and type of activities, products and services, the need to show that legal and other requirements are met, the complexity of processes and their interactions, and the competence of workers. The clause therefore requires a reasoned determination, not a standard bundle. Two organisations of different complexity can legitimately hold different amounts of documentation and still conform, provided each explicit requirement is met.

Identify explicit information requirements

Check the standard’s specific requirements for maintained and retained information. Examples include the scope, policy, relevant roles, planning determinations, competence evidence, objectives and plans, and specified evidence of evaluation and improvement. Read each requirement in context so the information serves its intended purpose.

Some clauses explicitly require documented information; others require an effective process without prescribing a standalone procedure. Do not assume that every clause needs a separate file. One controlled arrangement may support several requirements if the relevant information remains clear and sufficient.

Determine what else is necessary

Consider organisational size, activities, processes, products and services, the need to demonstrate fulfilment of legal and other requirements, process complexity and interactions, and worker competence. These factors influence how much detail is needed for consistent work and reliable evidence.

Ask where reliance on memory or informal knowledge would create a gap. Work involving changing teams, multiple employers or important interfaces may need explicit instructions and records. A simple stable process may need less detail, while still meeting every explicit documented-information requirement.

Why the right amount of documentation matters

Too little documentation leaves important knowledge in people's heads, which fails when staff change or work crosses teams and employers. Too much creates a maintenance burden, hides the instructions that matter and teaches workers to ignore the system. A reasoned decision about what is necessary saves money, makes training easier and gives auditors a coherent set of evidence to follow. It also stops an organisation from buying or copying a large template set whose content does not match how work is done.

How to implement clause 7.5.1

A sensible method is to decide the information set from the standard's requirements and then from the organisation's own risks. There is no benchmark for the correct quantity, so be ready to explain your reasoning to an auditor in terms of your own work and risks.

1. Read each clause and note where it explicitly asks for information to be maintained or retained.
2. Check where one controlled record could satisfy several requirements without losing clarity.
3. Consider size, activity type, process complexity, legal needs and worker competence, as the note to the clause suggests.
4. Ask where reliance on memory would be risky, for example in multi-employer work or high-turnover roles, and add instructions there.
5. Remove or merge items that nobody uses, after checking they are not explicitly required.
6. Record the reasoning so it can be explained to an auditor and revisited after change.
7. Revisit the decision after incidents, audit findings or process changes that show information was missing or no longer used.

Two illustrative documentation choices

Use existing information intelligently

Map information already held in procurement, project, HR or operational systems. Determine whether it is suitable and controlled for the OH&S purpose. Reusing an effective record can reduce duplication, but an unrelated business field should not be treated as evidence of a requirement it does not actually address.

Review the documentation need as work changes. More sites, new hazards, staff turnover or different contractual arrangements may require additional clarity. Conversely, redundant forms can be removed when the necessary information remains reliably available elsewhere.

Evidence and common mistakes