Five Signs Your Pipette Calibration Program Has Compliance Gaps

Most compliance gaps in pipette calibration programs don't surface during routine QA reviews. They show up during audits, failed proficiency tests, or data integrity investigations — which are exactly the moments when the cost of finding them is highest.

The five warning signs below give quality managers a way to identify and close those gaps on their own terms, before an inspector does it for them.

Quick Answer: What Are the Most Common Pipette Calibration Compliance Gaps?

The most common compliance gaps in pipette calibration programs include missing or incomplete calibration certificates, undocumented calibration intervals, no traceability to national standards, using non-accredited providers in regulated environments, and failure to recalibrate before use after a repair or impact event. Any of these can trigger an audit finding.

Why Pipette Calibration Is a Frequent Audit Target

Pipettes are among the most frequently used instruments in a lab. They're used across critical workflows in pharmaceutical, clinical, food safety, and environmental settings — which means their calibration records carry significant weight during inspections. Regulators and accreditation bodies such as FDA, CAP, A2LA, and ISO/IEC 17025 auditors routinely pull pipette calibration documentation because they know how often it's incomplete.

That means it isn't a question of whether your program will be reviewed — but whether it will hold up when it is. Understanding the most common failure points is the most direct way to make sure it does.

Sign #1 — Your Certificates Don't Include Measurement Data

Many labs have calibration certificates on file and assume that's sufficient. The problem arises when those certificates only document a pass/fail result with no underlying measurement data. Without as-found values, as-left values, and measurement uncertainty recorded, they are not enough to prove pipette calibration compliance.

Auditors expect to see the actual data that supports the conformance determination. When it is missing, there's no way to evaluate whether the instrument was marginally passing, trending toward failure, or whether the calibration was even performed to the required standard.

Data-bearing certificates are the baseline expectation under ISO/IEC 17025 and most GMP/GLP frameworks. If your certificates don't include measurement results and uncertainty statements, that's the first gap to close. For a full breakdown of what belongs on a compliant certificate, see what a pipette calibration certificate should include.

Sign #2 — Calibration Intervals Aren't Documented or Justified

Many labs are operating on set calibration schedules — such as every six months or annually — without any documented rationale for why that interval was chosen. The interval has simply always been what it is.

While regulatory frameworks don't generally require a specific calibration interval for pipettes, they do require that intervals be established, documented, and defensible. Arbitrarily choosing or keeping one the same just because that's how it's always been done is not defensible during an audit.

A compliant calibration interval is supported by a written SOP that specifies the interval, the rationale behind it, and the criteria that would trigger a review or an adjustment. Performance history, usage frequency, the criticality of the application, and manufacturer recommendations all factor into an interval's justification. If your program can't produce that documentation on request, the interval effectively doesn't exist on paper — regardless of what the lab has been doing in practice.

This is also where calibration interval reviews matter. Intervals should be revisited periodically and adjusted if performance data supports a change. A static schedule with no review history is a compliance gap. For guidance on setting a defensible interval, see how often pipettes should be calibrated.

Sign #3 — You Can't Confirm Traceability to National Standards

Traceability statements are easy to overlook because they often appear on certificates as a single line: "calibrated with standards traceable to NIST." However, auditors know that line doesn't tell them much on its own.

Under ISO/IEC 17025 and most GLP/GMP frameworks, traceability must be documented and unbroken. That means certificates should include reference standard identifiers, calibration hierarchy information, and a reference to the provider's accreditation scope or the specific traceability chain used. A general statement is not sufficient evidence of documented traceability.

This gap is particularly easy to inherit if you aren't careful to choose the right calibration provider. If your calibration provider issues certificates with vague traceability language and you accept and rely on those certificates, the gap belongs to your program. Labs are responsible for evaluating the traceability documentation their providers supply — not just filing whatever arrives with the calibrated instrument.

Sign #4 — Your Provider Isn't Accredited for Pipette Calibration

ISO/IEC 17025 accreditation is not a blanket credential. Accreditation is specific to both the instrument being calibrated and the method being used. A calibration laboratory that holds ISO/IEC 17025 accreditation for dimensional, electrical, or pressure calibration is not automatically accredited for pipette calibration.

Pipette calibration involves gravimetric methods governed by ISO 8655. A provider's accreditation scope must explicitly include pipette calibration under that standard for the work to count as accredited calibration in a regulated environment. Using a provider whose scope doesn't cover pipette calibration is a compliance gap regardless of how reputable or experienced that provider may otherwise be.

Fortunately, verifying scope is straightforward. Both A2LA and NVLAP maintain publicly searchable directories of accredited laboratories, and each entry includes the accreditation scope document. Look for an explicit listing of pipette calibration and a reference to ISO 8655. If it's not in the scope document, it's not covered.

This verification step should be part of your supplier qualification process and reviewed each time a provider's accreditation is renewed.

Sign #5 — Out-of-Cycle Events Aren't Triggering Recalibration

Without a formal SOP addressing out-of-cycle events, instruments are often returned to service after drops, repairs, and tip seal replacements without anyone flagging the need for recalibration. The scenarios are routine enough that they rarely raise concern in the moment — which is precisely what makes this gap one of the harder ones to catch through documentation review alone.

Most calibration standards and GMP guidance are clear on this point: any event that could affect instrument performance requires recalibration before the instrument returns to use. A fixed interval schedule does not account for what happens between calibration dates.

A compliant program includes a documented trigger list for out-of-cycle calibration. At a minimum, that list should cover:

• Physical impact or dropping
• Mechanical repair of any kind
• Tip seal or o-ring replacement
• Extended storage beyond a defined threshold
• Any QC result that falls outside expected ranges and can't be attributed to another cause

Without that documentation and the training to back it up, out-of-cycle events will keep slipping through — and when they aren't flagged for recalibration, it's an audit finding waiting to happen.

How to Assess Your Program Before the Next Audit

A focused internal review can identify most significant gaps in a few hours using the steps below:

1. Pull the last three calibration certificates for your highest-use pipettes.
Check each one for as-found and as-left measurement data, measurement uncertainty, reference standard identifiers, and a documented traceability chain. If any of those elements are missing, the certificate doesn't meet the standard for regulated environments.

2. Review your calibration SOP.
Confirm that it specifies the calibration interval, the written rationale for that interval, and the criteria that would trigger a review. Confirm it also includes a documented list of out-of-cycle recalibration triggers and the procedure for handling each one.

3. Verify your provider's accreditation scope.
Look up your current provider in the A2LA or NVLAP directory to confirm that pipette calibration is explicitly listed in the scope and that ISO 8655 is referenced as the applicable method.

4. Check your traceability documentation.
For each certificate you reviewed, confirm that the traceability chain is documented and not just assumed. A statement of NIST traceability without supporting reference standard data is not sufficient.

Frequently Asked Questions

Close Your Compliance Gaps Before the Next Audit

The five gaps above are the ones auditors find most often — and the ones that are most preventable with the right documentation and provider in place.

Talk to Accredited Labs about ISO/IEC 17025 accredited pipette calibration →

A Checklist Makes the Review Process Faster

For quality managers who want a more structured approach, the Pipette Calibration Compliance Guide formalizes this process into a downloadable checklist built around the documentation requirements auditors actually look for.