Start hereClassify the IVD and confirm the route
~184 days leftOpen step
Guide library
Authorization Europe

EU in vitro diagnostics

In Vitro Diagnostic Medical Devices Regulation (EU) 2017/746

Classify an IVD, plan performance evidence, and verify any remaining legacy transition conditions.

Who it applies to

Manufacturers and other economic operators placing covered in vitro diagnostic devices on the EU market under IVDR.

What you’ll produce

The required technical and conformity evidence, declaration, registration and any needed notified-body certificate.

A legacy deadline depends on earlier conditions, such as a valid route, no significant change and timely notified-body steps. Check EUDAMED obligations by module and role.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which path and official decision does the business need?
Confirm intended market or customer, covered product or service, and the required approval route. Fund evidence, test or assessment work, and time to respond to reviewers.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor outstanding evidence, external dependencies and authority responses due. Bring changes to the assessed product or service to the decision owner.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

EU in vitro diagnostics kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Classify the IVD and confirm the route · Regulatory affairs [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What analyte, specimen, clinical purpose, intended user and setting define the IVD?
  • Is it a new device or an eligible legacy device with evidence for every transition condition?

Worked scenario

A developer adds a new screening claim to a legacy assay. Regulatory affairs checks whether this is a significant change before relying on the old certificate. The performance team maps the claimed population to evidence and organises any new studies.

What to read next

  • EU medical devices

    Use the separate device regulation for a product outside the IVD definition.

  • ISO 13485

    Structure the quality system supporting design, performance evidence and post-market work.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 26 May 2027

    Legacy Class B and sterile Class A application milestone

    Eligible devices under Article 110(3b)(c) must meet the notified-body application condition in Article 110(3c). The written agreement condition has its own deadline.

    Official reference (opens in a new tab)
  • 31 Dec 2027

    Outer legacy deadline for specified Class D and certificate-based routes

    This date applies only under the relevant transitional provisions and conditions. Eligible Class C, Class B and sterile Class A categories can have later dates.

    Official reference (opens in a new tab)
The whole journeyabout 184 days across 4 steps
  1. 01Classify the IVD and confirm the routeRegulatory affairs · ~21 days
  2. 02Plan and generate performance evidenceClinical + analytical performance teams · ~70 days
  3. 03Build the technical file and complete assessmentQuality + regulatory affairs · ~65 days
  4. 04Maintain registration and post-market evidenceRegulatory operations + surveillance lead · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify the IVD and confirm the routeRegulatory affairsAt design initiation and when claims changeSet a start dateClassification rationale; Route memo; Applicability matrixOpen
Plan and generate performance evidenceClinical + analytical performance teamsBefore conformity assessmentSet a start dateTesting matrix; Study protocols; Performance evaluation fileOpen
Build the technical file and complete assessmentQuality + regulatory affairsBefore placing covered devices on the marketSet a start dateSafety requirements matrix; Technical documentation; DeclarationOpen
Maintain registration and post-market evidenceRegulatory operations + surveillance leadBefore initial market entry and ongoingSet a start dateRegistration/listing record; Surveillance file; Periodic reportsOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Classify the IVD and confirm the route

    Who Regulatory affairs When At design initiation and when claims change

    Record the intended purpose and apply classification rules. Confirm notified-body involvement, operator duties and whether any legacy route remains available.

    What to produce

    Classification rationaleSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Route memoSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Applicability matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

  2. 02

    Plan and generate performance evidence

    Who Clinical + analytical performance teams When Before conformity assessment

    Map scientific validity, analytical performance and clinical performance to specific claims. Record study, sample and acceptance criteria and maintain a performance evaluation record.

    What to produce

    Testing matrixSpreadsheet

    Gather first

    • Product claims and risk file
    • Applicable standards, study design and acceptance evidence
    • Design configuration and test facilities

    How to prepare it

    1. Trace each claim and risk control to a test objective and acceptance criterion. Specify units, sample rationale, version and worst-case configurations.
    2. Write the method and expected evidence before testing. Assign approvals and record protocol deviations and their effects.
    3. Compare results to the criteria. Keep failed cases, raw data and rationale for repeat testing. Link the approved reports back to the requirements.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or claim
    Battery alert appears before the device can no longer capture readings.
    Protocol and design
    TR-014, test the production hardware and locked firmware at worst-case temperature.
    Acceptance criteria
    Use the limits approved in the design input before testing.
    Sample and method
    Record sample sizes, lot IDs, conditions and operator.
    Result and evidence
    Link signed protocol, raw output and approved report.

    Check before handing it over

    Every essential claim and risk control has evidence or a documented justification for the gap.

    Give the approved protocol to the testing team and the traceability matrix to the submission owner.

    Study protocolsSpreadsheet

    Gather first

    • Product claims and risk file
    • Applicable standards, study design and acceptance evidence
    • Design configuration and test facilities

    How to prepare it

    1. Trace each claim and risk control to a test objective and acceptance criterion. Specify units, sample rationale, version and worst-case configurations.
    2. Write the method and expected evidence before testing. Assign approvals and record protocol deviations and their effects.
    3. Compare results to the criteria. Keep failed cases, raw data and rationale for repeat testing. Link the approved reports back to the requirements.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or claim
    Battery alert appears before the device can no longer capture readings.
    Protocol and design
    TR-014, test the production hardware and locked firmware at worst-case temperature.
    Acceptance criteria
    Use the limits approved in the design input before testing.
    Sample and method
    Record sample sizes, lot IDs, conditions and operator.
    Result and evidence
    Link signed protocol, raw output and approved report.

    Check before handing it over

    Every essential claim and risk control has evidence or a documented justification for the gap.

    Give the approved protocol to the testing team and the traceability matrix to the submission owner.

    Performance evaluation fileMemo

    Gather first

    • Approved IVD intended purpose and claims
    • Scientific, analytical and clinical evidence
    • Current performance evaluation plan and risk file

    How to prepare it

    1. Turn each claim into a row with analyte, specimen, population and setting. Identify which data support scientific validity, analytical performance and clinical performance.
    2. Link to study design and results, including limitations, biases and deviations. Reconcile all test, assay and software revisions with the intended claim.
    3. Explain how the evidence supports each claim. Record review and remaining issues, and plan post-market performance follow-up where applicable.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Claim
    Measure the specified analyte in the declared sample type for the approved use.
    Scientific validity
    Link evidence connecting the analyte to the condition or state.
    Analytical performance
    Link reproducibility and interference reports for the declared device configuration.
    Clinical performance
    Link the evaluation in the intended population and note evidence limits.
    Review and follow-up
    Clinical and regulatory leads confirm claim wording and post-market work.

    Check before handing it over

    A reviewer can follow a claim from label to evidence and see what was excluded or remains uncertain.

    Give the approved performance evaluation to regulatory affairs, quality and the notified body where required.

  3. 03

    Build the technical file and complete assessment

    Who Quality + regulatory affairs When Before placing covered devices on the market

    Reconcile QMS evidence, safety requirements, labels, traceability and performance findings. Coordinate notified-body assessment where required and retain the declaration.

    What to produce

    Safety requirements matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Technical documentationMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    The submitted package can be recreated from the index and the receipt is linked to the exact files.

    Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.

    DeclarationMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    The signer can explain the basis for each statement and the record reflects the required scope and period.

    Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.

  4. 04

    Maintain registration and post-market evidence

    Who Regulatory operations + surveillance lead When Before initial market entry and ongoing

    Check applicable EUDAMED modules, vigilance, surveillance and performance follow-up. Reassess changes and maintain the required reporting records.

    What to produce

    Registration/listing recordIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Surveillance fileMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    The submitted package can be recreated from the index and the receipt is linked to the exact files.

    Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.

    Periodic reportsMemo

    Gather first

    • Previous report and current reporting rules
    • Monitoring period and verified outcomes
    • Open issues, incidents and approval route

    How to prepare it

    1. Identify the official reporting period and the recipient. List the version, scope and method used to collect the facts.
    2. Summarize material changes, incidents, findings and actions using source counts, rates or records. Explain missing evidence and update decisions.
    3. Send the draft for technical approval, use official forms where required and archive the exact report and receipt.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Reporting period
    Oct through Dec 2026, confirmed scope as of period end
    Monitoring sources
    Operations events, incident register and service changes
    Finding and response
    Two failed scheduled jobs. Both recovered after retry. The report links to the root cause ticket.
    Approval and filing
    Accountable owner reviews. Save issued version and receipt.

    Check before handing it over

    The period, evidence and required metrics are complete and the reviewer can follow up on open items.

    Send the approved report to the required recipient and give ongoing actions to service owners.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes