waterbest.

Clinical precision for everyday oral health.

Community Advocacy

Public records requests: obtaining raw water fluoridation data

A water dashboard can show a clean, reassuring number such as 0.7 mg/L. It rarely shows how that figure was produced: which samples were taken, when they were tested, or how a utility handled readings that varied from day to day.

Public records requests: obtaining raw water fluoridation data

For parents asking about fluoride in water used to prepare infant formula, that gap matters. A summary can orient you, but it cannot answer every question about a particular system or a particular period.

A public records request is one way to look past the summary. It asks the agency or utility for records it already holds, such as monitoring logs, laboratory results, or chemical purchase documents. The process can feel formal, but the request itself can be plain and specific. The harder part is knowing which records exist, which office has them, and what a public dashboard can and cannot tell you.

Where the data lives, from federal databases to plant logs

Fluoridation information sits in layers. Federal and state databases help identify water systems and summarize information; utility records can show operational measurements and transactions. These layers serve different purposes, so a number in one place may not have a direct one-to-one counterpart in another.

The CDC’s Water Fluoridation Reporting System (WFRS) is a surveillance system for community water fluoridation information. It uses system identifiers associated with EPA’s Safe Drinking Water Information System (SDWIS) to help match records. Public-facing tools, including the CDC’s My Water’s Fluoride, may reflect information uploaded by participating states. State participation and uploads are voluntary, so dashboard data may be incomplete or less current than local records. A dashboard entry should not be read as a real-time account of every measurement made by a utility.

Below the federal view are state drinking water programs and local water systems. The utility may hold operational logs, laboratory reports, equipment records, and purchasing documents. The state may hold submissions made by the system, inspection materials, or other oversight records. The right place to ask depends on what you need: a state database entry and a plant’s daily readings are different records, often held by different offices.

A useful first step is to identify the system that serves the address you care about. A city name alone may not be enough. One municipality can have more than one water system, and a system can serve customers across municipal boundaries. The SDWIS identification number helps distinguish one public water system from another when you search state or federal records and when you write to an agency.

A dashboard is a starting point. The records behind it can show what was measured, what was submitted, and where the two views stop lining up.

Ask for records that answer a defined question

A focused request is easier to process and easier to interpret. Before sending one, decide what you want to learn. Are you looking for routine operational measurements? Trying to understand a gap in a public dataset? Checking what additive was purchased? Each question points to a different record set.

For fluoride concentration, the U.S. Public Health Service recommends an optimal level of 0.7 milligrams per liter in drinking water. That is a recommendation, not a compliance standard. A records request should not describe it as a legal limit that utilities must meet. Nor should an annual or quarterly average be framed as proof of compliance with that recommendation. Averages can be useful for understanding patterns, but they do not replace the underlying measurements or establish why a particular reading occurred.

Records worth asking about may include:

  • Daily operator monitoring logs. These can show the readings recorded by plant staff, along with dates and, depending on the utility’s system, the measurement method or instrument.
  • Laboratory reports. Ask for results from any outside laboratory testing or split-sample analysis related to fluoride. The report may help clarify how an operator’s measurement compares with another test.
  • Summary worksheets or calculations. These can show how a utility compiled results for a reporting period. Treat them as summaries, not as substitutes for the individual readings.
  • Fluoride additive procurement records. Invoices, purchase orders, delivery receipts, and product documentation may identify the purchased additive, supplier, quantities, and delivery dates, subject to applicable disclosure rules.
  • Equipment records. Calibration, maintenance, and repair records for relevant analyzers or feed equipment may help explain how measurements were taken and whether equipment was serviced.

The records available vary by system. A utility may use electronic logs, paper forms, a contractor’s laboratory reports, or a combination of these. It may not keep a document under the exact name you use. Describe the information you are seeking and invite the records officer to clarify what records the utility maintains.

Daily readings and summary figures answer different questions. A summary can help reveal broad patterns across a period; the individual entries show the measurements recorded on particular dates. Neither should be overinterpreted. A difference between a daily result and an average is not, by itself, evidence of a health effect, a reporting violation, or a dosing error. It is a reason to ask how the figures were collected and summarized.

Drafting a request for local records

For a municipal utility, the governing law is generally the state’s public records law, which may be called an Open Records Act, Sunshine Law, or another name. Federal FOIA applies to federal agencies, not automatically to a city utility. A request to the EPA or CDC may therefore follow a different process from a request to the water department serving your home.

Start with the utility’s or state agency’s records-request instructions. Some offices provide an online form; others accept requests by email or mail. Check where requests must be sent and whether the agency asks you to use a particular form. If the system is operated by a private contractor or regional authority, ask the municipality or state program which entity holds the records.

A clear request usually states:

1. Which water system you mean. Include its name, service area or relevant address, and SDWIS identification number if you have it.

2. The date range. A defined period is easier to search than a request for all records ever created.

3. The records sought. Name the categories, such as fluoride monitoring logs, laboratory reports, additive invoices, or equipment calibration records.

4. Your preferred format. If the records are kept electronically, ask for the electronic files in their existing format where available.

5. How to handle costs. You can ask the office to notify you before incurring fees above a stated amount, and say you are willing to discuss narrowing the scope.

6. The applicable law. Cite the state statute if you have confirmed it. For a federal agency, use that agency’s FOIA process.

