Process and Quality

How we work: an ISO 17100-aligned process for medical and financial Arabic

Every file that comes to Lingoarabia goes through the same three stages, whether it is a 300-word patient card or a 100,000-word device documentation set. The process follows the structure of ISO 17100:2015: translation by a qualified subject linguist, revision by a second linguist, and a final quality check before delivery. We describe it here so a procurement or vendor manager can see exactly what they are buying.

The three-stage workflow

Stage 1: Translation. The file is assigned to a linguist with training in the subject. Life sciences work is led by Dr. Ola Siam, a pharmacist. Financial work is led by Samer Diaa, a management accountant. The translator works in a CAT tool against the client glossary, translation memory and style guide, and logs every source ambiguity as a query rather than guessing.

Stage 2: Independent revision. A second linguist compares source and target segment by segment. The reviser checks meaning, terminology, numbers, units, register and completeness, and records changes so the client can see what was corrected. The translator and the reviser are never the same person.

Stage 3: Final QA. The revised file is run through Xbench and a written checklist: untranslated segments, number and tag mismatches, glossary breaches, double spaces, inconsistent translations of repeated segments, and formatting. The project lead signs the delivery off.

Subject qualification

ISO 17100 sets out who may act as a translator. Dr. Ola Siam meets the translator qualification criteria of ISO 17100:2015, clause 3.1.4 (b) and (c), through her pharmacy degree and 17+ years of full-time translation. Samer Diaa holds the CMA and an MBA and has worked as a finance manager and senior accountant, so he reads an income statement the way the author of it does. Additional linguists on volume projects are vetted against the same clause before they join a framework agreement.

Terminology management

We work to the client glossary and termbase first. Where none exists, we build one during the first project and hand it over at delivery, so the second project starts from an approved base. For accounts that need it, we author the Arabic style guide itself: register, numerals, treatment of English terms, and the sign-off criteria an in-country reviewer should apply. We have written such guides for pharmaceutical, consumer and corporate accounts.

Tools

Trados Studio, memoQ, Wordfast Pro and XTM for translation; Xbench for QA. We also work inside client portals and translation management systems when the client prefers to keep files and memories on its own platform. Over one million words of clinical reference content were translated inside one client’s own platform between 2024 and 2026.

Post-DTP proof review

Typeset Arabic breaks in ways English does not. Letters disconnect, lines break inside a word, numerals flip, and English product names in an Arabic sentence end up in the wrong order. We review the typeset proof before print or release and return a marked-up PDF covering right-to-left layout, line breaks, letter joining, numerals and mixed Arabic-Latin text. We review; we do not typeset.

Confidentiality

An NDA is signed before any file moves. Where a client’s quality management system applies, we work inside it: controlled terminology, change logs, SOPs and audits. Dr. Siam has worked this way under a direct contract with a global medical-device manufacturer since 2016. No confidential content is put through public cloud machine translation without the client’s written approval. Files are deleted on request after delivery.

Queries and delivery

Queries are collected in a single sheet and sent at agreed points, not one by one. Delivery is in the format requested: bilingual CAT package, target-only document, TMS upload, or both. Each delivery includes the QA report when the client wants it.

Capacity

A senior linguist translates 4,000 to 5,000 words a day and reviews 7,000 words a day. Larger volumes are split across vetted linguists under one project lead and one termbase, with the lead holding the final revision pass so the Arabic reads as one voice.

If you need a documented process you can describe to your own auditors, request a quote and tell us which of these stages you need.

Frequently asked questions

Does the company hold an ISO 17100 certificate?
Can you work in our translation management system instead of your own tools?
Do you use machine translation?
What does the revision stage actually change?
Can you review Arabic that another vendor produced?
Does the company hold an ISO 17100 certificate?

No. Our workflow follows the ISO 17100:2015 structure and our lead linguists meet its translator qualification criteria, but the company has not been audited for certification. We say “ISO 17100-aligned” for that reason.

Can you work in our translation management system instead of your own tools?

Yes. We work in XTM, memoQ server, Trados GroupShare, Smartcat, Wordbee, Phrase and client-specific portals. Memories and termbases then stay on your platform.

Do you use machine translation?

Only when the client asks for MTPE, and never on confidential content through a public cloud engine without written approval. Post-editing is done to full human quality against the same QA checklist.

What does the revision stage actually change?

Terminology against the glossary, numbers and units, omitted or added content, register and readability for the intended audience. Changes are tracked so you can audit them.

Can you review Arabic that another vendor produced?

Yes. We offer revision, LQA scoring and in-country review of third-party translations, with a written report of error categories and severity.