An integrated management system connects the way an organization manages more than one subject or standard. Instead of maintaining unrelated processes for every system, the organization identifies where responsibilities, information and evaluation can work together.
Integration does not erase the differences between standards. The ISO management system standards overview explains how shared structures can support the use of multiple standards.
Start with work, not with a combined manual
An organization may put several policies into one document and still operate disconnected systems. A more useful starting point is the work itself: how a requirement enters the organization, how decisions are made and how results are reviewed.
Ask where people currently enter the same information several times or receive conflicting instructions. Some duplication may be unnecessary; some information may need to remain distinct because it serves a different technical purpose.
Understand the boundaries
Integration is easier to discuss when the scope of each system is clear. Compare the entities, activities, sites and organizational functions involved. A central process may support several locations even when only some locations are included in a particular certification scope.
Document those relationships in a way the people responsible can understand. Do not assume that sharing an organization chart means every standard covers the same operation.
Examples of coordination
- One change-management process can prompt consideration of several relevant subjects.
- Internal audit planning can consider related processes without losing standard-specific criteria.
- Management review can bring related information together while preserving clear conclusions.
- Corrective-action arrangements can share a method while retaining the context of each issue.
These are examples of possible coordination, not a prescribed design for every organization.
Preserve specialist attention
A shared risk process should not flatten unlike issues into a generic list that no longer helps decisions. Information security, food safety and occupational health and safety may require different knowledge and evidence. Integration should improve understanding of interfaces, not remove needed competence.
For example, a supplier change might affect delivery quality and information access. The organization may coordinate the change while assigning the relevant parts of the review to different responsible people.
What does integration mean for certification?
Explain the degree of integration when discussing an assessment. The certification body needs to understand the systems, scopes and relevant competence requirements. Do not assume a fixed reduction in audit time or an automatic single certificate for every requested standard.
Each certification claim must remain traceable to the requirements and scope assessed. A coordinated programme does not turn a decision under one standard into a decision under another.
A useful first discussion
List the standards, existing certificates, system boundaries and shared processes. Identify where the organization still operates separate arrangements and why. That gives a clearer basis for planning than a general statement that the system is “fully integrated.”
Read EQRM’s integrated certification page or contact EQRM with the proposed combination and scope.
Draw a shared-process map
List document control, internal evaluation, management review and corrective action against each system you intend to integrate. Identify which steps are shared and which require subject-specific expertise or evidence. Mark any differences in sites or organizational boundaries. Use this map when discussing coordinated assessment so integration supports clear responsibilities rather than hiding different requirements.
Quick answers
Does integration remove separate standard requirements?
No. Sharing a process does not remove the need to demonstrate conformity to the requirements of each applicable standard.
What should be aligned before an integrated assessment?
Compare organizational boundaries, sites, activities, responsibilities and the degree to which the systems actually operate together.