How Are Responsibilities Divided for an EU Authorized Representative in Medical Device Registration?

Direct answer: Under the EU Medical Device Regulation (MDR) (EU) 2017/745, the manufacturer remains legally responsible for the device's conformity, the technical documentation evidence chain, and the accuracy of claims, while the EU authorized representative (EC REP) is the manufacturer's mandated contact in the EU and holds specific, non-delegable duties. The manufacturer must cover the product description, design and manufacturing information, General Safety and Performance Requirements (GSPR) conformity, risk management, performance verification, clinical evaluation, labelling and instructions for use, post-market surveillance and post-market clinical follow-up (PMS/PMCF), and the EU declaration of conformity. The authorized representative must verify that the EU declaration of conformity and technical documentation have been drawn up, keep copies available to competent authorities, comply with registration obligations, cooperate on vigilance and corrective actions, and inform the manufacturer of complaints, incidents, and non-compliance. If the manufacturer is non-compliant, the authorized representative must terminate the mandate. Responsibilities should be divided in a written mandate and reflected in contracts, labels, and submissions. Companies should not simply reuse legacy MDD files; they must reorganize the technical documentation according to the MDR evidence chain. The authorized representative may be held liable for failures in its own obligations and, under the MDR, can be liable on the same basis as the manufacturer for defects in devices it has placed on the market.

Published: 2026-07-15 21:37 | Updated: 2026-07-15 21:37

Content Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Errors
• Company Preparation Checklist
• AIMEILI Perspective
• Common Follow-up Questions
• Further Reading
• Scope of Application

Key Summary

EU MDR technical documentation requirements cover the product description, design and manufacturing information, GSPR conformity, risk management, performance verification, clinical evaluation, labelling and instructions for use, PMS/PMCF, and the declaration of conformity. Companies cannot simply carry over legacy MDD files; they must reorganize the technical documentation according to the MDR evidence chain.

For Chinese medical device companies, a practical approach is to first complete product classification and a documentation gap assessment, then determine whether NMPA, CE, FDA, ISO 13485, or other market documentation can be reused. Target market registration usually affects the technical file, authorized representative, importer cooperation, label language, quality system evidence, and subsequent change maintenance. If the project is driven only by a list of documents to submit, deficiencies or rework can easily arise in model coverage, evidence chain consistency, label claims, and certificate control. AIMEILI recommends placing the question within a GHWP member state and multi-country market access strategy, using one reusable core technical file to support localization in different markets rather than rebuilding documentation country by country.

Companies should also make project-based judgments based on the latest requirements of the target country's regulatory authority, the existing technical documentation basis, the product risk class, and the launch plan, avoiding mechanical preparation from a document checklist alone.

Applicable Scenarios and Core Questions

Companies searching for how EU authorized representative responsibilities are divided usually need more than a conceptual explanation. They want to know whether existing documentation can support target market submission, whether a local agent or authorized representative is required, why timelines are extended, and which issues affect the launch plan. This question typically involves product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibility at the same time.

If a company plans to enter multiple GHWP member states or markets in Southeast Asia, the Middle East, and Latin America at the same time, answering the process for one country alone is not enough. A more valuable approach is to first prepare reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence, and labelling and instructions for use, and then localize them according to each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the intended purpose, mechanism of action, use scenario, body contact, duration of use, sterility, active device status, and whether the product contains software or has IVD attributes, and then determine the risk class and submission pathway. If the pathway judgment is wrong, later translation, notarization, authorization, testing, and supplementary documentation will all deviate from the correct direction.

For a target market project, the applicant entity and local responsibility boundary must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles import and post-market events, who triggers changes, and who maintains renewal documentation. If these issues are handled vaguely in a commercial contract, they can easily affect market control later.

Documentation and Evidence

Common documentation includes the product description, model and specification matrix, intended purpose, risk classification basis, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labelling and instructions for use, authorization documents, existing registration certificates, manufacturer declarations, and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. Instructions for use claims, test report model coverage, clinical evidence scope, risk management conclusions, label warnings, and registration application form information must support one another. Regulators focus on whether the product is safe, effective, and traceable for its intended use, not on whether the company uploaded many documents.

Common Errors

• Treating registration as a simple document submission without first clarifying product classification, evidence coverage, and local responsibility relationships.
• Submitting directly translated NMPA documents without reorganizing evidence according to the target market pathway.
• Having too many models and specifications while test reports, clinical evidence, or labels do not provide sufficient coverage.
• Choosing a local agent only for sales cooperation without clarifying regulatory responsibility, certificate control, and post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional materials, and registration claims, leading to deficiencies or post-market compliance risks.
• Failing to plan multi-country documentation reuse in advance, causing repeated preparation in each country and amplifying cost and timelines.

Company Preparation Checklist

Before starting a project, companies should use a checklist to confirm the documentation basis and avoid discovering key evidence gaps after submission.

• Organize the target product list, model and specification matrix, and intended purpose statement.
• Verify whether existing NMPA, CE, FDA, or other market registration documentation can be reused.
• Prepare ISO 13485 certificates, test reports, risk management documentation, clinical evaluation, and English instructions for use.
• Confirm the local agent's or authorized representative's duties, fees, certificate control, and exit mechanism.
• Establish a target country gap assessment table specifying what needs additional testing, translation, notarization, or supplementary declarations.

