Eight published workflows · Regulation (EU) 2024/2847

Start with the product.
Follow the obligation it enters.

Route a product with digital elements from scope and operator role through classification, product readiness, support, change control, and Article 14 reporting. Every completed Flow stays tied to the exact CRA interpretation used.

01Scope the offering

Identify the product boundary, Union-market connection, exclusion, and operator role.

02Open the right route

Move into classification, product readiness, supply-chain, lifecycle, or change work.

03Record reportable events

Use the Article 14 records when an exploited vulnerability or severe incident occurs.

CRA operational route

Eight jobs across the product lifecycle.

The family separates questions that are often collapsed into one checklist. Scope, product class, economic-operator role, post-market change, and incident reporting have different facts and consequences.

01
Start hereEuropean UnionBinding EU regulationGuided assessment

Scope and operator role

Is the offering a product with digital elements in CRA scope, and which economic-operator role is being assessed?

Screen the product, Union-market, connection, commercial-activity, exclusion, free-and-open-source, and economic-operator boundaries before opening specialist work.

CRA · Articles 2, 3, 18 and 21–24
02
ClassificationEuropean UnionBinding EU regulationDetermination

Product class and conformity route

Is the product in the default, important class I, important class II, or critical route, and which conformity path remains available?

Record the product’s core-function classification and the corresponding conformity-assessment route without treating an ancillary component as the whole product.

CRA · Articles 7, 8, 27 and 32; Annexes III, IV and VIII
03
Product readinessEuropean UnionBinding EU regulationCompliance checklist

Essential requirements

Is the implementation package assembled for product-specific review against the CRA essential cybersecurity requirements?

Create a management readiness record across product-security properties, risk assessment, documentation, vulnerability handling, remediation, updates, and disclosure arrangements.

CRA · Article 13 and Annex I
04
Supply chainEuropean UnionBinding EU regulationCompliance checklist

Importer and distributor readiness

Has the importer or distributor completed the required checks before placing or making the product available?

Record pre-market checks and escalation paths for non-conformity, significant cybersecurity risk, corrective action, and manufacturer cessation.

CRA · Articles 19 and 20
05
LifecycleEuropean UnionBinding EU regulationCompliance checklist

Support period and vulnerability handling

Is the support period reasoned, disclosed, documented, and backed by vulnerability-handling and security-update arrangements?

Record the manufacturer’s support-period rationale and the disclosure, remediation, coordinated-disclosure, update, and technical-documentation controls that operate during it.

CRA · Article 13(6)–(11) and Annex I Part II
06
Change controlEuropean UnionBinding EU regulationDetermination

Substantial modification

Does this post-market change affect conformity or alter the intended purpose strongly enough to trigger a new manufacturer route?

Assess a physical or software change against the CRA substantial-modification definition and record the resulting manufacturer and conformity-review consequences.

CRA · Articles 3(30), 13, 21 and 22
07
Report from 11 Sep 2026European UnionBinding EU regulationStandard form

Actively exploited vulnerability

Has an actively exploited vulnerability triggered the 24-hour, 72-hour, corrective-action, user-notice, and final-report sequence?

Record manufacturer triage and the Article 14 notification sequence, including the final report due no later than 14 days after a corrective or mitigating measure becomes available.

CRA · Article 14(1), (2), (7)–(8) and Article 24(3)
08
Report from 11 Sep 2026European UnionBinding EU regulationStandard form

Severe security incident

Does this incident meet the CRA severe-incident threshold, and has the Article 14 reporting sequence been recorded?

Assess the severe-incident threshold and record the 24-hour early warning, 72-hour notification, user communication, and final report due within one month after the incident notification was submitted.

CRA · Articles 3(42) and 14(3)–(8)

Important boundary

Structured CRA work, not conformity certification.

Each workflow captures a defined assessment or readiness record under its published sources and exact release. Use the first two routes before assuming that a specialist obligation or conformity path applies.

Completing a Flow does not itself establish CRA conformity, authorise CE marking, replace the required conformity-assessment procedure, or remove the need for product-specific legal, technical, and notified-body judgment where applicable.

Preparing a digital product for the EU market?

Start at scope. Keep every later product decision connected to the route behind it.

Run the first workflow →

Privacy preferences

Privacy policy