# ISO 17025 Reporting of Results

> Design and validate test reports and calibration certificates per ISO/IEC 17025:2017 Clause 7.8. Creates compliant report templates with all mandatory elements (title, lab ID, unique reference, customer info, method, dates, results with units, signatures), handles opinions/interpretations per Clause 7.8.7, defines decision rules for conformity statements per Clause 7.8.6, and establishes amendment procedures.



Tags: ISO 17025, Reporting, Test Reports, Calibration Certificates, Clause 7.8


## Example Prompts

- Create a test report template that meets all ISO 17025 Clause 7.8 requirements
- Design a calibration certificate template for our metrology laboratory
- Define decision rules for conformity statements in our test reports
- Establish procedures for opinions and interpretations per Clause 7.8.7

URL: https://rakenne.app/skills/iso17025-reporting-results/index.md

Try this skill: https://rakenne.app/a/?skill=iso17025-reporting-results



## Overview

The test report is the only deliverable most customers ever see from a laboratory. It is the tangible product of all the method validation, uncertainty estimation, quality control, and technical expertise that goes into generating a result. ISO/IEC 17025:2017 Clause 7.8 specifies exactly what must appear on that report -- and the list is longer than most laboratories expect.

This skill builds compliant report templates with every mandatory element required by Clause 7.8.2: title, laboratory identification, unique report number on each page, customer information, method reference, item description, dates (receipt, testing, issue), results with units of measurement, authorized signatures, and amendment provisions. For calibration laboratories, it adds the Clause 7.8.4 requirements: calibration conditions, measurement uncertainty (always mandatory on certificates), and metrological traceability to SI units.

Beyond the template, the skill addresses two areas that frequently trip up laboratories in assessments. First, opinions and interpretations (Clause 7.8.7): when the lab offers professional judgment beyond raw data, the procedure must define who is authorized, what basis they use, and how opinions are clearly distinguished from objective test data. Second, decision rules for conformity statements (Clause 7.8.6): if your report says "PASS" or "complies with specification," you must define the decision rule, agree it with the customer, and account for measurement uncertainty using a guard-band method per ILAC G8:09/2019.

### What It Covers

- **Test report template** -- all Clause 7.8.2 mandatory elements with proper formatting and placement
- **Calibration certificate template** -- additional Clause 7.8.4 elements (calibration conditions, uncertainty, traceability)
- **Unique identification** -- report numbering system ensuring each page is traceable
- **Customer information** -- client identification, contact details, project reference
- **Method reference** -- test method identification with version and any deviations noted
- **Item description** -- unambiguous identification of the test or calibration item
- **Date fields** -- receipt, sampling (if applicable), testing/calibration, and report issue dates
- **Results presentation** -- results with units, significant figures, and uncertainty where required
- **Authorized signatures** -- signatory identification with method-specific authorization
- **Opinions and interpretations (Cl.7.8.7)** -- authorized personnel, basis documented, clearly distinguished from data
- **Decision rules (Cl.7.8.6)** -- conformity statement approach agreed with customer, guard-band method cited
- **Amendment procedures** -- process for correcting, supplementing, or reissuing reports
- **Electronic delivery** -- data integrity controls for electronically transmitted reports

## Example Conversation

