Battery Compliance - Doc Requirements


Battery compliance succeeds or fails on documentation. Regulations, safety standards, transport rules, EPR programs, and battery passport obligations all require controlled evidence that is traceable to a specific battery design, manufacturing site, and market. This page is a master checklist of the documents and records most organizations need to sell, ship, and support batteries across jurisdictions.

  • Use the tables below to build a document register and assign owners.
  • Treat documents as controlled records: versioned, traceable, and retained.
  • Link each artifact to products, markets, and SKUs in your PLM and ERP systems.

Core Document Categories

Most battery compliance evidence falls into a small number of repeatable categories. Your program scales when these categories are standardized and mapped to systems of record.

Category What It Covers Primary Owners
Regulatory scope and applicability Which rules apply by market, battery type, and role Compliance, Legal
Safety standards evidence IEC and other product safety test reports and certifications Engineering, Lab, Quality
Transport compliance evidence UN 38.3 test summary, DG classification, shipping documents Logistics, Compliance
Restricted substances and materials compliance RoHS, REACH SVHC, declarations, screening records Compliance, Supply Chain, PLM
Lifecycle obligations EPR, take-back, recycling evidence, downstream certificates Operations, Compliance, Legal
Battery passport data package Identity, compliance, provenance, carbon and recycled content records Compliance, IT, Product
Audit readiness and controls Internal controls, change control, CAPA, and audit logs Quality, Compliance, Risk

Minimum Viable Document Set

This is a practical baseline. Your exact list depends on battery type and target markets, but most commercial operations need the items below.

Document Purpose Common Trigger
Product scope statement Defines battery type, intended use, and market coverage New product release
Battery identification record Links design revision, cell type, and manufacturing site to a shipped SKU SKU creation, supplier onboarding
Bill of materials and controlled drawings Traceability from tested configuration to production configuration Engineering release, changes
Safety test report set Product safety evidence aligned to required standards Certification, major design change
UN 38.3 Test Summary Transport acceptance evidence for lithium battery shipments New battery configuration, shipping launch
Dangerous goods classification record Correct shipping name, UN number, packing instructions, labels Carrier onboarding, new route
SDS Hazard communication for logistics and downstream handling Shipping, customer requests
Restricted substance declarations Evidence for RoHS and other substance controls where applicable Customer compliance questionnaires
SVHC screening records REACH article communication readiness where applicable EU sales, Candidate List updates
EPR registrations and stewardship evidence Proof of registration and financing of end-of-life obligations Selling into covered jurisdictions
Recycling and downstream certificates Evidence of lawful treatment for collected waste batteries Audits, regulator requests

Transport Documentation

Transport compliance is frequently enforced by carriers. Most shipping failures are caused by missing or stale documents.

  • UN 38.3 Test Summary and supporting test reports.
  • Dangerous goods classification and packaging instruction reference.
  • Shipping documentation package for each route and mode.
  • Training records for staff who prepare shipments where required.

afety Standards Documentation

Safety standards evidence is often required for market access, certification, and customer qualification. Evidence must be traceable to the exact configuration tested.

  • Test reports referencing the exact standard edition used.
  • Sample identification linking test units to the released design.
  • Manufacturing site identifiers and quality controls supporting consistency.
  • Certificates and surveillance reports where a certification scheme applies.

Materials and Restricted Substances Documentation

Materials compliance scales through structured supplier data and controlled records. Testing is used selectively to validate high-risk parts and suppliers.

  • Supplier declarations and material declarations stored as controlled records.
  • SVHC screening workflow tied to the BOM and markets sold.
  • Targeted analytical test reports for high-risk categories.
  • Change control records showing when re-declaration or re-test is required.

EPR and End of Life Documentation

EPR and end-of-life obligations are documentation-heavy. Most audits focus on registration, reporting accuracy, and downstream treatment evidence.

  • Producer registrations, IDs, and stewardship organization memberships.
  • Placed-on-market reports and reconciliations to sales shipments.
  • Fee invoices and payments tied to reporting periods.
  • Collection and recycling certificates from qualified downstream partners.

Battery Passport Documentation

Battery passport compliance requires an evidence pipeline, not a static document. The passport system must be able to reproduce published claims from controlled records.

  • Identity data: model and unit identifiers linked to production lots.
  • Compliance claims and referenced standards evidence.
  • Material provenance and due diligence evidence where required.
  • Carbon footprint and recycled content records where applicable.
  • Access control records for public vs restricted data disclosure.

Record Control and Retention

Compliance programs fail when records are not controlled. Treat evidence as a quality system problem.

Control What It Prevents Implementation Hint
Document version control Using stale test reports and outdated declarations Central repository with approval workflow
Traceability to product configuration Mismatch between tested and shipped configurations Link evidence to PLM revision and manufacturing site
Change control triggers Invalidating compliance evidence without re-test or re-declaration Engineering change rules tied to evidence types
Retention and audit trail Inability to prove compliance for prior shipments Retention schedule aligned to markets and contracts

Implementation Checklist

  • Step 1: Build a compliance document register mapped to products and markets.
  • Step 2: Assign owners and systems of record for each artifact type.
  • Step 3: Standardize templates for declarations, test summaries, and data packs.
  • Step 4: Establish change control triggers and evidence refresh rules.
  • Step 5: Integrate reporting extracts into ERP and store signed outputs as controlled records.
  • Step 6: Run an annual internal audit of evidence completeness and validity.

Summary

A battery compliance program is an evidence program. The fastest path to audit readiness is a standardized document register, controlled recordkeeping, strong traceability to product configurations, and disciplined change control integrated into ERP and quality workflows.