Enterprise & API
Tracked per project: enterprise & api.
Practical detail on File Evaluation, including whatever stays pending until intake.
Browse the topics covered on this page and jump to the section you need.

Turnaround, formatting and delivery notes for enterprise & api.
View details →
What user demand rankings involves, what we need at intake, and how long it takes.
View details →
The steps, documents and review points involved in translation assessment.
View details →
Intake checklist and written scope for 2 page free trial.
View details →
Confirmed scope for customer cases, stated before any work starts.
View details →
Turnaround, formatting and delivery notes for sitemap.
View details →
How privacy & policies is handled here, with the receiving-institution rules called out.
View details →
Intake checklist and written scope for terms & compliance.
View details →Scope, review path and delivery for File Evaluation.
Scope for enterprise & api is fixed in writing before the first page is touched.
Documented handling for user demand rankings, stated up front.
Pricing for translation assessment is confirmed after intake and does not move afterwards.
Documented handling for 2 page free trial, stated up front.
Formatting is preserved on customer cases, including tables and stamps.
Every sitemap request gets a named contact and a written turnaround.
Covers File Evaluation end to end →documents, review and delivery.
Tracked per project: enterprise & api.
Available for user demand rankings on the same review path.
Runs translation assessment through the same check every time.
Covers 2 page free trial without restructuring the source document.
Available for customer cases on the same review path.
Available for sitemap on the same review path.
Scope, review path and delivery for File Evaluation.
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 enterprise & api and the file came back with the layout intact.
Enterprise & APIVerified reviewWe needed user demand rankings and the file came back with the layout intact.
User Demand RankingsVerified reviewWe needed translation assessment and the file came back with the layout intact.
Translation AssessmentVerified 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.
What this involves, and the points we confirm at intake.
Guides and checklists published on this site.
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