If your team submitted through PRISM before the September 15 deadline, the natural instinct is to close the file. That instinct is wrong. Under Amara's Law, the act of filing does not end your obligation. It begins a multi-year compliance relationship with the Minnesota Pollution Control Agency (MPCA). What you committed to after filing your Minnesota PFAS report includes public disclosure of your data, a recurring annual update duty, a five-year records rule, and an ongoing obligation to keep chasing the supplier information you could not get the first time.

This article explains those obligations in plain terms, using the statute (Minn. Stat. § 116.943) and the final administrative rules (Minn. R. Chapter 7026). If you have not yet filed, or want to revisit the mechanics, our Minnesota PFAS PRISM filing guide covers the submission process itself.

Key Takeaways

📄 Your report is a live document. What you filed is the baseline, not the final word.

⚠️ Most reported information becomes publicly accessible after an MPCA review period, except protected trade secrets.

📊 The "best available information" allowance applied to your initial report. It is not a permanent data standard.

⏳ Annual updates are due each February 1 when there are new or changed products, or new information to add.

📄 Due diligence records must be retained for at least five years after a product leaves the supply chain.

📌 The data you file now feeds Minnesota's path to the January 1, 2032 ban and future currently unavoidable use decisions.

Is Your Minnesota PFAS Report Public?

Yes. Under Amara's Law, all reported information except trade secrets will be publicly accessible after a review period. This is a deliberate design feature of the law, not an incidental disclosure. The state's stated intent is to build a comprehensive public inventory of products containing intentionally added PFAS sold in Minnesota. Minnesota Pollution Control Agency

For an enterprise, that changes the audience for your submission. The data you entered is not seen only by regulators. It can be read by competitors, customers, journalists, advocacy groups, and plaintiffs' counsel evaluating product-liability exposure. Treat every field as a public statement about your products.

If specific information qualifies as a trade secret, protection is not automatic. You must submit a trade secret data request under Minn. R. 7026.0070 and meet the criteria there. If you did not request protection during filing, review whether any sensitive formulation or concentration data warrants a request now. Details on the disclosure and review process are on the MPCA's Reporting PFAS in products page.

For manufacturers managing exposure across multiple states, this public-record dynamic is becoming the norm rather than the exception, as our overview of 2026 state PFAS regulations explains.

The "Best Available Information" Allowance Was for the First Report Only

Many teams filed using incomplete supplier data, and Minnesota permitted that. MPCA stated it will consider a manufacturer in compliance with the initial reporting requirement if the manufacturer timely reports all available PFAS information, retains due diligence documentation, and provides that documentation to the agency upon request. That accommodation is what let companies file on time despite unresponsive suppliers or multi-tier data gaps.

The critical point is scope. This was an accommodation for the initial report, not a permanent standard you can lean on indefinitely. It does not convert "best available information" into an acceptable steady state.

What the first-period allowance does not waive

The accommodation leaves several obligations fully intact:

✓ The ongoing due diligence duty under Minn. R. 7026.0080 to keep requesting missing information from your supply chain.

✓ The duty to update your report as better information arrives.

✓ The five-year records retention obligation covering your due diligence efforts.

✓ Public disclosure of what you reported.

✓ Reporting for new products and product changes going forward.

If information from your supply chain was incomplete, you must continue to request it and make updates as required by Minn. R. 7026.0080 and 7026.0040 as new information becomes available, and maintain documentation of these continued efforts, which MPCA staff may review to evaluate compliance and due diligence. In other words, a field you left as "function unknown" or a concentration you estimated is a task still open on your books, not a closed line item. Minnesota Pollution Control Agency

This is precisely where reactive, spreadsheet-based tracking breaks down, and where a continuous approach to supplier documentation matters. The obligation is not to have perfect data on day one. It is to demonstrably keep working the gaps.

Four ongoing obligations after filing Minnesota PFAS report under Amara's Law

