EQQ has long served environmental and compliance labs that need to produce the same regulatory cut every reporting period - identically, defensibly, and on a deadline. Here is the typical configuration we see.

Base configuration for a compliant EQQ deployment

  • One database scope per LIMS instance.
  • Roles: Chemist (read), QA (review + export), Compliance Officer (read + audit).
  • Queries authored by a senior chemist; reviewed by QA; flipped to Active only after sign-off.

What the EQQ audit trail captures for regulatory review

For each reporting period, a compliance officer runs the standard query suite. EQQ writes an audit record for every execution, capturing the user who ran it, the query name and version, the parameters supplied, the row count returned, and the elapsed time. If a regulator asks “how did you produce this number?”, the answer is: “query version X, executed by user Y at time Z, with parameters P.” The output file goes to a read-only archive, and the audit entry timestamps it — so the record and the result are traceable to each other without manual documentation.

Audit log: every run captured with user, query, parameters, timing.
Audit log: every run captured with user, query, parameters, timing.

Standardize MDL calculations once, reuse across every lab method

Labs routinely need to join sample data with method metadata to produce MDL / LOQ reports. EQQ's Function library lets you standardize the MDL calculation once and reuse across every method in the lab.

Immutable query lifecycle gives you defensible chain of custody

Because queries are immutable once Active (transitioning to Inactive or Void creates a new audit record), the number you reported last year is reproducible this year - a non-trivial property.