11. EPD records
How the EPD Generator seals an EPD record when the reviewer approves the EPD, what the record keeps, how the SHA-256 fingerprints protect it, and how to download the record files, the verification package and the EPD project report.
11. EPD records
A sealed EPD record keeps one EPD for good. It keeps the inputs and results of each product, the EPD tables, the EPD Hub request and the ILCD+EPD input. All come from your verified tool version. Nobody can change or delete a record. The verifier uses the record to examine the EPD.
When the tool seals a record
The tool seals the record when the reviewer approves the EPD (step 10). You do not seal a record yourself.
When you select Submit to reviewer, the tool:
- Examines the tool version and the data of each product of the EPD (the verified-data rule, see 1. Library and tool versions).
- Calculates each product again on the server. Values from the browser are not used.
- Locks the EPD Hub request and the ILCD+EPD input.
- Makes the EPD tables workbook (.xlsx) of the declared product from the same results. The workbook shows the "inputs and results fingerprint". This is a SHA-256 fingerprint of all that the tool locked.
- Keeps all of this until the reviewer approves or returns the EPD.
When the reviewer selects Approve, the tool:
- Writes the content of the record as one JSON file, from what it kept. It does not calculate again. The file contains the header, the tool version, the inputs and results of each product, the EPD Hub request and the ILCD+EPD input.
- Writes in the header who submitted the EPD, who approved it, when, and the inputs and results fingerprint.
- Calculates a SHA-256 fingerprint of the JSON file and of the workbook.
- Stores the tool version, the PCR and the code version. It gives the record an EPD number: EPD-year-sequence, for example EPD-2026-0003.
At the approval, the tool examines the tool version again. If your library moved to another tool version, or the version is no longer valid, the tool seals nothing. The reviewer then returns the EPD, and you submit it again.
Thus the record, the locked request and the reviewed results come from the same inputs. The record is linked to the EPD draft.
Before the tool gives a file of the record, it calculates both fingerprints again. If a fingerprint does not agree, the tool refuses the file.
If a condition of the verified-data rule is not true, the tool refuses the submission and lists each problem. Correct the problems and submit the EPD again.
NOTE: Older records have content schema version 1. A user sealed them with Create EPD in the EPD records dialog. They contain one product and no reviewer. That button is removed.
Record files
Each record in the dialog shows its EPD number, the date, the product, the tool version and the PCR. It also shows the first 12 characters of its fingerprint. It has these buttons:
| Button | File | Content |
|---|---|---|
| EPD tables | Workbook (.xlsx) | The results tables, the data quality sheets and the record sheet with the inputs and results fingerprint (the content fingerprint on records of schema version 1) |
| EPD Hub request | Dialog with the JSON request | The request to EPD Hub, as sealed |
| Full record | JSON file | The complete content of the record. Its SHA-256 is the content fingerprint. |
| Check fingerprint | — | Calculates both fingerprints again. "Unchanged since it was sealed" or "Changed after sealing". |
| Verification package | Zip file | The record (JSON), the EPD tables, the EPD Hub request, the ILCD+EPD data set, the review history and a README file. The README gives the approver and the tool version. |
The review panel on the EPD tab also has the Verification package button.
EPD project report
The tool makes the EPD project report from the sealed record, as a Word file (.docx). The report contains the tool version, the inputs of each module, the scenarios and the results. It also contains the main drivers, the data quality, the mass balance and the two fingerprints. The report marks each item that the tool cannot know with "To be completed by the LCA practitioner".
- Download the report. [INPUT NEEDED: the button is not in the EPD records dialog yet. Until it is, Dawn sends the report.]
- Complete each marked item.
- Give the report to the verifier with the verification package.
The verification package and the EPD project report come from the same sealed record. They do not replace each other:
- The verification package contains the sealed files without a change. The verifier uses them to calculate the fingerprints again and to read the data.
- The EPD project report is a document that the tool makes from these files. It explains the inputs, the scenarios and the results, and you complete the marked items. It shows the two fingerprints of the record.
The verification package does not contain the EPD project report.
The EPD project report is confidential. Give it to the verifier and EPD Hub only.
A new record for a changed EPD
To change an EPD after the approval, select Reopen for correction on the EPD tab and give the reason. Correct the input, and then submit the EPD for review again. The next approval seals a new record with a new EPD number. The new record replaces the old one. The old record stays unchanged.
Next step
Go to 12. Sending to EPD Hub.