ISO/IEC 17025 clause 3: laboratory terms that affect decisions

What clause 3 requires in practice

Clause 3 brings in two sets of terms: those in the metrology and conformity-assessment vocabularies named in clause 2, and nine definitions of its own. The nine cover impartiality, complaint, interlaboratory comparison, intralaboratory comparison, proficiency testing, laboratory, decision rule, verification and validation.

The definitions bind in a particular way. They fix what a word means whenever the later clauses use it, so a statement about impartiality in clause 4 or about proficiency testing in clause 7 must be read with the definition in hand. They do not themselves tell the laboratory to do anything; the duties sit in the clauses that use the terms.

Several definitions come with notes and examples that are part of how the term is explained, for instance the note separating verification from calibration. The output of clause 3 is therefore a team that applies each term consistently in contracts, methods, training and reports.

Objectivity, dissatisfaction and laboratory activities

3.1: impartiality

Impartiality concerns objective judgement. A relationship or commercial interest needs attention when it could distort decisions. Ownership by a manufacturer is not automatically disqualifying; allowing production pressure to influence a test conclusion is a different matter. Clause 4.1 develops the safeguards.

3.2: complaint

A complaint is an expression of dissatisfaction about the laboratory's activities or results for which a response is expected. It may come from someone other than the paying customer. The handling process under clause 7.9 should recognise the substance rather than depend on a message containing the word “complaint”.

3.6: laboratory

Within this standard, laboratory activities comprise testing, calibration and sampling associated with later testing or calibration. A body may perform one or several of these activities. The term does not automatically include every activity performed by its parent organisation.

Three comparison concepts that should not be merged

3.3: interlaboratory comparison

Two or more laboratories perform and evaluate work on the same or similar items under agreed conditions. Such a comparison can serve different purposes. Its existence alone does not establish that a proficiency-testing exercise has been conducted.

3.4: intralaboratory comparison

The comparison takes place within one laboratory under defined conditions. For example, results produced by different authorised analysts may be compared as part of monitoring validity. Design the comparison so the conclusion is meaningful, rather than simply collecting similar numbers.

3.5: proficiency testing

Participant performance is evaluated against criteria set in advance through an interlaboratory comparison. The evaluation purpose and predetermined criteria matter. Clause 7.7 connects suitable comparisons and proficiency testing to monitoring the laboratory's performance.

Decisions about acceptance and fitness for use

3.7: decision rule

A decision rule explains how measurement uncertainty is taken into account when declaring conformity with a requirement. It affects a pass/fail or in-tolerance conclusion. It is not merely the specification limit or an analyst's opinion after seeing the result; see clauses 7.1 and 7.8.6.

3.8: verification

Verification uses objective evidence to establish whether specified requirements are met. In method implementation, this includes showing that the laboratory can achieve the required performance. Verification is not synonymous with calibration, and not every verification establishes fitness for an intended use.

3.9: validation

Validation adds the question of whether the requirements are appropriate for the intended use. A method may perform consistently yet be unsuitable for the sample, concentration range or decision involved. Clause 7.2 explains when method validation is needed and what evidence supports it.

Why laboratory terminology matters to the business

Many laboratory disputes begin with a word. A customer who asks for validation may mean calibration. A manager who calls a chat between two analysts proficiency testing may leave an assessor unconvinced. A complaint treated as casual feedback can become a serious loss of trust.

Getting the vocabulary right lowers the risk of overselling, of issuing a report that answers a question nobody asked, and of failing an assessment on a technicality that was avoidable. It also helps new staff and customers understand quickly what the laboratory actually does.

How to implement clause 3

The aim is shared meaning, not a glossary for its own sake. Work through the definitions in the order that matches how your laboratory makes decisions.

1. Hold a short session for managers, analysts, reviewers and sales staff to walk through the nine definitions using your own examples.
2. Check complaint handling intake so that dissatisfaction raised by phone, email or a third party is recognised even when nobody uses the word complaint.
3. Review how your laboratory describes its comparisons, and label each one accurately as interlaboratory, intralaboratory or proficiency testing.
4. Look at contract wording for pass or fail statements and confirm that a decision rule is discussed whenever such a statement is requested.
5. Separate method verification from validation in your procedures so that staff know which question they are answering.
6. Remove or correct inconsistent terms in templates and customer documents, then repeat the check when documents are revised.
7. Revisit the vocabulary when a new standard, scheme or customer requirement arrives, since a familiar word may carry a slightly different meaning in a new context.

Evidence an assessor expects for clause 3

Evidence for clause 3 appears indirectly, through the clauses that apply the terms.

• Complaint records that include dissatisfaction raised informally or by someone other than the customer.
• Descriptions of comparison activities that name the type correctly and state their purpose.
• Contracts and reports where a decision rule is agreed before a pass or fail statement is made.
• Method records that show verification and validation being treated as different tasks.
• Staff interviews in which analysts explain the terms in their own work.

Common nonconformities with clause 3

Findings linked to terminology usually surface in the operational clauses, but they trace back to these terms.

• A comparison between two internal analysts is described in a report as proficiency testing.
• A complaint raised verbally by a customer's employee is not logged because the message did not use the word complaint.
• A conformity statement is issued without any agreed rule for handling measurement uncertainty.
• Verification evidence is offered as proof that a modified method is fit for a new use.
• Customer documents and internal procedures define the same term differently.

Two illustrative decisions

Put the vocabulary to work

Use these distinctions in quotations, training, methods and reports. The evidence requirements belong to the relevant operational clauses; clause 3 does not demand nine separate terminology procedures. Avoid adding a glossary that staff never consult while leaving contradictory terms in customer-facing documents.