The Scenario
Atlas Quality is a mid-sized certification body accredited for QMS audits across several EA codes. They have a client, a metals fabrication company that also operates a chemical treatment division. The certification scope covers EA 17 (Basic metals and fabricated metal products) and EA 28 (Chemicals, chemical products, and fibres).
The planner assigns two auditors to the Stage 2 audit. Both auditors are qualified for EA 17. Neither holds a qualification for EA 28. The planner, working from a spreadsheet of auditor qualifications, checks that the team has metals experience and moves on. The chemical treatment scope slips through the cracks.
The audit proceeds. The auditors conduct their assessment. The report is drafted. Everything looks routine until the accreditation body's witness assessor, present to observe one of the auditors, reviews the audit team composition against the client's scope.
"Who on the team is qualified for EA 28?" the assessor asks.
Silence.
This is not a minor administrative oversight. It is a nonconformity against ISO/IEC 17021-1:2015 Clause 7.1.2, which requires that the audit team collectively possesses the competence needed for the scope of the audit. The accreditation body raises a finding. Atlas Quality must explain how their process failed to catch the gap, take corrective action, and demonstrate that it cannot happen again.
Why Spreadsheets Cannot Prevent This
The root cause is not negligence. It is a system design problem. Atlas Quality's planner used a spreadsheet that listed each auditor's approved EA codes. The planner checked the spreadsheet, saw that both auditors were qualified for metals work, and confirmed the team. The problem is that the spreadsheet does not actively validate anything. It stores data. It does not enforce rules.
When a client's scope spans multiple EA codes, the planner must manually compare every EA code in the scope against every auditor's qualification list and verify that the union of the team's qualifications covers the full scope. For a two-standard, three-EA-code audit, this is tedious but manageable. For an integrated audit covering three standards and five EA codes, it becomes an error-prone exercise in cross-referencing.
The spreadsheet does not flag gaps. It does not warn the planner. It does not block the assignment. It simply holds data and trusts the human to catch every discrepancy.
How Certiva's Scope Coverage System Works
Certiva approaches audit team composition as a deterministic validation problem, not a manual review task.
Auditor Competence Profiles
Every auditor in Certiva has a competence profile that specifies exactly which standards and EA codes they are approved to audit. These profiles are maintained by the CB's competence management team and reflect the auditor's qualifications, training, and experience. When an auditor gains a new EA code approval or when one expires, their profile is updated in one place.
EA Code Matching
When a planner builds an audit team for a specific client and scope, Certiva compares the team's combined EA code coverage against the client's scope requirements. This comparison is automatic and exhaustive. The system checks every EA code in the scope and verifies that at least one team member is qualified for it.
If the team does not cover all required EA codes, Certiva flags the gap with a specific message identifying which codes are uncovered. The planner sees exactly what is missing and can adjust the team composition before the audit is scheduled.
In the Atlas Quality scenario, the system would have flagged EA 28 as uncovered the moment the planner assigned the two auditors. The message would be unambiguous: "EA 28 (Chemicals, chemical products, and fibres) is not covered by the assigned audit team." The planner would then add an auditor qualified for EA 28 or replace one of the existing team members.
Real Date-Overlap Availability Checking
Scope coverage is necessary but not sufficient. The auditors also need to be available on the audit dates. Certiva checks availability by comparing the proposed audit dates against each auditor's existing assignments, checking for real date overlaps rather than simple calendar-day conflicts. An auditor who is already assigned to another audit on the same dates is flagged as unavailable, preventing double-booking while ensuring coverage.
Deterministic Rule-Checking vs. Guesswork
The critical difference between Certiva's approach and manual processes is determinism. The system applies the same rules every time, without exception. It does not get tired at the end of a long planning session. It does not overlook a secondary EA code because the primary code was the focus. It does not assume that "close enough" qualification is acceptable.
This is not artificial intelligence making judgment calls. It is straightforward rule application: the scope requires these EA codes, the team covers these EA codes, here are the gaps. The logic is transparent and auditable.
When the accreditation body asks how the CB ensures audit team competence coverage, the answer is not "our planner checks a spreadsheet." The answer is "the system validates coverage against each auditor's competence profile and blocks assignment of teams with uncovered scope codes."
The Cost of Getting It Wrong
Atlas Quality's witness audit finding had consequences beyond the immediate nonconformity. They had to review previous audits to determine whether other team assignments had similar coverage gaps. They had to revise their procedure. They had to demonstrate the corrective action's effectiveness at the next assessment. And they had to live with the finding on their accreditation record.
All of this was preventable with a system that checks what a spreadsheet cannot.
Ready to eliminate scope coverage gaps before they reach the audit site?
Book a demo at getcertiva.com and see how Certiva validates audit team composition against your client scopes.