Guides
GLEC v3.2: data, calculations and report checks
GLEC v3.2 is a framework for calculating and reporting logistics greenhouse gas emissions. Smart Freight Centre describes it as aligned with ISO 14083. This practical guide helps you prepare inputs and review an output; it does not replace the framework.
Start with the shipment record
For a repeatable review, keep the shipment reference, date, origin, destination, transport mode, distance and cargo weight together. Record where each value came from. Missing values should remain visible rather than being silently treated as zero.
A small example: transport activity is not emissions
Illustrative data, not a customer shipment: 1.2 tonnes carried 500 km gives 600 tonne-km. This describes transport activity, not kg CO₂e. An emissions estimate also needs an appropriate calculation method and factors with a stated source, version, unit and boundary. Never apply an unexplained constant and call the result a verified GLEC report.
Keep assumptions next to the result
If weight, distance, vehicle or fuel data is estimated, mark it. Keep the selected calculation version and supporting records with the result so a reviewer can understand a later change. Do not mix a fuel amount, a distance and a tonne-km factor without checking their units.
Review a report before sharing it
Compare references and totals with the original shipment file. Check units, reporting period, omitted rows and duplicate shipments. Keep a methodology note and a register linking outputs to source records. A polished PDF alone does not show how a number was produced.
Try the workflow on a small file
The public LogisticsAI trial accepts 1–10 road-freight rows in CSV or XLSX. Download its example file for the supported column names, inspect the result and export a marked draft CSV without an account. This is a limited estimate for review, not certification, a full multimodal GLEC implementation or a complete evidence pack.
How this fits your work
- Audience
- Logistics teams preparing repeatable customer reporting workflows.
- Problem
- A PDF alone is difficult to update, review, integrate, or connect to source evidence.
- What LogisticsAI can do
- LogisticsAI packages executive PDF summaries with shipment workbooks, JSON, methodology, evidence registers, quality reports, and audit context.
Related guides and tools
Frequently asked questions
Is a PDF enough?
A PDF can summarize the result, but repeatable reporting benefits from workbook, JSON, methodology, evidence, quality, and audit artifacts.
Can this prove certification?
No. Do not claim certification unless a real external certification or verification process exists.
Related resources
See the next step
Open a prepared example or check a sample file. If this task comes up regularly, tell us how your team handles it and we can outline the next step.