How to Prepare Performance Verification Documentation for Medical Device Registration in Singapore

Key Summary

To prepare performance verification documentation for medical device registration in Singapore, a company should first confirm the target market, the product's risk classification, the applicable regulatory pathway and the documentation already available, and then assess the requirements for technical documentation, quality system evidence, labelling and instructions for use, local representation, clinical evidence and post-market maintenance. AIMEILI recommends completing a documentation gap assessment before formal submission, so that unclear classification, incomplete evidence or ambiguous authorization arrangements do not unnecessarily extend the project timeline.

For Chinese medical device manufacturers, the more reliable approach is to carry out product classification and a documentation gap assessment first, and only then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Singapore registration typically affects technical documentation, authorized representative arrangements, importer cooperation, label language, quality system evidence and subsequent change maintenance at the same time. If a project is driven only by the question of "which documents must be submitted," corrections or rework are likely to arise in areas such as model coverage, evidence chain consistency, labelling claims and control of certificates. AIMEILI recommends positioning this 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 preparing documentation from scratch for each country.

This article has been compiled from AIMEILI's regulatory practice reference materials, its medical device international registration knowledge base and publicly available regulatory information. Specific projects should be based on the latest requirements of the target country's regulatory authority and on the actual documentation base of the product.

Published: 11 July 2026, 11:10  |  Updated: 11 July 2026, 11:10

This article reviews the questions that companies need to address as a priority in real projects concerning medical device international registration, documentation preparation, compliance pathways and post-market maintenance.

Content Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Pitfalls
• Company Preparation Checklist
• AIMEILI Perspective
• Frequently Asked Follow-up Questions
• Further Reading
• Applicability Boundaries

Applicable Scenarios and Core Questions

Companies searching for guidance on how to prepare performance verification documentation for Singapore medical device registration are usually not looking for a conceptual explanation. What they need to determine is whether their existing documentation can support a Singapore submission, whether a local agent or authorized representative is required, why timelines are being extended, and which issues could affect their market launch plan. Behind this question there are usually several interconnected topics: product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibilities.

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

Registration Decision Logic

A company should first confirm the product's intended use, mechanism of action, use environment, method and duration of body contact, whether it is sterile, whether it is active, and whether it incorporates software or has IVD characteristics, and then determine the risk classification and submission pathway. Once the pathway assessment is wrong, the subsequent translation, notarization, authorization, testing and supplementary documentation will all move in the wrong direction.

For a Singapore project, the applicant entity and the boundaries of local responsibility must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market incidents, who triggers changes, and who maintains the documentation for certificate renewal. If these points are left vague in commercial contracts, market control can easily be affected later on.

Documentation and Evidence

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

The key to documentation quality lies not in quantity but in consistency. Claims in the instructions for use, the models covered by test reports, the scope of application of clinical evidence, the conclusions of risk management, label warnings and the information in the registration application form must all support one another. What regulators focus on is whether the product is safe, effective and traceable for its intended use, not how many documents a company has uploaded.

Common Pitfalls

The most common problem is that companies treat a registration project as a simple documentation submission, without first clarifying product classification, evidence coverage and local responsibility relationships.

• Submitting NMPA documentation for the domestic market after direct translation, without reorganizing the evidence in line with the Singapore pathway.
• Too many models and specifications, with insufficient coverage in test reports, clinical evidence or labelling.
• Selecting a local agent purely on the basis of a sales partnership, without clarifying regulatory responsibilities, control of the certificate and post-market maintenance obligations.
• Inconsistency between labels, instructions for use, promotional materials and registration documentation claims, leading to deficiency letters or post-market compliance risk.
• Failure to plan for multi-country documentation reuse in advance, resulting in repeated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before starting a project, companies are advised to use an internal checklist to confirm the documentation base, so that critical evidence gaps are not discovered only after submission has begun.

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

AIMEILI Perspective

AIMEILI recommends that companies not view Singapore registration as a one-off document submission, but manage it as an overseas market access programme. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first, and then converting it according to national requirements, is generally faster, more stable and more conducive to subsequent changes and certificate renewals than preparing documentation on an ad hoc basis country by country.

From a project management perspective, three things should be controlled as early as possible: first, product classification and pathway determination; second, the consistency of the documentation evidence chain; and third, the regulatory responsibility boundaries of local partners. If these three items remain unclear, the project may still encounter repeated deficiencies, agent communication problems and post-market maintenance issues, even if the documentation appears substantial.

