How a Technical File Gets Built: Experts, Rules, VI, and You

A technical file under the Medical Device Regulation (MDR) or the In Vitro Diagnostic Regulation (IVDR) is the argument a Notified Body reads before it decides anything about your device. Venitara builds that file from four parts, and each one has a single job: senior regulatory experts, classification rules, VI (Venitara Intelligence, the AI inside the platform), and you. This article shows each part where it lives in the portal, and then shows what happens when one answer reaches every document that needs it.

In short: Experts judge, rules trace the class, VI does the groundwork, and you make the decisions. Each part has one job, and none of them works alone. You answer a question once, and that answer flows into every template that needs it.

Experts judge

Senior regulatory experts review, challenge, and attest your documents before they count. If you get stuck along the way, you can ask our team directly.

Rules trace the class

In the Classification tool, your answers walk rule trees built on the annexes of the regulation, and the class follows from them. Every answer is recorded, so you can show a reviewer how the class was reached. The rules themselves are set out in MDR Annex VIII: How Device Classes Are Set.

VI does the groundwork

VI, the AI inside the platform, drafts from your own answers and flags gaps and missing evidence. Nothing enters your file until you accept it, and every draft carries the marker "AI-generated, not validated".

You learn, and you decide

Each step explains what the regulation asks for and why. Ask VI a question and it answers from the text of the MDR and IVDR, naming the article it used. Every regulatory decision stays with you.

One answer reaches every document that needs it

Your intended purpose, your classification, and your risk decisions flow into a full set of templates. Your documents stay consistent with each other, and you never type the same fact twice.

In the example below, one intended purpose feeds eight templates, from the device description and the general safety and performance requirements (GSPR) checklist through to the post-market plan. The device is fictional.

The usual way in

Most founders never see the inside of their own file. Some founders hand the whole file to someone else and get it back finished. Others ask a chatbot, which writes confident text that nobody has checked and nothing can trace.

Either way, the file belongs to somebody else. That shows the first time a Notified Body asks a question the founder cannot answer.

What Venitara promises, and what it does not

We get you to the door. A Notified Body opens it.

Only a Notified Body can certify conformity, and nobody can honestly promise approval. Venitara covers the part before that. You get a file that is ready for submission, the right Notified Body for your device, and a materially better chance of getting through quickly. Venitara has delivered more than 40 regulatory projects and works with 10 to 12 Notified Bodies.

That boundary is the same one drawn across the CE marking pathway for medical device software, which walks every step from intended purpose to the certificate.

Already deep in a conformity assessment? Start with a conversation rather than the Compass, so we can see where you are first.

Want the whole file built for you? That is Certify, where our experts lead. Talk to us before you start.

Where to begin

The MedTech Compass is free and takes ten minutes. It shows your likely device class, your route to market, and the gaps between them, so you can decide how much of the file you want an expert to look at.