A surface result from last March comes up in a trend review. It was above the alert level, not by much. The reviewer has a simple question: does it matter?
Answering it turns out not to be simple. The point it came from was moved in June when the line was reconfigured, so the floor plan now shows it somewhere else. The room was regraded in the summer, and the current room list shows the new classification. The schedule for that quarter was replaced by the next one. There may have been a photo of the site, but if there was, it's in a shared folder sorted by date, and nobody is sure which day to look under.
An environmental monitoring result can only be interpreted with its context: where the sample was taken, the area's classification at the time, the schedule it belonged to, the method used and any evidence captured. That context is usually lost through routine changes to layouts, classifications and schedules, not through error.
What context does a monitoring result depend on?
An environmental monitoring result is a measurement taken at one place, at one moment, under one set of conditions. Without those conditions it's just a number. To read it properly, you need to know where the sample was taken, what classification the area had and therefore which limits applied, whether it was a routine sample or one taken after an intervention, which method was used and what the technician saw or photographed at the time.
On the day of sampling, all of that is easy to find, because it's all current. The trouble is that most systems, whether paper or software, are built to show the current state of things. Update the floor plan and the old position disappears. Edit the room's classification and the old grade is gone. Every change is correct for today and quietly misleading about yesterday.
Some context can wait, some can't
It helps to sort the context a result depends on by how likely it is to change.
Some of it barely moves. The lab that ran the test, the method definition, the name of the technician: you can look these up later and get the right answer.
Some of it moves regularly. Sampling point positions shift with layout changes, rooms get reclassified, schedules get reissued. For anything in this category, you need one of two things. Either the value at the time of sampling is recorded with the result, or the place that holds it keeps a dated history you can query. If neither is true, the context is lost the first time it changes, and nobody notices until a review like the one above.
Evidence is its own case. A photo of a sampling site, a note about condensation on a wall, a PDF from an outside lab: these exist only from the moment they're created. If they're attached to the result then, they're simply there. If they're filed somewhere else, someone has to reconnect them later, and that gets harder every week. We cover practical ways to handle this in capturing monitoring evidence with a phone.
A good way to test any setup is to pick a result from a year ago and try to answer four questions without asking anyone who was there. Where was the point when this was taken? What classification applied? Which schedule was it part of? What evidence exists from that day? If any answer requires a phone call, that's the gap.
Can environmental monitoring software preserve this context?
Structured records remove most of the detective work. When a result is created from a scheduled event at a defined point, its connection to that point and that schedule exists from the moment it's recorded. When a photo is attached at sampling time, no one has to find it later.
What software won't do is make decisions for you. If a point moves a meter, is it the same location for trending, or a new one? That's a judgment for the program, not the tool, and it's one reason to record why each point exists when designing the monitoring plan. It's also worth checking, in whatever system you use, what actually happens to older results when a point moves or a room is regraded, rather than assuming the history survives.
In Uncountable, sampling points sit on their area's site map with a code and position, plans generate the scheduled events and their lab requests, and technicians can attach photos and files from a phone to the record at the time of sampling.
.png)
.png)
.png)