Click on image to view full

What Triggers a Minnesota PFAS Resubmission or Update

Amara's Law is built around annual maintenance. Subsequent reports or updates are due each year when required, including for newly covered products or changes to previously reported information. The recurring date is February 1.

One point of relief in the final rule: MPCA removed the earlier requirement that manufacturers "recertify" previous annual reports when no other update was necessary, along with its associated fees. You are not required to re-file simply to confirm nothing changed. Updates are event-driven.

The table below summarizes what does and does not require action.

The practical implication for a large portfolio is continuous monitoring at the product and component level. Every engineering change, new SKU, or supplier substitution is a potential reporting trigger. Linking regulatory obligations to your bill of materials and substance data is what makes this manageable at enterprise scale rather than an annual fire drill.

Note also the split jurisdiction for certain products. Pesticides and fertilizers containing PFAS are reported to the Minnesota Department of Agriculture, while PFAS in other components, including packaging, are reported to the MPCA. Confirm your products are filed with the correct agency.

What Records You Must Keep: The Five-Year Rule

Recordkeeping is where post-filing compliance is won or lost, because MPCA can request your documentation at any time. Manufacturers must maintain documentation of all communications with other manufacturers, including emails, letters, and responses or the lack of a response, and this documentation must be provided to the commissioner upon request. Records must be maintained for at least five years after the product is removed from the supply chain.

That retention clock is worth reading carefully. It does not start at the filing date. It runs for five years after a product exits your supply chain, which for long-lived industrial goods can mean retaining evidence well over a decade.

MPCA allows this documentation to be maintained in electronic formats. The rule text and retention provisions are set out in Minn. R. Chapter 7026, and the agency's supplemental reporting guide walks through how continued efforts should be documented.

For enterprises, the governing question is retrieval, not just storage. If an inspector or customer asks for the evidence behind a three-year-old declaration, can you produce the time-stamped supplier trail quickly? That is a data architecture problem, and it is the core of genuine audit readiness across frameworks.

Five-year records retention rule after filing Minnesota PFAS report under Amara's Law

Click on image to view full

Where This Sits on the Road to 2032

The reporting program is not an end in itself. It is the evidence base for Minnesota's larger objective. A full ban on intentionally added PFAS takes effect January 1, 2032, applicable to almost all products unless a use is determined to be currently unavoidable.

The data you filed feeds directly into that future. MPCA has indicated that complete and accurate supply-chain information supports later regulatory processes, including potential currently unavoidable use (CUU) determinations. If you expect to argue that a specific PFAS use in your product cannot yet be eliminated, the quality of the record you are building now will matter when that case is made.

This also connects to your federal obligations. Minnesota's timeline runs alongside, and does not replace, TSCA Section 8(a)(7) PFAS reporting to the EPA. Treating each state and federal PFAS obligation as a separate project multiplies work; treating them as one PFAS data program is what keeps the effort proportionate.

Keeping PFAS Data Audit-Ready Year-Round

The through-line of every obligation above is the same: Minnesota expects your PFAS data to be current, defensible, and retrievable long after you filed. Meeting that standard through annual manual effort is difficult once you are managing hundreds of products and a multi-tier supplier base.

This is the problem Certivo is built to address. Certivo serves as the system of record for product compliance data, with CORA-powered regulatory intelligence that connects reported substances to specific products and components. That supports the tasks Amara's Law now requires on an ongoing basis: automated supplier data collection to close the gaps left in your initial report, time-stamped due diligence records for the five-year rule, and continuous monitoring so that a new SKU or formulation change surfaces as a reporting trigger before February 1, not after. For companies with PFAS obligations spanning multiple states and the EPA, this shifts the model from reactive filing to continuous readiness.

If you filed with partial data, or want confidence that your records would hold up to an MPCA request, book a compliance risk assessment to review your current Minnesota PFAS exposure and audit-readiness across products and jurisdictions.