The Requirement Is Simple. The Execution Is Not.
The principle is straightforward: every audit team must collectively possess the competence to audit every element of the client's certification scope. This means coverage of every applicable standard, every EA code, and every scope category included in the certification.
ISO/IEC 17021-1:2015 Clause 7.1.2 requires the CB to ensure that audit teams have the necessary competence. IAF MD requirements further specify that auditors must be qualified for the specific EA codes within the scope. If the client's scope includes EA code 17 (basic metals) and EA code 19 (electrical equipment), the audit team must include auditors qualified for both.
In practice, this creates a daily puzzle for CB planners. They must match auditor qualifications to client scopes, accounting for multi-standard engagements, EA code combinations, and team availability. In a CB with 20 auditors and 300 clients, the permutations are enormous.
How CBs Currently Handle Scope Coverage
Most CBs manage scope coverage manually. The planner maintains a spreadsheet of auditor qualifications, typically organized by standard and EA code. When scheduling an audit, the planner cross-references the client's scope against the available auditors and tries to build a team that covers everything.
This approach has several failure modes:
- •The spreadsheet is out of date. An auditor completed additional training two months ago, but the spreadsheet was not updated. A qualified auditor is overlooked.
- •The planner misses a scope element. The client's scope includes five EA codes. The planner checks three and assumes the others are covered.
- •Partial coverage is accepted. The planner finds auditors who cover most of the scope but not all. Under schedule pressure, they proceed anyway, planning to "address the gap on site."
- •Nobody validates the team before the audit. The planner books the team, the auditors show up, and the gap is discovered during the audit or, worse, during the AB witness audit.
At "Central Euro Certification," a planner schedules an integrated ISO 9001 + ISO 14001 audit for a chemical manufacturing client. The lead auditor is qualified for ISO 9001 with EA code 12 (chemicals). The team auditor is qualified for ISO 14001 but only has EA codes 17 and 18 (metals and machinery). Nobody on the team has ISO 14001 qualification for EA code 12.
The audit proceeds. Six months later, an AB assessor reviews the file, checks the team qualifications against the scope, and raises a major nonconformity. The audit was conducted by a team that lacked the required environmental competence for the client's industry sector.
What an AB Assessor Looks For
During an accreditation surveillance assessment, the assessor will:
- 1. Select a sample of completed audit files
- 2. Check the client's scope (standards, EA codes, scope categories)
- 3. Check each team member's qualification records
- 4. Verify that the team collectively covers every scope element
If there is a gap, the assessor will ask the CB to explain how the audit was valid. If the CB cannot demonstrate adequate coverage, it is a finding. Multiple findings of this type suggest a systemic problem with the CB's team composition process, which can escalate to a major nonconformity.
How Certiva Validates Coverage Automatically
In Certiva, every auditor has a qualification profile that includes their approved standards, EA codes, and scope categories. When a planner builds an audit team for a specific audit set, the system automatically validates the team's combined qualifications against the client's scope.
The validation is not a simple pass/fail. Certiva generates specific gap messages that tell the planner exactly what is missing:
- •"Team lacks ISO 14001 coverage for EA code 12 (chemicals, chemical products, fibres)"
- •"No team member is qualified for ISO 45001 in scope category C (construction)"
- •"Lead auditor qualification for EA code 29 (wholesale and retail trade) expires on 2026-06-15"
These messages appear at scheduling time, before the audit is confirmed. The planner can adjust the team composition, add a specialist, or reassign the engagement.
The Validation Happens at Scheduling, Not After
This is the critical difference between Certiva's approach and a manual process. Manual validation happens when someone remembers to check. Certiva's validation happens automatically, every time a team is assembled.
The planner cannot dismiss the validation. If the system identifies a coverage gap, the gap is recorded. The planner can proceed with a justified reason, but the gap and the justification are both part of the audit record. If the AB assessor reviews the file, they will see that the CB identified the gap and documented why the team composition was accepted despite it.
Compare this to the manual scenario where the gap is never identified. The CB does not know there was a problem until the AB finds it. There is no justification to offer because the CB was not aware of the issue.
Multi-Standard Engagements Multiply the Complexity
Scope coverage validation becomes significantly more complex when the client holds multiple certifications. An integrated ISO 9001 + ISO 14001 + ISO 45001 audit requires coverage across three standards, each with its own EA code requirements. The team must include auditors who, collectively, are qualified for every standard-EA code combination in the scope.
For a client with three standards and four EA codes, the planner is managing up to twelve qualification checks. Doing this manually with a spreadsheet and hoping nothing is missed is not a reliable process.
Certiva handles the combinatorial complexity automatically. The system checks every standard-EA code pair against the team's qualifications and reports all gaps in a single validation result. The planner sees the complete picture and can make informed decisions about team composition.
Scope Coverage Is an Accreditation Requirement, Not a Best Practice
There is no flexibility in this requirement. The CB must demonstrate that audit teams have the required competence for the scope they audit. If they cannot, the audits are invalid and the certifications issued based on those audits are questionable.
Certiva treats scope coverage as a hard constraint because that is what it is. The system does not allow planners to ignore gaps without documenting a justification. The validation runs every time, for every audit, automatically.
Every scope element must be covered. Every time. No exceptions.
Certiva validates coverage automatically with specific gap messages. See it at getcertiva.com.