Witness assessment planning for accreditation bodies
Witness assessment planning for accreditation bodies: IAF MD 17 cluster and critical code rules, sourcing suitable audits and matching assessors in time.
A witness assessment is an accreditation body observing a conformity assessment body carry out real work at a client. For management system certification bodies, IAF MD 17 requires witnessing of stage 1 and stage 2 for each scheme at initial accreditation, and at least one witness in every technical cluster within the first five years, with critical codes deciding which audits count.
Key takeaways
- Witnessing depends on the certification body's own calendar, so planning starts with its forward audit programme.
- IAF MD 17 sets coverage by technical cluster and critical code, so the choice of audit matters as much as the date.
- Assessor competence for the IAF code has to be confirmed before the witness date is agreed.
- A live coverage tracker per scheme and cluster stops a gap surfacing late in the accreditation cycle.
What is a witness assessment and why is it hard to schedule?
A witness assessment is an accreditation body assessor observing a conformity assessment body (CAB) performing its real work: an audit, an inspection or a test at a client's premises. ISO/IEC 17011 lists witnessing alongside on-site assessment, remote assessment, document review and file review as assessment techniques. For management system certification bodies, IAF MD 17 sets how much witnessing is needed and in which technical areas.
The scheduling difficulty is that the accreditation body does not own the date. The audit belongs to the certification body's programme, the client has to agree to an extra observer, and the audit may move. The accreditation body must find an audit in the right scheme, technical cluster and critical code, then match an assessor competent in that area to the date the certification body has already set.
The certification body's side of this is covered in planning witnessed audits.
What does IAF MD 17 require?
IAF MD 17:2023 (Issue 2, Version 2) applies to accreditation of management system certification bodies. Its rules work at two levels: the scheme (for example ISO 9001, ISO 14001, ISO 45001) and, within each scheme, technical clusters that group IAF codes. Some codes in a cluster are marked critical. Check the current issue before building your programme.
Initial accreditation (4.2.6)
For each management system scheme, witness both stage 1 and stage 2 for at least one client. If no new clients exist, one renewal or two surveillances covering the key processes can be witnessed.
Cluster coverage (4.2.3)
In the first five years after initial accreditation of each scheme, at least one witnessing activity in each technical cluster. After that, witnessing continues cluster by cluster, with other activities, so each cluster is assessed within ten years.
Critical codes (4.2.4)
Accreditation for all codes in a cluster needs a witness in its critical code. Where critical codes are joined by 'and', each must be witnessed; where joined by 'or', one of them.
Whole scope (4.2.2)
The assessment programme must assess competence throughout the scope, for all IAF codes of each scheme, within the accreditation cycle.
IAF MD 17 also covers extensions: accreditation for new IAF codes is granted where the certification body has already taken certification decisions in them or has shown competence by other means. For IAF codes and clusters, see IAF codes explained.
How should the witness planning cycle run?
Witness planning is a loop that repeats every year of the accreditation cycle. The coverage tracker is the centre: it shows which scheme, cluster and critical code combinations still need a witness, and by when.
- Map gapsclusters and critical codes still unwitnessed
- Request programmeCB shares forward audits in those codes
- Select auditright code, audit type and timing
- Assign assessorcompetent in the code, free on the date
- Witness and reportfindings feed the accreditation decision
- Update trackerclose the gap, plan the next one
The weak point is usually the request step. Ask certification bodies for their forward programme in the codes you need at least a quarter ahead, and ask for more than one candidate audit per gap. Audits move, clients decline observers, and a single candidate leaves no fallback.
Which audits make good witness candidates?
The best candidate shows the certification body's competence where risk is highest. IAF MD 17 expects the programme to cover different audit types: initial audits (stage 1 and stage 2), surveillance and recertification. In practice, planners weigh four things: the code and cluster the audit covers, whether it hits a critical code, the audit type, and the team. A multi-code audit at a client whose scope spans a critical code can close more than one gap.
| Candidate | Coverage it closes | Planning note |
|---|---|---|
| Stage 2, ISO 9001, food manufacturer | Food cluster, critical code | Strong choice: new client, critical code, full team |
| Surveillance, ISO 9001, hotel group (IAF code 30) | Food cluster, non-critical code | Useful only once the critical code has been witnessed |
| Recertification, ISO 14001, chemicals site | Chemicals cluster, several critical codes joined by 'and' | One audit may not close the cluster; plan follow-ups |
| Integrated QMS and EMS audit | Two schemes at once | Check the team covers both codes; see integrated audit time |
How do you match assessors to witness dates?
The assessor needs competence in the scheme and in the technical area of the audit, and must be free of conflicts with both the certification body and its client. Assessor diaries fill with office assessments first, so witness dates, which arrive late and move often, compete for the gaps. Keeping a small pool of assessors qualified across several clusters gives the plan room to absorb a moved audit.
Where no internal assessor holds the code, a technical expert can join the witness. Book them at the same time as the lead assessor, because a witness with a lead but no technical cover does not close the competence gap.
- ✓Scheme and IAF code competence confirmed for the assessor or technical expert
- ✓No conflict with the certification body or its client
- ✓Client consent to the observer confirmed by the certification body
- ✓Travel and duration agreed against the audit plan
- ✓A second candidate audit held in reserve
What does a five year witnessing programme look like?
The timeline shows an illustrative programme for a certification body accredited for ISO 9001 in four clusters. It front-loads critical codes, keeps the busiest clusters early and leaves room at the end of the five years for audits that fall through.
- Year 0Initial accreditationStage 1 and stage 2 witnessed for one client
- Year 1Food and mechanical clustersCritical codes first
- Year 2Construction clusterPlus a surveillance in mechanical
- Year 3Services clusterIntegrated audit covers two schemes
- Year 4Reserve and repeatClose any gap from moved audits
- Year 5Coverage completeEvery cluster witnessed at least once
Accreditation bodies publish their own implementation policies for IAF MD 17 (UKAS, for example, publishes TPS 66). Apply those alongside the IAF document. For inspection bodies and laboratories, the ILAC/IAF FAQs on ISO/IEC 17011 note that technical witnessing should be on site where the work is normally done in person.
How can software support witness assessment planning?
The work is a matching problem with moving parts: coverage gaps, candidate audits from many certification bodies, assessor competence, conflicts and travel. A scheduling engine can hold the coverage tracker, match candidates to assessors and re-plan when an audit moves, while planners decide which witness to confirm. ScheduleAI supports accreditation bodies in this way; see the ISO/IEC 17011 accreditation cycle and competence matrices.
For certification bodies, audit scheduling software that checks competence, rotation and windows on every audit takes most of this work off the planning team.
ScheduleAI tracks witness coverage by scheme, cluster and critical code, matches candidate audits to assessors with the right competence and no conflict, and re-plans when audits move, with planners confirming each witness.
Book a demo Estimate your savingsQuestions
What is a witness assessment?
An accreditation body assessor observing a conformity assessment body carrying out real work, such as an audit, inspection or test, to assess its competence in practice.
How often must an accreditation body witness each technical cluster?
IAF MD 17 requires at least one witness in each technical cluster in the first five years after initial accreditation of each scheme, and continued coverage after that so each cluster is assessed within ten years.
What is a critical code in IAF MD 17?
An IAF code within a technical cluster that must be witnessed to grant accreditation for the whole cluster. Where several critical codes are joined by 'and', each must be witnessed.
What is witnessed for initial accreditation?
For each management system scheme, both stage 1 and stage 2 audits for at least one client, or one renewal or two surveillances if there are no new clients.
Can a remote audit be witnessed?
It depends on how the work is normally done. The ILAC/IAF FAQs on ISO/IEC 17011 say technical witnessing should be on site where inspections are normally in person; see IAF MD 4 remote audits.