Fixed date
18 February 2027
In-scope battery passports move from planning concern to operating requirement.
Battery passport readiness
Battery DPP readiness starts with supplier evidence, not a QR page.
In-scope battery passports have a fixed 18 February 2027 obligation. Redy helps teams turn material, carbon, recycled content, due diligence, and supplier attestation gaps into governed requests and versioned passport data before the deadline becomes the project.
Readiness snapshot
Fixed date
18 February 2027
In-scope battery passports move from planning concern to operating requirement.
In scope
LMT, industrial >2 kWh, EV
The passport obligation applies by battery category, not by whether the supplier data is easy to collect.
Access path
QR + unique identifier
The passport has to be reachable through a QR code linked to a unique identifier.
Output posture
Interoperable and access-controlled
Public, restricted, and legitimate-interest access needs should inherit the same reviewed evidence trail.
Deadline posture
The date is fixed. The hard work is upstream evidence.
The battery passport is accessed through a QR code linked to a unique identifier, but the defensibility problem starts before the scan: manufacturers need reviewed, supplier-backed data for the fields that make the passport credible.
In scope
LMT, industrial >2 kWh, EV
The passport obligation applies by battery category, not by whether the supplier data is easy to collect.
Access path
QR + unique identifier
The passport has to be reachable through a QR code linked to a unique identifier.
Output posture
Interoperable and access-controlled
Public, restricted, and legitimate-interest access needs should inherit the same reviewed evidence trail.
Battery evidence
The hard part is evidence collection across the battery supply chain.
Materials
Composition and component evidence
Collect supplier records for chemistry, component identity, source declarations, and bill-of-material context without spreading data across email threads.
Circularity
Recycled content and recovery claims
Request and review evidence for recycled material claims, reuse context, and recovery-related fields as schemas mature.
Impact
Carbon and production footprint inputs
Coordinate source documents, LCA references, and supplier attestations that support carbon and footprint-related passport claims.
Responsibility
Due diligence and supplier attestations
Keep due diligence declarations, audit letters, certifications, and supplier approvals tied to the passport version they support.
Field map
Map passport fields to the supplier evidence that proves them.
Redy keeps the domain schema, supplier submission, reviewer decision, and published DPP version connected so a battery program can explain where each claim came from.
Material composition
Supplier evidence
Chemistry declarations, component records, source references, and bill-of-material context.
Redy control
Scoped request, supplier-owned response, review state, version attribution.
Carbon footprint inputs
Supplier evidence
LCA references, production footprint data, energy inputs, and supporting methodology notes.
Redy control
Document attachment, extracted values, source context, approval before publication.
Recycled content
Supplier evidence
Supplier declarations, certificates, batch context, and recovery or recycled material claims.
Redy control
Reusable evidence records and grant controls so approved data can support more than one DPP.
Due diligence
Supplier evidence
Audit letters, policy attestations, certifications, and risk-screening evidence.
Redy control
Audit log, reviewer attribution, and a clear split between submitted evidence and approved claims.
State-of-health / lifecycle data
Supplier evidence
Operational, service, repair, repurposing, or recycling information when applicable to the battery category.
Redy control
Role-aware access posture and passport version history as data changes after publication.
Workflow fit
Battery-specific fields, Redy-wide control model.
Battery evidence is domain-specific, but the control model should stay consistent: scoped requests, supplier-owned responses, manufacturer review, provenance, versioning, and controlled publication.
Readiness questions
- Which battery categories are in scope?
- Which required fields sit with suppliers?
- Which evidence can be reused across product lines?
- Which outputs must be public, restricted, or role-based?
- Which passport fields need version history after publication?
- 1Identify missing battery passport fields
- 2Send scoped supplier evidence requests
- 3Attach declarations, certificates, and source documents
- 4Review claims before they become passport data
- 5Publish a versioned DPP with provenance intact
Outputs
Publish only after the evidence trail is defensible.
Redy keeps output surfaces tied to approved data, source context, and version history.
Manufacturer portal
Supplier response workspace
Versioned passport records
B2B API and export surfaces
Consumer passport view after publication