Lithium compliance evidence // SPOKE RECORD

Lithium Supplier Carbon Declarations

Store supplier carbon declarations for lithium inputs with hashes, dates, scope notes, and non-certifier language.

Permanent record copy

Evidence page

This page is part of the Lithium Record pillar-and-spoke content layer for provenance, carbon-footprint, due-diligence, and Battery Passport evidence.

Supplier carbon declarations are often the first carbon file a battery team receives for lithium inputs. The declaration should be preserved exactly, not turned into a broader claim by the vault. 1 2

This spoke belongs to the Lithium Carbon Footprint Evidence pillar at /lithium-carbon-footprint-evidence/.

Declaration capture

A supplier declaration can identify the lithium product, production site, reporting period, calculation boundary, unit, methodology reference, and responsible issuer. Lithium Record can host that declaration and expose the hash. The page should state whether supporting files exist or whether the declaration is the only uploaded evidence. That distinction matters because a declaration without source data is not the same as a complete evidence package.

Downstream use

Battery manufacturers may use supplier declarations as inputs to purchased-goods emissions or battery carbon-footprint work. The vault page should not rephrase the supplier claim as Lithium Record’s claim. It should attribute the statement to the document issuer and keep the file available for review.

Change management

Supplier declarations change when methodology, energy data, process data, or reporting periods change. Each new declaration should be added as a separate record or version. A stable archive prevents the evidence trail from losing the document that supported an earlier customer decision.

Compliance boundary

Stored evidence, not formal approval

Lithium Record should be described as a vault, record, hashing, hosting, indexing, and verifier-handoff layer. It should not be described as a certifier, auditor, regulator, notified body, conformity-assessment body, legal adviser, or automated compliance decision-maker. The page copy should keep the distinction between stored evidence and formal compliance determination explicit.

Source freshness register // evidence record

Last-reviewed evidence boundary for this record

Static source register reviewed for lithium supplier carbon declarations within the Lithium compliance evidence evidence context.

Last reviewed
2026-05-11
Source count
2
Review type
Static route and source-register inspection
StepSource categoryFreshness boundary
1Article 7 evidence referencesRecord source category reviewed for static availability and conservative boundary language.
2LCA source-file cuesRecord source category reviewed for static availability and conservative boundary language.
3Supplier carbon declarationsRecord source category reviewed for static availability and conservative boundary language.
4Transport energy and version-control recordsRecord source category reviewed for static availability and conservative boundary language.

Evidence boundary

Reviewed for availability, not approval

This record-level freshness note confirms that the static route, source register, internal links, and compliance-boundary copy were reviewed for availability and conservative language. It does not certify compliance, approve the underlying documents, provide legal advice, or replace accredited verification.

Verifier next action: Inspect the source register on this page, compare related lane records, and route any formal determination to the responsible operator, qualified counsel, customer, or accredited review process.

Verifier questions

FAQ

Who makes the supplier declaration?

The supplier or another named issuer makes the declaration. Lithium Record stores the uploaded document.

Can a declaration be used in Scope 3 accounting?

It may support purchased-goods emissions work if the responsible team accepts it and applies the relevant accounting guidance.

Should old declarations be deleted?

They should usually be retained as historical evidence unless a lawful retention policy requires removal.

Evidence record FAQ // verifier Q&A

Common review questions for this record

These static answers explain how to interpret this individual evidence record, where it connects to the lane graph, and which compliance boundary remains outside Lithium Record.

Record FAQ

How should a verifier use this Lithium Record page?

Use this page as a static spoke evidence-record entry for lithium supplier carbon declarations. It organizes route metadata, source references, internal context, and verifier handoff links so the reviewer can decide which source files, vault records, or adjacent evidence pages to inspect next.

Record FAQ

What does this record not prove on its own?

On its own, this page does not certify EU Battery Regulation compliance, validate carbon-footprint calculations, approve provenance claims, or replace accredited verification. Lithium Record provides a vault, record, hashing, hosting, indexing, and verifier-handoff layer for review support.

Record FAQ

How does this record connect to the evidence lane?

This record belongs to the Carbon Footprint evidence lane at /records/carbon-footprint/. The lane page groups the pillar and spoke records so reviewers can move between regulation, carbon-footprint, provenance, and Battery Passport context without relying on a dynamic checkout or private dashboard route.

Record FAQ

What is the next handoff after reading this record?

A reviewer can follow the source register, open related records, use the verifier handoff route, or request manual onboarding. The static page preserves discovery and orientation; any formal determination remains with the appropriate verifier, customer, or accredited review process.

Source register

Primary regulatory references

Lithium Record content is written as technical infrastructure guidance, not legal advice. Formal compliance decisions should be reviewed with qualified counsel and accredited verifiers.

RefReferenceSource domain
[1]GHG Protocol Scope 3 Category 1 guidanceghgprotocol.org
[2]Regulation (EU) 2023/1542eur-lex.europa.eu