A customer changes a specification. Quality sees a new requirement. Who checks the implications for people, the environment and continuity before the change moves into work?
ORR IMS is an evolving learning example, currently connecting five starter kits. It is not a complete implementation of the four standards in its intended scope.
For someone interested in integrated management systems, this is a useful place to begin. One change can touch several responsibilities, and the people examining those responsibilities need a way to connect their conclusions.
Integration can help the organisation identify the relevant questions early, assign competent people and make an informed decision. It cannot turn one person’s incomplete assessment into four complete ones.
Start with the same change
The Cedar Estuary worked example follows communication of a customer-specification change through a fictional two-shift business. Its immediate problem is access to the correct instruction.
The case is deliberately limited. It does not provide chemical recipes, hazard classifications or technical instructions. Environmental and occupational health and safety implications of any physical change require specialist assessment. Those matters remain open in the story.
That limitation gives us an important discussion point: a shared administrative process can reveal where further assessment is required without pretending to have completed it.
Start by describing the change in a way that each affected function can recognise. Include what is proposed, the activities and users involved, the intended timing and the information currently missing. Keep the description consistent across the discussions.
Quality asks about the agreed outcome
The quality questions concern what the customer requires and how the changed work will deliver it. What specification applies? Who confirms the requirement? Which instructions, checks and records depend on it?
ISO 9001 concerns quality management systems. In this article, the practical example is narrower: making sure an authorised customer requirement reaches the affected work.
An efficient notification is useful only if it supports that outcome. The team still needs to establish which version is effective, which orders are affected and what evidence supports the relevant release decision.
If the customer change is unclear, record the uncertainty and obtain clarification. A neatly completed change form cannot substitute for an agreed requirement.
Environment asks what else changes
An environmental review may need to examine materials, resource use, waste, emissions or other relevant aspects, depending on the proposed activity. These are questions to assess, not assumed consequences of every specification change.
ISO 14001 addresses environmental management systems. The competent people in an adopting organisation need to determine which requirements and criteria apply to its circumstances.
For the fictional case, the honest position is that broader assessment remains pending. We should preserve that status rather than embellish the story with an invented environmental approval.
A useful integration mechanism would make the pending question visible to whoever decides whether and how the proposed change proceeds. That prevents an unanswered specialist question from becoming invisible simply because the document workflow is complete.
Health and safety asks about affected people
Who performs the changed work? What might change in their exposure, task demands, equipment or working conditions? Which people should contribute operational knowledge to the assessment?
ISO 45001 concerns occupational health and safety management, including worker participation. In implementation discussions, affected workers can help identify circumstances that the change author has not considered.
A discussion about a new instruction might reveal that it is difficult to access while wearing required protective equipment, or that relief staff receive information through a different route. These are illustrative possibilities to investigate, not events established by Cedar Estuary’s record.
The point is to bring knowledge of actual work into the decision while preserving the need for appropriate technical and safety expertise.
Continuity asks what the work depends on
The Cedar Estuary case identifies access to authorised specifications during an information-system outage as a continuity dependency. It does not claim that recovery requirements or a complete strategy have been established.
That distinction gives the team a next step. What activities depend on the information? What are the consequences of losing access over time? Which recovery priorities and arrangements require an accountable decision?
ISO 22301 addresses business continuity management systems. A copied file or a single maintenance activity cannot establish that the wider continuity arrangements are adequate.
In an integrated discussion, the dependency can be recognised alongside the other change questions. The specialist continuity work still needs to be done and evidenced.
Bring the answers back to one decision
The value of shared coordination is that somebody can see what is ready, what is unresolved and what conditions attach to each conclusion.
A useful record would identify the affected disciplines, the people consulted, the information examined, the conclusions reached and the matters still open. It would also identify the accountable decision and how that decision reaches the people doing the work.
This need not mean forcing every discipline into an identical checklist. Some questions need distinct methods, records and expertise. The shared mechanism should connect those outputs without stripping away their meaning.
Time is part of the challenge. When a customer wants a quick response, explain which information is needed to make a sound decision and who can resolve the obstacle. Avoid silently treating urgency as evidence that an unanswered question is unimportant.
Build a four-question change screen
A fictional print shop considers changing its packaging. Customer presentation, waste implications, handling tasks and supply interruptions prompt different questions. Listing them together identifies who must assess each one; it does not supply the assessments.
For one fictional change, record a question, competent reviewer and open dependency for quality, environment, health and safety, and continuity. State what the decision-maker must wait for.
Start with the context-and-scope worksheet. Which discipline would you bring into the conversation earlier? Leave a comment below; a question or fictional example is enough. If you want to propose a document change, the contribution guide explains the optional GitHub route.
Use fictional examples only. Do not share employer or client records, personal information or copied standards text.
Images are AI-generated illustrations, not photographs or evidence of actual implementation.
Part 5 of 12 in Making IMS Work with ORR IMS. Explore the series.
Leave a Reply