Fluoride additive procurement: essential records for advocates

The purchase file can show what product a utility specified, how a supplier demonstrated compliance, and how the contract calculated payment. It cannot, by itself, establish the fluoride concentration delivered to every customer or resolve the health-policy debate.

For advocates reviewing municipal water fluoride additive procurement records, the useful starting point is the contract lifecycle: solicitation, bid evaluation, award, delivery, and payment. Each stage produces a different record, and each answers a different question. A procurement audit is strongest when it follows those records in sequence rather than treating a product certificate as a complete account of water quality.

Identify the records that define the purchase

The first documents to request are the Invitation to Bid (ITB), request for proposals (RFP), or equivalent solicitation, along with the final executed contract and any amendments. These show what the utility asked suppliers to provide and what the successful vendor agreed to deliver.

A solicitation may identify the chemical form, required assay range, packaging or delivery method, applicable technical standards, and documentation required with each shipment. The contract can add details about inspection, rejected loads, delivery schedules, price adjustments, and remedies for noncompliance. Amendments matter because they may change quantity estimates, contract duration, pricing terms, or technical requirements after award.

The bid file helps explain how the utility selected a supplier. It may include submitted bids, scoring sheets, award recommendations, and records of any exception to the published specifications. Not every procurement uses a scored proposal process; some are awarded primarily on price among bids meeting stated requirements. The solicitation and evaluation record establish which method applied.

A practical request can name the records directly:

1. The solicitation and all addenda for the fluoride treatment chemical contract.

2. The bids received, bid tabulation, evaluation documents, and award notice.

3. The executed contract, renewal documents, amendments, and current pricing schedules.

4. Delivery tickets, invoices, and payment records for the contract period.

5. Any written deviations, waivers, rejected-load reports, or contract performance notices.

This scope helps distinguish procurement documentation from broader water-quality monitoring records. If the question concerns what was purchased, ask for purchasing records. If it concerns what concentration was measured in finished water, request the utility’s operational and water-quality records separately.

Read certification as a defined claim

Municipal specifications commonly require current NSF/ANSI/CAN 60 certification for treatment chemicals and a lot-specific Certificate of Analysis (CoA) with each delivery. NSF/ANSI Standard 60 is a benchmark for health-effects evaluation of chemicals used in drinking-water treatment. The U.S. EPA does not directly approve or certify individual commercial batches of fluorosilicic acid.

That distinction is central to interpreting municipal water chemical safety documentation. A certification listing concerns a product under the conditions and scope described by the certifying program. A CoA concerns a specific lot or shipment. Neither document should be treated as a substitute for the other, and neither alone demonstrates the fluoride level in finished water.

The record review should establish:

• Whether the contract required current NSF/ANSI/CAN 60 certification at the time of delivery.
• Whether the delivered product and manufacturer correspond to the certification identified in the file.
• Whether the certification listing specifies a Maximum Use Level (MUL), and how that limit is expressed.
• Whether the utility required an AWWA standard or another technical specification in addition to certification.
• Whether shipment records connect each CoA to a delivery date, lot number, and invoice.

The NSF/ANSI Standard 60 MUL is a product-use limit within the certification framework. For fluorosilicic acid, the listed example may be 6 mg/L, or 2.7 mg/L depending on product concentration. Those figures are not interchangeable with the community fluoridation target of 0.7 mg/L: they answer different technical questions. The target concerns fluoride concentration in treated drinking water; the MUL concerns the use of a treatment product under the standard’s evaluation. The contract and certification listing must be read in their own units and context.

The EPA’s enforceable Maximum Contaminant Level for fluoride in drinking water is 4.0 mg/L, while the Secondary MCL is 2.0 mg/L. These regulatory values also have a different function from a utility’s fluoridation target. A records review should avoid presenting them as competing product specifications or as evidence that a particular shipment met a finished-water target.

Certification documents identify the scope of a product review; delivery and operating records establish what entered the system and what the system produced.

Match each Certificate of Analysis to a shipment

A CoA is most useful when it can be traced to a delivered lot. Request the certificates for the relevant contract period, together with delivery tickets or receiving records that identify the corresponding shipment. If the utility supplies only a general product specification, ask whether lot-specific certificates were required by the contract and whether they are retained.

