Dawn
Tutorials/EPD Generator review

Guide for the EPD verifier

For the EPD Hub verifier of an EPD made with the pre-verified tool Dawn AI: the scope of the check, the record files, how to recompute the SHA-256 fingerprints, and how to read the EPD project report.

Guide for the EPD verifier

This guide is for the EPD Hub verifier of one EPD made with Dawn AI (the tool). It tells you which files you get, how to show that they are the sealed files, and where each item of your check is.

Scope of the check

EPD Hub has pre-verified the tool: its LCA model, its fixed data and its menus. The verification agreement between Dawn and EPD Hub limits the check of each EPD to four items:

ItemWhat you checkWhere
1. Plausibility of the menu-governed inputsThe variable input data are plausible for the product, and inside the pre-defined menus and rangesEPD project report, sections 4–7. Free-variable reference.
2. OutputsThe results, the scenarios and the EPD agree with the inputsEPD project report, sections 10–12. EPD tables workbook.
3. "Additional information"The texts, the declarations of substances, and the information that the tool does not calculateEPD project report, sections 1, 3, 13 and Annex A. EPD Hub request.
4. Formal aspectsTool version, PCR, declared modules, data period, file integrityEPD project report, sections 2, 5 and 14. Fingerprints.

The tool model and the library data sets are outside this check. The tool version in the record shows which verified version made the EPD.

Files you get

FileName in the toolFormatFingerprint
Content of the recordFull recordJSONContent fingerprint (SHA-256 of the file)
EPD tablesEPD tables.xlsxWorkbook fingerprint (SHA-256 of the file)
EPD Hub requestEPD Hub requestJSONNone of its own. The same request is inside the content file.
EPD project report—.docxNone. It prints both fingerprints, and the result of the integrity check when it was made.
Digital EPDILCD tabILCD+EPDNone
Verification packageVerification package.zipNone of its own. It contains the content file and the workbook without a change, the EPD Hub request, the ILCD+EPD data set, the review history (review.json) and a README file.

The record has a number, EPD-year-sequence, for example EPD-2026-0003. Each file belongs to one record number.

Recompute the fingerprints

The tool calculates a SHA-256 fingerprint of the content file and of the workbook when it seals the record. You can calculate the fingerprints again on your own computer.

CAUTION: Do not open and save the files before you calculate the fingerprints. An editor that saves the file changes its bytes, and the fingerprint then does not agree. Do not format or re-indent the JSON file.

  1. Download the files. Keep them unchanged.
  2. Calculate the SHA-256 of each file:
    • Windows PowerShell: Get-FileHash -Algorithm SHA256 <file>
    • Windows command prompt: certutil -hashfile <file> SHA256
    • macOS: shasum -a 256 <file>
    • Linux: sha256sum <file>
  3. Compare the result of the content file with the content fingerprint in section 14 of the EPD project report.
  4. Compare the result of the workbook with the workbook fingerprint in section 14 of the EPD project report.
  5. Open the workbook, sheet EPD record. Read the value "Inputs and results fingerprint (SHA-256)". For a record with schemaVersion 2, compare it with record.inputsAndResultsHash in the content file. For schemaVersion 1, compare it with the result of step 3.

If all fingerprints agree, the files are the sealed files. Letter case does not matter: the tool writes lower-case hexadecimal.

NOTE: The content file is JSON with sorted keys and no spaces. The tool calculates the fingerprint from the bytes of this text in UTF-8. Another JSON program can write the same data with different bytes, for example a different number format. Always calculate the fingerprint of the downloaded file, not of a re-written copy.

Content of the record file

