Certification Planned: Clarify Approach, Sequence and Effort Realistically
Anyone planning ISO certification first needs clarity on the objective, standard, scope, existing evidence and the sequence of implementation.
A planned ISO certification becomes much easier when the project does not start immediately with document templates. The first step is a clean status review: Which standard is relevant, which area should be certified, which processes already exist and which evidence is truly missing?
Clarify the Objective First, Then Standard and Scope
Many companies start with the question: "Which documents do we need?" The better question is what the certification is supposed to achieve. Is it about a customer requirement, a tender, internal process reliability, regulatory expectations or several objectives at once?
The standard and scope are derived from that objective. A manufacturing company may need ISO 9001 for quality, ISO 14001 for environmental management, ISO 45001 for occupational health and safety or an integrated combination. A software or AI-related company is more likely to assess ISO 27001 or ISO 42001. What matters is that the scope matches the actual business and is not chosen artificially too large or too small.
What Should Be Checked Before the Project Starts
Before actual implementation, a short but structured check is worthwhile. It prevents the team from working in the wrong places.
| Review Field | Typical Question | Why It Matters |
|---|---|---|
| Scope | Which sites, products, services and processes should be included? | The scope determines audit effort, evidence and certificate wording. |
| Roles | Who owns processes, documents, internal audits and management review? | Without clear responsibilities, implementation remains secondary to daily business. |
| Evidence | Which minutes, KPIs, inspections, training records or approvals already exist? | Existing practical evidence is often more valuable than newly written manuals. |
| Gaps | Which standard requirements are not yet defined or evidenced? | The gaps determine sequence, effort and timeline. |
The Useful Sequence
- Define standard and target picture: Which certification is needed and for what purpose?
- Review current state: Compare existing processes, documents and evidence against the standard.
- Create the project plan: Prioritize gaps and assign tasks realistically to internal roles.
- Implement the system: Build processes, documentation, training and evidence logic in a lean way.
- Check internally: Conduct internal audit and management review before the certification audit.
- Have the system audited externally: Select the certification body and prepare Stage 1 and Stage 2.
When a Gap Analysis Makes Sense
An ISO gap analysis is useful when you do not yet know how far you are from certification readiness. It shows which requirements are already fulfilled, which gaps are critical and which tasks can wait.
For small and medium-sized companies in particular, this creates a pragmatic roadmap. The team does not work on everything at the same time, but on the points that really matter for audit readiness and process reliability.
Typical Mistakes in the Planning Phase
- Selecting a standard before customer requirements and the business model are understood.
- Taking over too many templates even though the company's processes are simpler.
- Not naming internal roles in a binding way.
- Starting audit preparation only after documentation has been written.
- Comparing certification-body offers before the scope is clearly described.
How Sternberg Consulting Supports You
We clarify the standard, objective, scope and starting point with you. Based on this, we create a realistic sequence for implementation and show which tasks are feasible internally and where external support makes sense. A common starting point is an ISO gap analysis or directly the right ISO 9001 consulting project, depending on the standard and objective.
Frequently Asked Questions
How early should certification planning begin?
The earlier standard, scope and gaps are clarified, the better effort can be controlled. If a customer deadline or tender is already in view, planning should start immediately with a realistic status review.
Does everything have to be newly documented before certification?
No. Good ISO systems use existing workflows, evidence and responsibilities. New documentation is created only where something is truly missing for control, traceability or conformity with the standard.
Is a gap analysis mandatory?
No, but it is often the most economical entry point. It prevents wasted effort and shows which tasks have priority before the certification audit.
