The Declaration of Performance You Cannot Find: The Compliance-Evidence Gap in Construction Catalogs
Why construction distributors struggle to link Declarations of Performance, declared values, EPDs, and product variants—and how to audit the gaps.
A Declaration of Performance (DoP) is a manufacturer’s statement of a construction product’s declared performance against the applicable technical specification. Distributors may need to retrieve the right DoP for the right product. The recurring data failure is often not an absent document—it is that nobody can reliably link the document to the sellable SKU and variant.
This guide describes catalog and evidence operations, not legal advice. Whether a requirement applies, whether evidence is sufficient, and what action is required remain questions for qualified compliance specialists using the applicable law and standards.
The tender question that breaks the catalog
A specifier requests reaction-to-fire classifications and environmental product declaration data for 400 line items by Friday. The merchant sells 30,000 SKUs from 90 manufacturers. Documents exist across supplier portals, shared drives, email attachments, and PIM links—but the team cannot produce a current, variant-specific evidence pack.
The bottleneck is not PDF storage. It is product identity, evidence linkage, and coverage measurement. The same pattern appears whenever teams treat product compliance as a product-data problem first or try to populate a product-compliance evidence matrix.
What actually has to be linked
For a useful construction-product record, the chain may need to connect:
| Object | What the catalog must preserve | What must not be inferred |
|---|---|---|
| Product and variant | Manufacturer, product type, model or family, format, thickness, colour where relevant, identifiers, and market | That a family document necessarily covers every sellable variant |
| Declaration of Performance | Unique declaration reference, intended use, applicable technical specification, declared performances, issuer, version, and source | That possession of a DoP proves every downstream requirement is satisfied |
| Declared performance | For example reaction-to-fire class under EN 13501-1, thermal conductivity λ in W/(m·K), compressive strength, or water absorption—only where declared | A missing value or class from product category alone |
| Batch or production evidence | Batch, lot, date, or factory references when the evidence and workflow require them | That a current family-level file resolves a historical batch |
| EPD | Program operator, declaration number, product scope, EN 15804 basis where applicable, validity, declared or functional unit, and indicators such as GWP | That an EPD is a DoP or a CE-marking record |
A DoP, CE marking, EPD, and digital product passport are related to different purposes; they are not interchangeable documents. Maintaining that distinction is the same discipline explained in product-compliance readiness versus product certification. Reliable review begins with a product-identity-first compliance check and does not assume taxonomy alone determines compliance requirements.
Why the document repository does not solve it
A shared folder can prove that someone downloaded Supplier_A_DoP_2025.pdf. It does not prove which active SKUs the file covers, whether it supersedes another version, which declared value belongs to which variant, or which products still have no matched evidence.
That is why a compliance document repository is not enough. A useful system needs relationships among product, variant, manufacturer, supplier, document, claim, version, source, and review decision. The guide to building a product evidence graph turns those relationships into a reviewable model.
Variant granularity is where it fails
A DoP may refer to a product type or family while the customer purchases a particular format, thickness, finish, or other variant. Supplier codes in the PDF may differ from distributor SKUs; the family name may be abbreviated; and one source may omit the GTIN entirely.
Matching is therefore an entity-resolution problem before it is a filing problem. The workflow must compare manufacturer identity, MPN, GTIN, supplier code, product naming, dimensions, variant attributes, intended use, and document text. It must preserve ambiguity rather than attaching the nearest-looking PDF. Use the operational guide to matching compliance documents to the correct product variant.
The revised CPR and the construction digital product passport
The EU’s revised Construction Products Regulation is Regulation (EU) 2024/3110, published in the Official Journal on 18 December 2024. It establishes a framework for a construction digital product passport system, with implementation dependent on further acts and product-specific measures. Rather than guessing a single phase-in date for every product, teams should track the applicable measures and current official text with their compliance advisers.
The direction of travel is nevertheless clear: more product-specific information must be structured, accessible, and connected across a product’s record. A QR code or a folder link cannot compensate for broken identity and provenance. Catalog teams can prepare the data model now by understanding the digital product passport, connecting DPP readiness to product-data provenance, and running a passport-ready catalog audit.
A coverage audit you can run this month
- 1Inventory the in-scope catalogGroup active products by category, manufacturer, supplier, product family, and variant. Preserve identifiers and lifecycle status; do not begin from the document folder.
- 2Map the applicable evidence questionWith the responsible specialist, record which technical specification and evidence type may apply. Keep unknown and not-applicable states separate from missing.
- 3Find and version the documentsCollect current supplier sources, retain document identifiers and dates, and distinguish DoPs from EPDs, certificates, datasheets, and instructions.
- 4Resolve evidence to the variantMatch identifiers and product facts. Record match confidence, the supporting signals, conflicts, and whether human review is required.
- 5Score and assign the gapsReport coverage by supplier and category; send missing or ambiguous records to an owner; then re-check them whenever supplier data or documents change.
The supplier-documentation gap-report template provides the handoff, while the product-compliance readiness scorecard keeps unknown, missing, stale, and mismatched evidence distinct. Use a supplier data scorecard to make follow-up specific, then adopt continuous compliance-data monitoring so the audit does not become another aging snapshot. For broader preparation, see product-compliance data readiness and the product-compliance readiness glossary.
Before and after: from folder inventory to measurable coverage
| State | What the team knows | What happens next |
|---|---|---|
| Before | 30,000 SKUs; 90 suppliers; a shared drive; unknown variant-level DoP and EPD coverage | A tender triggers a manual search across folders and inboxes |
| After | Coverage percentage by supplier and category; document-to-variant match status; current, stale, missing, conflicting, and ambiguous evidence separated | Gaps have owners and due dates; affected matches are re-checked when feeds or source documents change |
The goal is not to automate the legal conclusion. It is to give the responsible specialist a complete, current, source-backed work package instead of a folder search. That is the foundation for a defensible compliance review and a more reliable tender response.
Compliance coverage audit
See which construction SKUs lack usable evidence
Book a demo to map supplier documents to products and variants, measure coverage, and route unresolved evidence to the right reviewer.
For distributors
Make supplier evidence operational
See how Claro turns changing multi-supplier files into matched, source-backed product records.
Claro
Stop maintaining this by hand
Claro keeps product and supplier data trusted as catalogs change — matching, deduplication, enrichment, and validated write-back into the systems you already run.
Book a demo