KeyContent
schemaVersionThe version of the record format. Version 2: the record is sealed when the internal reviewer approves the EPD. Version 1: a user sealed it on demand.
recordEPD number, product, variant, date of sealing, code version. Version 2 adds who submitted the EPD and when (submittedBy, submittedAt), who approved it (reviewedBy), the record that it replaces (replaces) and the inputs and results fingerprint (inputsAndResultsHash).
toolVersionTool version, PCR, LCA settings, release note, status, verifier, verification reference, verification date, "Valid until"
declaredUnitThe declared unit (unit: "unit", "m2" or "kg"), whether the PCR sets it (lockedByPcr), the width and height (widthM, heightM) and the mass (itemMassKg) of one produced item, and the number of declared units in one produced item (quantityPerItem).
productsVersion 2: one entry for each product of the EPD. Each entry has the name, the SKU, declared (true for the product that the request and the EPD tables come from), inputs, results and resourceUse.
inputsVersion 1 only, and in each entry of products: the product model at submission. These are the assembly, its parts and sub-assemblies, the calculation settings and the end-of-life inputs.
resultsVersion 1 only, and in each entry of products: the results per module and the inventory of each input (lciByPart)
epdHubSubmissionThe EPD Hub request (submission), the issues open at submission (issues) and the field counts (summary)
ilcdInputVersion 2: the input of the ILCD+EPD data set, locked at submission

The values in products are per produced item, as calculated. The values in epdHubSubmission and ilcdInput are per declared unit: the tool divides each amount by declaredUnit.quantityPerItem. In the workbook, only the sheet Declared unit is per declared unit. It shows the conversion and the results that the EPD declares. All other sheets are per produced item, and the sheet EPD record says so.

To compare the EPD Hub request with the sealed request, compare it with epdHubSubmission.submission in the content file.

Read the EPD project report

The tool makes the EPD project report from the sealed record. It follows the content of the EPD Hub background report template. Each number comes from the sealed record, except the numbers marked "derived" (sums and shares).

SectionTitleUse it for
1General informationManufacturer, programme operator, standard, PCR
2Tool, tool version and verificationFormal aspects: the tool version and its verification
3Goal and scopeIntended application and audience, data period
4Declared unit and conversionDeclared unit, mass per declared unit, the width, height and mass of one produced item, the number of declared units in one produced item, packaging, material content
5System boundary and declared modulesDeclared modules and their information modules, system model of each input
6Inputs per modulePlausibility of each variable input: value, unit, data set
7Scenarios A4–D and reference service lifeScenario information of EN 15804+A2 Tables 10–15, and the RSL
8Allocation and cut-offAllocation, cut-off rules, production-loss model
9Data qualityData quality assessment and scores of the data sets
10ResultsAll indicators per module. "ND" for a module that is not declared.
11Main driversThe three largest inputs per core indicator, with their share. The contributions are per produced item.
12Mass balanceProduct mass, material content and end-of-life flows
13LimitationsThe issues open when the EPD was submitted for review
14Record fingerprints and integrity checkThe two fingerprints and the result of the integrity check
Annex AContent not supplied by the toolEach item that the practitioner completes

Two markers show content that the tool does not supply:

  • "To be completed by the LCA practitioner." The manufacturer or the practitioner adds this content. Examine it as "additional information".
  • "Not in the sealed record." The record format does not contain this content yet. Ask the manufacturer for it.

Suggested order of the check

  1. Recompute the fingerprints (formal aspects).
  2. Read sections 2 and 5: tool version, PCR and declared modules (formal aspects).
  3. Read section 13 and the issues in the content file. Ask the manufacturer about each open issue.
  4. Read sections 6 and 7 against the free-variable reference (plausibility of the inputs).
  5. Read sections 10 and 11. Compare the main drivers with the drivers in the tool project report (outputs).
  6. Compare the EPD Hub request and the ILCD+EPD with section 10 (outputs).
  7. Read the texts and Annex A ("additional information").
  8. Ask the manufacturer for the evidence of each input that you cannot accept from the report.

The manufacturer keeps the review record of the internal four-eyes review. You can ask for it. The review history of the tool is in review.json of the verification package. See the reviewer checklist.

Subscribe to our newsletter