Accreditation Fundamentals
Complaints and appeals: building a defensible process
How to design a fair, timely, and auditable complaint and appeal workflow.
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.
- Separate investigation from decision authority.
- Set clear timelines and communicate outcomes.
- Record evidence and rationale for every decision.
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.
- A documented workflow with timelines and roles.
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.
- Closing complaints without documented investigation results.
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.
- Maintain a register of complaints and appeals with status.