NEQS monitoring: turning a logbook into something that can answer a question

An environment department at a plant takes the same readings every day — stacks, effluent outfalls, ambient stations, cooling water. Several hundred of them. Written into a logbook they prove that the readings were taken and almost nothing else.

Nobody trends them. A breach is noticed days later if at all. And the evidence pack for an audit gets assembled the week the auditor is due, from paper.

The limit check belongs at entry

This is the single change that matters. A reading checked against its permitted limit at the moment it is entered cannot be filed quietly. A reading checked at month end has already been filed, and the conversation is now about why nobody noticed.

National Environmental Quality Standards set limits by parameter, and a plant typically has its own tighter internal thresholds as well. Both should be held against the sampling point so the check happens automatically, rather than depending on the person entering the figure knowing the limit by heart.

A breach should raise something, not just colour a cell

When a value exceeds its limit, a non-conformance should open against the machine, the point and the shift that recorded it — routed for root cause, corrective action and verified closure.

The reason to automate this is not elegance. It is that a breach noticed informally gets handled informally, and three months later nobody can demonstrate what was done about it. The record of the response is as important as the record of the breach.

Capture at the point, not afterwards

Readings copied from a notepad into a system at the end of a round lose the one thing that makes them defensible: the time and place they were actually taken.

Capture on a handheld at the sampling point, working offline because plants have dead spots, with the point identified by scanning rather than selected from a list. Selecting from a list is how readings end up against the wrong stack.

The instrument has to be valid

A reading is only as good as the device that produced it. If the meter is past its calibration date, the result is open to challenge, and so is every other result taken on it since.

Holding instrument calibration in the same system as the readings — and refusing a result from an overdue device — closes that gap at the point it would otherwise open.

What an audit should cost you

ISO 14001, 45001 and 17025 evidence is the same data viewed differently. If it is captured properly once, the audit pack is a report rather than a project.

The test is whether you can produce, on request: every reading for a given parameter and point over a period, with the instrument and analyst; every exceedance and what was done about it; and the calibration status of each device across that period. If those take a week to assemble, the data exists but the system does not.

Common questions