Express + expert help

View pricing →
Skip to main content
referenceCEMark, CRA, RED, EMC, LVD4 min read

Official Journal monitoring for hardware compliance — a quarterly review workflow

A practical workflow for tracking EU product legislation, OJ standards citations, restrictions and transition dates, with a review record for each affected product.

By Vladimír VicianUpdated

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; check the authentic acts and relevant dates when making the final decision.

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 and CRA main product obligations 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.

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.

Withdrawals and restrictions

Record the date of withdrawal or cessation and evaluate the remaining evidence. Do not assume a standard citation guarantees all essential requirements, or that every change comes with the same transition period. 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 2022/30 and its repeal by Delegated Regulation 2026/339, which 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.

For example, a review of April–June 2026 would use a publication window of 2026-04-01 to 2026-06-30. That window alone says nothing about when an included act starts to apply. This article does not claim to contain the completed or exhaustive ledger for that 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.

Using Cenitia

Cenitia helps prepare evidence-linked working drafts and source-change review within its supported regulatory catalogue. Confirm the monitored scope and coverage. Assign a responsible reviewer for the applicability decision and follow-up evidence.

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.

  • Is this an audited list of Q2 2026 publications?

    No. It is a review workflow. It does not supply an independently verified, exhaustive quarter-specific ledger. A digest should name and link each included act and record its publication date and practical effect.

  • Can I rely on an automated alert alone?

    An alert prompts a review. Confirm source coverage and freshness, assess the actual product impact and record a responsible reviewer’s decision. This article does not establish that Cenitia monitors every OJ 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.