QA/QC Workflows for Environmental Labs: How to Evaluate a Configurable LIMS

Environmental laboratories do not need a generic promise that a LIMS “automates QC.” They need to know whether the system can represent the rules governing a specific method, matrix, analyte group, project, and reporting use—and whether authorized staff can review and change that configuration responsibly.

EPA’s Quality Assurance Project Plan Standard makes the project-specific nature of this work clear. For covered work, a QAPP identifies performance and acceptance criteria for analytical methods by matrix, analyte or analyte group, and concentration level. It also identifies the method and version and describes what happens after an analytical failure, who owns corrective action, and how effectiveness is documented.

That is the right shape for a software evaluation: begin with approved requirements, then test whether the workflow carries them from batch setup through review and disposition. Do not begin by adopting a vendor’s default list of QC types or limits.

Build a governing-rule packet first

Choose one routine workflow and one difficult variation. Assemble a sanitized packet containing the approved method reference, relevant project or program requirements, laboratory SOP, QC definitions, formulas, frequencies, acceptance criteria, review roles, qualifiers, and exception procedure.

Record the source and version for every rule. Where a method permits options, identify the option the laboratory approved. Where project requirements supplement a routine workflow, mark the difference explicitly.

The examples below—blanks, laboratory control samples, spikes, and duplicates—illustrate an evaluation approach. They are not a universal prescription. Derive required QC types, frequency, calculations, limits, and responses from the documents governing the work.

Test configuration at the right level

A useful configuration model can distinguish rules that vary by laboratory location; program, client, project, or contract; method and revision; matrix and preparation process; analyte or analyte group; concentration range; batch type; and effective date.

Ask the vendor to show how conflicts are resolved. If a project criterion differs from a routine criterion, which one appears to the analyst? Can a reviewer see why it applied? Does a historical batch retain the rule set used when it was processed, or does it change after a later edit?

A configurable system is not automatically a controlled system. Document who may draft, test, approve, activate, retire, and review a rule. Include an effective date and a traceable relationship to the governing document.

Evaluate batch assembly without assuming one model

The lab should define what constitutes a preparation batch, analytical batch, sequence, workgroup, or other grouping under the applicable method. Test whether the proposed system preserves those relationships.

Use routine samples, required QC, a re-preparation, and a reanalysis. Confirm that the system distinguishes original from repeated work and maintains the relationship between samples and the QC used to evaluate them.

EPA SW-846 Chapter One describes different purposes for common QC elements. A laboratory control sample assesses general method performance, a matrix spike assesses interference from a particular sample matrix, duplicates help evaluate precision, and a method blank assesses background interference or contamination. It also says duplicate frequency depends on project requirements and points users to the QAPP or method for some frequencies. A demo should therefore test the lab’s selected rules, not a universal template.

Separate calculations, flags, and decisions

These are different functions:

1. Calculation transforms inputs into a recovery, difference, ratio, control value, or other metric using an approved formula.
2. Flagging compares the result with an applicable criterion and makes the condition visible.
3. Disposition records an authorized decision about affected work, including qualification, rework, rejection, release, or escalation allowed by the governing procedure.

Ask the vendor to trace each step. Inspect units, rounding, significant figures, treatment of non-detects, missing values, dilutions, and edited inputs. Independently calculate one passing and one failing example.

Then test whether a flag is informative or controlling. A red icon does not determine data usability. The workflow should route the condition to the role authorized by the lab’s procedure and preserve the rationale, affected scope, action, and review.

Run a failure through closure

Create a sanitized failure scenario that matters to the selected method. Do not stop when the dashboard turns red. Continue through the path defined by the lab:

• identify the failed criterion and source rule;
• place affected samples or results in the proper state;
• assign an investigation or response;
• document observations and evidence;
• identify the affected scope;
• record the authorized disposition;
• perform approved repeat work;
• review the outcome; and
• document the effectiveness check when required.

The EPA QAPP Standard addresses analytical-system failure, corrective-action responsibility, and effectiveness documentation for covered projects. Your lab’s steps must come from current procedures and governing documents; the LIMS should represent them without inventing the scientific decision.

Test one failure affecting only part of a batch and one unresolved condition discovered after initial review. These reveal whether the system can manage scope and reopen work without erasing prior decisions.

Inspect review and reporting context

A reviewer should see sample results, associated QC, applied criteria, calculations, flags, exceptions, repeated work, and prior decisions in context. Ask what is visible at analyst review, technical review, quality review, and report authorization under your role model.

Generate the proposed output. Confirm how qualifiers, narratives, omitted results, and exception references are produced. Compare it with the project and program requirements in your packet. A report template should not silently turn a workflow flag into a regulatory conclusion.

Test rule change control

Change one criterion in a test environment. Require the vendor to show the proposed rule, reason, source document, test evidence, approval, effective date, and activation. Reopen an older batch and confirm that its historical evaluation remains intelligible.

Also test a method revision. Can the lab run old and new versions during a controlled transition? Can staff tell which version applies before work begins? Can retired rules be blocked from new use while remaining available for reconstruction?

Score the workflow with evidence

Classify each capability as standard, configured, custom, external, or unavailable. Include the people and work needed to maintain methods and rules after go-live. The best fit is the workflow your laboratory can govern, explain, and test—not the one with the most preloaded acronyms.

Evaluate one QA/QC workflow with Clearline

If configurable QC is your current selection question, schedule a Clearline LIMS evaluation with one sanitized rule packet and failure scenario. Ask for rule precedence, batch relationships, calculations, exception closure, review context, and method-version change control to be addressed in the written scope.

Sources

• U.S. EPA — Quality Assurance Project Plan Standard, CIO 2105-S-02.1 (2024)
• U.S. EPA — SW-846 Chapter One: Project Quality Assurance and Quality Control, Revision 2
• The NELAC Institute — 2016 TNI Laboratory Accreditation Standard summary