Can't make September 15? Minnesota's extension, explained.
Minnesota will move your PFAS reporting deadline to December 14, 2026, but only if your request was postmarked by August 16, and only if it said the right things. Here's the whole picture from the source documents — including what to do if that window has already closed, which is the situation most people reading this are actually in.
Who this applies to
Every “manufacturer” selling products with intentionally added PFAS into Minnesota owes an initial report by September 15, 2026 (Minn. Stat. § 116.943; Minn. R. 7026). Manufacturer is broader than factory: it includes the brand owner whose name is on the product and, when neither producer nor brand owner has a US presence, the importer or first domestic distributor. E-commerce sales into Minnesota count.
The extension in three facts
- Your request must be postmarked by August 16, 2026.
- If granted, your deadline moves to December 14, 2026, a 90-day extension.
- It is discretionary: the MPCA commissioner can say no, so a bare “we need more time” is risky.
MPCA publishes the request form (form c-pfc1-29 on the MPCA reporting page). A separate waiver form (c-pfc1-30) exists for the narrow case where equivalent information is already publicly available.
What a persuasive request contains
The form asks for substance. Strong requests describe:
- Circumstances: what makes the deadline unworkable, e.g., supplier data still outstanding after documented requests, components 8 to 10 layers deep in the supply chain, testing lead times.
- Efforts already made:dates you contacted suppliers, response rates, follow-ups sent, testing ordered. (This mirrors the rule’s due-diligence standard in Minn. R. 7026.0080, keep those records five years.)
- A plan:what you’ll do between now and December 14 to close the gaps, escalations, TOF testing, component grouping.
Extension vs. filing best-available now
The extension isn’t your only path. Minnesota lets you file with “unknown” values (unknown chemical, unknown concentration, unknown function) as long as you keep pursuing the data and document your efforts, MPCA has said companies filing best-available information with documented efforts will be treated as compliant. Many brands should simply file by September 15 with honest unknowns and update by the next Feb 1 cycle. The extension makes more sense when your catalog is largely unmapped or supplier answers are arriving late in bulk.
If August 16 has already passed
The extension window is closed and there is no late route — but this is much less bad than it sounds, because the extension was never the main path. September 15 is still workable with an incomplete catalog.Minnesota accepts a report filed with honest “unknown” values so long as you are still pursuing the data and can show what you did to get it. What you cannot do is not file.
Concretely, between now and September 15:
- Register in PRISM this week, not in September, the consultant and association paths have their own approval steps that take days.
- Group aggressively before you enter anything. A 50-SKU catalog often collapses to a dozen report entries, and grouping after data entry is wasted work.
- Send the supplier request now and log every send. The log is what makes your unknowns defensible rather than negligent.
- File what you have by September 15, then correct at the February 1 update cycle, which exists precisely for this.
If you requested an extension and it was granted, your date is December 14, 2026 and everything above still applies, you simply have ninety more days to do it in.
The decision, simply
- Catalog mapped, some gaps: file by Sept 15 with documented unknowns. Skip the extension.
- Just discovering you’re covered: request the extension before Aug 16 and start the supplier chase the same week, December arrives fast.
- Genuinely out of scope (no intentionally added PFAS, confirmed by suppliers): no filing, but keep the attestations; that claim gets tested.
Not sure any of this applies to you?
Run the free 60-second checker →