For fluorosilicic acid, assay refers to the concentration of the active chemical in the supplied product. Commercial bulk product commonly falls in the 23% to 25% assay range. A difference within that range can matter to feed calculations and to a contract that pays according to active concentration. It does not, on its own, show whether a treatment system was operated correctly.

A careful review compares the CoA against the contract’s stated requirements, rather than assuming a universal minimum. Some specifications may set a minimum assay, but the exact requirement varies by contract. The available records should show whether the delivered lot met the utility’s own stated specification. If the certificate reports analytical values, methods, or limits, preserve those fields as written; do not infer that an unreported contaminant was tested or absent.

For each shipment, create a simple record map:

• Contract product and specification, including the required assay range.
• Supplier, manufacturer, lot identifier, and delivery date.
• CoA values and any stated analytical method or acceptance limit.
• Receiving documentation, including quantity and any exception noted.
• Invoice line, unit of measure, and applicable price calculation.

This makes gaps visible. A missing CoA is a documentation gap if the contract required one, but it does not prove that the chemical was defective. A certificate with an assay value below a contractual minimum may warrant follow-up about acceptance, replacement, or an authorized exception. The conclusion should remain tied to the actual contract language and delivery record.

Decode the price basis before comparing invoices

Fluoride supply contracts can calculate payment on an assay-adjusted basis or a quantity-adjusted basis. The distinction affects how a reviewer interprets delivered volume, weight, and invoice totals.

The contract may define adjustments, tolerances, rounding, or the measurement used for billing. Those details should be read before comparing one invoice with another. A price per gallon is not directly comparable to a price per ton without the relevant product concentration, density or conversion basis, and contract terms. The available facts do not support a general market price: costs vary with location, freight distance, and supply conditions.

A utility procurement audit checklist should therefore separate three questions: what quantity arrived, what assay was documented, and how the invoice converted those inputs into payment. If the invoice total does not appear to follow the formula, request the calculation detail or supporting worksheet. The mismatch may reflect a contract adjustment, a unit conversion, or an error; the records determine which explanation is supported.

Make the public-records request precise

Municipal utilities and water districts are generally governed by state and local public-records laws, not the federal Freedom of Information Act. The applicable statute and submission process depend on the jurisdiction. A request should go to the records custodian or other designated office and identify the contract, department, or time period as narrowly as the requester can.

A useful request states the subject, dates, and document categories. For example, it can seek the solicitation and contract for fluorosilicic acid, all amendments, supplier bids and award materials, shipment-specific CoAs, delivery records, and invoices for a defined period. If the utility uses sodium fluoride or sodium fluorosilicate instead, name the chemical form shown in the procurement file; different products should not be collapsed into a single generic category.

If the response is incomplete, follow up by identifying the specific record that appears to be missing. Ask whether the utility maintains the document under another name, such as receiving report, batch analysis, chemical acceptance record, or payment voucher. A targeted follow-up is more productive than repeating a broad request for all records relating to fluoridation.

A few procedural points improve the result:

• Ask for electronic copies in the format in which the records are maintained, where available.
• Define a contract period or a bounded number of deliveries to keep the search manageable.
• Request the records index or a description of withheld material if the response cites an exemption.
• Keep procurement records separate from finished-water monitoring data in the request.
• Preserve the utility’s response, including any stated retention limits, fees, or appeal instructions.

Public-records laws differ, so a requester should use the local statute’s terminology and deadlines. An agency’s inability to locate a record is not proof that a required control was absent; it may reflect retention practices, a different record custodian, or a different document title. The next step is to ask how the record is created and maintained.

What the procurement file can establish

Taken together, the solicitation, contract, certification records, CoAs, delivery documents, and invoices can show whether the utility documented its purchase according to its stated requirements. They can also reveal how the chemical was specified, which supplier won the award, what basis governed payment, and whether each delivery was linked to the required supporting documents.

The file has limits. Product certification is not batch testing by the EPA. A CoA does not establish the finished-water fluoride concentration at every point in the distribution system. Procurement records do not resolve questions about the efficacy, risk, or ethics of community water fluoridation. Those questions require evidence and analysis suited to them, including operational monitoring data and systematic reviews of health outcomes.

The disciplined conclusion is therefore narrow: records can verify the procurement trail and expose gaps between contract requirements and documented performance. Whether a particular utility met its treatment target, and how the policy should be judged, remain questions that procurement documents alone cannot settle.