A mine-water report may contain a clean table of concentrations, units and limits. But that table is only the end of the process. If a reviewer cannot trace a value back to the monitoring point, field event, sample, method, analytical batch, quality controls and approval history, the result cannot be reviewed in its full context.
Consider a reported arsenic result. The value alone does not establish whether the sample came from a fixed groundwater well, a surface-water station, a process circuit or an unscheduled investigation. It does not show whether the result was total or dissolved, which preservation was specified and recorded, which method and reporting limit applied, or whether the value is preliminary, approved or revised.
For mining laboratories, performing the analysis is only part of the job. The record behind the result must also be retrievable without relying on disconnected spreadsheets, email threads or personal memory.
One value can describe different events
A concentration only becomes meaningful when it remains attached to its context. That context can include:
- the authorised monitoring-point identifier and location;
- the type of water and the programme under which it was collected;
- the sampling date and time, field observations and responsible personnel;
- the requested fraction, method, unit and reporting basis;
- the detection or reporting limit in force for that method;
- the analytical batch and instrument run;
- the controls used to assess the batch; and
- the result status and any later revision.
A seasonal surface-water result should not be treated as if it were a routine groundwater result. A dissolved-metals result should not be compared casually with a total-metals result. A value reported below a method-specific limit should not be stripped of that limit when transferred to another system.
None of these distinctions is cosmetic. They determine what the result actually says and what it does not say.
The laboratory receives a sample, not the aquifer
The laboratory cannot reconstruct field conditions that were never recorded. It receives a container, an identifier, a request and the information supplied with the sample. The representativeness of that sample depends on decisions and work performed before laboratory receipt.
This is why responsibilities need to remain separate:
- Programme design determines where, when and how often sampling takes place.
- Field execution covers collection, field measurements, preservation, identification, sealing, custody and transport.
- Analytical evidence covers receipt, preparation, analysis, QA/QC, technical review, approval and reporting.
- Interpretation and compliance compare the authorised result with the applicable permit, baseline, hydrogeological model and jurisdictional criteria.
A laboratory information management system can strengthen the third layer and preserve continuity into the fourth. It does not design the monitoring network, prove that a sample represents an entire water body, assign causality or make a regulatory determination on its own.
The minimum evidence chain
The exact records depend on the programme, method and jurisdiction. A laboratory record that can support technical review typically relies on the following connections:
| Evidence layer | Records that should remain connected |
|---|---|
| Monitoring point | Authorised code, location, point type and associated programme |
| Field event | Date and time, sampler, observations, field measurements and applicable procedure |
| Sample | Unique identity, container, preservation, seal, custody transfers and receipt condition |
| Analytical request | Required analytes, fractions, methods, units and reporting limits |
| Preparation and analysis | Preparation steps, method version, instrument, run and raw-data reference |
| QA/QC | Blanks, duplicates, spikes, certified reference materials and other controls required by the method or laboratory plan |
| Technical review | Exceptions, reruns, dilutions, comments, acceptance decision and approver |
| Publication | Authorised version, recipient, export event and revision history |
The point is not to collect every possible field indiscriminately. It is to preserve the records needed to evaluate sample identity, the basis of the analysis and the status of the result.
ISO 5667-11 addresses groundwater sampling. ISO 5667-22 addresses the design and installation of groundwater monitoring points. These are different activities, and neither should be collapsed into laboratory processing. For laboratory competence, ISO/IEC 17025 provides the broader requirements for competent, impartial and consistent laboratory operation.
What to investigate when a result changes
When a new value differs from the historical pattern, the investigation should preserve several hypotheses rather than jumping directly to a site conclusion.
Start with identity. Confirm the monitoring point, event, sample and requested fraction. Then review field notes, preservation, transport and receipt condition. Within the laboratory, inspect the analytical batch, blanks, duplicates, reference materials, calibration information, dilutions and reruns. Confirm which method version and reporting limit applied, and whether the result was pending, approved or subsequently revised.
Only after that evidence has been reviewed should the authorised result be assessed against the correct programme, permit, baseline and site interpretation framework.
This sequence matters because an unusual result can arise from different causes: a real environmental change, a field problem, a custody error, matrix interference, contamination, transcription, an unsuitable comparison basis or a legitimate analytical result that requires site-level interpretation. A LIMS does not decide which explanation is true. It should make the evidence required for that investigation available and attributable.
Where OnLIMS fits
OnLIMS is designed to maintain laboratory continuity from sample receipt to approved reporting. In a mine-water workflow, that can include:
- registering routine samples from fixed monitoring points and finite campaign samples under controlled identities;
- maintaining the sample lifecycle and laboratory status;
- connecting methods, instrument outputs and results to the analytical work;
- importing compatible instrument output rather than retyping result files;
- associating QA/QC records with the relevant analytical batch;
- recording review, approval, comments, exceptions and authorised changes; and
- producing controlled outputs for downstream environmental or corporate systems, according to the configured workflow.
This extends the instrument-focused workflow described in Environmental Water Monitoring in Mining. Related OnLIMS capabilities are described in Mining Laboratory LIMS, Sample Tracking and Chain of Custody, QA/QC for Mining Laboratories and Laboratory Instrument Integration.
The value is operational: a reviewer should be able to move from a published result back through approval, QA/QC, analytical work, sample receipt and the supplied field identity without rebuilding the record manually.
The product boundary must remain explicit
OnLIMS does not replace:
- hydrogeological programme design;
- selection of monitoring locations or frequencies;
- field sampling procedures and professional judgement;
- site-wide assessment of representativeness;
- environmental modelling or causal interpretation; or
- compliance decisions under a permit or jurisdiction.
The system manages laboratory evidence and controlled data continuity. The mine, its environmental specialists and the authorised laboratory remain responsible for the decisions and professional work outside that boundary.
A result is stronger when its history survives
Mining water programmes may run for years and pass through different field teams, laboratories, instruments and reporting systems. The result table is not enough to preserve that continuity.
A useful long-term record keeps the monitoring-point identity, custody, analytical work, quality controls, approval and publication history connected. When an anomaly appears or a regulator asks for support, the laboratory can retrieve the evidence behind the number instead of reconstructing it after the fact.
For laboratories reviewing mine-water workflows, the useful starting point is simple: select one reported result and trace it backwards. If any step depends on an uncontrolled spreadsheet, an email attachment or one person's memory, that step is a data-integrity risk worth addressing.
Discuss a mine-water laboratory workflow with OnLIMS
Primary references
- International Organization for Standardization. ISO 5667-11:2009, Water quality — Sampling — Part 11: Guidance on sampling of groundwaters.
- International Organization for Standardization. ISO 5667-22:2010, Water quality — Sampling — Part 22: Guidance on the design and installation of groundwater monitoring points.
- International Organization for Standardization. ISO/IEC 17025:2017, General requirements for the competence of testing and calibration laboratories.