ISO 17100 CERTIFIED · SAME-DAY TURNAROUND
How Technical Translation Differs from General Translation
Technical translation converts specialised documents with strict terminology and regulatory accuracy; general translation handles everyday content where fluency and cultural tone matter more than
- ISO 17100 Certified
- Same-day Turnaround
Get a free, no-obligation quote
Choosing between technical translation and general translation shapes cost, turnaround and legal exposure for UK businesses commissioning work from a London ISO 17100 agency. Technical translation wins for regulated, terminology-dense documents; general translation wins for everyday content where fluency carries the message.
What is the difference between technical translation and general translation?
Technical translation converts specialised documents containing domain terminology, regulated content and measurable specifications; general translation converts everyday texts where fluency, tone and cultural context matter more than terminological precision or regulatory compliance. Technical translation is defined by the presence of controlled vocabulary, subject-matter expertise requirements and a formal quality workflow, whereas general translation is defined by its priority on natural-sounding, culturally adapted output for a broad audience.
The difference between general and technical translation shows up on four measurable axes, each of which determines which tier your document falls into:
- Terminology density — how many controlled terms per 1,000 words the document contains, and whether those terms are managed in a dedicated termbase.
- Regulatory exposure — whether UK MDR, MHRA, HSE, CLP or UKIPO rules apply to the translated output.
- Cost of error — the legal, safety or commercial consequence of a single mistranslated word or unit of measurement.
- Reviewer profile — whether the final reader is a regulator, engineer or clinician, or a general member of the public.
A single high score on any axis forces a technical-tier workflow, including ISO 17100 Translate–Edit–Proofread (TEP) quality steps and a subject-matter-expert linguist. A low score across all four means general translation is appropriate, with a single reviser pass focused on fluency and style delivering the required output at a faster throughput rate.
What is technical translation?
Technical translation is the translation of specialised documents — user manuals, engineering datasheets, patents, safety data sheets, clinical protocols and software strings — performed by a subject-matter-expert linguist using controlled terminology, CAT tools and an ISO 17100 Translate–Edit–Proofread workflow. Technical translation requires deep understanding of the source sector, not only strong language skills.
We deliver technical translation across 200+ languages under ISO 17100, with same-day turnaround available for urgent updates. Our operational example is Technical Translation in Liverpool, which shows how the TEP workflow runs on the ground for engineering and life-science clients.
What types of documents require technical translation?
There are 8 common document classes that require technical translation:
- User manuals and user guides for regulated products.
- Engineering datasheets and technical specifications.
- Safety data sheets (SDS) under HSE COSHH and CLP.
- Medical device instructions for use (IFU) under UK MDR.
- Patents filed at the UKIPO.
- Clinical trial protocols reviewed by MHRA.
- Software UI strings, help content and localisation files (XLIFF, JSON, .strings, .resx) — see Software and App Localization in Nottingham.
- Technical specifications for public-sector tenders.
Which technical sectors rely on technical translation most?
Technical translation is most critical in 6 UK sectors:
- Medical devices under UK MDR and UKCA marking.
- Pharmaceuticals under MHRA labelling rules.
- Engineering and manufacturing, including CE and UKCA conformity files.
- Chemicals under HSE COSHH and CLP for SDS.
- Software, IT and app localisation.
- Patent filings at the UKIPO.
Finance, legal and fintech also commission technical translation services when terminology and regulatory exposure justify the tier.
Services
What is general translation?
General translation refers to translating everyday texts — correspondence, blog articles, marketing copy, personal letters, general web content — that use non-specialised vocabulary and prioritise fluency, tone and cultural adaptation over strict terminology control or regulatory accuracy. A general translation is produced by a fluent bilingual linguist with strong command of both languages and cultural sensitivity; deep subject-matter expertise in a technical sector is not required because the source material does not contain controlled terminology or regulated specifications.
- Personal correspondence and letters.
- Marketing copy and blog articles.
- General website pages for a broad audience.
- Internal business emails and notices.
- Non-specialised informational articles.
How is technical translation different from general translation across the 6 key differences?
Technical translation and general translation differ on 6 axes: terminology density, subject-matter expertise, regulatory exposure, quality workflow, tools and translation memories, and cost per word. General translation prioritises fluency and cultural nuance; technical translation prioritises accuracy, consistency and compliance. Both are two of the most common types of translation UK buyers commission, but the resources, timelines and pricing that apply to each are markedly different.
Technical translation vs general translation — comparison table
The table below sets the two tiers side by side so UK buyers identify their tier at a glance.
| Axis | Technical translation | General translation |
|---|---|---|
| Terminology | Controlled, managed in termbases and translation memories | Everyday vocabulary, synonyms accepted |
| Linguist profile | Subject-matter expert with sector background and ISO 17100 credentials | Fluent bilingual translator with cultural sensitivity |
| QA workflow | ISO 17100 TEP with SME review and terminology QA | Single reviser pass focused on fluency and style |
| Tools | CAT tools, TMs, termbases, post-edited MT | CAT tools optional |
| Throughput | 1,500–2,000 words per linguist per day | 2,000–2,500 words per linguist per day |
| Price band (GBP) | From £30 per page plus SME and terminology premium | From £30 per page |
| Reviewer | Regulator, engineer, clinician, patent examiner | General target audience |
How does terminology differ between technical and general translation?
Technical translation requires controlled terminology managed in termbases and translation memories, because a single mistranslated term can cause regulatory or safety failure. General translation uses everyday vocabulary where synonyms are acceptable and stylistic variation is welcome. Terminology management enforces cross-document consistency so that repeated technical jargon stays identical across a 500-page manual set or a suite of regulatory submissions. CAT tools segment the source text and integrate both the termbase and the translation memory at the point of translation, ensuring the approved equivalent is applied every time a controlled term appears.
How does accuracy differ, and why does accuracy matter more in technical translation?
Accuracy matters more in technical translation because errors carry measurable regulatory, safety or commercial cost. Three worked examples show the exposure:
- Torque spec mistranslated — a wrong Nm value in an engineering manual voids UKCA conformity and triggers product recall.
- Dosage unit wrong — mg swapped with mcg on a medical device IFU breaches MHRA rules and endangers patients.
- Hazard pictogram mislabelled — a wrong CLP pictogram on an SDS breaches HSE COSHH duties and blocks workplace use.
General translation errors produce awkward phrasing or a tone mismatch — outcomes that affect reader experience rather than legal standing or product safety.
How does the linguist profile differ — technical translator vs general translator?
A technical translator is a linguist with an engineering, medical, legal or scientific background plus ISO 17100 credentials, while a general translator relies on strong command of both languages and cultural sensitivity without needing subject-matter expertise. The technical translator must read diagrams, resolve ambiguous source text, apply sector-specific conventions and validate output against regulatory norms. The general translator brings cultural intelligence and stylistic fluency — skills that are equally demanding in their own domain but applied to entirely different source material.
How does the QA workflow differ?
Technical translation runs the full ISO 17100 Translate–Edit–Proofread (TEP) workflow with a subject-matter-expert reviewer and terminology QA, while general translation typically uses a single reviser pass focused on fluency and style. The lower throughput of 1,500–2,000 words per linguist per day in technical TEP reflects the additional time required for terminology lookup, source-text analysis and SME review. The TEP steps are:
- Translate — an SME linguist produces the first target-language draft, applying termbase and translation memory matches.
- Edit — a second qualified linguist compares source against target for accuracy, terminology compliance and completeness.
- Proofread — a final reviewer checks the translated document for consistency, formatting and overall readability before delivery.
What skills does a technical translator need that a general translator does not?
A technical translator requires a combination of linguistic proficiency and domain expertise that a general translator is not expected to hold. Where a general translator succeeds through cultural sensitivity and strong bilingual fluency, a technical translator must also understand the subject matter deeply enough to identify errors in the source, resolve ambiguous specifications and produce output that satisfies a regulator or engineer rather than a general reader.
A technical translator needs 5 skills beyond general fluency:
- Subject-matter expertise in the target sector (medical, legal, engineering, IT) — the translator must understand the content, not merely the words, so that ambiguous or erroneous source passages are flagged rather than faithfully reproduced incorrectly.
- Terminology management using termbases and CAT tools — controlled terms must be applied consistently across every segment, with deviations caught during the edit stage of the ISO 17100 TEP workflow.
- Working knowledge of UK regulatory frameworks — including UK MDR, MHRA requirements, HSE COSHH and CLP obligations, and UKIPO patent filing conventions, because translated documents must satisfy these frameworks in their final form.
- Ability to read technical source material — including engineering specifications, diagrams, IMRaD-structured scientific papers and legal patent claims, each of which carries its own document conventions and structural logic.
- Disciplined consistency across long documents and project sets — a 500-page manual translated across multiple linguists requires identical terminology throughout; the technical translator enforces this via translation memories that recycle previously approved segments.
ISO 17100 credentials formalise these competencies: a credentialled technical linguist has demonstrated both language proficiency and the professional processes needed to deliver accurate, consistent, regulation-ready output.
Why is technical translation important for UK businesses?
Technical translation is important for UK businesses because domestic regulations require accurate, terminology-consistent documentation, and a single translation error can block market access, trigger product recall or create legal liability. Businesses that export products, operate in regulated industries or handle hazardous materials are legally required to provide translated documentation that meets specific standards — and those standards demand the subject-matter expertise and ISO 17100 quality workflow that technical translation delivers.
The four primary UK regulatory drivers that make technical translation a business necessity are:
- UK MDR and UKCA — translated Instructions for Use and labelling are mandatory for medical devices and conformity-marked products sold in Great Britain, and errors in these documents can trigger regulatory non-compliance and product withdrawal.
- MHRA — pharmaceutical labelling, patient information leaflets and clinical trial documentation must be accurately translated and terminology-consistent to satisfy MHRA review.
- HSE COSHH and CLP — Safety Data Sheets for hazardous substances used in UK workplaces must be translated with correct CLP pictograms, hazard statements and precautionary statements; mistranslations breach employer duties under COSHH.
- UKIPO — patent filings require exact claim translation, because a mistranslated claim boundary can narrow the scope of protection or invalidate the filing entirely.
Beyond product regulation, Home Office and UKVI evidence rules require certified, accurate translation for immigration and visa documentation — extending the need for technical-tier accuracy into the HR and legal functions of many UK businesses. With coverage across 200+ languages under ISO 17100 quality standards, a properly resourced technical translation service allows UK businesses to meet these obligations in every market they operate in.
What are the main challenges of technical translation?
Technical translation is challenging because it combines the inherent difficulty of cross-language transfer with the additional demands of domain expertise, regulatory accuracy and long-term document consistency. Each challenge has a direct operational consequence: unresolved, any one of them can introduce errors that carry legal, safety or commercial cost.
There are 5 main challenges of technical translation:
- Complex terminology without direct target-language equivalents — highly specialised terms in engineering, medicine or law sometimes lack an established equivalent in the target language, requiring the linguist to apply a controlled neologism recorded in the termbase rather than an improvised approximation.
- Cross-document consistency across releases and product lines — a product range may span hundreds of documents translated by multiple linguists over several years; translation memories that recycle previously approved segments enforce consistency, but they must be maintained and updated as terminology evolves.
- Keeping pace with evolving UK and EU regulations — regulatory frameworks such as UK MDR, CLP and UKIPO patent rules change over time, and translated documents must reflect current requirements rather than the rules that applied at the date of the original translation.
- Integrating translation memories with client CMS, DITA repositories or Git — technical documentation is increasingly managed in structured content environments; connecting CAT tools and translation memory assets to these systems requires technical integration work that sits outside pure linguistic skill.
- Coordinating subject-matter expert review under tight deadlines — the ISO 17100 TEP workflow requires a qualified SME reviewer at the edit stage; securing that reviewer’s time while meeting same-day or rapid-turnaround deadlines is a scheduling challenge that requires a well-resourced project management process.
Rush handling is available for urgent technical updates, though it carries a 25–50% surcharge that reflects the additional coordination required to compress the TEP workflow without reducing quality.
How does technology support technical translation?
Technology supports technical translation by automating repetitive linguistic tasks, enforcing terminology consistency and enabling subject-matter-expert linguists to focus their attention on the segments that genuinely require human judgement. Four tool categories each address a distinct aspect of the technical translation workflow:
- CAT tools — segment the source text into manageable units and integrate both termbases and translation memories at the point of translation, so the linguist sees approved equivalents for controlled terms and previously translated segments without leaving the working environment.
- Translation memories — store every previously approved segment and recycle it automatically when an identical or closely matching source sentence recurs, enforcing cross-document consistency and reducing the volume of new translation required on updated documents.
- Termbases — hold the controlled terminology for a client, product line or sector, and surface the approved target-language equivalent whenever a controlled source term appears; entries are updated as regulations or product specifications change.
- Machine translation with full post-editing — accelerates high-volume technical documentation by producing a machine-generated draft that a subject-matter-expert linguist then reviews, corrects and approves to ISO 17100 standard.
Are CAT tools and machine translation enough on their own?
CAT tools and machine translation accelerate technical translation but cannot replace a subject-matter-expert human reviewer. Machines apply statistical or neural pattern matching; they cannot verify whether a translated torque value satisfies UKCA conformity, resolve an ambiguous pronoun reference in a patent claim, or take legal responsibility under ISO 17100 for the accuracy of the final delivered document. Only a qualified linguist with sector knowledge can perform those functions. Technology is therefore a force-multiplier for the expert human, not a substitute for them — and the throughput figure of 1,500–2,000 words per linguist per day in a technical TEP workflow reflects the irreducible time that genuine expert review requires.
What is the difference between technical and literary translation?
Technical translation prioritises terminological accuracy and regulatory compliance for factual documents; literary translation prioritises voice, style, rhythm and cultural resonance for creative works such as novels, poetry and drama. The two disciplines demand entirely different translator profiles and quality criteria, and a linguist who excels in one rarely operates at the same level in the other.
A technical translator is a subject-matter-expert linguist with sector credentials and ISO 17100 qualifications, trained to produce zero-deviation, terminology-consistent output that satisfies a regulator or engineer. A literary translator is a writer in the target language, trained to recreate the artistic effect and emotional register of the source — an outcome that may legitimately involve departing from the literal words when doing so better preserves the author’s voice.
The quality workflow differs just as sharply: technical translation runs the full ISO 17100 Translate–Edit–Proofread cycle with terminology QA and SME review, while literary translation is evaluated against aesthetic criteria — does the target-language text read as literature? — rather than against a termbase or regulatory checklist. The cost of error also differs: a mistranslated controlled term in a medical device IFU can breach MHRA requirements and endanger patients, whereas a literary translator’s interpretive choice, even if debatable, rarely carries legal consequence. Technical vs literary translation therefore splits on a single fundamental question: is the purpose of the document to transfer precise specifications, or to transfer a human voice?
What are the four types of translation?
The four common types are technical translation, general translation, literary translation and specialised translation (legal, medical, financial). Each differs in terminology density, linguist profile and quality workflow:
- General translation — everyday content, fluency-first.
- Technical translation — regulated, terminology-controlled documents.
- Literary translation — novels, poetry, drama; voice and style lead.
- Specialised translation — legal translation services, medical translation services and financial translation, treated as sub-types of technical translation for regulated content.
How do you choose the right type of translation for your document?
To choose the right type of translation, score your document on 4 axes: terminology density, regulatory exposure, cost of an error, and reviewer profile. A high score on any axis means technical translation; a low score across all four means general translation is appropriate. The decision flow for choosing the right type is:
- Read the source text — count controlled terms per 1,000 words.
- Check regulator exposure — does MDR, MHRA, HSE or UKIPO apply?
- Estimate error cost — recall, injury, contract loss, or none?
- Identify the reviewer — regulator, engineer, clinician, or general reader?
- Map the score — high on any axis routes to technical; all-low routes to general.
- Receive an indicative GBP quote from £30 per page, tier-adjusted.
When is general translation the right choice?
General translation is the right choice when the document is non-regulated, uses everyday vocabulary, targets a broad audience, and a stylistic imperfection has no legal or safety consequence. Typical cases: marketing blog posts, internal emails, personal correspondence, general website pages.
When is technical translation required?
Technical translation is required when the document contains sector-specific terminology, is subject to UK regulation, carries measurable cost of error, or will be reviewed by a subject-matter expert. Typical cases: medical device IFU, SDS, patent claims, engineering manuals, clinical protocols, software strings.
How do you get a quote for technical or general translation in London and the UK?
To get a quote, send the source document to our London agency; we return a fixed GBP quote from £30 per page within one working day, confirm the ISO 17100 workflow tier, and deliver same-day for urgent work in 200+ languages under a signed SoW. Start with our hub, Professional Translation Services in London, UK, and attach the file for a tier recommendation.