Water quality reports: identifying data gaps in fluoride disclosure

A Consumer Confidence Report (CCR) is a useful starting point for identifying fluoride levels in local water reports, but its summary format may not show when or where concentrations changed.

For readers assessing municipal water quality report fluoride disclosure accuracy, the central task is to distinguish three things: the concentration reported, the period and locations it represents, and whether the fluoride is naturally occurring or added during treatment. Federal rules set reporting duties and regulatory limits, but a CCR does not necessarily provide the time resolution needed to reconstruct day-to-day operating conditions.

Decoding the Consumer Confidence Report: beyond the annual average

Under the Safe Drinking Water Act, community water systems serving at least 25 year-round residents must distribute an annual CCR by July 1. The report covers detected contaminants from the prior calendar year. It is designed to communicate water-quality information to customers, including results relevant to regulatory standards.

That purpose matters when interpreting what is absent. A CCR is an annual public summary, not a real-time record of every sample collected across a distribution network. Fluoride may appear as an annual average, a range, or a result associated with a particular sampling arrangement. Those formats can establish a broad picture while leaving the timing and location of individual measurements unclear.

The first step is to locate the fluoride entry and read its units. Concentration is commonly expressed in milligrams per liter (mg/L). Then identify the reported statistic: an average is not interchangeable with a maximum, minimum, or detection range. If the report gives only one figure, the reader should not assume it represents every part of the service area or every day of the year.

A focused reading can record the following:

• Reporting period: Confirm that the result refers to the previous calendar year and note the report’s issue date.
• Statistic shown: Record whether the number is an annual average, a range, or a single sample result.
• Sampling context: Look for the number of samples, sampling locations, and any explanation of where measurements were taken.
• Units and benchmark: Check that the concentration is in mg/L and identify the standard or target listed beside it.
• Source description: Look for language distinguishing naturally occurring fluoride from fluoride added during treatment.

This is a reading protocol, not a compliance determination. A report that presents an annual average without monthly detail is not, on that fact alone, evidence of a federal reporting violation. The format may simply be too aggregated to answer a more specific question about operational variation.

An annual average describes a period. It does not show the sequence of concentrations that produced it.

That distinction is especially relevant in systems drawing from multiple sources or operating across a large service area. Water is treated and distributed through infrastructure whose conditions may vary by source, facility, and location. A system-wide summary can therefore be accurate within its stated method while still offering limited visibility into localized differences.

The 4.0 mg/L threshold and the 0.7 mg/L target

The regulatory figures are easy to conflate because they address different purposes. The EPA sets an enforceable Maximum Contaminant Level (MCL) and a Maximum Contaminant Level Goal (MCLG) for fluoride at 4.0 mg/L. It also sets a non-enforceable Secondary Maximum Contaminant Level (SMCL) of 2.0 mg/L, intended to prevent cosmetic dental fluorosis. Separately, the U.S. Public Health Service recommends 0.7 mg/L as the optimal concentration for preventing dental caries while minimizing dental fluorosis risks.

The 0.7 mg/L recommendation is a public health target for community water fluoridation. It is not the same kind of regulatory threshold as the EPA’s enforceable MCL. Likewise, the 2.0 mg/L SMCL and the 4.0 mg/L MCL answer distinct regulatory questions. Treating them as interchangeable can lead to an incorrect reading of a report.

The comparison does not determine whether a particular system is operating appropriately. It gives the reader a way to interpret the figures in context. A reported value below 4.0 mg/L does not by itself establish that the system is operating at the 0.7 mg/L public health target. Conversely, a value above 0.7 mg/L should not automatically be described as exceeding the federal MCL.

The distinction also matters when a report lists a value without explaining its origin. Naturally occurring fluoride can contribute to the measured concentration, while some systems add fluoride as part of treatment. A concentration result alone does not establish which source accounts for it. Readers looking for hidden fluoride additives in utility reporting should therefore seek a description of treatment practices, rather than infer the use of an additive from the measurement alone.

Identifying reporting omissions: what a detection range can hide

A range contains more information than a single average, but it still has limits. Without dates and locations, a reader cannot tell whether the high and low values occurred in different months, at different facilities, or at distinct points in the distribution system. A range also does not show how frequently either endpoint occurred.

Annual averages have a different limitation. A stable average can coexist with changes over time, because high and low measurements may offset one another. That is a feature of aggregation, not proof that a report is inaccurate. To evaluate discrepancies in municipal water treatment data, the reader needs to compare like with like: the same period, units, sampling locations, and type of statistic.

A useful audit separates the questions instead of treating a single number as a complete account:

1. What does the reported number summarize? Note whether it is an average, range, or isolated result. If the method is not described, mark that uncertainty rather than assigning a meaning to the figure.

2. When were the samples collected? A yearly value without monthly results cannot establish whether concentrations fluctuated during the year.

3. Where were samples taken? A treatment-plant result may not represent every point in the distribution network. CCR summaries may not provide enough detail to assess point-of-use variation.

4. How many measurements support the summary? A reported range or average is easier to interpret when the sampling count and sampling schedule are available.