Frequently Asked Follow-up Questions

Can domestic (NMPA) documentation be used directly for Singapore registration?

Domestic documentation can serve as a basis, but it generally cannot be submitted as is. Companies need to adjust the documentation structure, language, labelling, authorization documents and evidence chain in accordance with local regulatory requirements.

When is the best time to start a gap assessment?

A gap assessment should be started as soon as the target market and product list are confirmed. 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 the choice of local agent affect registration quality?

A local agent is typically involved in registration communication, changes, certificate renewal and the handling of post-market incidents. Unclear responsibilities and authority can affect control of the certificate and the stability of the market thereafter.

Project Execution Recommendations

When executing this type of registration project, companies should establish a project log that manages the product list, model and specifications, registration pathway, documentation owners, translation status, testing status, records of communication with the local agent and estimated submission dates in a single table. This makes documentation gaps easier to identify promptly and helps management judge whether the project will affect the market launch plan.

For companies that already have registrations in several countries, an evidence reuse matrix should also be established, specifying which documents can serve as core evidence and which must be reissued or supplemented according to national requirements. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates must be kept version-consistent.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify the local agent and control of the certificate.
• Track translation, notarization, testing and deficiency response 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 generally examine whether the manufacturer's name, manufacturing address, product scope, certificate validity period, applicable standards and technical documentation are consistent with one another. If the scope covered by the ISO 13485 certificate does not match the product being registered, or if the manufacturing address, model specifications or instructions for use version do not match the test reports, the authority may request supplementary clarification even when a large volume of documentation has been prepared.

Companies should establish an evidence consistency checklist before submission, mapping product name, model and specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and instructions for use version, and quality system certificates item by item. This step appears basic, but it can significantly reduce the probability of deficiency letters, especially for projects involving simultaneous submissions in multiple GHWP member states or for multiple product families.

Localization Conversion and Authorized Representative Responsibilities

Singapore registration projects typically involve arrangements for a local agent, authorized representative, importer or registration holder. Companies need to confirm in advance whether the local partner is responsible only for submitting documentation, or whether it also handles regulatory communication, certificate maintenance, post-market incident reporting, change applications and renewal reminders. Different responsibility boundaries directly affect control of the certificate and the stability of the market thereafter.

Labelling, instructions for use and authorization documents also cannot simply be translated. Companies should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information and after-sales contact details. For companies that already hold 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 a separate, isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Completing registration does not mean the compliance work is finished. Companies also need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, label versions and records of regulatory updates. Many companies invest considerable effort in obtaining the certificate but neglect post-market maintenance; subsequently, when a manufacturing address change, model expansion, instructions for use update or agent replacement occurs, the certificate can easily become disconnected from actual market sales.

AIMEILI recommends that companies manage this topic within an annual international registration plan: first establish market priorities, then build a reusable documentation package and a country gap list, and finally schedule submission, deficiency responses, post-market maintenance and certificate renewal milestones. The value of doing so is not only improved efficiency for registration in a single country; more importantly, it enables companies to develop repeatable compliance capabilities for going global, reducing the cost of starting documentation preparation from scratch each time they enter a new market.

Further Reading

• Previous article: What Are the Requirements for Risk Management Documentation in Medical Device Registration in Singapore?
• Next article: What Should Be Done When Quality System Evidence Is Inconsistent in Medical Device Registration in Singapore?
• Recommended reading: What are the requirements for risk management documentation in medical device registration in the Philippines?
• Recommended reading: How should performance verification documentation be prepared for medical device registration in the Philippines?
• Recommended reading: What should be done when quality system evidence is inconsistent in medical device registration in the Philippines?
• Recommended reading: How should the registration dossier be prepared for medical device registration in Singapore?
• Recommended reading: How should product classification be determined for medical device registration in Singapore?
• Recommended reading: How should technical documentation be organized for medical device registration in Singapore?
• Return to the FAQ Centre
• News and Insights
• Contact AIMEILI

Content Review and Applicability Boundaries

Content author: AIMEILI Regulatory Editorial Team

Professional review: AIMEILI Medical Device International Registration Project Team

Sourcing principles: Priority is given to official regulatory authorities, international organizations, standards organizations and publicly available regulatory materials; industry media and project experience are used only as supporting references.

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