Practical guide · Educational reading
Implementation and certification are separate planning decisions. Learn how to define useful improvements while checking what external evidence your organization needs.
Audience / jurisdiction: International guidance for organizations considering management system standards; local legal and contractual obligations require separate checks.
Separate improvement from certification
When an organization considers a management system standard, two questions can become tangled: how should we improve the way we work, and do we need certification? ISO’s public guidance explains that organizations can benefit from implementing management system standards without certification. Implementation and certification should therefore be treated as separate planning decisions, even when an organization intends to pursue both.
Suggested practice: begin with a short statement of purpose. Identify the operational problem the organization wants to address and, separately, what evidence customers or other interested parties expect. This avoids making a certificate the entire project objective. It also avoids the opposite mistake: assuming that improving internal practices will necessarily satisfy an external request for certification.
Sources: [1]
Write a brief that captures both decisions
ISO’s distinction between implementation benefits and certification provides a useful starting point for a project brief. Rather than immediately building an audit timetable, describe the intended outcome in operational terms. What should work more consistently? Where are responsibilities unclear? Which recurring problems should the management system help the organization address?
Suggested practice: record the selected standard reference, the reason for choosing it, the activities the project will cover and the person responsible for coordinating the work. Add a separate field for certification status: needed, being considered or not currently planned. These are suggested planning fields, not prescribed ISO documentation.
Keep unresolved questions visible. For example, if a customer has asked for certification, obtain the actual wording of that request before deciding that an internal improvement project is enough. This guide does not establish whether certification is required by any particular contract or law.
Sources: [1]
Make implementation progress observable
Because implementation can provide benefits without certification, it is useful to define progress in terms of changed working practices rather than certificate status alone. A project can otherwise accumulate documents without making clear what employees should do differently.
Suggested practice: select a manageable activity and describe its current problems, intended improvements and responsible owners. Then choose a few practical observations that would indicate progress. Depending on the activity, these might include clearer handovers, fewer repeated mistakes or quicker resolution of unanswered questions. These examples are editorial suggestions, not ISO performance measures.
Use the selected standard itself to establish its applicable requirements. The public guidance used for this article is not a substitute for that document and does not support a clause-by-clause implementation checklist.
Sources: [1]
Apply the distinction to a customer request
Hypothetical example: a small service provider wants more consistent handovers between its sales and delivery teams. Separately, a prospective customer asks whether the provider has certification. The provider should not treat these as interchangeable questions.
Suggested approach: the project lead records the handover problem and assigns an owner to test improvements. Another owner clarifies exactly what the customer is requesting and when the evidence is needed. Management then considers the implementation work and the certification decision together, without assuming that one automatically resolves the other.
The example illustrates ISO’s point that implementation has value without certification. It does not demonstrate conformity with a particular standard, satisfy a real customer requirement or establish that certification is optional in the provider’s circumstances.
Sources: [1]
Review outcomes and evidence separately
Suggested practice: close each planning review with two separate updates. First, state what has changed in day-to-day operations and what remains unresolved. Second, state the certification decision and the evidence behind it. If the external expectation is still unclear, record that uncertainty rather than presenting an assumption as a settled obligation.
Keep communications equally precise. Describe implementation work as implementation work, and do not present it as proof of certification. The practical lesson from ISO’s guidance is straightforward: pursue useful management-system improvements while making a deliberate, separately evidenced decision about certification.
Sources: [1]
Sources
Your experience
Does your management-system project clearly separate the improvements you want from the certification evidence others expect?
Originally published by AdviseISO, a knowledge-sharing initiative of W3 Solutionz.