5. Does the report describe fluoride’s source? The measured concentration does not, by itself, distinguish natural fluoride from fluoride added by the utility.

6. Are the comparison figures clearly labeled? Confirm whether a report is referring to the 0.7 mg/L public health recommendation, the 2.0 mg/L SMCL, or the 4.0 mg/L MCL.

The key limitation is resolution. CCRs typically present fluoride as an annual average concentration or a detection range. Such summaries can obscure temporary operational fluctuations and localized point-of-use variances. The available evidence does not establish the exact share of municipal reports nationwide that voluntarily distinguish added from naturally occurring fluoride. It also does not establish real-time variation at household taps across distribution networks.

Those gaps should be described precisely. A reader may conclude that a report does not disclose monthly values, or that it does not identify fluoride’s source. The reader cannot conclude from those omissions alone that the utility added fluoride, concealed a particular concentration, or violated reporting law.

Verifying public utility fluoride testing

When a CCR leaves a material question unanswered, the next step is to seek the underlying monitoring context. The aim is to clarify how the published result was generated, not to replace one incomplete summary with an unsupported estimate.

A practical request to the utility can ask for the fluoride sample dates, sample locations, number of measurements, and whether the published figure is an average or a range. It can also ask whether fluoride is naturally present, added during treatment, or both, and whether that distinction appears in the report. These questions target the gaps that a yearly summary may leave open.

For a useful comparison, keep the scope consistent:

• Compare measurements from the same calendar year.
• Keep units consistent, especially when reading documents that may report concentrations in different formats.
• Separate treatment-plant measurements from distribution-system or consumer-tap measurements.
• Distinguish a target concentration from a maximum regulatory limit.
• Record whether the utility explains the sampling method and the source of fluoride.

A utility response that supplies only another annual summary may still leave temporal detail unresolved. That does not make the response false; it means the available record does not answer the more granular question. If records are presented in different formats, the reader should avoid comparing a monthly result from one document directly with an annual average from another as though they were equivalent.

Federal monitoring data provide a broader comparison, although they do not substitute for local records. CDC Water Fluoridation Reporting System data from 2016 to 2021 showed that 16.3% of population-weighted monthly fluoride measurements reported by community water systems fell below 0.6 mg/L. This statistic describes reported monthly measurements weighted by population. It does not establish that 16.3% of individual households received water below that level, nor does it identify the cause of each low result.

The 0.6 mg/L figure should also be read in relation to the 0.7 mg/L U.S. Public Health Service recommendation. The former appears here as a threshold associated with effective dental caries prevention in the research facts; the latter is the recommended optimal concentration. Neither figure turns an annual CCR average into a monthly monitoring record. A local report and a national trend measure different scales of the system.

The 2024 NTP findings and the status of federal review

In August 2024, the National Toxicology Program released a report associating fluoride levels exceeding 1.5 mg/L with lower IQ in children. The finding prompted an expedited EPA scientific evaluation of the current 4.0 mg/L regulatory standard under the Safe Drinking Water Act. In April 2025, the EPA announced an expedited review of the drinking-water fluoride standard.

An association reported at a particular exposure level is not itself a revised standard, and it should not be presented as proof that a specific local water supply caused an outcome. The 1.5 mg/L figure belongs in a different category from the EPA’s current 4.0 mg/L MCL and the Public Health Service’s 0.7 mg/L recommendation. Each figure arises from a different policy or scientific context.

For readers auditing a municipal report, the immediate implication is limited but practical: record the reported concentration and its time frame, then keep it separate from the evolving federal review. The EPA has not finalized a lower mandatory fluoride standard below 4.0 mg/L in the information available here. Any account of a local system should reflect the standard currently identified in the report and avoid describing an ongoing evaluation as a completed regulatory change.

The review also reinforces why clear disclosure matters. A public reader needs to know whether a measurement represents an annual average, a range, or a sequence of samples; whether it comes from a treatment facility or another point; and whether the fluoride is naturally present or added. Without those details, readers can identify the limits of the public record, but they cannot reconstruct exposure conditions from the CCR alone.

The present record supports scrutiny of reporting resolution. It does not support filling missing measurements with assumptions.

What a municipal report can and cannot establish

A CCR can establish the fluoride concentration that a utility chose or was required to report for the relevant period, along with any stated benchmark and method. It can help residents locate the reported value and determine whether it is presented as an average or a range. It may also identify treatment practices, though the completeness of those disclosures varies.

A CCR may not establish how concentrations changed month by month, how they differed across the distribution network, or what a household’s tap concentration was at a specific time. Nor does a measured fluoride concentration, without additional information, establish whether the fluoride was naturally occurring or added. Those are limits of inference, not findings of misconduct.

The most defensible audit therefore keeps three layers distinct: the utility’s reported measurement, the applicable regulatory and public health reference points, and the questions the report leaves unanswered. That approach permits a precise account of disclosure gaps without overstating what the data show.

At present, the clearest established gap is one of visibility. Annual summaries can leave timing, location, and source unresolved. Whether those omissions materially affect a particular system’s exposure profile remains unproven unless more detailed monitoring records are available.