Thai Technical Translation

Technical translation is a terminology-control problem

In technical work the difficulty is rarely the sentence; it is the consistency of a few hundred terms across a few hundred pages. A pressure-vessel specification that renders the same component three different ways in Thai will fail inspection review even though every individual sentence is defensible. Our process therefore begins with a term base extracted from the source and approved by the client's own engineer before translation starts.

The second discipline is unit and standard handling. We do not silently convert units; we render the source value and, where the destination reader needs it, add the converted value in brackets so an auditor can trace the original. Standard references — ISO, IEC, ASTM, JIS, TIS — are kept in their original designation because a Thai regulator checks the designation string, not a translated description of it.

Third is layout fidelity. Engineering documents carry meaning in their structure: drawing callouts, revision blocks, tag numbers on P&IDs, table footnotes. We reproduce the structure so the translated document can be laid alongside the original page for page, which is what a reviewing authority expects and what makes a revision cycle survivable.

Domains we handle and the constraints in each

Quality control we actually perform

1. Source triage: We identify document type, audience and destination authority. A manual for internal operators and a dossier for a regulator are edited to different registers even from identical source text.
2. Term base build: We extract candidate terms, propose Thai equivalents with rationale, and get the client's subject-matter expert to sign off before production. This one step removes most late-stage rework.
3. Translation by domain specialist: Assigned by field, not by availability. An electrical control narrative and a pharmaceutical IFU are not interchangeable work.
4. Bilingual revision: A second linguist compares source and target segment by segment against the approved term base, checking numbers, units and cross-references.
5. Technical review: Where the client provides an engineer, we run a review pass with them and record decisions back into the term base so the next document inherits them.
6. Layout and final QA: DTP to match the source, then a final check on figure numbering, table continuity, headers and revision blocks before delivery.

Certification, and when technical work needs it

Most technical translation is delivered as a working document with our Statement of Accuracy and company seal, which is what a client, contractor or auditor needs. Certification becomes relevant when the document enters an official process: a device registration dossier, a tender submission to a state agency, a patent filing, or a document that must accompany a legal claim.

Where the document must be used abroad, the chain matters. Until Thailand's accession to the HCCH Apostille Convention enters into force on 28 February 2027, documents leaving Thailand for a foreign authority generally require certification, Ministry of Foreign Affairs legalisation and then endorsement by the destination country's embassy. We tell clients which of their technical documents genuinely need that chain and which do not, because legalising an operations manual that nobody will ever authenticate is wasted money.

Common mistakes and how we avoid them

More questions we are asked

Do you sign an NDA before receiving files?

Yes. We execute a confidentiality agreement before any technical material is shared, and we can work within the client's own NDA template.

Can you keep our existing Thai terminology?

Yes, and we prefer to. If you already have approved shop-floor or regulatory terminology, we import it as the authoritative term base.

What file formats can you handle?

Editable office formats, PDF, and common DTP and CAD-export formats. For drawings we work from exported text layers or a rebuilt callout table depending on what you can supply.

Is machine translation used?

Not as a delivery method. Translation memory is used for consistency and cost control on revisions, with human translation and a separate bilingual revision pass on every segment.

Can the translation be certified for a government submission?

Yes. We issue a numbered Statement of Accuracy with the company seal and, where the receiving authority requires it, arrange notarisation and onward legalisation.