Start hereClassify the device and identify who applies
~98 days leftOpen step
Guide library
Authorization North America

Canada medical device licence

Health Canada Medical Device Licence (MDL) applications for Class II, III and IV

Match the device class to its Canadian licence, quality evidence and submission contents.

Who it applies to

Manufacturers seeking a new or amended Canadian licence for a Class II, III or IV medical device, with separate establishment obligations where applicable.

What you’ll produce

A class-appropriate application package and an issued MDL if Health Canada grants it.

The device licence and Medical Device Establishment Licence serve different purposes. Verify both at the appropriate legal-entity level.

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.

Canada medical device licence 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 device and identify who applies · Regulatory affairs + Canadian operations [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 is the device class and is this a new device, private-label application or amendment?
  • Does the quality certificate cover the manufacturer, facilities and device scope in the application?

Worked scenario

A Canadian importer plans to distribute a Class II device under someone else’s licence. It confirms the device and manufacturer are covered by the actual licence, then checks its own establishment licensing and distribution obligations.

What to read next

  • ISO 13485

    Build QMS evidence and confirm the appropriate MDSAP certification arrangement.

The whole journeyabout 98 days across 4 steps
  1. 01Classify the device and identify who appliesRegulatory affairs + Canadian operations · ~14 days
  2. 02Collect class-specific and quality evidenceQuality + clinical and technical leads · ~42 days
  3. 03Submit and track Health Canada reviewRegulatory affairs · ~21 days
  4. 04Confirm the licence and maintain recordsRegulatory operations + post-market team · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 10 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify the device and identify who appliesRegulatory affairs + Canadian operationsBefore selecting formsSet a start dateClassification memo; Role mapOpen
Collect class-specific and quality evidenceQuality + clinical and technical leadsBefore submissionSet a start dateQMS records; Test reports; LabelingOpen
Submit and track Health Canada reviewRegulatory affairsWhen evidence and forms are readySet a start dateSubmission dossier; Response logOpen
Confirm the licence and maintain recordsRegulatory operations + post-market teamAfter the decision and on material changesSet a start dateExternal decision; Renewal calendar; Postmarket planOpen
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 device and identify who applies

    Who Regulatory affairs + Canadian operations When Before selecting forms

    Confirm Canadian classification, legal manufacturer, grouping and whether a new, amended or private-label licence applies. Identify establishment obligations separately.

    What to produce

    Classification 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 mapMemo

    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

    Collect class-specific and quality evidence

    Who Quality + clinical and technical leads When Before submission

    Check the applicable quality system certificate, intended use, labels and performance evidence. Use the current application and guidance for the device class.

    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.

    Test reportsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

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

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    LabelingMemo

    Gather first

    • Approved intended use and indications
    • Risk controls, warnings and test evidence
    • Labeling rules, markets and device configuration

    How to prepare it

    1. List the required label locations and formats for the product, packaging, instructions and software. Pull claims and warnings from the approved regulatory and risk files.
    2. Check language, symbol, version and identification requirements in each market. Route clinical, usability and regulatory review and reconcile changes to the design.
    3. Proof the production art or software screens, approve the exact version and retain a copy with the submission and release records.

    Worked example

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

    Label location
    Device instructions for use
    Claim or control
    Explain when a low-charge warning appears and what action the user should take.
    Supporting evidence
    Approved intended use, risk control R-014 and usability review
    Version and market
    IFU v3, applicable market and language versions listed
    Approval
    Regulatory and quality approval before release

    Check before handing it over

    The production artifact agrees with the intended use and evidence. Warnings and symbols are consistent across channels.

    Give the approved labeling files and control history to manufacturing, release and regulatory teams.

  3. 03

    Submit and track Health Canada review

    Who Regulatory affairs When When evidence and forms are ready

    Verify the dossier, current submission channel and fee. Save the receipt, log information requests and coordinate timely answers.

    What to produce

    Submission dossierMemo

    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.

    Response logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

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

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

  4. 04

    Confirm the licence and maintain records

    Who Regulatory operations + post-market team When After the decision and on material changes

    Verify the issued scope, maintain annual or other applicable licence obligations, and assess changes for amendments and post-market action.

    What to produce

    External decisionIssuer 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.

    Renewal calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

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

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

    Postmarket 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.

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