Start hereConfirm sponsor, kind and class
~105 days leftOpen step
Guide library
Authorization Asia–Pacific

Australia ARTG medical devices

Australian Register of Therapeutic Goods inclusion for medical devices

Connect Australian sponsor responsibilities, manufacturer evidence and device inclusion.

Who it applies to

Australian sponsors and manufacturers seeking to supply covered medical devices, including IVDs under the applicable classification and route.

What you’ll produce

Accepted ARTG inclusion where required, with sponsor and manufacturer evidence available for audits.

Plan manufacturer evidence acceptance separately from ARTG inclusion. A foreign approval is an input only where the relevant Australian route accepts it.

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.

Australia ARTG 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  Confirm sponsor, kind and class · Australian sponsor + 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

  • Who is the Australian sponsor, and what kind of device and classification will be included?
  • Which conformity evidence does TGA accept for the device and manufacturer on this application?

Worked scenario

A device manufacturer appoints an Australian sponsor. The sponsor matches the proposed kind of device to the manufacturer evidence, checks certificate scope, and asks operational staff how quickly they could retrieve technical documentation if TGA audits.

What to read next

  • EU medical devices

    Start with underlying EU conformity evidence if that is part of the Australian evidence route.

The whole journeyabout 105 days across 4 steps
  1. 01Confirm sponsor, kind and classAustralian sponsor + regulatory affairs · ~14 days
  2. 02Secure manufacturer evidenceManufacturer quality + sponsor · ~35 days
  3. 03Lodge the inclusion and support reviewSponsor + regulatory operations · ~35 days
  4. 04Maintain inclusion and manage future changesSponsor + post-market lead · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Confirm sponsor, kind and classAustralian sponsor + regulatory affairsBefore choosing a routeSet a start dateClassification memo; Role matrixOpen
Secure manufacturer evidenceManufacturer quality + sponsorBefore ARTG application where requiredSet a start dateQMS records; Technical documentation; Evidence indexOpen
Lodge the inclusion and support reviewSponsor + regulatory operationsWhen the application is readySet a start dateSubmission package; Response log; External decisionOpen
Maintain inclusion and manage future changesSponsor + post-market leadDuring supplySet a start datePostmarket plan; Change log; Notification recordOpen
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

    Confirm sponsor, kind and class

    Who Australian sponsor + regulatory affairs When Before choosing a route

    Map intended purpose, classification, device identity, manufacturer and sponsor responsibilities. Check exceptions and any IVD-specific provisions.

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

    Secure manufacturer evidence

    Who Manufacturer quality + sponsor When Before ARTG application where required

    Identify the accepted conformity evidence, check scope, dates and identifiers, and record how the sponsor can retrieve the manufacturer documentation.

    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.

    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.

    Evidence indexSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

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

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Lodge the inclusion and support review

    Who Sponsor + regulatory operations When When the application is ready

    Use the applicable portal and complete the preliminary assessment requirements. Coordinate audit responses and preserve the decision and receipt.

    What to produce

    Submission packageMemo

    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.

    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.

  4. 04

    Maintain inclusion and manage future changes

    Who Sponsor + post-market lead When During supply

    Monitor complaints and adverse events, retain required records, meet conditions and evaluate changes or cancellation when needed.

    What to produce

    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.

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

    Notification recordSpreadsheet

    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.

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