How to Check a Construction Product Declaration Before Material Approval: DoP / DoPC Buyer Checklist
A construction-product declaration should not be accepted simply because the supplier has attached an official-looking PDF.
For procurement, the real question is:
Does this declaration apply to the exact product being proposed, and does the declared performance actually satisfy the project requirement?
Declaration-review rule: a PDF can be genuine and still be irrelevant to the product or inadequate for the project. Confirm the applicable route, exact product, intended use, technical basis and declared performance before material approval.
The Declaration of Performance has been a core part of the EU Construction Products Regulation framework, providing information about product performance. Under the newer Regulation (EU) 2024/3110, the framework also introduces the Declaration of Performance and Conformity. During the current transition, buyers may encounter documentation operating under outgoing and newer CPR routes, so the applicable framework and technical basis should be confirmed before judging a document simply by its format.
A practical procurement review should follow this sequence:
Declaration Received
↓
Confirm Applicable Framework
↓
Confirm Exact Product
↓
Check Technical Basis
↓
Extract Declared Performance
↓
Compare With Project Specification
↓
Cross-Check Other Documents
↓
PASS
Proceed to material approval.
HOLD
Clarify missing or inconsistent evidence.
FAIL
Do not approve, or raise a formal technical deviation.
The key principle is:
Document Exists ≠ Product Meets Specification
Step 1: Identify Which Declaration Framework Applies
Do not begin by comparing the supplier's document with a random declaration template found online.
This declaration review follows the upstream CE Marking Verification for Construction Products workflow and sits inside the broader Construction Product Certification for Procurement evidence chain.
First establish the context.
Record:
- Product Category
- Intended Use
- Applicable Technical Specification
- Declaration Type
- Document Date
- Document Revision
- Applicable Assessment Route
You may encounter references to:
- Declaration of Performance — DoP
- Declaration of Performance and Conformity — DoPC
- Harmonised Technical Specifications
- European Technical Assessment routes where relevant
The newer CPR requires a Declaration of Performance and Conformity to express product performance in relation to essential characteristics according to the relevant harmonised technical specifications or European Assessment Document.
The procurement question is therefore:
Which regulatory and technical route applies to this particular product?
If that cannot be established:
HOLD
Ask the supplier to identify the applicable basis before continuing.
Step 2: Confirm the Exact Product Identity
This is the first hard verification gate.
Check:
- Manufacturer
- Brand
- Product Name
- Product Type
- Model
- Product Code
- Product / Type Identification
- Intended Use
- Manufacturing Location where relevant
Then compare these against:
- Supplier Quotation
- Product Datasheet
- CE Information
- Material Submittal
- Sample Reference
For example:
Supplier Quotation
Model X100
Datasheet
Model X100
Declaration
Model X200
The declaration may be genuine.
But it does not clearly support the product you are buying.
Status:
HOLD — Product identity mismatch
Do not accept:
“X200 is almost the same product.”
Ask the supplier to demonstrate why the declaration covers X100 or provide the correct document.
A genuine declaration for another product is not evidence for the proposed product.
Step 3: Check the Intended Use
Product identity alone may not be enough.
A product can belong to the same family but be assessed for a different intended use.
Compare:
Declared Intended Use
with:
Project Application
For example:
| Item | Supplier Declaration | Project |
|---|---|---|
| Product | Product A | Product A |
| Intended Use | Application X | Application Y |
| Result | Clarify | |
The question is:
Does the declared intended use correspond to how the product will actually be used on this project?
If the answer is unclear:
HOLD
Do not continue based only on the product name.
Step 4: Confirm the Technical Basis
The declaration should identify the technical basis used for assessing and declaring performance.
Depending on the applicable route, this may involve:
- a harmonised technical specification;
- a harmonised standard;
- a European Assessment Document;
- an ETA-related route.
The European Commission describes harmonised standards as part of the common technical framework used to assess and communicate construction-product performance, while the EOTA route provides a path for products outside relevant harmonised-standard coverage.
Record:
- Technical Reference
- Product Scope
- Relevant Version / Date
- Intended Use Relationship
Do not use this logic:
“It contains an EN number, therefore it is correct.”
Instead ask:
Does this technical reference actually apply to this product and intended use?
If unclear:
HOLD
Use current official technical resources rather than guessing from the product category.
Step 5: Review Assessment and Third-Party Information
Construction products do not all require the same level of third-party involvement.
Under the existing CPR framework, the Assessment and Verification of Constancy of Performance system defines different levels of manufacturer and third-party involvement depending on the product, product family and essential characteristic.
Therefore, do not apply a universal rule such as:
“Every declaration must show a notified-body certificate.”
Instead check:
- Assessment / Verification System
- Is notified-body involvement applicable?
- Notified Body Number, where relevant
- Certificate / Assessment Reference
- Third-Party Role
Possible outcomes:
Third-Party Involvement Not Required
Record:
N/A
Required and Clearly Identified
Continue.
Required but Unclear
HOLD
A deeper notified-body check can then be completed through the relevant official database. The European Commission identifies notified bodies as recognised third parties for construction-product assessment activities.
Step 6: Find the Declared Performance
This is the core of the document review.
Do not stop at:
DoP received ✓
Extract what the manufacturer has actually declared.
For example:
| Characteristic | Declared Result |
|---|---|
| Characteristic A | Class 3 |
| Characteristic B | 1.5 W/m²K |
| Characteristic C | NPD / Not Declared |
| Characteristic D | Pass |
Create a working list containing:
- Characteristic
- Value
- Class
- Level
- Category
- Not Declared / NPD where shown
- Relevant Assessment Reference
The declaration exists to communicate performance information; therefore the procurement value comes from reading that performance, not simply filing the PDF.
Step 7: Decide Which Characteristics Matter to the Project
A declaration may contain many characteristics.
Procurement does not need to treat every line as equally important.
Start with the project requirement.
Use:
- Project Specification
- Drawings
- Material Schedule
- Consultant Requirements
- Client Requirements
- Applicable Technical Requirements
Then classify each characteristic as:
Mandatory
Failure prevents approval.
Relevant
Needs technical review.
Not Required for This Project
Reference only.
This converts a regulatory document into a procurement decision tool.
Project Requirement vs Declared Performance Matrix
Build a comparison table.
Where declared values or classes affect supplier technical compliance, record the result in the Technical Bid Evaluation Template instead of leaving the finding inside a standalone PDF review.
| Characteristic | Project Requirement | Declared Performance | Status |
|---|---|---|---|
| Characteristic A | ≥ X | Y | PASS |
| Characteristic B | Class 3 | Class 2 | FAIL |
| Characteristic C | Required | NPD | HOLD |
| Characteristic D | Not required | Declared | N/A |
Use only three main procurement outcomes.
PASS
Declared performance satisfies the requirement.
HOLD
Information is incomplete, unclear or needs technical confirmation.
FAIL
Declared performance clearly falls below the specification.
This table is more valuable to procurement than a simple:
Declaration Received: Yes / No
How to Handle NPD or Missing Performance
If a required characteristic appears as:
NPD / Not Declared
do not automatically write:
Non-compliant.
First ask:
Does the project require a declared value, level or classification for this characteristic?
If the Project Does Not Require It
Record:
N/A
If the Project Requires It
Record:
HOLD
Then request:
- clarification;
- additional evidence;
- technical review;
- updated documentation where appropriate.
The key is to connect the declaration to the actual project requirement.
Step 8: Check Who Is Taking Responsibility for the Declaration
Where applicable, review identifying and responsibility information such as:
- Manufacturer
- Authorized Representative where relevant
- Responsible Entity
- Declaration Reference
- Date
- Signature / Authorization Information
You do not need to turn this into a corporate-law investigation.
The procurement question is simpler:
Can we clearly identify the manufacturer or responsible entity behind this declaration?
If the declaration names Manufacturer A but the proposed product is sold as Manufacturer B:
HOLD
Resolve the relationship before approval.
Step 9: Cross-Check the Declaration Against Other Documents
Never review the declaration in isolation.
Create a consistency matrix.
| Field | Declaration | Datasheet | CE Information | Material Submittal |
|---|---|---|---|---|
| Manufacturer | ABC | ABC | ABC | ABC |
| Model | X100 | X100 | X100 | X100 |
| Intended Use | A | A | — | A |
| Technical Reference | EN xxx | EN xxx | EN xxx | EN xxx |
| Performance | Class 3 | Class 3 | Reference | Class 3 |
| Revision | 02 | 02 | — | 02 |
Look for:
- Model mismatch
- Manufacturer mismatch
- Different technical references
- Different performance claims
- Different revisions
- Test reports referring to another product
If one critical document says:
Class 3
and another says:
Class 2
do not choose the more convenient number.
HOLD
Ask the supplier to explain and correct the evidence.
A complete document package still fails if the documents describe different products.
Step 10: Check Supporting Evidence References
A declaration may refer to:
- Test Reports
- Certificates
- Assessment Reports
- ETA
- Notified Body
- Technical Documentation
You do not need to perform a full audit of every supporting document at this stage.
But confirm that referenced evidence is:
- identifiable;
- relevant;
- associated with the same product;
- consistent with the declared result.
If the declaration claims a performance value based on a test report for another model:
HOLD
The declaration and supporting evidence are not sufficiently connected.
Declaration Review Checklist
Use this before releasing the declaration into the material-approval package.
Use the Construction Material Submittal Checklist to make the correct declaration, technical references and supporting evidence part of the formal approval package requirements.
Framework
- Applicable declaration framework identified
- Declaration type understood
- Technical route identified
Product
- Manufacturer matches
- Product model matches
- Product code matches
- Intended use matches
- Supplier proposal matches
Technical Basis
- Technical specification identified
- Product scope appears relevant
- Assessment route understood
- Notified body addressed where applicable
Performance
- Project-required characteristics identified
- Declared values / classes extracted
- NPD / missing items identified
- Performance compared with specification
Consistency
- Datasheet matches
- CE information matches
- Material submittal matches
- Supporting evidence references align
Final Status
PASS
HOLD
FAIL
Declaration Review Decision Gate
Use this workflow:
Declaration Received
↓
Applicable Framework / Technical Route Clear?
NO
→ HOLD
YES
↓
Correct Manufacturer / Product / Intended Use?
NO
→ HOLD or REJECT if clearly unrelated
YES
↓
Technical Basis Relevant?
NO
→ HOLD
YES
↓
Required Performance Declared?
NO
→ CLARIFY
YES
↓
Declared Performance Meets Specification?
NO
→ FAIL / Technical Deviation Review
YES
↓
Documents Consistent?
NO
→ HOLD
YES
↓
DECLARATION REVIEW PASSED
↓
Proceed to material approval.
What If the Product Almost Meets the Specification?
Procurement should not silently convert a failed technical requirement into an approval.
Example:
Specification
Class 3
Declared Performance
Class 2
Do not mark:
“Close enough.”
Instead create a:
Technical Deviation
Record:
- Specified Requirement
- Declared Performance
- Difference
- Supplier Explanation
- Technical Reviewer
- Consultant / Client Decision
Procurement's responsibility is to identify the deviation.
The technical authority should decide whether the exception is acceptable.
Declaration Passed Does Not Mean Material Approved
A successful declaration review means:
A passed declaration review should then move into the Construction Material Submittal Process for formal project review rather than being treated as final approval.
The declaration appears relevant to the proposed product, the reviewed performance is acceptable against the identified requirements, and the documentation is sufficiently consistent to continue.
The product may still require:
- Other Certifications
- Test Reports
- Shop Drawings
- Physical Samples
- Finish Approval
- Installation Information
- Consultant Review
- Client Approval
The correct workflow is:
Declaration Review Passed
↓
Complete Material Submittal
↓
Formal Project Review
↓
Final Material Approval
Common Declaration Review Mistakes
Checking Only Whether a Declaration Exists
Read the performance.
Accepting a Declaration for a Similar Product
Match the exact proposed product.
Ignoring Intended Use
Confirm that the declaration covers the actual application.
Assuming an EN Reference Is Automatically Correct
Confirm the technical basis.
Treating NPD as Automatic Failure
Compare it with the project requirement first.
Ignoring Differences Between Documents
Cross-check the declaration, datasheet, CE information and submittal.
Treating a Valid Declaration as Final Project Approval
The declared performance must still satisfy the specification.
Using One Old Template as the Universal Rule
The CPR framework is currently transitioning, so verify the applicable route and current official technical resources rather than judging every declaration against one historical template.
Where Declaration Review Fits in the Procurement Workflow
The wider construction-product verification process can be:
After approval, record the exact product, declaration reference and approved status in the Material Approval Register before PO / production release.
Supplier Proposed Product
↓
Verify CE Claim
↓
Review DoP / DoPC
↓
Verify Notified Body Where Required
↓
Compare Technical and Compliance Evidence
↓
Complete Material Submittal Checklist
↓
Formal Material Submittal
↓
Record Final Approval
↓
Release PO / Production
The declaration is therefore not just a compliance document.
It is one of the inputs to the project's technical purchasing decision.
Tools and Resources for Declaration Review
Construction procurement teams may need:
- EU CPR Official Resources
- Harmonised Technical Specification Resources
- Declaration Guidance
- NANDO
- ETA / EAD Resources
- Product Certification Databases
- Technical Document Tools
- Material Submittal Templates
Official CPR and technical resources help determine the applicable framework.
NANDO supports notified-body checks where relevant.
Document comparison tools help cross-check product identity and technical information.
Material-submittal templates move the reviewed evidence into formal project approval.
Build Procurement Hub organizes these resources around the actual construction-product verification workflow so buyers can move from receiving a supplier declaration to deciding whether the declared product performance is suitable for material approval.
Read the Declared Performance — Not Just the PDF Title
Confirm the applicable framework and technical route, match the declaration to the exact product and intended use, extract the declared performance, compare it with the project requirement, resolve NPD or document inconsistencies, and only then move the evidence into material approval.
FAQ
What should a buyer check in a Declaration of Performance?
Check the manufacturer, exact product identity, intended use, applicable technical basis, assessment information and declared performance, then compare the relevant performance with the project specification.
Is a Declaration of Performance enough to approve a construction product?
No. It is one part of the technical and compliance evidence. Drawings, certificates, samples, additional test evidence and formal project approval may still be required.
What should procurement do if a required characteristic is marked NPD?
Determine whether the project requires a declared value or class for that characteristic. If it does, hold approval and request clarification or additional evidence.
Can a declaration be valid but the product still fail material approval?
Yes. A declaration can be correctly issued while the declared product performance still falls below the project's technical requirement.
The core principle is:
The purpose of reviewing a construction-product declaration is not to confirm that a PDF exists. It is to verify that the declaration applies to the exact proposed product, follows the appropriate technical basis, and declares performance that actually satisfies the project requirement.
