Translation company FAQ: clear answers for busy buyers

Your go-to translation company FAQ for stress-free vendor selection and smoother projects. Here you’ll find straight answers, checklists, and links to dig deeper.

translation company FAQ explained with process, quality and security

What does “quality” really mean in translation services? — translation company FAQ

Quality is repeatability and fitness for purpose—not just eloquent wording. A robust provider combines native, specialist linguists with a documented process (brief → terminology → translation → independent review → final checks). See the structure of our own translation services for how that looks in practice.

What defines quality in a translation company FAQ

A credible answer references standards and workflows. ISO 17100 sets requirements for roles, competencies, two-linguist review, and records. When a provider says they are ISO 17100-certified, it means an accredited auditor checks that the system exists and is used in real projects. If your content is public-facing or regulated, that matters. Learn what ISO 17100 covers on the official standard page. (iso.org)

Quality is also cultural: continual feedback loops, training, and measurable improvement. That’s why we document how we work in our continuous improvement and ongoing training pages—so you can see how lessons learned translate into fewer defects on your next job.

Finally, check domain expertise. For complex content, browse focused pages like technical translation or legal translation to verify the provider handles the risks typical in your sector.

How do pricing and quotes work?

Most quotes are based on word count, language pair, subject matter, and workflow. Prices reflect whether the job follows a two-linguist ISO 17100 path or a lighter path for internal use. Providers should tell you what’s included: translation, independent review, layout checks, and project management.

Expect transparent scoping. A helpful translation company FAQ spells out assumptions (file formats, reference materials, required terminology), plus options for speed vs. cost. Our translation services page outlines two service levels so you can choose what fits your risk and deadlines.

For multi-language or long-running programs, ask about team continuity and termbase management. Our “We translate the world” overview explains how stable teams and glossaries keep tone and terminology consistent across updates.

What timelines are realistic—and how to hit them

Turnaround depends on scope, complexity, and required reviewers. Good project managers propose a schedule with handoffs (translation, review, QA, DTP). If you’re up against a hard date, share it early; we can parallelize safely on well-prepared files.

Hit your dates by freezing scope, providing editable sources, and clarifying priority sections. Many FAQs recommend distinguishing “publish” content from “for reference” content; the former goes through the full ISO 17100 route, the latter can be lighter. Our “Zero Errors, Total Satisfaction” commitment describes how we protect quality when speed is critical.

Security, confidentiality, and GDPR compliance

Serious providers use NDAs, secure transfer, limited access, and auditable records. Under the EU GDPR, translation companies are typically processors: Article 28 requires a contract that defines processing and security duties, including sub-processor controls. You can review Article 28 directly on EUR-Lex or consolidated resources. (eur-lex.europa.eu)

Ask for the data flow: who sees your files, where they’re stored, and retention periods. Our operational pages (e.g., translation services) and client materials describe encryption in transit, role-based access, and documented deletion after delivery.

Certified translations vs. ISO-certified services

Two different things often get mixed up in a translation company FAQ. “Certified translation” is a legal result—a translator’s signed accuracy statement, sometimes notarized or with a Hague Apostille—used for official submissions. See our dedicated page on certified translations for common use cases and requirements.

ISO-certified services refer to the process standard (ISO 17100) behind regular projects. It governs how translation is planned and reviewed, not whether a document is legally certified. The official ISO listing summarises the scope and governance of the standard. (iso.org)

How to evaluate a provider beyond price

Look for proof, not promises:

If you want a quick sense-check, this translation company FAQ recommends requesting a small, representative pilot with terminology and layout requirements. Insist on reviewer independence and named roles; that aligns with ISO 17100’s principles. (iso.org)

What happens after delivery?

Post-delivery is where good partners shine. Expect a structured way to log feedback and corrections, update glossaries, and roll improvements into the next release. Our continuous improvement and ongoing training pages describe how we close the loop across projects and keep quality trending upward.

If your content is official (e.g., court or immigration), ensure you requested a certified translation from the outset. If you need that after the fact, we can often convert the delivered work into a certified package—ask our translation company team to confirm local rules.

FAQ

Q1. What’s the difference between “professional,” “certified,” and “sworn” translations?

“Professional” refers to expertise and process: native specialist translators, documented workflows, and independent review. Many buyers align this with ISO 17100 so outcomes are predictable. “Certified translation” is a legal package: the translator’s signed statement of accuracy (and, where required, notarization or an Apostille). “Sworn” translation exists in countries that appoint sworn translators; only these professionals can issue certain official translations. A single project can involve both: ISO-driven production quality and a certified or sworn legal wrapper for submission. Start by confirming what the receiving authority requires; we advise on the correct path and handle the paperwork so your documents are accepted the first time. (iso.org)

Q2. How fast can a translation company deliver without hurting quality?

Speed comes from preparation and parallelization—not skipping review. We plan handoffs across translators, revisers, and DTP while preserving glossaries and style. For urgent cases, an experienced linguist can self-revise with added QA, but for public-facing content we recommend the two-linguist ISO 17100 route. Share deadlines and source files early; editable formats and clear scope accelerate everything. On multi-file drops, we stagger deliveries so your teams can start approvals while the rest progresses. Our internal commitments and processes help maintain quality under pressure, but we will always flag risks honestly and propose the safest schedule. (iso.org)

Q3. How do you protect sensitive data during translation?

We operate under controller–processor contracts aligned to GDPR Article 28, restricting processing to agreed purposes, defining security controls, and governing sub-processors. Practically, that means encrypted transfer, role-based access, NDA-bound linguists, and time-boxed retention with documented deletion. We avoid unvetted public MT; where MT is approved, we use opt-out or on-prem options and perform human post-editing under ISO 18587 when required. We also redact sets of personal data on request and keep an audit trail of who accessed what and when. You can read Article 28 obligations on official EU sources to see what we put in writing with every client. (eur-lex.europa.eu)

Q4. What should I include in a good brief to get an accurate quote and fewer revisions?

A winning brief states purpose (publish vs. internal), audience, tone, and any regulatory constraints. Include reference materials (previous translations, term lists), style guides, and editable files. Flag priority sections and non-negotiables (legal clauses, UI character limits, numbers that mustn’t change). Tell us where the text will live (web, print, product) and any formatting needs (DTP, PDF rebuilds). With that, we recommend the right workflow—full ISO 17100 for publication or a lighter path for internal use—plus a realistic timeline. This simple preparation typically cuts back-and-forth, reduces defects, and shortens total time to approval. (m21global.com)

Leave a Reply

Your email address will not be published. Required fields are marked *

REQUEST A QUOTE NOW