ISO 9001 & 45001 document control with SafetyDocs
What clause 7.5 of ISO 9001, 45001 and 14001 asks for in document control, how SafetyDocs meets each requirement, and what an auditor will ask to see.
9 min read

Clause 7.5 of ISO 9001, ISO 45001 and ISO 14001 asks you to control your documented information: give each document an identity, review and approve it before use, get the current version to the people who need it, stop old versions being used, and keep the records that prove it all happened. SafetyDocs meets the requirements for documented information (clause 7.5) of all three standards. It numbers and versions every document, keeps the approval with a fingerprint of exactly what was approved, reminds you when a review is due, tracks who has read and signed each version, archives rather than deletes, and logs every change. That helps you stay compliant with ISO document control and be audit-ready, so a certification auditor can see each requirement met.
One point to keep clear: software isn't certified to ISO 9001, 45001 or 14001, and using it doesn't certify you. Certification is granted to your organisation by an accredited certification body, after it audits your whole management system. SafetyDocs gives you the controlled documents and the evidence that system needs.
What clause 7.5 asks for, in plain words
ISO 9001 calls documents and records "documented information". Clause 7.5 has three parts.
7.5.1 General. Your system must include the documented information the standard requires, plus whatever else you decide you need for the system to work. A small business can need far less than a large one. The point is that what you have is controlled.
7.5.2 Creating and updating. When you write or change a document, make sure it has:
- Identification and description: a title, a number or reference, a date, an author or owner, so anyone can tell which document this is.
- The right format and media: the language, the layout and whether it lives on paper or on screen, suited to the people who use it.
- Review and approval: someone competent checks it's suitable and adequate before it's used.
7.5.3 Control. Once it exists, control it so that:
- It's available and suitable for use, where and when it's needed. A procedure locked in the office does nothing for the crew on site.
- It's protected from loss of confidentiality, improper use and loss of integrity: nobody changes it without a trace, and only the right people see it.
- Distribution, access, retrieval and use are managed. You know who has it, and whether they can only read it or can also change it.
- Storage and preservation keep it legible and intact for as long as you need it.
- Changes are controlled, for example with version control, so everyone works from the current version.
- Retention and disposition are decided: how long you keep it, and what happens after that.
- Obsolete documents don't get used. The 2015 edition folds this into control of changes and distribution; the 2008 edition said it outright, and auditors still look for it.
- External documents are identified and controlled. Documents from outside, such as a safety data sheet, a manufacturer's manual or a client's site rules, are marked as external and kept current.
- Records kept as evidence are protected from unintended changes. A signed record of an inspection, a training session or a SWMS sign-on has to stay exactly as it was.
The clause numbers here are from ISO 9001:2015, ISO 45001:2018 and ISO 14001:2015, the editions most organisations are certified to today. If you're moving to ISO 9001:2026, check the numbering with your certification body. Our ISO 9001 beginner's guide covers the rest of the standard and the transition.
How SafetyDocs meets each requirement
| Clause 7.5 requirement | How SafetyDocs meets it |
|---|---|
| Identification and description | Each document gets a number on first publish, such as SWMS-014, SOP-003 or POL-001, with a prefix per document type that you can change. Every version shows its number, date and change note, and search finds documents by number |
| Format and media | Documents read in one clean column on a phone and print to a tidy PDF. Translate them into your workers' languages, with the English kept as the record |
| Review and approval | Name an approver and reviewers. They comment, then the approver decides. The decision is kept with a fingerprint of exactly what was approved, and "Changed since approval" shows if the words change afterwards. You can require approval before publishing, for every document or chosen types |
| Available and suitable for use | Workers open the current version from a text, link or QR code on their own phone, with no app or account, or on a site tablet in kiosk mode |
| Protected | Share with people, groups or the whole organisation, to view or to edit. Every change is logged against the person who made it. Uploads are virus-scanned |
| Distribution, access, retrieval and use | Put documents on jobs, where the crew read and sign or acknowledge them. Read tracking shows who has seen which version, and automatic reminders chase the rest |
| Storage and preservation | Every version is kept and every past version can be opened, so a document stays readable for as long as you keep it |
| Control of changes | Numbered versions (1.0, 1.1, 2.0) with a change note on each, the full history, and restore. A new major version asks everyone to sign again. A job's copy knows which version it came from, shows "Newer version in Documents", and updates in one step |
| Retention and disposition | Set retention periods per document type. A legal hold stops anything being erased |
| Obsolete documents | Past versions are marked "Superseded", and a superseded version's PDF says "Superseded by 2.1: not for use". A withdrawn document is archived, read-only and marked "Withdrawn: not for use". Every printed page says "Uncontrolled when printed", with the version, date and page X of Y |
| External documents | Mark a document as external and record its publisher, reference, revision and the date you last checked it |
| Retained evidence protected | A published document is never erased, only archived with its versions, approvals and review history. Each signature keeps a SHA-256 fingerprint of what was signed, where it was signed from and the device. The audit trail logs every change, publish, approval, review, share, read and signature |
Reviews keep it current, too. Set a review date of 6 months, 1 year, 2 years or a date you choose. SafetyDocs gives a heads-up two weeks before, then shows "Review overdue". An approval lapses when its review date passes, and "Mark as reviewed" or a fresh approval sets the next date, with every review kept in the document's review history.
The same clause in ISO 45001 and ISO 14001
ISO 9001, ISO 45001 and ISO 14001 share one harmonised structure, set out in Annex SL of the ISO directives. Each has the same clause numbers and much of the same core text, so clause 7.5 "Documented information" asks the same things in all three: create and update documents properly, then control them.
What changes is what you're controlling:
- ISO 45001 (health and safety) covers documents such as your WHS policy, risk assessments, SWMS, SOPs, emergency plans, and records of consultation, training, inspections and incidents. It puts weight on worker participation (clause 5.4) and communication (clause 7.4), so the evidence that workers have read and understood a document matters. Our ISO 45001 guide explains the standard.
- ISO 14001 (environment) covers your environmental policy, aspects and impacts register, legal requirements, environmental procedures and monitoring records. See what an environmental management system is.
If you run two or three of these, one set of document controls serves them all. Our list of integrated management system documents shows what that combined paperwork looks like, and the ISO 45001, 14001 and 9001 integrated management system gives you the plans, policy, forms and registers ready to edit. Start your document controls with the document control policy, which sets out how your organisation creates, approves, issues and retires documents.
Keeping SWMS: the WHS rule as well as the standard
ISO standards let you decide how long to keep records. Australian WHS law sometimes decides for you. Under the model Work Health and Safety Regulations, you must keep a SWMS until the high-risk construction work is finished. If a notifiable incident happens during that work, you must keep it for at least 2 years after the incident (regulation 303). While you keep it, it must be readily accessible to the workers doing the work and available for an inspector.
In SafetyDocs, set the retention period for SWMS to match, or longer if your contracts or insurer ask for it. If an incident is being investigated, a legal hold stops anything being erased until you lift it.
What an auditor will ask for, and where to find it in SafetyDocs
A certification auditor tests clause 7.5 by picking documents and following the trail. Expect questions like these:
- "How do you control documents?" Show your document control policy, then show the settings that put it into practice: document number prefixes, approval rules and retention periods per type.
- "Show me the current version of this procedure, and who approved it." Search by its number, such as SOP-003. The document shows its version, its approval and the approver's decision. If the words changed after approval, "Changed since approval" says so.
- "What changed from the last version, and why?" Open the version history. Every version has its change note, and every past version opens as it was.
- "How do you stop people using an old version?" Show a superseded version marked "Superseded", its PDF marked "Superseded by 2.1: not for use", and a job's copy showing "Newer version in Documents". Printed copies carry "Uncontrolled when printed" on every page.
- "How do the people doing the work get the current version?" Show the job's documents and the read tracking: who has read and signed which version, and who was asked to sign again after a major change.
- "When was this last reviewed?" Show the review date, the review history and anything marked "Review overdue".
- "How do you control documents from outside?" Show an external document, such as a safety data sheet, with its publisher, reference, revision and the date it was last checked.
- "How long do you keep records, and how are they protected?" Show the retention periods, any legal hold, the audit trail, and a signature's fingerprint of what was signed.
- "What happened to the document you withdrew?" Show it in the archive: read-only, marked "Withdrawn: not for use", with its versions, approvals and review history intact.
The audit trail on each document answers most follow-up questions. A document's full history is always on the document, whatever your plan.
Getting started
- Write down how you control documents. Edit the document control policy to match how you actually work: who approves what, how often each type is reviewed, and how long you keep it.
- Set the rules in SafetyDocs. Choose your number prefixes, which document types need approval, review periods and retention periods.
- Bring your documents in. Upload your Word or PDF files and convert them, or start from expert-written templates. The SOP library covers common plant and tasks.
- Publish and distribute. Each document gets its number and version 1.0. Share it, or put it on jobs for the crew to read and sign.
- Let the reminders do the chasing. Review dates, signing reminders and "Newer version in Documents" keep everyone on the current version between audits.
Using SafetyDocs outside construction? See document management for safety, quality and HR.
Common questions
Is SafetyDocs ISO certified? ISO 9001, ISO 45001 and ISO 14001 certify an organisation's management system, not software. SafetyDocs meets the requirements for documented information (clause 7.5) of all three, which helps you stay compliant with ISO document control and be audit-ready. Certification is granted to your organisation by an accredited certification body.
Will using SafetyDocs get my business certified? No software can do that. The certification body audits your whole system: your policy, risks, objectives, operations, internal audits and management review, as well as your documents. SafetyDocs covers the document control part and keeps the evidence ready.
Do I need a separate document control system for ISO 45001 and ISO 9001? No. Clause 7.5 asks the same things in both, so one set of controls covers your safety, quality and environmental documents together.
Does ISO require a document number on every document? Clause 7.5 asks for suitable identification, and a number is the simplest way to give it. SafetyDocs numbers every document on first publish, so you don't have to keep a separate register of numbers.
Template library
Put it into practice with a ready-made SWMS.
Browse SWMS templates written for Australian trades. Preview any of them free, then tailor one to your job in minutes.


