Express + expert help

View pricing →
Skip to main content
guideCRA, MDR, RED, LVD, EMC, MachineryReg6 min read

Risk assessment for CE compliance — methodology overview and standards reference

How to document product-specific safety and cybersecurity risks, choose methods within their verified scope, and connect risk controls to conformity evidence.

By Vladimír VicianUpdated

Fact-checked against the law as of Reviewed by Vladimír Vician on How we check

A risk assessment supports the manufacturer's conformity claim by explaining what can go wrong, how risks are reduced and what evidence shows the controls work. A completed template without product-specific engineering evidence is insufficient.

Start with scope and application dates

Identify intended use, users, foreseeable misuse, interfaces, energy sources and the product configuration being assessed. Separate the safety, radio, chemical and cybersecurity requirements that apply.

Product or obligationRelevant starting pointTiming and scope check
Radio equipmentRadio Equipment Directive 2014/53/EU, Article 21 and Annex V: the technical documentation must show how the Article 3 requirements are met. The express wording "adequate analysis and assessment of the risk(s)" is in Annex III, for EU-type examinationCheck which Article 3 requirements apply and which Article 17 route you use
Electrical equipment and apparatus outside the Radio Equipment DirectiveLow Voltage Directive 2014/35/EU, Annex III, point 2 and EMC Directive 2014/30/EU, Annex II, point 3: the technical documentation must include an adequate analysis and assessment of the risksThese Directives are not cited separately for radio equipment
Machinery placed on the market before 20 January 2027Machinery Directive 2006/42/EC, Annex I: a risk assessment is required and its documentation belongs in the Annex VII technical fileThe Directive applies until 19 January 2027
Machinery from 20 January 2027Machinery Regulation (EU) 2023/1230, Annex III, with the risk assessment documentation in the Annex IV technical documentationThe Regulation applies from 20 January 2027
Medical devicesMDR, Regulation (EU) 2017/745, Annex IRisk management is a lifecycle obligation. Devices covered by the MDR are outside the scope of the Cyber Resilience Act
Products with digital elementsCyber Resilience Act, Regulation (EU) 2024/2847, Article 13(2) to (4) and Annex IThe risk assessment duty applies to products placed on the market from 11 December 2027. Article 14 reporting has applied since 11 September 2026
Consumer products that are not subject to Union harmonisation legislationRegulation (EU) 2023/988, Article 9: an internal risk analysis and technical documentationArticle 9 sits in Chapter III, Section 1, which Article 2(1) disapplies for products under Union harmonisation legislation, so it does not apply to a CE-marked product. The Regulation does not provide for CE marking

The Commission's machinery overview explains the transition from the Directive to the Regulation. Apply each act to the units it covers, and check its transitional provisions. Machinery placed on the market before 20 January 2027 stays under the Directive. Under the Cyber Resilience Act, Article 69, products placed on the market before 11 December 2027 become subject to its requirements only if they are substantially modified from that date, although Article 14 reporting applies to them regardless.

The Commission's Blue Guide 2022, section 4.3 explains what an adequate analysis and assessment of the risks means in practice: identify all possible risks of the product, determine which acts and essential requirements apply, document that analysis in the technical documentation, and document how each identified risk is addressed, for example by applying harmonised standards.

Choose a method within its verified scope

EN ISO 12100 is a machinery risk-assessment and risk-reduction reference. ISO 14971 addresses medical-device risk management. For EU presumption of conformity, check the applicable European edition, amendments and OJ citation rather than treating an ISO catalogue entry as proof of harmonisation.

For radio cybersecurity, check the actual EN 18031 part and its restrictions through the Commission's RED standards list. A RED citation does not automatically cover CRA Annex I. Electrical-safety references such as EN 62368-1 also require a product-scope and edition check.

These standards do not all use the same risk scales or acceptance rules. Read the licensed text before claiming to follow a specific procedure, and do not assume that a standard prescribes a numerical scoring scheme or an acceptance threshold unless its text says so. The Commission explains the general role of harmonised standards.

NIST SP 800-30, threat modelling and other security methods can support the engineering analysis. Their use alone does not establish EU presumption of conformity.

A practical evidence record

