Converting a Clause-Based Management System into Something Usable
Clause-Based Management Systems in Brief
- No ISO standard requires documentation to follow its clause structure
- Clause-based systems repeat themselves badly once more than one standard is involved
- Correlation documents let a business-structured system be audited clause by clause
Converting a Clause-Based Management System
A clause-based management system is one where the documentation mirrors the numbered structure of the ISO standard. There is a section four, a section five, a section six, and each one restates what the standard asks for. It is a common way to build a system and it is rarely the right one.
The reason it happens is understandable. Writing a manual that follows the standard makes the certification audit feel safer, because every requirement has an obvious home. The cost lands later, on everybody who has to use the thing afterwards.
Conversion means keeping the content and changing the organising principle. The system stops being a commentary on the standard and becomes a description of how the business runs, which is what a management system is supposed to be.
Why Clause-Based Management Systems Fail
The problem is not that these systems are non-compliant. They usually pass audit. The problem is that they are unusable, and an unusable system decays between audits.
- Nobody can find anything - a supervisor looking for the process for handling a customer complaint has to know which clause complaints live under before they can look it up.
- The language is borrowed - text lifted from the standard carries terms like interested parties and documented information into a business that has never used either phrase.
- Multi-standard systems repeat themselves - the management standards share a common structure, so following the clauses of three standards produces three versions of the same content on context, leadership, planning and review.
- Important things get buried - the operational detail that actually matters ends up scattered across clause eight of three different documents.
- Maintenance becomes a job in itself - a change to one process means finding and editing it in several places, so in practice the edits do not get made.
None of this is required by the standards. ISO 9001 states in Annex A that the documentation of a quality management system does not need to follow the clause structure of the standard, and no other management standard requires it either.
What a Clause-Based Management System Costs You
The visible cost is the time spent maintaining documents nobody reads. The larger cost is that the system stops reflecting reality. Processes change on the floor and the manual does not follow, so the gap between the documented system and the actual one widens quietly until an auditor finds it.
There is a second cost at the point of adding a standard. An organisation certified to one standard that wants to add another faces a choice between a second clause-based document set, with all the duplication that brings, or the conversion it should have done at the start.
How to Convert a Clause-Based Management System
Conversion is mostly reorganisation rather than rewriting. The content largely exists already and the work is deciding where it belongs.
Start by mapping what the organisation actually does. Top-level processes first: how work comes in, how it gets done, how it gets checked, how people and equipment are managed, how the whole thing is reviewed. That map becomes the structure of the new manual.
Then move the existing content into it. Most clauses map cleanly onto a business process. Where the same content appears in three places because three standards asked for it, the three collapse into one. Where a requirement has no natural home in the business, that is usually a sign the requirement was being met on paper only, and it is worth asking what the organisation genuinely does about it.
The last step is the correlation document, and it is the step that makes the rest safe.
Keeping Auditors Comfortable After Converting from Clause-Based
The worry that stops organisations converting is the audit. If the manual no longer has a section per clause, how does an assessor confirm every requirement is met?
A correlation document answers that. It lists each clause of the standard alongside where in the system that requirement is addressed. The assessor works down the clauses as they always have, and is directed to the relevant part of a system organised around the business. One correlation document per standard covers an integrated system without any of the duplication that clause-based documentation creates.
People get talked into clause-based systems because it feels safer, and then they are stuck with a manual that reads like a legal document nobody asked for.
You do not need it. The standard says as much in its own annex. Write down how the business works, in the words the business already uses, and then produce a wee table that shows the auditor where each clause is covered. That is the whole trick.
Ours was clause-based when I took over. Three standards, three manuals, and the same paragraph about management commitment in all three with slightly different wording.
I did not rebuild anything from scratch. I took an alphaZ toolkit, which is already laid out around business processes instead of clauses, and worked through the old documents dropping each bit of content into the section it belonged in. Most of it went straight across, and the duplication fell away on the way because there was only one place left for it to go.
It took a couple of hours, not the weeks I had braced myself for. The correlation sheets came with the toolkit so the auditor still had a clause by clause route through. First surveillance after the change produced no findings against the documentation, and people started using it because they could finally find things in it.
Practical Compliance Guidance
Section 1 of the IMS1 manual sets out the management system, its scope and how the documented information within it is controlled. The manual is deliberately not built around the clause structure of any standard, which is what makes it a conversion target rather than another version of the same problem.
Because the alphaZ documents are integrated rather than split up standard by standard, any of the toolkits works as a starting point for a conversion. Pick the toolkit covering the standards in scope and move the content of the existing system into it section by section. Where the old documentation said the same thing three times over for three standards, there is only one place for it to land, so the repetition disappears as it goes across. Correlation documents come with the toolkit, and support is available for organisations that would rather hand the job over.
| alphaZ document | How to use it |
|---|---|
| ISO 9001 / 14001 / 45001 IMS Toolkit | The integrated document set organised around business processes rather than clauses. The destination structure for a conversion. |
| Remote Support - Full Clause Conversion Service | Existing documentation reviewed and rebuilt into an integrated business-structured system, with correlation documents supplied. |
| ISO 9001:2015 Correlation | Maps each clause of the quality standard to where it is addressed in the system, so assessors can audit clause by clause. |
| ISO 14001:2015 Correlation | The equivalent clause map for the environmental standard, for systems covering environmental management. |
| ISO 45001:2018 Correlation | The clause map for the health and safety standard, used the same way during audit. |
| I-C IMS Gap Analysis Checklists | Run before a conversion to confirm what the existing system genuinely covers and what only appears to be covered. |
| Remote Support - Project | A defined day of remote support, useful for agreeing the new structure before doing the reorganisation in-house. |
Note - all the above files can be downloaded with an alphaZ subscription.
