There is a difference. Most organisations do not know which one they have.

Here is a test.

Walk up to any member of your operations team today, not the quality coordinator, not the HSEQ manager, not the person whose job title includes the word “systems”, and ask them one question:

“How does your work connect to the organisation’s quality commitments, environmental obligations, and health and safety requirements?”

If they answer clearly, without prompting, connecting all three, your system may actually be integrated.

If they look at you, pause, and then describe one of the three, you have a silo wearing an integrated management system badge.

The Naming Problem

There is a version of IMS implementation that is extremely common across organisations in East Africa, and it is doing real damage to audit outcomes, operational performance, and the return on investment that ISO certification is supposed to deliver.

It works like this: an organisation implements ISO 9001, gets certified, then adds ISO 14001, gets certified, then adds ISO 45001, gets certified. Three audits. Three certificates. Three annual surveillance visits. Three management review meetings. Three corrective action registers.

And somewhere along the way, someone puts the word “integrated” in front of “management system”, because it is on the same shelf.

This is not integration. It is cohabitation.

The difference is not semantic. In an integrated management system, the three standards share one policy, one scope, one risk register, one internal audit cycle, one management review, and one corrective action process. There is no quality version of any of these and a separate safety version. There is one version, and it covers all three.

That level of integration is not achieved by combining documents. It is achieved by rebuilding how the organisation thinks about its management system at the strategic level.

Why the Silo Survives

The silo is not a failure of intention. It is a structural outcome.

Most organisations that end up with fragmented IMS implementations did not plan for fragmentation. They planned for integration, invested in certification, and then watched the silo re-emerge, because the structure of the organisation reasserted itself.

When ISO 9001 was implemented, it lived in the Quality department. When ISO 14001 was added, it lived in the Environmental team. When ISO 45001 arrived, it lived with the Safety Officer. Three departments. Three owners. Three systems, each optimised for its own certification cycle, its own audit calendar, its own reporting line.

The integration existed in the documentation. The organisation continued to operate in thirds.

This is why the most important question in IMS implementation is not “have we integrated our documents?” It is “have we integrated our decision-making?”

The Audit Tells You What the Documentation Cannot

An integrated management system audit surfaces something that three separate audits never will: whether the organisation actually functions as one system.

When an auditor enters an organisation claiming an IMS, they are not looking at three compliance checklists. They are looking at a single management system and asking whether it has genuinely absorbed the requirements of all three standards into the way the organisation plans, operates, monitors, and improves.

The signals come early. The policy on the wall. The scope on the manual cover. The structure of the risk register. The agenda of the last management review. Whether the Clause 8 operational requirements of each standard, the most unique, non-overlapping requirements in the entire ISO framework, are evidenced in the same operational processes or tracked in separate departmental files.

The organisations that sail through integrated audits are not the ones with the thickest documentation. They are the ones whose operational teams, when interviewed by an auditor on the floor, describe their work in terms that connect quality, environmental, and safety outcomes without being prompted to.

That is cultural embedding. And it does not happen by accident.

The Integration Roadmap Most Organisations Skip

Integration is not a switch. It is a journey, and one that benefits from a deliberate roadmap rather than an aspiration.

The most practical framework is to break integration into levels, each one building on the last:

• Level one is documentation integration. One policy. One scope. One document control process. One master register. This is the starting point, achievable within the first year and immediately visible to any auditor.
• Level two is audit integration. One internal audit programme that covers all three standards in the same cycle, conducted by auditors with competence across all three. No more separate audit plans for quality, environment, and safety.
• Level three is management review integration. One meeting. One agenda that covers the performance of all three standards. One set of decisions that addresses quality, environmental, and OH&S objectives together. Top management in the chair, not a systems coordinator.
• Level four is risk integration. One risk register. One risk management process. Process owners assessing quality, environmental, and safety risks in the same activity, in the same document, at the same time.
• Level five is structural integration. One functional unit owns all three standards. Resources, responsibilities, and improvement activities sit within a single home, which means that when a new standard is added, it has an obvious place to live.

Most organisations that claim integration have achieved Level one at best. Very few reach Level four or five. And the gap between where they are and where their certification implies they are is exactly what shows up in an integrated audit.

The Certification Body Conversation Nobody Has

There is a step in IMS implementation that is consistently skipped, with consistently expensive consequences.

Most organisations contact their certification body when they are ready to schedule their audit. By that point, assumptions have been made about scope, about how standards will be combined in the audit, about what evidence is required and in what form. Some of those assumptions are wrong. And by the time they are discovered, the cost of correcting them, in time, in resource, in readiness, is significant.

The conversation with the certification body should happen at the beginning of integration planning. Before implementation. Not before scheduling.

What you are trying to achieve, the level of integration you are targeting, which standards will be combined, what your single scope looks like, needs to be agreed, not assumed. A certification body that understands your integration roadmap from the start can give guidance that shapes implementation. One that only encounters it at the audit stage can only flag what is missing.

The Strategic Alignment Question

Here is the question that exposes whether an IMS is genuinely embedded or merely documented: can the leadership team articulate why they integrated?

Not “because it reduces audit days”, though it does. Not “because it is more efficient”, though it can be. But specifically: how does this integrated management system serve the organisation’s strategic goals? Where does it connect to what the business is trying to achieve this year and next?

When leadership cannot answer that question, the management system is being maintained by coordinators and audited by consultants. It is not driving performance. It is surviving certification cycles.

When leadership can answer it, when the IMS is explicitly linked to supply chain credibility, to regulatory positioning, to client prequalification, to operational risk reduction, then the system has strategic ownership. And strategic ownership is what produces the culture that makes an integrated audit genuinely easy to pass.

The Question Worth Asking This Week

Before the next audit. Before the next management review. Before the next round of surveillance fees.

Ask the question that the auditor will ask.

“Do we have an integrated management system, or do we have three management systems that share a building?”

The answer shapes everything that comes after it: how you plan, how you audit, how you report, how you improve, and whether your investment in ISO certification is actually serving the organisation or just serving the certificate.

We work with organisations across Kenya and East Africa to answer that question honestly, and to build systems that hold up when the auditor does the same.

📩 info@saladinglobal.com | 📞 +254 729 127 702 | 🌐 saladinglobal.com

---

Saladin Consulting Ltd — HSEQ advisory, ISO gap assessments, IMS implementation support, and PECB-aligned training across East Africa.