> **You:** We need to overhaul our test report template for LabTech Analytical. Right now our LIMS (Element) generates a report, but our consultant flagged a bunch of missing items during the mock assessment. We're a testing lab -- no calibration certificates.
>
> **Agent:** Let me work through the Clause 7.8.2 checklist systematically. Can you share what your current report includes? I'll identify the gaps.
>
> **You:** Our current report has: lab name and address, report number (auto-generated by LIMS), client name, date of issue, method references, sample IDs, results with units, and a signature line for the lab director. Our consultant said we're missing at least 5 things.
>
> **Agent:** Let me check against the full Clause 7.8.2 list:
>
> | Required Element | Present? | Notes |
> |-----------------|----------|-------|
> | Title ("Test Report") | ? | Does your report have a title at the top? |
> | Lab name and address | Yes | |
> | Location of activity | ? | Is this your Austin lab address, or do you test at client sites? |
> | Unique ID on each page | Partial | Report number on first page -- is it on every page? |
> | Customer identification | Yes | |
> | Method reference | Yes | |
> | Item description | ? | Do you describe the sample beyond the ID? |
> | Date of receipt | ? | |
> | Date of testing | ? | |
> | Date of issue | Yes | |
> | Results with units | Yes | |
> | Amendments clause | ? | Statement about how amendments are handled? |
> | Authorized signature | Yes | |
>
> **You:** No title -- it just says "LabTech Analytical" at the top. Location is always our Austin lab. Report number is only on page 1 -- page 2+ just have "continued" at the top. We don't include date of receipt or date of testing, just the issue date. Sample description is just the sample ID from the COC. And no amendments clause.
>
> **Agent:** That's 6 gaps, which matches your consultant's findings. Here's what I'll add to the template:
>
> 1. **Title**: "Test Report" prominently at the top of page 1
> 2. **Location**: "Testing performed at: 4200 Research Blvd, Suite 300, Austin, TX 78759"
> 3. **Unique ID on every page**: Report number in the header/footer of every page, formatted as "Report No. TR-2024-NNNN, Page X of Y"
> 4. **Date of receipt and date of testing**: Add fields for both alongside the issue date
> 5. **Item description**: Expand beyond sample ID to include matrix, collection date/time, preservative, container type -- pulled from your COC/LIMS data
> 6. **Amendments clause**: "Amendments to this report shall be issued as a supplementary document identified as 'Amended Test Report TR-2024-NNNN-A1' with clear identification of the changed information"
>
> Now for decision rules. Do your reports currently include any pass/fail statements -- like comparing results to EPA MCLs or state drinking water standards?
>
> **You:** Yes, for drinking water compliance reports we flag anything exceeding the MCL. We put a bold "EXCEEDS MCL" next to the result.
>
> **Agent:** That's a conformity statement, which triggers Clause 7.8.6. You need a defined decision rule. The simplest approach for environmental testing:
>
> **Simple acceptance rule (shared risk)**: "Results are compared to the stated specification limit without adjustment for measurement uncertainty. The risk of false acceptance or false rejection is shared between the laboratory and the customer." This must be agreed with the customer -- typically in your contract/service agreement.
>
> However, given that you have measurement uncertainty budgets (from the MU skill), you could offer a more rigorous approach:
>
> **Guard-band rule (ILAC G8 w4)**: "A result is declared conforming only if the result plus the expanded uncertainty U falls below the specification limit." This protects the customer from false acceptance but increases the chance of false rejection.
>
> Which approach fits your customer base better?
>
> **You:** Our municipal clients are used to simple pass/fail. Let's go with shared risk as the default but note in the service agreement that customers can request the guard-band approach.
>
> **Agent:** I've drafted the complete reporting procedure and test report template. Running validators...
>
> `report_compliance_checker` -- **PASS**. All Clause 7.8.2 mandatory elements present.
>
> `opinion_interpretation_validator` -- **REVIEW**:
> - MISSING: Basis for opinions/interpretations not documented
>
> Do your reports ever include interpretive statements beyond the raw data? For example, "Based on these results, the water is safe for human consumption" or trend analysis comments?
>
> **You:** No, we just report numbers. If anything exceeds a limit we flag it, but we don't provide interpretations.
>
> **Agent:** Then I'll add a statement in the procedure: "LabTech Analytical does not provide opinions or interpretations on test reports. Reports contain objective test data only. If interpretive services are requested, the laboratory will evaluate the request per the opinions and interpretations procedure before accepting." That satisfies the clause by documenting your position.
>
> Running again -- **PASS**. All documents saved to `output/`.

## Sample Output Excerpt

The skill produces a reporting procedure and test report template. Here is a representative excerpt from the test report template.

---

# TEST REPORT

**LabTech Analytical LLC** | A2LA Accredited Laboratory (Certificate No. pending) | 4200 Research Blvd, Suite 300, Austin, TX 78759

Report No.: TR-2024-0847 | Page 1 of 2

---

| Field | Value |
|-------|-------|
| **Customer** | City of Austin Water Utility, 625 E. 10th Street, Austin, TX 78701 |
| **Project reference** | PO-2024-DW-1847 |
| **Date of receipt** | 2024-10-14 |
| **Date of testing** | 2024-10-14 through 2024-10-16 |
| **Date of issue** | 2024-10-18 |

### Sample Information

| Lab Sample ID | Client Sample ID | Matrix | Collection Date | Preservative | Container |
|--------------|-----------------|--------|-----------------|-------------|-----------|
| WO-2024-0847-001 | DW-MLK-0147 | Drinking water | 2024-10-14 08:30 | HNO3 (pH<2) | 500 mL HDPE |
| WO-2024-0847-002 | DW-MLK-0148 | Drinking water | 2024-10-14 09:15 | None | 250 mL plastic |

### Results -- Metals by ICP-MS (EPA 200.8 Rev 5.4)

