Regulatory brief • Information checked October 19, 2026

Minnesota’s general initial reporting deadline for per- and polyfluoroalkyl substances (PFAS), September 15, 2026, has passed. Manufacturers with approved extensions have a different deadline. Your next step depends on your reporting status and the evidence still missing from your supply chain. [1]

In SiliconExpert’s compliance webinar, the central challenge was connecting regulatory requirements to products, components, suppliers, and source declarations. That work continues after a report is submitted. This brief translates that workflow into practical actions for the months ahead. [6]

Confirm your reporting status first

Check the formal Minnesota Pollution Control Agency (MPCA) notice and your submission records before setting an internal deadline. The extension-request postmark deadline was August 16, 2026; do not treat that request window as still open. [1]

Deadline guidance: MPCA [1]

Recheck scope at the product and component level

The reporting framework covers products containing intentionally added PFAS sold, offered for sale, or distributed in Minnesota, subject to statutory and rule exemptions. A manufacturer can be the producer or brand owner; for imports, the definition also covers the importer or first domestic distributor when the producer or brand owner has no U.S. presence. [2]

The 2026 amendment limits the reporting provision to products manufactured after July 1, 2023. Record the manufacturing date evidence used in your scope decision; obtain advice on any boundary-date uncertainty. [7]

Do not assume that relief from a sales prohibition removes a reporting obligation. MPCA specifically states that products with PFAS only in internal or electronic components can remain subject to reporting despite exemption from the 2025 sales prohibition. [1]

Start with your Minnesota product list, then connect each product to its bill of materials and supplier evidence. For each potential PFAS use, ask what function the substance serves and which declaration supports the answer. A broad supplier statement may need clarification if it does not identify the part, revision, or scope reviewed. This is a practical review method, not a substitute for an applicability determination.

Turn incomplete evidence into specific requests

Minnesota Rule 7026.0080 requires manufacturers to request detailed disclosure from their supply chain until all required information is known. Reporting responsibility remains with a manufacturer unless it receives the specified confirmation that another manufacturer has fulfilled the reporting requirements. An expectation that a supplier will report is insufficient. [3]

Use the required report fields to make each request precise: identify the product or component, request the PFAS chemical name and CAS Registry Number or other permitted identifier, establish its function, and obtain the required concentration information. Rule 7026.0030 allows a concentration response indicating PFAS is present but its amount or range is unknown. That option does not mean the product is PFAS-free. [4]

For example, if a supplier confirms PFAS in a connector but provides no concentration information, preserve that response, request the missing field, and record the affected product and component. Do not fill the gap with an estimate or convert it to a negative declaration. Use only the reporting options permitted for that field.

Give every unresolved request an owner, a follow-up date, and a clear description of the missing evidence. Keep technical review separate from outreach: supply chain can obtain a response, while the designated compliance reviewer evaluates whether it answers the reporting question. This division is a recommended operating practice.

Keep a record that survives the submission

Rule 7026.0080 requires documentation of communications with other manufacturers and reporting-responsibility agreements, provision of that documentation to MPCA on request, and retention for at least five years after PFAS-containing products are removed from the supply chain. The retention period does not start at the filing date. [3]

Build a retrievable record for each affected product: the source declaration, the version reviewed, the scope decision, unresolved questions, outreach history, the report version, and the internal review record. Store the applicable extension or waiver determination alongside it. These organizing fields are recommended practices; the rule remains the authority for required records.

Test the record with one question: could a colleague reconstruct why a particular answer was submitted without searching someone else’s inbox? If not, close that traceability gap before the people involved move to their next project.

Make February 1, 2027, an evidence milestone

Rule 7026.0040 requires a reporting update by February 1 when, during the previous calendar year, a product changed significantly, new product information was provided to the manufacturer, or a new product was sold, offered for sale, or distributed in or into Minnesota. Relevant changes during 2026 therefore matter for February 1, 2027. This is a triggered update requirement, not an instruction to resubmit every unchanged report annually. [5]

Create a change log now. Record when new evidence arrives, the products it affects, what changed from the submitted information, and who will review the reporting consequence. Include new products and significant product changes in the same review queue.

Consider a report that identified PFAS but used an allowed unknown concentration response. If a supplier later provides the missing concentration during 2026, route that information for an update assessment. Preserve both versions and the date the new information arrived. [4] [5]

Work backward from February 1 with internal dates for supplier follow-up, technical review, and submission preparation. A completed initial filing should hand off into this process rather than close the evidence file.

Separate reporting from the product decision

A PFAS report is not blanket permission to sell a product. Minnesota’s law separately addresses sales prohibitions, exemptions, and the broader 2032 prohibition, including currently unavoidable uses determined by the commissioner through rulemaking. An internal conclusion that a substance is technically useful does not itself establish that exception. [2]

Keep two decisions visible: what information must be reported, and whether the product may be sold under the applicable restrictions. Where a material change or alternative is being considered, involve engineering in performance evaluation and compliance in the regulatory assessment. Do not treat a replacement component as approved before both reviews are complete.

Choose one next action

If you are still preparing a report, start with the status check and assign the largest evidence gaps. If you have filed, establish the change log and the 2027 update review. Use the 2027 Compliance Readiness Checklist to identify process gaps and the companion Playbook to organize ownership, evidence review, and continuing monitoring.

Explore our compliance readiness resources.

This brief provides general information and practical process recommendations, not legal advice or a product compliance determination. Check current MPCA guidance and the applicable law for your products and circumstances.