How Analytical Labs Run Proficiency Testing in a LIMS

Analytical labs run proficiency testing programs out of a LIMS by treating every PT round as a tracked sample with its own due date, assigned analyst, and result record — not as an email thread with a spreadsheet attached. Proficiency testing (PT) is an interlaboratory comparison where an accreditation-recognized provider sends you a sample of known value and scores your answer. Handled inside the LIMS, PT stops being an annual scramble and becomes a dated, auditable trail an assessor can follow.

A LIMS supports proficiency testing by scheduling each round, routing the PT sample through the same chain of custody and result-entry path as client work, storing the provider's report against that record, and linking any outlier to a documented corrective action. The goal isn't a better score. It's being able to prove, on demand, what you did about the score you got.

Why ISO 17025 labs run proficiency testing at all

ISO/IEC 17025 asks labs to monitor the validity of their results, and names interlaboratory comparison — proficiency testing being the common form — as one of the ways to do it. Accreditation bodies turn that into a schedule. A2LA, the TNI/NELAP programs behind environmental accreditation, and most state cannabis regulators each publish how often you must participate per method and matrix.

The scoring is usually a z-score: how far your result sits from the assigned value, in standard deviations. Inside ±2 is acceptable, ±2 to ±3 is a warning, beyond ±3 is a fail. Simple enough on paper.

What assessors actually examine is rarely the z-score. It's the paper trail behind a bad one.

Where PT programs break

Four failure modes show up again and again, and none of them are about analytical skill.

That last one is the easiest to fix and the most common finding.

How to set up a PT round in your LIMS

The setup that holds up under assessment is unglamorous:

  1. Register the PT sample like any other sample, with its matrix, its methods, and the provider's reporting deadline as the due date.
  2. Route it through the routine workflow — the same preparation steps, the same instrument queue, the same review gate your client samples pass through.
  3. Capture analyst and instrument automatically, so the record answers "who ran this, on what" without anyone remembering.
  4. Enter results against the method's normal acceptance path, not a side spreadsheet.
  5. Attach the provider's score report to that same record when it arrives, typically weeks later.
  6. Open a nonconformance for anything outside the acceptance window, and keep it open until the corrective action is written, approved, and verified.

Treat the PT sample like a client sample — that's the whole trick

Everything else follows from step two. A lab running configurable sample types and workflows in Confident can define a PT sample type that inherits the routine route rather than bypassing it, which means the round tests the process you actually use. The audit trail then records every entry, edit, and approval against that sample without anyone maintaining a separate log.

Labs on Confident process more than 5M samples a year, and the ones getting real value from PT share a habit: when a round comes back poor, they pull the same method's internal QC over the same weeks and ask whether the miss was a one-off or a drift they'd been quietly tolerating. That comparison is only cheap when both sets of results sit in the same system.

Turning PT results into a trend

One round is a data point. Four rounds across two analysts and two matrices is information.

Track outcomes by method, by matrix, and by analyst, and the pattern usually names itself — a single technique that slips at low concentrations, a matrix that nobody has refreshed the extraction for, a new hire whose results are fine but whose documentation is not. Labs that review PT alongside internal control charts quarterly catch these before the next round, rather than after it.

What assessors ask to see

Expect requests for the PT schedule by method and matrix, evidence of participation for the current cycle, the raw data behind each submitted result, the provider's score report, and — for any flagged result — the investigation, the corrective action, and the evidence it worked. Five documents. Labs that keep them in one system produce them on request; labs that don't spend days reconstructing them.

Frequently asked questions

How often do analytical labs need to participate in proficiency testing?

It depends on your accreditation body and the method. Many environmental and cannabis programs expect two rounds per year for each method and matrix on your scope of accreditation; some require one. Check the specific program rather than assuming a general rule, and record the required frequency against each method in your LIMS so the schedule maintains itself.

What happens if a lab fails a proficiency test round?

A single unacceptable result rarely costs accreditation on its own. Repeated failures in the same method, or a failure with no documented investigation behind it, is a different matter. Most programs expect an investigation, a corrective action, and often a successful follow-up round before the method is considered back in good standing.

Can internal QC replace proficiency testing?

No. Internal quality control tells you whether your method is behaving consistently against your own reference materials. Proficiency testing tells you whether your answer agrees with everyone else's. A lab can be perfectly precise and consistently wrong, and only the external comparison catches that.

Does a LIMS submit PT results to the provider directly?

Submission usually happens on the provider's own portal, in their format and on their deadline. What the LIMS should own is everything either side of that: the scheduling, the raw data, the reviewed result you transcribe, the returned score report, and the follow-up. Treat the portal as the last step, not the system of record.

How long should proficiency testing records be kept?

Match your retention policy for technical records under ISO 17025 and any program-specific requirement, which commonly runs several years. Keeping PT records in the same system as the sample data they came from means one retention rule covers both.

Putting it to work

Pick the next PT round on your calendar and ask one question: if an assessor asked today for the raw data, the score, and the corrective action behind it, how many places would you look? The labs that answer "one" built that answer long before the round arrived.

Confident supports environmental, cannabis, and food and beverage labs that need proficiency testing rounds, chain-of-custody records, and corrective-action tracking to live in one place rather than three. To see how it handles your own accreditation program's schedule, See How It Works.