Skip to contentArticle 14 reporting has applied since 11 September 2026. See the worked example and get the free 4-page overview.
See the kit

Worked example: Lumora TH-200

A fictional company and a fictional smart thermostat. 26 of the 27 templates are filled in. The authorised representative mandate is left out, because the company is established in the EU and does not need one.

Get the free overviewFree PDF, 4 pages. Polar emails you the download link.

Scope decision: in scope, manufacturer, default class, Module A

Risk assessment: 12 risks, from firmware tampering to loss of heating in winter; every completeness check at zero

Annex I evidence matrix: 22 requirements, each with its proof

Article 14 exercise: a simulated botnet case, reportable on both tracks

EU declaration of conformity, complete

Compliance tracker: every applicable requirement marked "Evidenced"

Six lessons from the example

01

Reporting comes first

Article 14 has applied since 11 September 2026, also to units already on the market, so Lumora adopted the reporting playbook before it wrote the technical file.

In the kit:M06
02

Your class depends on what your product is

The thermostat has a Wi-Fi module and a secure element inside, yet stays in the default class. What changes is the due diligence on those parts.

In the kit:M01–M02M09
03

One file, many links

Every document has an ID. One risk leads to two requirements, a test report and a section of the technical file.

In the kit:M03M04M07
04

Not every change restarts the process

Firmware 4.1 adds a local Matter interface with a listening port. It raises the cybersecurity risk in a way the risk assessment did not foresee, so it is a substantial modification. A security-only fix, and an upgrade that brings older units to the design already assessed, are not.

In the kit:M10
05

The declaration has a start date

Signed on 1 October 2027, it covers units placed on the market from 11 December 2027.

In the kit:M08
06

Choices must match everywhere

The SBOM policy reads the same in the procedure, the technical file and the user information. An assessor will compare them.

In the kit:M05M07M08

Reading the example correctly

Article 14 exercise. The simulated case EX-2027-01 of 18 March 2027 is reportable on both tracks: as an actively exploited vulnerability and as a severe incident, because the takeover of about 300 thermostats could affect important functions such as remote control and heating commands (Art. 14(5)(a)). Awareness is at 13:40 UTC, so the early warnings are due on 19 March at 13:40 and the notifications on 21 March at 13:40. The vulnerability final report is due on 8 April, 14 days after the fix of 25 March; the incident final report within one month after the incident notification.

100 % on the dashboard. The compliance tracker shows 100 % because every applicable requirement is marked "Evidenced": the evidence is filed where the tracker says. The figure measures how complete the evidence is. It is not a conformity decision or a certificate, and Lumora still signs the EU declaration of conformity on its own responsibility.

Substantial modification. Three changes are assessed with the same seven questions (LUM-SM-2027-04 to -06). The result depends on whether the change alters the intended purpose, and whether it raises the cybersecurity risk or affects the Annex I requirements in a way the risk assessment did not foresee (Art. 3(30), Commission guidance C(2026) 5252). Whether an update is free or paid plays no part.

Get the free overviewFree PDF, 4 pages. Polar emails you the download link.

The 26 filled example files come with the full kit.

Lumora Home Technologies GmbH and all people, documents and cases in the example are fictional.