Accreditation Fundamentals
Accreditation vs Certification: the non-negotiable distinction
A clear guide to the difference between accreditation and certification, why it matters for public trust, and how to communicate it accurately.
Why this matters
Credible accreditation depends on consistent methods, clear decisions, and evidence that stands up to independent review. This publication translates essential expectations into practical steps so teams can prepare, communicate, and operate with confidence.
Key requirements and expectations
- Define the role of accreditation in the conformity assessment ecosystem.
- Clarify who the customer is and what competence means in practice.
- Establish scope boundaries and decision authority.
- Maintain evidence that decisions are impartial and consistent.
- Accreditation recognizes the competence of conformity assessment bodies (CABs).
- Certification attests that a product, process, or organization meets requirements.
- Public claims must always state scope and status to avoid confusion.
Evidence and records to prepare
- Approved governance or program policies tied to the scope.
- Decision logs that show evaluation and decision separation.
- Conflict of interest declarations for key roles.
- Records that show consistent application over time.
- Public statements that use correct terminology and scope qualifiers.
Common pitfalls to avoid
- Confusing accreditation (CAB competence) with certification (product or org conformity).
- Scope statements that are vague or inconsistent with capability.
- Uncontrolled templates or outdated procedures.
- Decisions made without traceable rationale.
- Using certification language to describe accreditation decisions.
Practical checklist
- Define scope boundaries and exclusions in plain language.
- Assign accountable roles and document competence.
- Standardize forms, records, and retention periods.
- Run an internal review before external assessment.
- Review all public copy to ensure accreditation is described precisely.