AIMEILI Perspective

AIMEILI recommends that companies do not treat target market registration as a one-time document submission but manage it as an overseas market access project. For companies preparing to enter multiple countries, first building a clear core technical file and evidence matrix and then converting it according to each country's requirements is usually faster, more stable, and more conducive to subsequent changes and renewals than preparing documents country by country on an ad hoc basis.

From a project management perspective, companies should control three things in advance: first, product classification and pathway judgment; second, evidence chain consistency; and third, the regulatory responsibility boundary of local partners. If these three items are unclear, even if the documentation appears extensive, the project may still face repeated issues during deficiency responses, agent communication, and post-market maintenance.

Common Follow-up Questions

Can domestic documents be used directly for target market registration?

Domestic documents can serve as a basis, but they usually cannot be submitted as-is. Companies need to adjust the documentation structure, language, labels, authorization documents, and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment?

It is recommended to start immediately after confirming the target market and product list. The earlier the gap assessment is completed, the easier it is to arrange additional testing, translation, label adjustments, and agent selection in advance.

Why does local agent selection affect registration quality?

The local agent usually participates in registration communication, changes, renewals, and post-market event handling. Unclear responsibilities and authority can affect certificate control and subsequent market stability.

Project Execution Recommendations

When executing this type of registration project, companies should establish a project ledger that manages the product list, models and specifications, registration pathway, document owners, translation status, testing status, local agent communication records, and expected submission time in one table. This helps identify documentation gaps in time and allows management to judge whether the project will affect the launch plan.

For companies with existing registrations in multiple countries, an evidence reuse matrix should also be established to specify which documents can serve as core evidence and which must be reissued or supplemented according to country requirements. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification, and quality system certificates must remain version-consistent.

• Confirm the target market and product list.
• Complete risk classification and pathway judgment.
• Establish a documentation gap assessment table.
• Clarify the local agent and certificate control.
• Track translation, notarization, testing, and deficiency status.
• Arrange post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not an isolated certificate. Regulators usually check whether the manufacturer name, manufacturing address, product scope, certificate validity period, applicable standards, and technical file are consistent. If the ISO 13485 certificate scope does not match the submitted product, or if the manufacturing address, model and specification, instructions for use version, and test report are inconsistent, the company may be asked for supplementary explanations even if it has prepared a large number of documents.

Before submission, companies should establish an evidence consistency checklist that maps the product name, model and specification, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and instructions for use version, and quality system certificate item by item. This action appears basic, but it can significantly reduce the probability of deficiencies, especially for projects submitted simultaneously to multiple GHWP member states or for multiple product lines.

Localization Conversion and Authorized Representative Responsibilities

Target market registration projects usually involve arrangements for a local agent, authorized representative, importer, or registration holder. Companies need to confirm in advance whether the local partner is only responsible for submitting documents or also for regulatory communication, certificate maintenance, post-market event reporting, change applications, and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labelling, instructions for use, and authorization documents also cannot be simply translated. Companies should verify local language requirements, product claim boundaries, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information, and after-sales contact details. For companies that already have CE, FDA, NMPA, or other market documentation, the focus of localization conversion is to transform reusable evidence into a submission structure acceptable to the target country, rather than writing an isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Registration completion does not mean compliance work is over. Companies also need to maintain certificate validity, change records, distributor authorization, complaint handling, adverse event reporting, recall processes, label versions, and regulatory update records. Many companies invest heavily at the approval stage but neglect post-market maintenance. Once a manufacturing address change, model expansion, instructions for use update, or agent replacement occurs, the certificate and market sales can easily become disconnected.

AIMEILI recommends that companies manage this question within an annual international registration plan: first clarify target market priorities, then establish a reusable document package and country gap list, and finally schedule submission, deficiency response, post-market maintenance, and renewal milestones. The value is not only improving registration efficiency in a single country but also enabling companies to build a replicable global compliance capability and reduce the cost of starting from zero each time they enter a new market.

Further Reading

• Previous: How to Choose a Local Agent for EU Medical Device Registration?
• Next: Why Is the EU Medical Device Registration Timeline Extended?
• Recommended: How to Choose a Local Agent for Medical Device Registration in Brazil?
• Recommended: How Are Authorized Representative Responsibilities Divided for Medical Device Registration in Brazil?
• Recommended: Why Is the Medical Device Registration Timeline Extended in Brazil?
• Recommended: What Are the Common Reasons for Documentation Deficiencies in Brazil Medical Device Registration?
• Recommended: How to Conduct Post-Market Surveillance for Medical Device Registration in Brazil?
• Recommended: When Must Registration Changes Be Filed for Medical Device Registration in Brazil?
• Return to FAQ Center

Content Review and Scope of Application

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team.

Source principle: Priority is given to official regulatory authorities, international organizations, standards organizations, and public regulatory information; industry media and project experience are used only as auxiliary judgment.

Scope of application: This article is intended for preliminary understanding, documentation preparation, and project planning. It does not replace the official requirements of the target country's regulatory authority, testing conclusions, or legal advice.

Compiled from AIMEILI's regulatory practice knowledge base, its medical device international registration knowledge base, and public regulatory information; specific projects should be based on the latest requirements of the target country's regulatory authority and the product documentation basis.