Express + expert help

View pricing →
Skip to main content
tutorialCEMark, EURLex, RED, CRA, AIAct5 min read

Official Journal monitoring for hardware compliance — a quarterly review workflow

A quarterly workflow for checking the Official Journal: which sources to read, what to record for each change, and how to turn a change into a product decision.

By Vladimír VicianUpdated

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

Official Journal changes can affect product scope, available conformity-assessment routes and the presumption of conformity attached to standards. The useful output is a reasoned product-impact decision, linked to the actual legal entry.

Sources to check

SourceWhat it establishesWhat to record
EUR-Lex Official JournalPublished legal acts and authentic OJ textIdentifier, publication date, amendment chain and annexes
EUR-Lex searchActs and document relationshipsSearch terms, review window and included/excluded results
Commission harmonised-standards pagesSector reference lists and links to implementing decisionsExact edition, covered requirements, restrictions and withdrawal dates
CEN-CENELEC catalogue and relevant ESO cataloguesStandard editions and publication statusEdition and amendments; publication alone is not an OJ citation

The legally authentic OJ is available through EUR-Lex. A consolidated text is useful for reading amendments together, but it has no legal effect; check the authentic acts and relevant dates when making the final decision. The Commission's summary lists of harmonised standards are also for information only.

Between reviews, EUR-Lex email and RSS alerts on the acts you rely on tell you when something changes; How to navigate EUR-Lex explains how to set them up.

Five change categories

New legislation

Read the scope, exclusions, application dates and transition. Identify products potentially affected before adding a new conformity claim. For example, CRA manufacturer reporting (since 11 September 2026) and the CRA product requirements (from 11 December 2027) have different application dates.

Amendments

Read what the amending act actually changes. Its publication or entry into force may differ from the date when a particular requirement applies. Preserve the original act and amendment references in the review record. Regulation (EU) 2026/1744 is an example: it was published on 24 July 2026 and entered into force on 27 July 2026, and what it changes for hardware is a set of later dates — the AI Act high-risk rules now apply from 2 December 2027 for Annex III systems and from 2 August 2028 for AI in Annex I products.

Standards-reference decisions

Check the exact edition cited, the requirements covered and any restrictions. An ESO publication is not enough to establish presumption of conformity. A citation under RED does not automatically give CRA presumption. Commission Implementing Decision (EU) 2026/2003 of 4 September 2026, published on 7 September 2026, is an example: it amends the list of harmonised standards for radio equipment in Decision (EU) 2022/2191, and EUR-Lex shows its changes taking effect on 7 September 2026 and 7 March 2028.

Withdrawals and restrictions

Record the date of withdrawal or cessation and evaluate the remaining evidence. A standard citation does not guarantee that all essential requirements are covered, and transition periods differ from one change to the next. Review newly placed units and previously placed units against the applicable act and transition.

Delegated and implementing acts

Check the act's legal basis and its concrete effect on scope, technical descriptions, procedures or timing. For RED cybersecurity, examine both Delegated Regulation (EU) 2022/30 and its repeal by Delegated Regulation (EU) 2026/339. The repealing act was published on 29 April 2026, and the repeal takes effect on 11 December 2027. This concerns the delegated cybersecurity requirements; the RED itself continues to apply.

A quarterly review record

For a chosen quarter, search the date window and relevant acts, then verify every candidate against the published entry. A row should contain:

  • Act identifier and primary-source link.
  • Publication, entry-into-force, application and withdrawal dates, keeping their meanings distinct.
  • The exact provision, standard edition or restriction changed.
  • Affected product models, configurations, markets and units.
  • Required evidence review, assessment-route decision and action owner.
  • Reviewer, decision date, due date and completion evidence.

A review of April–June 2026, for example, uses a publication window of 2026-04-01 to 2026-06-30. Delegated Regulation (EU) 2026/339 falls inside that window by its publication date, yet its effect comes on 11 December 2027: the window says when an act was published, not when it starts to apply. The three acts named in this article are worked examples, not a complete record for any quarter.

Turn the finding into an action

Compare the changed requirement with the existing scope analysis, technical documentation, test evidence and issued declaration. Decide whether further evidence, testing, a different assessment route or a document update is needed. Record a justified no-change decision too.

Keep the previous signed declaration and supporting file version. A source alert does not reissue a signed declaration or establish compliance. See Updating a Declaration of Conformity.

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

FAQ

Frequently asked questions

  • Where should I check Official Journal entries?

    Use EUR-Lex for the authentic act, the Commission product-sector standards pages for reference lists and the relevant standards body for the actual edition. Record the act, annex, restrictions, application and withdrawal dates relevant to your product.

  • Does a new standard automatically invalidate my Declaration of Conformity?

    No. Check the applicable legislation, withdrawal date, covered requirements and the units affected. Loss of presumption of conformity requires an evidence and assessment-route review. Standards are generally voluntary; alternative solutions need adequate evidence.

  • Does this article list the acts published in a given quarter?

    No. It is a workflow for building that list yourself, not a digest. It uses three 2026 publications only as worked examples: Delegated Regulation (EU) 2026/339 (published 29 April 2026), Regulation (EU) 2026/1744 (published 24 July 2026) and Implementing Decision (EU) 2026/2003 (published 7 September 2026). They are illustrations, not a complete list for any quarter.

  • Can I rely on an automated alert alone?

    No. An alert prompts a review; it does not decide anything. Confirm which sources the alert covers and how fresh they are, assess the actual impact on your product and record a responsible reviewer's decision. Cenitia's source-change prompts cover only its supported catalogue, not every Official Journal entry, standard edition or national rule.

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.