Customer Cases
Runs customer cases through the same check every time.
Scope, review path and delivery for Enterprise & API.
Browse the topics covered on this page and jump to the section you need.

Coverage, requirements and turnaround for customer cases.
View details →
Turnaround, formatting and delivery notes for sitemap.
View details →
The steps, documents and review points involved in file evaluation.
View details →
Confirmed scope for privacy & policies, stated before any work starts.
View details →
The steps, documents and review points involved in terms & compliance.
View details →
Practical detail on all services: what we can confirm and what depends on the recipient.
View details →
Intake checklist and written scope for all file formats.
View details →
Coverage, requirements and turnaround for all document types.
View details →Practical detail on Enterprise & API, including whatever stays pending until intake.
Formatting is preserved on customer cases, including tables and stamps.
Second-reader review is mandatory on sitemap →not an optional add-on.
Every file evaluation request gets a named contact and a written turnaround.
Pricing for privacy & policies is confirmed after intake and does not move afterwards.
Pricing for terms & compliance is confirmed after intake and does not move afterwards.
Requirements for all services are checked against the receiving institution, not a generic standard.
Covers Enterprise & API end to end →documents, review and delivery.
Runs customer cases through the same check every time.
Covers sitemap without restructuring the source document.
Handles file evaluation against the terminology list you supply, or one we build.
Covers privacy & policies without restructuring the source document.
Handles terms & compliance against the terminology list you supply, or one we build.
Runs all services through the same check every time.
Where Enterprise & API fits, and the parts we cannot confirm without seeing the file.
Scope, format, deadline and glossary are agreed in writing at intake, so nothing is renegotiated later and the brief is fully documented.
A project glossary is locked before drafting, so sector terms stay consistent across the whole file and future revisions.
A domain translator drafts your file against the locked glossary, preserving layout, register and the exact wording of the source.
A separate linguist verifies terminology, numbers, dates and names line by line, never the original translator.
Fonts, tables, headers and numbering are rebuilt to match the source, and the final file is checked against it before it ships.
Selected feedback from public discussions about this need area.
We needed customer cases and the file came back with the layout intact.
Customer CasesVerified reviewWe needed sitemap and the file came back with the layout intact.
SitemapVerified reviewWe needed file evaluation and the file came back with the layout intact.
File EvaluationVerified reviewWhat each service level includes, so you can pick the one that fits the document.
Answers are limited to what we can confirm at intake.
We review the document, confirm the language pair and the receiving institution, then send pricing and turnaround in writing.
Practical detail on Enterprise & API, including whatever stays pending until intake.
Prices depend on the document and service level, so they are quoted after review rather than listed as a fixed figure.
Practical detail on Enterprise & API, including whatever stays pending until intake.
Tell us the document type and the language pair, and we will confirm what we need to start.
Tell us about your document and we will confirm the next step by email.
Send request