For example, a request might say: “Under [state public records law], I request the fluoride monitoring logs and related laboratory reports maintained for [water system name and SDWIS ID] from [start date] through [end date]. If these records are maintained electronically, please provide them in their existing electronic format. Please contact me before incurring fees above [amount].”

That language is a starting point, not a universal form. Some states require particular details, and response deadlines, fee rules, and appeal procedures differ. Avoid assuming that the same timeline or fee limit applies everywhere. If you are unsure which statute governs, ask the records officer to identify the law and process that apply to the request.

Specificity does not mean asking for only one narrow document. It means describing the records in a way the office can search. If you ask for daily results and the utility calls them “operator worksheets,” the records officer may be able to locate them. If your request names only “the compliance spreadsheet,” you may miss the underlying logs entirely.

When a response is partial, delayed, or unclear

A first response may not settle the matter. Records can be held in different departments, an office may interpret a broad request narrowly, or documents may be unavailable in the format you expected. A calm follow-up that identifies the missing category and date range is often more useful than repeating the entire request.

If the response says “no records,” ask whether the utility maintains the type of monitoring or documentation you described under a different name. You can also ask which office or contractor holds the records, or whether the utility has submitted related information to the state. Do not treat the absence of a particular document as proof that no monitoring occurred. It may reflect how records are organized, what was requested, or where they are held.

Fee estimates deserve a close look. Ask for an itemized estimate and the basis for any search or copying charges. If the estimate is too high, narrow the date range or ask first for an index, a sample month, or a specific record category. Whether public-interest fee reductions are available depends on the applicable law and the agency’s rules, so check before relying on one.

A utility may withhold portions of records under an exemption, including claims involving confidential business information. Ask the agency to identify the legal basis for withholding and to release any reasonably separable, non-exempt portions. An exemption claim is not necessarily a reason to abandon the request; it is a reason to find out exactly what was withheld and why.

Deadlines and appeal options also vary by jurisdiction. If a response is overdue, send a concise follow-up with the original request date and ask for an estimated response time. Keep the request, acknowledgement, correspondence, fee estimates, and released files together. If the issue remains unresolved, the applicable state law may provide an administrative appeal, an ombudsman, or a route to court. Check the statute or seek local legal guidance before choosing a next step.

The paper trail matters for interpretation as much as for enforcement. A dated record of what you asked for, what you received, and what remains missing makes it easier to share a clear question with a utility board, a state program, a community group, or a local reporter.

Use the SDWIS number to compare records carefully

Once records arrive, the SDWIS identification number can help confirm that they refer to the same water system shown in state or federal data. Check the system name and service area as well; a number is useful, but mismatched names, shared infrastructure, or changes in how a system is described can complicate comparisons.

A simple comparison table can keep the questions grounded:

Local recordState or federal informationQuestion to investigate
Daily monitoring entriesA period-level summaryWhich readings and dates were included in the summary?
Laboratory reportA system-level public entryDoes the report cover the same system and period?
Missing dates in a logInformation appears for the full period in a public datasetAre the gaps explained by the record format, a separate file, or a reporting process?
Purchase or delivery documentsA general additive descriptionDo the documents identify the product or supplier, and is any detail withheld?

The table does not turn a discrepancy into a conclusion. A blank stretch in a local log, for example, could mean the information is stored elsewhere, was not retained, or was not produced in response to the request. A state or federal entry may represent an upload or summary rather than an independent measurement. Ask the utility or state program how the records relate before assigning a cause.

Procurement records can help answer a different question from monitoring logs. They may identify what a utility purchased, but an invoice alone does not establish the precise concentration delivered to customers on a particular day. For that, operational records and relevant laboratory results are more directly useful. Keeping those questions separate prevents a document from being asked to prove more than it can.

If records appear inconsistent, describe the mismatch precisely: which documents, dates, system identifiers, and figures are involved. Then ask the agency how it reconciles them. That approach is more persuasive than treating every difference as evidence of misconduct, and it gives officials a concrete issue to answer.

Public records requests cannot make a dashboard complete or guarantee a particular response. They can make the path from summary to source material more visible. For communities concerned about infant exposure, that distinction matters: the recommendation, the measurements, the summaries, and the purchasing records each tell a different part of the story. A careful request does not settle every question about water, but it can replace guesswork with records that neighbors and officials can examine together.

FAQ

What is the difference between a water dashboard and a public records request?
A dashboard provides a high-level summary of water data, while a public records request allows you to access the underlying source documents, such as daily monitoring logs and laboratory reports.
Why should I include an SDWIS identification number in my request?
The SDWIS ID helps distinguish one specific public water system from another, ensuring you receive records for the correct utility when searching state or federal databases.
Can I use a public records request to prove a utility is violating fluoride standards?
Records requests provide data for examination, but they do not automatically prove violations. A difference between daily readings and averages is not, by itself, evidence of a health effect or a reporting violation.
What should I do if a utility claims they have no records for my request?
Ask if the utility maintains the requested information under a different name, or inquire which specific office or contractor holds those records.
Are fluoride levels of 0.7 mg/L a legal requirement for all water systems?
No, the 0.7 milligrams per liter level is a recommendation from the U.S. Public Health Service, not a mandatory compliance standard.