Transport and energy records often explain why one lithium carbon-footprint file differs from another. They need their own evidence page because they change more often than the product description. 1 2
This spoke belongs to the Lithium Carbon Footprint Evidence pillar at /lithium-carbon-footprint-evidence/.
Transport evidence
A transport record can include origin, destination, mode, distance, carrier document, container reference, batch reference, and date. In a lithium carbon file, those details may affect emissions inputs. The vault page should state whether the transport file covers one shipment, a period average, or a modeled route. Without that boundary, a downstream reviewer may read a narrow shipment file as a general product claim.
Energy evidence
Energy files can include electricity purchase evidence, production-site energy mix, fuel consumption notes, renewable attribute records, or supplier calculation extracts. Lithium Record can store and hash those files. It does not verify the energy claim or decide whether the claim is acceptable under any carbon-footprint methodology.
Why separate records matter
Transport and energy values can shift without changing the lithium product name. Separate records make those changes visible. They also allow a carbon version-control page to show which files supported each calculation period.