We’ve simplified and automated how scenario documentation is handled when creating Environmental Product Declarations (EPDs). These changes reduce the number of questions you need to answer, improve data consistency, and help you publish faster — while staying fully aligned with EPD Hub and other requirements.
What Changed
Automated data sourcing
Scenario documentation now reuses data you already provide in your project (see below).Fewer questions
Many scenario questions have been removed or merged. Only data that can’t be derived automatically is still asked.Consistent output format
Scenario data in reports now follows one clear structure:
English name, source database, quantity, unit, and impact metrics (e.g., GWP-total).Unified view
Instead of separate, collapsible sections for each stage (A3, A4, A5, B2–B7, C1–C4), there’s now a single Scenario documentation block.Reports updated
Report layouts have been refreshed for clarity but remain familiar. You’ll see the same content presented in a cleaner way across all supported report types.Expanded availability
Full scenario documentation scope is now supported across all regions and schemes (including RTS, INIES, NMD, PEP, NA, FR).
How This Affects You
Less manual data entry
If you’ve already filled in your LCA model (e.g., energy use, transport details, installation resources), this information is now reused automatically.Smarter calculations
Bulk density and other derived fields are now calculated in the background from existing data.Clearer, standardized reports
All reports — including EPD Hub, national databases, and project exports — now use the same format and terminology.No data loss
Your previously entered information remains valid and is simply reorganized or automated.
Automated Data Sourcing
A3 (Manufacturing energy): Data now comes from the Energy Use query.
A4 (Transport): Automated transport data, with distances pulled automatically. Bulk density is calculated from product/packaging mass and volume.
A5 (Installation): The software now splits into resources and waste using Installation resources and Installation waste queries.
B2–B5 (Maintenance/Repair/Replacement/Refurbishment): Data auto-filled from the model.
B6–B7 (Use of energy & water): Energy/water use exported separately, with B6 and B7 split.
C1–C4 (End-of-life): Data auto-filled from the model.
User-required Inputs
With all of the above streamlined and automated, only the remaining questions require user input:
A4 - Capacity utilization (including empty returns):
This is declared as the average percentage of load capacity used, considering empty return trips.
If return trips are empty, utilisation will be lower, e.g., if one-way is fully loaded and return is empty, then (100+0)/2 = 50%.of the vehicle's weight that is utilised during delivery.
A4 - Volume capacity utilization factor:
This is the ratio of the actual load volume to vehicle’s total volume capacity. Please choose the correct value from the dropdown menu.
1 if fully utilised
<1 if less than full
>1 only for compressed/nested packaging (compressing them or fitting smaller items inside larger ones—to increase load efficiency)
B2-B7 - Various inputs
The inputs here are product category specific so please see the help text related to each input after the answer field. They are only required if you declare the use stage.
C1-C4 - Scenario assumptions, e.g., transportation
This is an open text field for any assumptions that have been made for the end of life scenario. For example, "Transportation to landfill has been conservatively assumed as 50km by truck."
Actions to Take
Review your project inputs
Check that your declared unit, product mass, packaging volume, and transport distances are accurate — these are now used to fill scenario documentation automatically.Check the new scenario documentation section
Answer the remaining questions for your declared life-cycle stages.Open and review updated reports
Preview your EPD reports to see the new unified scenario documentation section.
Contact Us
If you have any questions about the automated scenario documentation, or those that require user input, please don't hesitate to Contact Us.