| Analyte | Result (ug/L) | MDL | MRL | MCL | Conformity |
|---------|:------------:|:---:|:---:|:---:|:----------:|
| Arsenic (As) | 3.2 | 0.5 | 1.0 | 10 | Conforms |
| Cadmium (Cd) | < 0.5 | 0.5 | 1.0 | 5 | Conforms |
| Chromium (Cr) | 8.7 | 0.5 | 2.0 | 100 | Conforms |
| Lead (Pb) | 18.4 | 0.5 | 1.0 | 15 | **Does not conform** |

**Decision rule**: Simple acceptance (shared risk per service agreement SA-2024-AWU). Results are compared to the stated MCL without adjustment for measurement uncertainty. Measurement uncertainty is available upon request.

**Note**: This report shall not be reproduced except in full without written approval from LabTech Analytical LLC. Amendments to this report, if any, shall be issued as supplementary documents referencing this report number.

**Authorized signatory**: Sarah Chen, Laboratory Director | Date: 2024-10-18

<!-- /excerpt -->

## Extension Tools

### `report_compliance_checker`

Validates test report or calibration certificate templates for all mandatory elements per Clause 7.8.2 and 7.8.4.

| Check | What It Validates | Severity |
|-------|-------------------|----------|
| **Title** | Report or certificate title present (Cl.7.8.2.1a) | MISSING if absent |
| **Laboratory name/address** | Lab identification (Cl.7.8.2.1b) | MISSING if absent |
| **Location of activity** | Where testing/calibration was performed (Cl.7.8.2.1c) | MISSING if absent |
| **Unique identification** | Report number on each page (Cl.7.8.2.1d) | MISSING if absent |
| **Customer identification** | Customer name and contact (Cl.7.8.2.1e) | MISSING if absent |
| **Method reference** | Test/calibration method identification (Cl.7.8.2.1f) | MISSING if absent |
| **Item description** | Unambiguous item identification (Cl.7.8.2.1g) | MISSING if absent |
| **Date fields** | Receipt, sampling, testing/calibration dates (Cl.7.8.2.1h) | MISSING if absent |
| **Date of issue** | Report issue date (Cl.7.8.2.1i) | MISSING if absent |
| **Results with units** | Measurement results with units (Cl.7.8.2.1j) | MISSING if absent |
| **Amendments clause** | How amendments/additions are handled (Cl.7.8.2.1k) | MISSING if absent |
| **Authorized signature** | Signatory or equivalent authorization (Cl.7.8.2.2) | MISSING if absent |
| **Calibration conditions** | Environmental conditions during calibration (Cl.7.8.4.1a) | MISSING if calibration cert |
| **Measurement uncertainty** | Uncertainty on calibration certificates (Cl.7.8.4.1b) | MISSING if calibration cert |
| **Traceability** | SI traceability statement (Cl.7.8.4.1c) | MISSING if calibration cert |

### `opinion_interpretation_validator`

Validates opinions/interpretations (Clause 7.8.7) and decision rules for conformity statements (Clause 7.8.6).

| Check | What It Validates | Severity |
|-------|-------------------|----------|
| **Decision rules** | Decision rule defined for conformity statements (Cl.7.8.6) | MISSING if absent |
| **Decision rule type** | Approach specified (simple acceptance, guard band, shared risk) | MISSING if absent |
| **Customer agreement** | Customer agreement to decision rules documented (Cl.7.8.6.1) | MISSING if absent |
| **Basis for opinions** | Basis for opinions/interpretations documented (Cl.7.8.7.1a) | MISSING if opinions section exists |
| **Authorized personnel** | Personnel qualified to give opinions identified (Cl.7.8.7.1) | MISSING if opinions section exists |
| **Distinction from data** | Opinions clearly separated from objective test data (Cl.7.8.7.1b) | MISSING if opinions section exists |
| **Conformity guidance** | Guidance for pass/fail or conformity statements | WARNING if absent |

## Getting Started

Start by activating the *ISO 17025 Reporting of Results* skill. The agent will ask about your laboratory type (testing, calibration, or both), your current report format, and whether you issue conformity statements.

Have this information ready:
- Your laboratory type -- testing only, calibration only, or both
- A copy or description of your current test report or calibration certificate format
- Your LIMS system and how it generates reports
- Whether you make pass/fail or conformity statements on reports (and against which specifications)
- Whether you provide opinions or interpretations beyond raw test data
- Who is authorized to sign reports and for which methods
- Your report numbering system
- How you currently handle report amendments or corrections
- Any customer-specific reporting requirements

If you have already completed the **ISO 17025 Measurement Uncertainty** skill, the agent will incorporate your uncertainty reporting approach and decision rules directly into the report template. The measurement uncertainty and decision rule sections of the report template align with the budget outputs from that skill.



---

Back to [Skill Library](https://rakenne.app/skills/index.md)