The following fields are an editorial working structure, rather than the mandated table of any standard:

  1. Product boundary: model, hardware and firmware versions, interfaces, associated remote processing and operating assumptions.
  2. Hazard or threat: the affected asset or person, initiating conditions and relevant requirement.
  3. Evaluation: the selected method, defined scales where used, evidence and uncertainty behind the estimate.
  4. Control: design protection, implementation reference and responsible owner. Information for use does not substitute for required design protection.
  5. Verification: report, configuration, result and evidence that the implemented control addresses the identified risk.
  6. Residual risk: remaining exposure, the manufacturer's reasoned decision and any required user information.
  7. Change trigger: the events that require the analysis and evidence to be revisited.

Keep uncertainty visible. A laboratory test, code review or field record that has not been performed belongs in the evidence plan, not in the completed-results column. An auditor's preference is not a substitute for the applicable legal requirements or justified acceptance criteria.

Connect the record to the Technical File

Link the assessment to the product description, applied standards, design controls and test reports in the Technical File. Keep versioned links to the firmware release, SBOM where relevant, instructions and declaration. The section numbering in a team's folder structure is an organisational choice; use an act-by-act coverage checklist for the actual annex requirements.

A connected machine needs a scope analysis across the applicable acts. Do not automatically cite the Low Voltage Directive for every machine, or the Low Voltage Directive and the EMC Directive for radio equipment: the sector act determines how those safety and EMC objectives are addressed. For radio equipment, Article 3(1) of the Radio Equipment Directive 2014/53/EU covers both.

Common gaps to resolve

  • A generic hazard list without the assessed product configuration.
  • Numerical scores without defined scales or supporting reasoning.
  • Claimed controls without implementation or verification evidence.
  • A standard name without its edition, OJ scope and restrictions.
  • No documented residual-risk decision or required user information.
  • A firmware change that breaks traceability to the existing assessment.
Explore Cenitia’s compliance workflow

Review the supported scope and workflow

FAQ

Frequently asked questions

  • Is a risk assessment required for CE marking?

    It depends on the act. The Low Voltage Directive 2014/35/EU (Annex III, point 2) and the EMC Directive 2014/30/EU (Annex II, point 3) require the technical documentation to include an adequate analysis and assessment of the risks. The Radio Equipment Directive 2014/53/EU uses the same wording in Annex III, for EU-type examination; its Annex V list of technical documentation does not mention it, but the Commission's Blue Guide expects the risk analysis to be documented in the file in every case. Machinery law requires a documented risk assessment, and the MDR requires risk management throughout the device lifecycle. The Cyber Resilience Act, Article 13(2), requires a cybersecurity risk assessment for products placed on the market from 11 December 2027. A risk analysis under the General Product Safety Regulation does not create a CE-marking obligation.

  • Must I use a harmonised standard as my risk-assessment method?

    Harmonised standards are generally voluntary. A cited edition can provide presumption of conformity only for the requirements it covers and subject to its OJ restrictions. Other solutions need adequate evidence and may affect the available conformity-assessment route. Use the licensed standard to check its actual method; do not infer a prescribed scoring system from this overview.

  • Can EN 18031 automatically establish CRA conformity?

    No. EN 18031-1, -2 and -3:2024 are cited in the Official Journal under the Radio Equipment Directive 2014/53/EU, for the cybersecurity requirements of Article 3(3)(d) to (f), and with restrictions. They can inform the evidence plan for the Cyber Resilience Act, but a citation under the Radio Equipment Directive does not create a presumption of conformity with the Cyber Resilience Act. Check the part, the edition, the restrictions and the requirements it covers before relying on it.

  • Can software prepare the risk assessment for me?

    Software can help organise a working draft and link evidence. Engineers must establish the actual architecture, hazards, exposure, controls, tests and residual risks. Cenitia output needs a product-specific review before it supports an issued conformity claim.

  • When should the assessment be reviewed?

    Review it when design, firmware, intended use, operating conditions, applicable requirements or new field evidence may affect the analysis. Record the impact decision and connect the assessment to the exact product and firmware versions. A newly published standard prompts an applicability review; it does not automatically invalidate every product already placed on the market.

Continue reading

Related guides

Put this into practice

Free tools & references

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.