Gerencialab
Clause by clause

ISO/IEC 17025 requirements map

The worst time to find out where the standard isn't covered is in front of the auditor. Instead of promising 'compliance' and hoping, here you open it clause by clause and point to exactly where each requirement is met, and where it isn't yet. It's the map that takes the audit out of improvisation and the sales pitch out of overstatement.

4.1 Impartiality.

Identify and manage risks to impartiality: access control by profile and action, audit trail of who did what, segregation of duties in document and financial approval. (Formal impartiality risk management is on the roadmap.)

6.2 Personnel.

Competence, authorization and record of who does each activity: profiles and permissions by screen and action, SOP read confirmation tied to the document, owner recorded on every approval and action. (A dedicated competence matrix is on the roadmap.)

6.4 Equipment.

Suitable, calibrated equipment identified by status: lifecycle record, calibration plans and validity with status light, preventive/corrective/predictive maintenance, and use locking for failed or expired-calibration equipment.

6.5 Metrological traceability.

Results traceable to references: CRM with lot, validity and certified values, calibration certificate recorded per instrument, holding times per parameter and matrix.

7.5 Technical records.

Original records with traceable corrections: results, analysis sheets and result review with audit trail, preserved history and ALCOA+.

7.7 Ensuring validity of results.

Monitor validity through quality control: analytical quality control with 24 QC types, Levey-Jennings, 7 Westgard rules, CUSUM and EWMA, with automatic action on failure.

7.8 Reporting results.

Clear reports with controlled template and signature: configurable report templates, auto-filled variables, signature and template version control, PDF generation.

7.10 Nonconforming work.

Handle nonconforming results: release block by mandatory QC, automatic NC from control failure and a full CAPA cycle.

8.3 Control of documents.

Controlled, approved, up-to-date documents: single master list, automatic code, versioning with automatic obsolescence, approval flow and read confirmation.

8.4 Control of records.

Legible, accessible, protected records: audit trail, access control by profile, controlled distribution with recall and immutable history.

8.5 Actions to address risks and opportunities.

Risk-based thinking backed by correlated operational controls: QC failure action, blocking, NC and statistical charts that detect trends. (A formal risk-management feature is on the roadmap.)

8.7 Corrective actions.

CAPA with root cause and effectiveness: NC with Ishikawa and 5 Whys, 5W2H action and effectiveness verification that reopens the cycle if the action didn’t work.

Ever notice the clause that trips up labs in an audit most isn't the technical one, it's document and record control? It's the wrong SOP on the bench, the record that went missing. Exactly what the map ties down first.
Open the map and walk the clauses: each one points to the screen that meets it, and the two roadmap gaps (measurement uncertainty and the formal risk management of 8.5) come flagged, no makeup. That honesty is what you carry into the audit.

How to actually use the map in an audit

The map isn't a brochure. It's the agenda you open side by side with the auditor to show the evidence for each clause without digging through folders.

From the clause straight to the evidence.

Each requirement points to the screen that meets it. The auditor cites 6.4, you open calibration with the status light. Cites 8.3, you open the master list.

What's on the roadmap shows up flagged.

Measurement uncertainty and formal risk management come marked as pending. You walk into the audit knowing where you'll need supplementary evidence.

Less improvising, fewer lost nights.

Instead of rebuilding the audit folder from scratch each cycle, you open the map and the evidence is already linked to each item.

Frequently asked questions

Does Gerencialab cover 100% of ISO/IEC 17025?

No, and we say so up front. Most clauses are covered with on-screen evidence. Two points remain on the roadmap: measurement uncertainty calculation and the formal risk management of clause 8.5. The map shows where each requirement is met and where it isn't yet, with no makeup.

Why does the map mark some items as roadmap?

Because we'd rather tell you up front than have you find out in the audit. Combined and expanded measurement uncertainty and the formal risk-and-opportunity matrix aren't dedicated features yet. If those points block your accreditation scope, talk to us so we can align on timing.

Can I show this map to the auditor?

That's what it's for. You open it clause by clause and, on each one, go straight to the screen that meets the requirement. The audit stops being a PDF hunt and becomes navigation through the evidence.

Does the system calculate measurement uncertainty?

Not today. It stores the uncertainty stated on the reference material certificate, but it doesn't have a combined-and-expanded uncertainty engine with coverage factor k. That's on the roadmap, and we don't hide it.

Want to see the QMS running with your lab’s routine?

Get through the next audit without burning a weekend night hunting for PDFs. Book a demo and see document control, CAPA and Westgard working with a case similar to your lab's.

ISO/IEC 17025 requirements map · Qualidade · Gerencialab