Class I Medical Device Technical Documentation Under MDR: Why “Low Risk” No Longer Means Simple

Compared with higher-risk implants, active devices or complex surgical technologies, Class I products often sat in the “straightforward” category. Many manufacturers could self-certify, prepare documentation internally, and bring products to market without the same level of notified body scrutiny.

Under the EU Medical Device Regulation, that reality has changed.

Class I devices are still considered low risk from a clinical perspective, but the regulatory burden behind them has increased significantly. Manufacturers now need to maintain structured, complete and inspection-ready technical documentation under MDR Annex II and Annex III. For many smaller manufacturers, especially those without dedicated regulatory affairs teams, this has created a difficult situation: the products may be simple, but the documentation is not.

This is particularly true for Class I devices that fall into special categories such as sterile devices, measuring devices and reusable surgical instruments - commonly referred to as Class Is, Class Im and Class Ir.

The Class I Problem: Simple Products, Complex Documentation

The biggest misconception around Class I medical devices is that “low risk” means “low effort”.

In practice, many Class I manufacturers are small or medium-sized companies producing products such as surgical instruments, procedure packs, wound care products, non-invasive devices, accessories, examination tools or other relatively simple devices. These companies often have strong technical and manufacturing knowledge, but limited internal regulatory capacity.

Under MDR, they are expected to produce and maintain documentation that covers device description, intended purpose, classification rationale, risk management, clinical evaluation, General Safety and Performance Requirements, verification and validation, labelling, post-market surveillance and more.

The challenge is not only writing these documents once. The real challenge is keeping them aligned over time.

A small change to a product label may affect the IFU. A change in material may affect biological safety, risk management and clinical evaluation. A new version of a harmonised standard may require a review of existing evidence. A complaint trend may trigger PMS follow-up. An audit finding may reveal that a document exists, but is outdated, inconsistent or disconnected from the rest of the technical file.

For larger companies, this is painful. For smaller Class I manufacturers, it can become overwhelming.

Why MDR Has Made Class I Documentation More Difficult

The MDR was designed to create a more robust regulatory system for medical devices in Europe. It increased expectations around clinical evidence, post-market surveillance, traceability, risk management and lifecycle documentation.

For Class I manufacturers, this means that technical documentation can no longer be treated as a one-off regulatory file prepared for CE marking and then left untouched.

The documentation needs to function as a living evidence base. It must show not only that the device was compliant at the point of placing it on the market, but that the manufacturer continues to monitor safety, performance and regulatory changes throughout the device lifecycle.

This is where many companies struggle.

Their documentation is often spread across Word documents, Excel files, PDFs, email folders, shared drives and old templates. Different people may own different parts of the file. Some documents may have been created under the Medical Device Directive and later adapted to MDR. Others may have been updated manually several times, without a clear overview of which changes affected which sections.

The result is a fragmented system where the manufacturer may technically “have the documents”, but still lacks confidence that the file is complete, consistent and ready for inspection.

The Deadline Pressure Is Real

For many Class I devices, MDR has already applied since 26 May 2021. In general, new Class I devices placed on the EU market after that date must comply with MDR requirements. The European Commission’s MDR timeline specifically notes that devices not covered by extended transition arrangements - including many Class I devices - needed to comply from the MDR date of application.

However, the situation is more nuanced for certain legacy Class I devices that require notified body involvement under MDR, such as Class Is, Class Im and Class Ir devices. Regulation (EU) 2023/607 extended transition periods for certain legacy devices, with many Class IIa, Class IIb and Class I devices requiring notified body involvement having transition routes running to 31 December 2028, provided the required conditions are met.

This matters because many manufacturers are now operating in a compressed transition window.

The deadline may sound far away, but in regulatory terms it is not. Preparing technical documentation, closing evidence gaps, engaging a notified body, responding to questions, updating procedures, and maintaining market continuity can take far longer than expected.

For smaller manufacturers, the risk is that MDR compliance becomes a reactive project only when a customer, distributor, authority, consultant or notified body asks for documentation. By that point, the company may discover that the issue is not one missing document, but an entire technical file that needs restructuring.

Class Is, Im and Ir: The Hidden Complexity Inside Class I

Class I is not one uniform category.

A basic Class I device may often be self-certified by the manufacturer. But Class Is, Class Im and Class Ir devices introduce additional layers of complexity because notified body involvement is required for specific aspects of the device.

For Class Is devices, the notified body involvement relates to sterility. That means the manufacturer needs to demonstrate appropriate control over sterilisation, sterile barrier systems, packaging validation and related processes.

For Class Im devices, the focus is on the measuring function. Manufacturers need to support claims around measurement accuracy, calibration, performance and traceability.

For Class Ir devices, the focus is on reuse. Reusable surgical instruments remain Class I under MDR, but the notified body reviews aspects linked to reuse, including cleaning, disinfection, sterilisation, maintenance and functional testing.

This creates a strange situation for manufacturers.

