When Your Reporting Limit Exceeds the MCL: How to Handle Non-Detects Above Regulatory Standards

You get results back from the lab. Benzene is non-detect with a U qualifier. Your VLOOKUP says the MCL for benzene is 5 ug/L. The result is "<5 ug/L." Compliant, right?

Not necessarily. Look at the reporting limit. If the lab reported a RL of 5 ug/L and the MCL is 5 ug/L, you have a problem. The true concentration could be anywhere from zero to just below 5 ug/L. You cannot confirm compliance because the analytical method was not sensitive enough to distinguish between compliant and non-compliant concentrations.

This is the detection limit adequacy problem — and it is one of the most commonly missed issues in compliance reporting at small firms. Your Excel VLOOKUP sees "non-detect" and moves on. A regulator reviewing your report will not.

Laboratories report multiple detection thresholds, and understanding the hierarchy is essential for compliance work.

The Method Detection Limit (MDL) is the lowest concentration that can be distinguished from zero with 99% confidence. It is a statistical determination specific to the lab, the instrument, and the matrix. The MDL is the floor — anything below it is analytically indistinguishable from noise.

The Practical Quantitation Limit (PQL) is typically 3-10 times the MDL. It represents the lowest concentration the lab can reliably quantify with acceptable precision and accuracy. Results between the MDL and PQL are detected but estimated — they receive a J qualifier.

The Reporting Limit (RL) is the concentration the lab reports as the threshold for a non-detect. For routine commercial lab work, the RL is usually set at the PQL. But for samples with matrix interference, high dissolved solids, or dilutions, the RL can be elevated significantly above the standard PQL.

When we talk about detection limit adequacy, we are comparing the RL to the applicable standard. If the RL is at or above the standard, the non-detect result cannot confirm compliance.

Detection limit inadequacy is not a theoretical concern. It occurs routinely in environmental consulting work:

**PFAS at parts-per-trillion levels.** EPA MCLs for PFOA and PFOS are 4 ppt (ng/L). Many commercial labs have method reporting limits of 2-4 ppt for some PFAS compounds. If matrix effects or dilution raise the RL to 5 or 10 ppt, you cannot confirm compliance with a non-detect. With PFAS compliance monitoring ramping up through 2027-2031, this will become the most common detection limit adequacy issue in environmental consulting.

**Metals in high-TDS matrices.** Groundwater from coastal or industrial sites often has high total dissolved solids. Matrix interference forces the lab to dilute the sample, raising all detection limits proportionally. If a 10x dilution raises the arsenic RL from 1 ug/L to 10 ug/L, and the MCL is 10 ug/L, your non-detect does not confirm compliance.

**State standards more stringent than federal.** New Jersey's arsenic MCL is 5 ug/L versus the federal 10 ug/L. A lab reporting arsenic ND at <10 ug/L satisfies the federal MCL but tells you nothing about compliance with the NJ standard. If you are screening against state standards (as you should be), the detection limit must be evaluated against the state standard, not the federal one.

**VOCs in soil gas or low-flow groundwater samples.** Volatile organic compounds at low concentrations can have elevated RLs depending on sample collection and preservation. TCE has a federal MCL of 5 ug/L — an RL of 5 ug/L from a matrix-affected sample creates an adequacy problem.

**RSLs for residential tap water.** EPA RSLs for many contaminants are lower than MCLs because they incorporate additional exposure pathways and risk factors. A non-detect that clears the MCL may not clear the applicable RSL.

When you identify detection limit adequacy issues, they need to appear in your compliance report in three places:

**In the exceedance/screening table itself.** The result should not be classified as "compliant" or "exceedance." It should have a distinct classification: "Non-Detect — Cannot Determine Compliance" or "ND — Detection Limit Exceeds Standard." Use a visual indicator distinct from both compliant (green) and exceedance (red) — yellow or hatching works well. Include the RL, the applicable standard, and the gap between them.

**In a dedicated Detection Limit Adequacy table.** List every analyte/location/event combination where the RL exceeds any applicable standard. Columns should include: Location, Sample ID, Analyte, RL, RL Units, Applicable Standard, Standard Value, Standard Source, and Gap (RL minus Standard). This table allows the reviewer — your PM, your client, or the regulatory agency — to see the full scope of the issue at a glance.

**In the compliance narrative.** The text accompanying your tables should explicitly state: 'For X analyte-location combinations, the laboratory reporting limit exceeded the applicable standard. Compliance cannot be confirmed from these results. [Recommendation: request re-analysis with lower detection limits / note that the lab has been contacted regarding improved detection limits for future sampling events / discuss with the regulatory agency regarding data adequacy.]'

The recommendation depends on the project context. For an ongoing monitoring program, you can request the lab lower detection limits for the next round. For a one-time investigation, you may need re-analysis of the existing samples (if holding times have not expired). In some cases, you document the limitation and let the regulatory agency determine whether additional data is needed.

The best practice is to prevent RL-above-standard situations before samples go to the lab:

**Specify required detection limits on your chain of custody.** When you submit samples, include a table of target analytes with the required RL for each — set at least 2x below the most stringent applicable standard. Most commercial labs can meet specific RL requests if told in advance.

**Request low-level methods when needed.** For PFAS, specify EPA Method 533 or 537.1 with isotope dilution and request RLs at or below 2 ppt. For metals at low standards (arsenic at 5 ug/L in NJ), request EPA Method 200.8 with appropriate dilution controls.

**Review the lab's standard RL list before selecting a lab.** Most labs publish their standard method detection limits. Compare these against your project's applicable standards before committing. A lab with a standard arsenic RL of 10 ug/L is not suitable for a New Jersey drinking water compliance project.

**Flag matrix-affected samples early.** If you know a location has high TDS, high turbidity, or other matrix challenges, discuss sample preparation options with the lab before sample collection. Pre-treatment, matrix spike studies, or alternative methods can keep RLs below standards.

**Track detection limits across sampling events.** If a lab's RLs are creeping upward over time, address it before it creates a pattern of inadequate data in your compliance record.

Purpose-built compliance reporting tools can automate detection limit adequacy checking — comparing every non-detect RL against every applicable standard, flagging inadequacies, and generating the dedicated summary tables described above. This eliminates the most common failure mode: the Excel VLOOKUP that reports "non-detect = compliant" without evaluating the RL.

But software cannot replace professional judgment in how you respond to detection limit inadequacy. Whether to request re-analysis, accept the limitation, or recommend additional sampling depends on the regulatory context, the project objectives, the client relationship, and the specific contaminant's health risk. A tool can surface the problem; a licensed professional decides what to do about it.

The goal is not to eliminate the consultant's role. It is to ensure the detection limit adequacy question is asked for every non-detect result, every time — because the one you miss is the one a regulator finds.