Start hereDetermine intended purpose and classification
~169 days leftOpen step
Guide library
Authorization Europe

EU medical devices

Medical Device Regulation · Regulation (EU) 2017/745

Classify an EU medical device and plan conformity assessment, clinical evidence and post-market duties.

Who it applies to

Manufacturers and other economic operators placing in-scope medical devices on the EU market under MDR.

What you’ll produce

EU declaration of conformity, applicable notified-body certification and CE marking when requirements are met.

IVDs sit under a separate regulation. Legacy transitions have eligibility conditions and device-specific dates.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What intended purpose will the manufacturer stand behind?
Agree population, indications, users, environment and claims with Clinical and Regulatory. Document the classification rationale and confirm the assessment route before you fund studies or commit to dates.
Which evidence or assessment could delay launch?
Review clinical evidence, conformity route, notified body capacity where needed, language and labeling, and post-market costs. Budget to close evidence gaps and keep the assessment coordinated with design changes.
Who owns the product after it enters the market?
Confirm who performs obligations for the manufacturer and each relevant economic operator. Assign responsibility for technical documentation, UDI and registrations, vigilance and change control.

How to spend the first week

  1. Compare intended purpose and proposed claims with current device design, markets, labeling and the clinical evidence available.
  2. Create a classification memo and initial traceability matrix. Highlight evidence gaps that could change the route, schedule or budget.
  3. Agree review ownership with Quality, Clinical, Regulatory, Engineering and the relevant external body. Put the post-market plan into launch planning.

What to review each week

Track claims without clinical or performance evidence, conformity file gaps, notified body findings, registration tasks and overdue vigilance or post-market actions.

Kickoff brief to share with your team

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

EU medical devices 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  Determine intended purpose and classification · 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. Compare intended purpose and proposed claims with current device design, markets, labeling and the clinical evidence available.
2. Create a classification memo and initial traceability matrix. Highlight evidence gaps that could change the route, schedule or budget.
3. Agree review ownership with Quality, Clinical, Regulatory, Engineering and the relevant external body. Put the post-market plan into launch planning.
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.
The whole journeyabout 169 days across 4 steps
  1. 01Determine intended purpose and classificationRegulatory affairs · ~21 days
  2. 02Build QMS and evidence strategyQuality + clinical + engineering · ~45 days
  3. 03Compile the conformity file and assessRegulatory lead + notified body if required · ~75 days
  4. 04Maintain post-market evidencePost-market surveillance + regulatory · ~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
Determine intended purpose and classificationRegulatory affairsBefore choosing assessment routeSet a start dateClassification rationale; Route memo; Role matrixOpen
Build QMS and evidence strategyQuality + clinical + engineeringBefore submission or declarationSet a start dateQMS records; Clinical evaluation plan; Safety requirements matrixOpen
Compile the conformity file and assessRegulatory lead + notified body if requiredBefore placing on the marketSet a start dateTechnical documentation; Certificate where applicable; DeclarationOpen
Maintain post-market evidencePost-market surveillance + regulatoryAfter placement and ongoingSet a start dateSurveillance file; Vigilance logs; 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

    Determine intended purpose and classification

    Who Regulatory affairs When Before choosing assessment route

    Apply the relevant classification rules. Confirm economic operator roles, authorized representative and notified body needs.

    How to do this step

    Before you start

    Device description and variants, intended purpose, user and patient groups, mode of action, claims and proposed markets.

    1. Write the proposed purpose and compare it across the instructions, clinical plan and commercial claims.
    2. Apply the relevant classification rules to the facts. Record rules considered, how competing outcomes were resolved and the applicable conformity route.
    3. Confirm which economic operators, registration obligations and notified body involvement apply. Set a decision date for unresolved items.

    What a reviewer should see

    A dated memo ties specific design features and use to the chosen rule, classification and conformity route.

    When to escalate

    Raise any marketing claim or design change that could alter classification or require different clinical evidence.

    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.

    Role matrixMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

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

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

  2. 02

    Build QMS and evidence strategy

    Who Quality + clinical + engineering When Before submission or declaration

    Map general safety and performance requirements, risk management and clinical evidence. Plan technical files and post-market follow-up.

    How to do this step

    Before you start

    Approved route, design and supplier processes, risk management file, clinical data and applicable requirements.

    1. Map applicable safety and performance requirements to documented evidence. Name the owner of each requirement and any rationale for inapplicability.
    2. Build a clinical evaluation plan and a strategy to close gaps in safety and performance evidence. Align clinical, design and post-market teams around claims and versions.
    3. Document essential QMS controls for design, suppliers, production and changes. Confirm review and approval responsibilities and version history.

    What a reviewer should see

    A device claim traces to a risk, clinical or verification evidence, tested version and accountable reviewer.

    When to escalate

    Escalate an evidence assumption that cannot support the final claims or design verification for a changed configuration.

    What to produce

    QMS recordsMemo

    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.

    Clinical evaluation planMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

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

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    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.

  3. 03

    Compile the conformity file and assess

    Who Regulatory lead + notified body if required When Before placing on the market

    Assemble technical documentation and labeling, support applicable assessment and close findings. Finalize declaration and CE marking if eligible.

    How to do this step

    Before you start

    Technical and post-market documentation, traceability, labeling, clinical evaluation and audit evidence.

    1. Assemble the technical file and link relevant Annex II and Annex III content to controlled documents. Reconcile identifiers, variants and labels across sections.
    2. Coordinate the required assessment and document answers to findings, including reviewer approval and changes to affected artifacts.
    3. Verify the applicable declaration, certification, marking, registration and release conditions with Regulatory before placing the device on the market.

    What a reviewer should see

    The released file identifies exactly which variants the conformity evidence and decisions cover and records approval and submission versions.

    When to escalate

    Raise findings or a released configuration that falls outside the certificate or technical documentation scope.

    What to produce

    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.

    Certificate where applicableIssuer 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.

    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 post-market evidence

    Who Post-market surveillance + regulatory When After placement and ongoing

    Operate vigilance, trend reporting and surveillance. Maintain registrations, identifiers and periodic reports as applicable.

    How to do this step

    Before you start

    Post-market surveillance plan, UDI and registration records, complaint data and current vigilance thresholds.

    1. Have Quality collect complaints, field performance and feedback in line with the surveillance plan. Link each item to device identity and affected lots or versions.
    2. Evaluate potential vigilance requirements and update risk, clinical and corrective action records where evidence changes.
    3. Review registration, periodic reporting and intended purpose after changes. Preserve records of updates and notifications as applicable.

    What a reviewer should see

    A complaint record traces the product and lot, evaluation, reporting decision, corrective action and follow-up with the affected teams.

    When to escalate

    Escalate a possible serious incident promptly through the vigilance process while facts and timelines are confirmed.

    What to produce

    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.

    Vigilance logsSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

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

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.

    Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.

    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