PFAS Evidence Packet Deliverables

Know what PFAS evidence you have for each product, and what still needs follow-up.

Liberty Tree assembles source-indexed PFAS evidence packages for manufacturers responding to customer documentation requests. The packet is built from your files, supplier records, and usable public evidence.

What a PFAS Evidence Packet is

A PFAS Evidence Packet is an organized documentation package for a defined product scope. It shows which documents exist, which products they support, which statements are source-backed, and which gaps still require supplier, manufacturer, or customer follow-up.

The packet is not a certification, legal opinion, or laboratory result. It is a documented record that helps your team respond carefully when a customer asks for PFAS evidence.

Who it is for

PFAS Evidence Packets are built for manufacturing compliance managers, quality leaders, operations teams, sales teams handling customer documentation requests, and counsel reviewing the final response.

Typical uploads

  • Customer PFAS requests, questionnaires, and response templates
  • Safety Data Sheets, technical data sheets, and product data sheets
  • Supplier declarations, manufacturer declarations, and material statements
  • Product lists, SKUs, part numbers, bills of material, or product families
  • Prior compliance files, correspondence, and evidence already collected

What you receive

  • Executive Summary
  • Document Inventory
  • Evidence Matrix
  • Source Index
  • Missing Documentation Register
  • Gap Summary
  • Supplier Request Package
  • Human-Reviewed Final Evidence Package

Pricing

The PFAS Evidence Readiness Engagement is a $7,500fixed-fee engagement for one customer request and up to three specifically identified products or SKUs. A $2,500deposit reserves the engagement and is credited to the fee. The $5,000 balance is invoiced after scope confirmation and is due before production begins.

Standard turnaround

Delivery is targeted within 10 business days after Liberty Tree receives the complete intake, required core documents, written scope confirmation, and remaining balance. Missing inputs or requested scope changes pause the delivery clock.

Packet structure

Built to support review without overstating the record.

The goal is a clearer record: what is known, what is supported, what conflicts, and what remains unresolved.

Traceable

Every packet statement is tied to a source document so reviewers can see the support behind it.

Product-aware

Generic declarations are separated from product-specific evidence, and SKU gaps remain visible.

Bounded

Unknown facts stay marked as unknown. Expert judgment is highlighted instead of guessed.