A Well Logger Chart Drops During a Storm: Ask Which Corrections the Report Includes

Answer first: obtain the chart definition before approving a repair

If a professionally supplied private-well logger chart appears to show a sudden water-level change, ask what quantity is plotted, which sensor produced it and which atmospheric and reference corrections were applied. A non-vented pressure record is not automatically a finished depth-to-water report. The provider should explain the processed series before it becomes the reason to lower a pump, deepen a well or replace equipment.

This guide reviews a report already supplied by a professional. It does not install a logger, open a well or calculate corrections. A storm occurring near a plotted change can be useful context, but it does not prove that the change is an artifact or that the well level actually fell. Keep the raw observation, processing history and professional interpretation separate until the relevant evidence supports a conclusion.

Identify the sensor and the plotted quantity

Ask the report provider to name the logger and describe its measurement principle, actual channel and units. A pressure series, sensor-depth series, elevation and depth below a reference point answer different questions. Retain the original axis labels and report version rather than copying a line into a new chart and renaming it water level. A visually convincing trend still needs a defined quantity to support a property decision.

For the named HOBO U20/U20L example, Onset’s guide distinguishes a resulting series with a reference water level from one representing absolute sensor depth without that reference. Solinst’s Data Wizard discussion likewise distinguishes barometric compensation from manual reference adjustments and other parameter changes. These examples explain the questions to ask; they do not establish what was done to a particular report or supply universal software instructions.

Ask how atmospheric information was matched

For a non-vented pressure-based record, have the professional explain the relevant atmospheric compensation and identify the source and time coverage of the accompanying information. Keep whether compensation was applied explicit. Onset’s selected guide discusses an atmospheric series overlapping the water-pressure period and distinguishes that option from a fixed-pressure input. An unexplained constant or an unrelated record should prompt a question about the intended analysis, not an owner-created adjustment.

Ask the provider to state any gaps, timing uncertainty or assumption affecting the corrected result. A chart covering a long interval can conceal the fact that supporting information is shorter or differently timed. This article gives no subtraction formula, atmospheric source selection or interpolation method. The professional must determine what is appropriate for the actual sensor, installation and question, and explain the limitations in the report.

Preserve the reference observation and direction

Ask which documented reference anchors the reported level, when the relevant observation was obtained and how it relates to the logged record. A depth below a casing point and an elevation above another datum can move in opposite numerical directions for the same physical change. The provider should explain that convention clearly. Do not reverse a chart axis or change a sign merely to make a line look more intuitive.

The changed static-level guide covers comparable reference points, rest and pumping conditions for conventional water-level records. A logger adds processing provenance to those questions. Even a properly compensated series may describe pumping or recovery rather than a resting condition. Ask how known household use and the measurement purpose were accounted for before comparing it with a static level on an old construction report.

Request a processing summary another reviewer can follow

Keep the provider’s explanation beside the actual chart and source file identity. A processed graph should not replace the original record without a trace of what changed. Ask which operations were applied and which were not, preserving the sequence and the final series name. If a report is revised, keep both versions and the reason for revision rather than silently overwriting the figure used in a repair discussion.

Pressure-logger interpretation needs provenance as well as a line
Field	Evidence to request	Unsupported conclusion
Sensor/channel	Actual logger, measurement type and units	Every channel is depth to groundwater
Atmospheric correction	Source, overlap and processing status	Storm timing proves a measurement artifact
Reference	Point, observation time and direction convention	Another report uses the same datum
Other parameters	Actual density/unit/reference adjustments and limits	Any unexplained offset is harmless
Operating context	Pumping, recovery and known data gaps	The entire record is static level
Professional finding	Corrected interpretation and uncertainty	A graph alone justifies pump lowering

Keep other adjustments distinct from barometric compensation

Solinst describes manual data and parameter adjustments separately from the basic atmospheric-compensation function. Those distinctions matter when a report combines several processing steps. Ask whether units, density, reference or another applicable parameter changed, and request the provider’s basis for each. A label saying corrected is incomplete if it does not explain which correction was performed and what remaining assumptions affect the result.

Do not enter an arbitrary offset to align two plots or use a neighboring owner’s correction value. Nor should old software menus be treated as a current universal workflow. The Onset document is 10572-J, copyright 2008-2017, and concerns its specified software and logger family. This guide uses its processing concepts without instructing a homeowner to operate the software, obtain paid tools or reinterpret the professional dataset independently.

Require the report finding to support the actual proposed change

If the provider proposes lowering a pump or another physical alteration, ask how the defined corrected record supports that scope together with the well construction and equipment findings. A level trend does not alone establish the suitable pump position, sustained yield or need for deeper drilling. Keep any separate flow, construction and pump assessment identified by its own purpose and limitations. No design calculation is provided here.

Likewise, a level chart is not a drinking-water laboratory result. A plausible explanation for a plotted change does not resolve contamination concerns, and a satisfactory water sample does not validate logger processing. Use the appropriate well and water professionals for their actual questions. If household supply is unstable or another hazard develops, obtain a prompt matched response instead of waiting for a more attractive chart to settle an immediate need.

Illustrative scenario: a storm and a pump-lowering quote

Imagine a homeowner receives a logger plot with an apparent decline near a storm and a proposal to lower the pump. This is an illustrative scenario, not measurements we collected. Before approving the change, the owner requests the sensor identity, plotted quantity, atmospheric record, reference and professional corrected interpretation. No well cap is opened and no household formula is used to decide whether the line is real.

The provider explains the processing and any remaining uncertainty, then connects actual findings to the proposed scope. The result may support more assessment rather than an immediate alteration. The example promises no cause or repair outcome. Its useful result is that the chart’s definition and provenance become reviewable before a consequential well change is authorized.

Frequently asked questions

Is every pressure plot finished water-level data? No. Does storm timing prove an artifact? No. Are depth and elevation interchangeable labels? No. Can a fixed offset settle a mismatch? Obtain the professional basis. Does a corrected plot establish yield or drinking safety? No. Should I open the well to check it? No owner field procedure is supplied. What should the report retain? Sensor, units, atmospheric/reference processing, operating context, version and explained limitations.