Readiness report — worked example

Illustrative example. This is not a client report, not real client data, and not a legal finding. It uses the cement demonstration product to show the shape a readiness report takes.

A readiness report answers one question for a catalogue: for each declared characteristic, is there evidence that a machine can read, and is that evidence bound to a published data dictionary entry?

Readiness score

out of 100

Each applicable characteristic counts one point when Ready, half a point when it needs work, none when the evidence is missing; characteristics that do not apply are left out of the count entirely.

Every finding here is validated against the PDTs.pt data dictionary — the national dictionary published for the Portuguese market — and not against a model we invented. A characteristic is Ready only when its declared value is bound to a published dictionary entry that anyone can look up.

Readiness by family and product

Product family	Product	Characteristics assessed	Readiness
Cement · EN 197-1:2011	AURORA CEM II/B-L 32,5 N	16	44%

A real report covers every family in the catalogue. This example has one product, so there is one row.

Findings

Required means an obligation that applies today. Expected means an obligation we anticipate from published drafts, where the timing can still move — it is not a requirement yet. Best practice is neither: it is what makes the data usable.

Characteristic	Status	Evidence found	Evidence missing	Why it matters	Recommended action	Regulatory status
Constituents and composition	Ready	Declared in the DoP as CEM II/B-L, bound to the dictionary entry for cement constituents and composition.	—	The composition is what the product is; every downstream system keys off it.	Nothing. Keep the binding when the declaration is revised.	Required (in force now)
Compressive strength (early and standard)	Ready	Declared as 32,5 N, bound to the dictionary entry for early and standard compressive strength.	—	The strength class is the characteristic specifiers select on.	Nothing.	Required (in force now)
Setting time	Warning	Declared, bound to the dictionary entry, with the value written as a statement of conformity.	The measured figure and its unit.	A conformity statement cannot be compared, filtered or checked by a system; a figure in minutes can.	Carry the measured value from the factory production control record into the declaration alongside the conformity statement.	Required (in force now)
Soundness (expansion)	Warning	Declared and bound to the dictionary entry, again as a statement of conformity.	The measured expansion in millimetres.	Same reason: a value a machine can read is worth more than a word it cannot.	Add the measured figure.	Required (in force now)
Sulfate content (SO₃)	Warning	Declared and bound, as a statement of conformity.	The percentage by mass.	Chemical limits are the characteristics most often re-checked downstream.	Add the measured percentage.	Required (in force now)
Chloride content (Cl⁻)	Warning	Declared and bound, as a statement of conformity.	The percentage by mass.	Chloride content governs use in reinforced concrete.	Add the measured percentage.	Required (in force now)
Insoluble residue	Warning	Declared as NPD (no performance determined), bound to the dictionary entry.	A performance value, if one is determined.	NPD is a legitimate declaration, but it carries no data, and a buyer asking for the figure will ask you rather than the file.	Decide deliberately whether NPD is the intended position for this product, and record why.	Required (in force now)
Loss on ignition	Warning	Declared as NPD, bound to the dictionary entry.	A performance value, if one is determined.	Same as above.	Same as above.	Required (in force now)
Environmental indicators (EN 15804+A2 core set)	Ready	An EPD covering A1–A3 for a declared unit of 1 t, with each core indicator bound to a dictionary entry.	—	Environmental characteristics can only be declared where an EPD exists; here one does.	Keep the EPD in date and re-bind the indicators when it is renewed.	Expected (anticipated, timing may move)
Life cycle stages beyond A1–A3	Missing	—	Modules A4–A5, B, C and D.	Cradle-to-gate answers part of the question; whole-life questions from designers need the later modules.	Scope the extension with the EPD programme operator at the next renewal.	Expected (anticipated, timing may move)
Unique product identifier and data carrier	Missing	—	A persistent identifier for the product and a carrier (QR or equivalent) that resolves to it.	Without an identifier that resolves, nothing downstream can point at this product unambiguously.	Assign identifiers per product model and place the carrier on delivery documentation first, packaging second.	Expected (anticipated, timing may move)
Economic operator identifier	Missing	The company name and address on the declaration.	A registered operator identifier (for example an EORI or VAT number) recorded as data.	A name is not an identifier: two companies can share one, and none of them resolve.	Record the identifier once, at company level; it does not change per product.	Expected (anticipated, timing may move)
Machine-readable declaration (DoPC)	Warning	A structured declaration can be generated from the bound characteristics.	A published, versioned copy that a customer can fetch.	A declaration written for a person to read is opaque to everything else.	Publish the structured declaration alongside the human-readable one and version it with the product.	Expected (anticipated, timing may move)
Substances of concern	Missing	—	A recorded position on substances of concern for this product.	It is among the information the passport is expected to carry, and it takes longest to assemble.	Start the assessment now; it depends on supplier information you do not control.	Expected (anticipated, timing may move)
Access tiers on commercially sensitive data	Warning	All declared characteristics are public, which is correct for a declaration.	A decided position on which supporting evidence stays restricted.	Deciding this late tends to mean either over-sharing or publishing nothing at all.	Mark supporting certificates and test reports restricted before publication, not after.	Best practice
Integrity of the published declaration	Missing	—	A hash or signature over the published content.	It is what lets a recipient show that the copy they hold is the copy you issued.	Hash and sign at publication; it costs nothing per version once it is set up.	Best practice
Identifier granularity (model, batch or item)	Not applicable	—	—	This declaration describes a product model, which is the right granularity for a cement. The finer granularities are a separate decision, and not one this product needs.	No action.	Not applicable

Constituents and composition

ReadyRequired (in force now)

Evidence found: Declared in the DoP as CEM II/B-L, bound to the dictionary entry for cement constituents and composition.
Evidence missing: —
Why it matters: The composition is what the product is; every downstream system keys off it.
Recommended action: Nothing. Keep the binding when the declaration is revised.

Compressive strength (early and standard)

ReadyRequired (in force now)

Evidence found: Declared as 32,5 N, bound to the dictionary entry for early and standard compressive strength.
Evidence missing: —
Why it matters: The strength class is the characteristic specifiers select on.
Recommended action: Nothing.

Setting time