If you're preparing for CE marking and still have little or no documentation in place, you're not alone. This guide explains how to start, what to prioritise, and how to avoid the mistakes that lead to delays, rework, and unnecessary cost.
Many teams focus first on product development or investment readiness — and only later realise that regulatory documentation cannot be left until the end. The good news is that this can be fixed.
Start with intended use and classification — not with writing documents. Build in order: intended use statement, classification rationale, regulatory roadmap, risk management framework, then technical documentation structure. Wrong foundations create expensive rework; structure before paperwork.
Lack of documentation does not automatically mean your project is in trouble. What matters is whether you now take a structured approach.
Many startups begin with:
That is not unusual. The real problem is not missing documentation itself. The real problem is building the wrong documentation, in the wrong order, based on the wrong assumptions.
CE marking is not just a certificate or a label. For medical devices, it depends on a complete regulatory framework that usually includes:
If these foundations are missing, the first step is not "write everything quickly." The first step is to build the right structure.
When companies realise they need CE marking, they often jump immediately into writing documents. That is usually the wrong move.
Before creating documentation, you need to establish:
Your intended use drives everything: whether the product is a medical device, which rules apply, what claims you can make, and what clinical and technical evidence you need.
Classification affects documentation depth, Notified Body involvement, conformity assessment route, and regulatory timeline.
You need to define which regulation applies, whether a Notified Body is required, and what the realistic route to CE marking looks like.
Without these first steps, documentation becomes guesswork. Getting the foundation wrong costs far more to fix than getting it right from the start.
If you are starting from zero, do not try to write everything at once. A better approach is to prioritise the core building blocks in the right order.
One of the most important starting documents. It should clearly define what the product is, who it is for, what it is intended to do, and in what context it will be used.
You need a clear, defensible explanation of your classification under the applicable rules.
This should outline your route to CE marking, the required documents, key milestones, and who needs to do what and when.
Risk management cannot be treated as an afterthought. It should begin early and evolve with the product.
Even if the content is not complete yet, the structure should be defined early so the documentation grows in an organised way.
If your intended use is still vague, your documentation will not hold together.
Templates can help, but they are not a shortcut to regulatory compliance.
This usually leads to incomplete, inconsistent, or weak documentation.
Clinical strategy should not be bolted on at the end. It shapes the entire technical file.
If your early assumptions are wrong, you often end up rewriting multiple parts of the technical file later.
If you have no documentation, the best approach is usually:
This is usually far more effective than trying to generate a full technical file in one rush.
At Regvo, we often work with startups and early-stage companies that have strong products but limited or no regulatory documentation in place. Our role is to help create structure before unnecessary cost and delay build up.
This typically includes:
The goal is not to overcomplicate the process. The goal is to give you a clear, defensible route forward.
If you have no documentation yet, that does not mean you are too late. But it does mean this is the moment to stop guessing and start building the right regulatory foundation. CE marking becomes much more manageable when the process is structured correctly from the beginning.
Book a free discovery call and we can help you define the right starting point for your device.
Book a free discovery callStart with intended use and classification — not with writing documents. Define what your product does and who it is for, confirm your regulatory class, and map out the required documentation before producing anything. Building on a weak foundation leads to rework.
Start with: (1) intended use statement, (2) classification rationale, (3) regulatory roadmap, (4) risk management file, (5) technical documentation structure. Building in this order prevents documentation from becoming guesswork.
It depends on your device class. Class I devices (non-sterile, non-measuring) can self-certify under MDR without a Notified Body. Class IIa and above require Notified Body involvement. This should be determined as the first step in your regulatory roadmap.
Writing documents before properly defining the product, or treating CE marking as an admin task rather than a strategic process. This creates incomplete, inconsistent documentation that will need to be rewritten — at significant cost.
Templates can provide a structural starting point, but copying without a proper strategy is a common mistake. Your documentation must be built on correct intended use and classification. Templates filled in without understanding the regulatory logic are often rejected or require significant rework.