Picture a request from a market surveillance authority in 2031. A vulnerability in one of your products has made the news, and the authority wants to see the risk assessment, the support period decision and the record of how you handled the report. The people answering will be your engineers, not whoever helped you in 2026.
The CRA makes that scenario normal. The manufacturer carries the obligations in Article 13 and the reporting duty in Article 14, draws up the technical documentation (Article 31) and signs the EU declaration of conformity (Article 28). Vulnerability handling runs for the support period, which is at least five years unless the product is expected to be in use for a shorter time (Article 13(8)). The technical documentation and the EU declaration of conformity have to be kept for at least ten years after the product has been placed on the market, or for the support period if that is longer (Article 13(13)).
Measured against that timeline, the three usual ways of organising the work look quite different.
Option 1: a consultant
A good consultant reads your situation quickly, knows where assessors look and can write a convincing document. For a second opinion on an unusual product, or a review before an audit, that is money well spent.
As the main vehicle, it has two problems. The meter runs by the day, and it starts again with every new product and every update cycle. And when the engagement ends, the reasoning behind the documents tends to leave with the consultant. Your team inherits a file it did not write and has to defend decisions it did not make.
Option 2: a compliance platform
Compliance platforms sell automation: SBOM generation, vulnerability scanning, deadline tracking and a document store, by subscription. For a software team that ships every week, the automation is real.
What the platform needs from you depends on the provider and how it is deployed. A hosted service usually receives SBOMs and vulnerability findings, and sometimes build artefacts or incident details. Some providers also offer deployment on your own infrastructure. Either way, your security team and procurement will usually want to review the provider first. The fee recurs for as long as you use the service: at EUR 300 a month, for example, that is EUR 18,000 over a five-year support period, and more if the price is per product. Check the export format and terms, because the retention period in Article 13(13) can outlast the contract. The scanning part is not exclusive to platforms. Free open-source tools can generate SBOMs and match them against vulnerability databases in the build pipeline you already run.
Option 3: a template kit
A template kit gives you the documents and workbooks the regulation implies, laid out article by article, with guidance and filled-in examples. Your team completes them on your own systems.
That sounds like more work, and in the first weeks it is. It is also the option where the knowledge stays with your team. An engineer who has worked through the risk assessment and the support period record knows why the product is rated the way it is, and can explain it to an authority five years later.
The rest follows from owning the files:
- The files are in Word, Excel and PDF formats, which open in common office software, including free programs. Keep editable copies on your own systems.
- No cloud deployment is required, and the kit does not require you to upload product or vulnerability data to us. Your order details are processed by Polar, which sells the kit as reseller and Merchant of Record.
- The Company licence covers your company's own products, including products you add later.
- Whatever scanner you use, open-source or commercial, its results can be recorded in the kit's SBOM and vulnerability procedures.
A kit also fits every product class. Every conformity assessment route is built on the technical file. Where a notified body is involved (Class II and critical products, and Class I when harmonised standards, common specifications or a certification scheme are not applied in full, Article 32(2)), the notified body assesses that same file. The kit gives that file a structure.
What a kit will not do is decide for you. It shows what has to be decided and how to record it. That is what authorities expect to find: a manufacturer that understands the risks of its own product.
Side by side
| Consultant | Platform | Template kit | |
|---|---|---|---|
| Who holds the knowledge afterwards | Largely the consultant, unless your team took part | Partly the provider's system | Your team, if it did the work |
| Cost model | Day rate, repeated for every product and update | Yearly subscription, often per product or user | One payment |
| Cost over a five-year support period | Grows with every engagement | Five or more years of fees | Paid once |
| Where your product data lives | Shared with the consultant as far as the work requires | Depends on the provider and how it is deployed | On your own systems |
| Format of your technical file | Whatever is delivered | The provider's format; export terms vary | Word, Excel and PDF that you control |
| When the contract ends | The reasoning can leave with the consultant | Export terms decide what you keep | You keep the files you completed |
| Notified body routes | Supported | Supported | Supported: the kit structures the file the notified body assesses |
| Time to start | After contract and onboarding | After vendor review and setup | After purchase and download |
| Code scanning and SBOM generation | Advice on tools | Included | Your existing tools or free open-source tools |
Combining the options
The options can be combined. The kit carries the structure, the decisions and the technical documentation. Your existing scanners, or open-source ones, do the automation, and their results go into the kit's records. If you want an outside view, book an expert for a day or two to review the finished file before an audit. A short review costs less than a long engagement, and the documents stay with your team.
Four questions to ask about any option
- Who in our company will understand this file in five years?
- What does it cost over the whole support period, not just the first year?
- Where does our product data go, and what do we keep if the contract ends?
- Can we hand the result to an authority or a notified body as it is?
This article explains Regulation (EU) 2024/2847 in plain words. It is not legal advice.