Philippines Dossier Language: English Submission and Certified Translation

1. Key takeaways

Yes, it is required. Philippine submissions must be in English, or in English together with Filipino. Non-English originals — Chinese test reports, quality system documents, instructions for use — must be accompanied by certified English translations. Compared with the English-only system in Singapore, the difference is that non-English originals still have to be translated, whereas Singapore accepts English originals and therefore needs no translation at all.

GRZAN note: the cost of translation is predictable and easy to budget; the risk it creates is not. Inconsistent terminology can make one component look like three different components across three modules, and no amount of correct grammar repairs that impression. The workstream can be remembered as 1 submission language, 1 glossary fixed before drafting starts, and 1 label red line that admits no exception.

• Submissions in English, with Filipino optional;
• Non-English originals accompanied by certified English translations;
• Labels in English; labels containing Chinese are not accepted;
• Sticker labelling permitted for supplementary local information on imports.

The sequencing point matters more than it appears. Terminology has to be settled before the first module is translated, because retrofitting a glossary across a finished dossier means reopening every document that used the old wording, and each reopening is a fresh opportunity for a version mismatch to enter the file. The same logic applies to the choice of translator: a single supplier working from a single glossary produces a more coherent file than several suppliers each working from their own understanding of the product.

2. Legal basis

The language requirement, the label rule and the authentication chain that applies to foreign-language originals are summarised below. The comparison row is included because the differences between neighbouring markets drive most scheduling decisions in a regional programme.

3. Expert insights

Insight 1: translation creates a consistency risk, not merely a cost. Translation itself is not difficult; terminological consistency is. Within a single Chinese technical document, several expressions may refer to the same component, and if those expressions are rendered as three different English terms in three different modules, a reviewer will reasonably conclude that three different objects are being described. The workable control is a project-level glossary that fixes the product name, model designation, component names and technical parameter names, with every translation following it. The glossary should be treated as a controlled document in its own right, versioned and dated, because a glossary that changes mid-project produces exactly the inconsistency it was created to prevent.

Insight 2: the required form of translation certification should be confirmed in advance. A certified English translation may in practice require a translator qualification statement, a translation agency stamp, or notarisation. Requirements can differ between document types and can change over time. It is prudent to confirm with the CDRRHR, before submission, which form of translation certification is currently accepted, so that the file is not returned for a reason that has nothing to do with its content. A single written confirmation at project start is sufficient to settle the question for the whole file.

Insight 3: label language is a hard line, and Chinese on a label leads to rejection. A label must carry the product name and model, the CMDN or CMDR registration number, the name and address of the manufacturer and of the local licence holder, the country of origin, the batch or serial number, the date of manufacture and the expiry date, the sterilisation status and method where applicable, storage conditions, warnings and precautions, and the intended use. Any Chinese on the label will cause the file to be returned. The remedy is sticker labelling: an English supplementary label applied over the original, carrying the locally required elements. Because the sticker becomes part of the approved labelling once accepted, its content has to be controlled to the same standard as the original artwork rather than treated as a warehouse task.

Insight 4: measured against its neighbours, the Philippine language workflow sits in the middle. Singapore is the lightest: English originals, no translation and no authentication chain. The Philippines sits in the middle: English submission, translation for non-English originals, and notarisation plus Apostille for foreign documents. Vietnam, Thailand and Indonesia are the heaviest: local-language submission, translation, and embassy legalisation for foreign documents. When planning across Southeast Asia, these differences in language and authentication workflow should be treated as scheduling variables rather than as administrative detail, because they determine how long each country file takes to assemble even when the underlying technical evidence is identical.

4. Practical recommendations

• Build a project glossary and fix terminology before translating. Prevent one object from acquiring several English names.
• Finalise labels at the submission stage. File an English label specimen so that later label changes are not required.
• Use sticker labelling for import-stage supplementary information. The added content must still match what was approved.
• Confirm the accepted form of translation certification with the CDRRHR in advance.

These four measures address the same failure from different directions: a dossier that is linguistically clean but terminologically unstable reads as inconsistent even when every individual sentence is correct. Fixing vocabulary at the start, labels at submission, sticker content at approval and certification form before filing keeps the language workstream from feeding defects into the technical one.

5. Verification checklist

• □ All documents in English, checked one by one
• □ Non-English originals accompanied by translations corresponding to the source
• □ Terminology consistent, checked against the project glossary
• □ Translation certification form confirmed against the current CDRRHR position
• □ Labels free of Chinese, verified on the specimen
• □ All ten label elements present, checked against the element list

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including the Philippines. Our team prepares CMDN/CMDR dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with the FDA Philippines, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com