They may still think of themselves as “only Class I”, but in practice they are dealing with notified body expectations, validation requirements and lifecycle documentation that can feel much closer to higher-risk regulatory work. If you’re unsure which subclass applies to a given product, our explainer on MDR device classification walks through the logic.

The Real Pain Is Not Knowing What Is Missing

One of the biggest challenges for Class I manufacturers is not simply producing documents. It is knowing whether the documentation is good enough.

Many companies use templates. Templates can help, but they do not solve the underlying problem. A template does not know whether the clinical evaluation is aligned with the intended purpose. It does not know whether the GSPR checklist properly links to evidence. It does not know whether PMS data creates an obligation to update the risk file. It does not know whether a change in cleaning instructions affects the IFU, validation report and risk management file.

This is why Class I documentation often becomes a confidence problem.

Manufacturers may ask themselves whether the technical file is genuinely complete. Whether the documents are consistent with each other. Whether the correct MDR requirements have been addressed, or whether outdated MDD-era assumptions are still embedded. Whether the file would stand up to a competent authority request, or be acceptable to a notified body for Is, Im or Ir aspects. And what happens when a standard, guidance document or product claim changes.

These questions are difficult because technical documentation is not a collection of isolated files. It is a connected system of evidence. But most manufacturers still manage it as disconnected documents.

Why This Is Especially Hard for Smaller Manufacturers

Smaller Class I manufacturers often do not have large regulatory affairs departments. In many cases, regulatory work is handled by a quality manager, founder, operations lead, external consultant or someone who has multiple responsibilities.

This creates several practical problems.

First, regulatory knowledge may sit with one person. If that person leaves, the company loses important context. Second, external consultants may help prepare documentation, but the company still needs to maintain it afterwards. Third, technical files are often built project by project, not as a structured operating system. One product may have a strong risk file but weak PMS. Another may have an updated IFU but outdated GSPR mapping. A third may have inherited legacy documentation from an older certification route. Fourth, manufacturers often do not have a simple way to understand how one change affects the rest of the file.

This is where the burden becomes operational, not just regulatory.

The work is not only “write the technical documentation”. The work is understanding the relationships between requirements, evidence, product claims, standards, risks, clinical data, PMS findings and documentation updates.

That is exactly where many current tools fall short.

The Problem With Static Technical Files

Most technical documentation is still created and maintained using static files.

A manufacturer may have a folder containing a risk management file, clinical evaluation, GSPR checklist, PMS plan, IFU, labels, validation reports, supplier documentation and declarations. Each document may be technically correct on its own, but the system as a whole is fragile.

If one document changes, someone needs to manually check whether other documents are affected.

If a new MDR guidance document is published, someone needs to understand whether it applies to the product portfolio.

If an audit report identifies a gap, someone needs to trace that gap back to the relevant product documentation.

If a complaint trend appears, someone needs to decide whether the risk file, PMS report or clinical evaluation needs updating.

This is where regulatory teams lose time. Not because they lack expertise, but because the information architecture is broken.

The technical file is treated as a folder. In reality, it should behave more like a living regulatory system.

What Class I Manufacturers Need Now

Class I manufacturers do not necessarily need more generic templates.

They need clarity.

They need a way to understand what documentation is required for their specific device type and subclass. They need to know what changes for Class Is, Class Im and Class Ir. They need to identify gaps before an audit, authority request or notified body review. They need to connect the GSPR checklist with the actual evidence. They need to keep PMS, risk management, clinical evaluation and labelling aligned over time.

Most importantly, they need a way to make MDR compliance manageable without building a large internal regulatory department.

This is the real market pain.

The companies most affected are not necessarily ignoring compliance. Many are trying to do the right thing. But they are working with fragmented systems, limited time, unclear expectations and documentation that becomes harder to control as the product portfolio grows.

Class I Is the Ideal Starting Point for a Better Regulatory System

Class I is often overlooked because it is considered low risk. But from a workflow perspective, it is one of the clearest examples of why regulatory documentation needs to change.

The devices may be simple enough for a focused first use case. The manufacturer pain is real. The documentation requirements are structured enough to support automation. And the market includes many companies that need practical help now, not a massive enterprise implementation.

At Artifakt, we believe the future of medical device compliance is not another static template library.

It is a connected regulatory workspace where technical documentation, requirements, evidence and updates sit together in one living system.

For Class I manufacturers, this could mean turning a fragmented documentation process into something more structured, guided and continuously maintained. For Class Is, Im and Ir manufacturers, it could help clarify which additional evidence is needed for sterility, measuring or reusability aspects. For smaller companies, it could reduce the burden of navigating MDR documentation alone.

Class I may be the lowest-risk device category, but it is not a low-effort regulatory category anymore.

The manufacturers who recognise this early will be better prepared for MDR deadlines, notified body expectations, competent authority scrutiny and long-term documentation maintenance.

The ones who wait may discover too late that the hardest part of Class I compliance was never the device itself.

It was the documentation system around it.