Construction Products RegulationCPR technical file builder

Construction products

Construction Products Regulation (305/2011) is a core part of EU product legislation and is often linked to CE marking requirements.

Scope depends on product design, intended use, and how you place it on the market. Borderline cases happen alot, so xMarkings maps applicability from your product description instead of guessing from a category name.

Manufacturers are expected to maintain a technical file demonstrating how the product meets essential requirements and harmonized standards.

• Product description and drawings
• Risk assessment
• Applicable standards and test evidence
• Instructions and labeling
• EU Declaration of Conformity

xMarkings helps manufacturers structure Construction Products Regulation compliance with AI-assisted intake, checklists, and audit-ready document export.

Construction Products Regulation (305/2011) shows up on projects sooner than most teams expect. Someone mentions CPR in a customer questionnaire, or a Notified Body RFQ asks which essential requirements you cover. If you only have a short product description at that point, you are already behind.

Typical products include facade panels, insulation, and structural connectors for buildings. That list is not exhaustive. Borderline cases happen when one product combines radio, mains power, and moving parts. Then you stack directives and your technical file must show how requirements interact, not treat each in isolation.

We talk to manufacturers who assumed CPR was "handled by the supplier." Sometimes true for components, rarely true for the finished product you place on the market. Your name is on the DoC.

Directives state essential requirements in plain legal language. Harmonized standards give you a practical route to presume conformity if you meet them. Most teams design to standards because it is faster to explain to auditors.

You can comply without using harmonized standards, but then you need deeper justification in the technical file. That path is valid for novel tech, just more work.

Always cite the correct edition of each standard on the DoC. Using an withdrawn EN version is one of the fastest ways to fail a spot check.

Identity and intended use come first. Photos help. So does a clear statement of variants and accessories that ship together.

Design documentation includes schematics, mechanical drawings, and software version if behavior affects safety or radio performance. Bill of materials with supplier declarations for critical parts saves time later.

Risk assessment ties hazards to mitigations. For many products under this rule set, mechanical, electrical, thermal, and misuse scenarios all belong in one coherent narrative.

Test reports, calculations, and certificates from notified or accredited labs close the loop. If you rely on internal testing for some clauses, document methods and equipment calibration too.

Some products allow internal production control. Others force involvement of a Notified Body for type examination or quality system approval. Picking the wrong module invalidates the whole conformity path.

If a body is required, engage early. Their backlog and document expectations vary. Sending a messy file slows everyone down.

When no body is required, you still need discipline. Self-certification means you personally accept legal responsibility, not that work disappears.

Testing the golden sample while production uses different firmware or supplier parts. Auditors compare serial numbers.

Copy-pasting a risk assessment from another product without updating hazards. Reviewers notice generic text immediately.

Forgetting to update the DoC after a design change. The file and declaration must match the product you ship today.

Shipping to multiple EU countries without checking national transpositions or language rules for instructions.

Lab slots drive schedules more than paperwork. Book testing before you freeze tooling if possible.

Post-market surveillance is not optional paperwork. Track complaints, field failures, and regulatory updates that affect your standards list.

If authorities request the technical file, you typically have days to respond. Keep it indexed and searchable, not buried in a shared drive nobody maintains.

Procurement teams rarely read the full Construction Products Regulation text. They send a spreadsheet with yes/no columns. Can you show conformity? Can you share the technical file on request? Which standards did you test against? If you cant answer in one email, you lose the deal to someone who can.

Distributors also ask about serial number traceability. They want to know which firmware or hardware revision matches the test reports on file. That sounds picky until a market surveillance letter arrives and they forward it to you the same afternoon.

For the EU and EEA, language and labeling questions come up alot. Even when the product is technically compliant, missing local instructions can block customs or retail listing.

Start with a one-page product brief: intended use, power source, connectivity, and countries you plan to sell into. That drives directive mapping better than guessing from a category name on your web shop.

Next, freeze a BOM for compliance purposes. Production can iterate later, but the file you certify against needs a named configuration. When engineering swaps a capacitor or radio module, run a quick impact check instead of assuming "its minor."

Collect supplier declarations early for RoHS, REACH, and battery rules where they apply. Chasing a steel vendor for paperwork during shipment week is miserable.

Write the risk assessment while design is still active. Hazards you fix in CAD are cheaper than hazards you document around later.

Generate the Declaration of Conformity last, when the evidence list is stable. Signing early and changing hardware afterward creates legal drift that is hard to unwind.

Confirm the mark on the product matches the regulations cited on the DoC. CE, UKCA, UKNI, and other marks have placement rules. Double check artwork proofs.

Print or export the technical file index. Someone on your team should find any test report in under five minutes.

Verify user instructions match the shipped variant, including accessories in the box.

Store a photo record of label placement on the production unit, not only the design file.

If you use a notified or approved body, confirm certificate numbers on the DoC match the PDF they issued.

Brief customer support on what compliance documents they can share and what needs engineering review first.

We built xMarkings because most teams dont lack intelligence. They lack a single place to connect product facts, Construction Products Regulation requirements, standards, and evidence. Spreadsheets and shared folders work until they dont, usually right before audit season.

The product intake chat captures what marketing and engineering already know, then maps likely directives and document gaps. You still make the decisions. The platform keeps the trail.

Technical files get structure and version history. Risk assessments link to clauses. DoC exports pull from the same source so you are not retyping standard numbers by hand at midnight.

We are not a Notified Body and we wont sign your DoC for you. When third-party assessment is mandatory, we help you arrive prepared instead of apologizing for missing appendices.

If you want to pressure test the workflow, start a product and walk through the builder. A 7-day Pro trial is enough to see whether your team actually uses it or goes back to email chains.

Products rarely sit under one directive alone. A mains-powered radio device may need LVD, EMC, RED, and RoHS evidence in the same file. Each piece must be consistent about model numbers and firmware.

General Product Safety can still apply even when CE marks are present. Do not treat GPSD as optional background noise.

Environmental rules like WEEE registration and EcoDesign labels are separate from CE paperwork but show up in retailer onboarding. Plan them in parallel, not after launch.

Assign a document owner. Compliance files rot when everyone assumes someone else updates them.

When customers report field issues, log them against the risk assessment. If the hazard was not considered, update the file and evaluate whether conformity is still valid.

Before each new production run with material changes, diff the BOM against the certified configuration. Small supply chain swaps are where silent non-compliance starts.