Translation service providers
Keep the language brief and delivery responsibilities explicit.
Organize customer contacts, source material, reviewer tasks and delivery versions around translation work while CAT tools and linguistic quality checks stay specialist processes.
- 01Clarify
- 02Assign
- 03Resolve
- 04Deliver
The assignment needs more than two language names.
A translation provider needs intended use, audience, source version and the person who can resolve terminology questions. Tsumira supports the business coordination around that assignment. It is not a translation memory, terminology database or certified translation service, and multilingual communication does not establish linguistic or legal acceptance of a deliverable.
A concrete workflow
Clarify
Record language direction, use and authoritative source material.
Assign
Give translation and review work explicit owners and dates.
Resolve
Record customer answers to terminology and scope questions.
Deliver
Check the final file and share the intended version.
Make the language brief actionable.
Record the customer company and contacts in CRM. A shared brief can state language direction, audience, format and unresolved questions. Keep the source version identifiable and agree how customer revisions are handled before contributors start work against different versions of the same document.
- Customer contacts and source-version notes
Separate translation, review and delivery work.
Assign preparation, linguistic review and delivery checks with owners and dates. Use time records when appropriate for the service model. Tsumira organizes responsibilities; language production, translation memory leverage and word-count-based quoting remain in your chosen professional tools and commercial process.
- Owned review tasks and actual effort
Share the reviewed output without exposing internal discussion.
Store delivery files in Drive and give internal contributors appropriate access. An external link opens the particular version shared, not every later upload, and does not expose internal comments. Keep terminology decisions in a maintained document so the next assignment can consult them without claiming a dedicated terminology engine.
- Controlled files and reusable decision notes
An illustrative working example
Illustrative scenario: a product guide translation
A language provider receives a revised product guide. The coordinator records the source version, assigns review tasks and captures customer answers about terminology. Translation happens in specialist software. The reviewed output is shared through Drive while internal discussion and source-management responsibilities remain clear. The client replaces a source paragraph after translation has begun. The coordinator records which version changed and confirms the commercial effect before assigning revision work. A reviewer checks that the final delivery corresponds to the agreed source. The pilot tests whether another coordinator can identify the current file, terminology answers and remaining action without opening every historical email. Specialist translation production stays in the chosen language tools.
Questions about this topic
Does Tsumira replace a CAT tool?
No. Translation memories, terminology matching and specialist linguistic workflows remain in appropriate language tools.
Are AI drafts certified translations?
No. Human professional review and any legal certification requirements are separate from AI drafting or multilingual communication.
Can source changes be tracked commercially?
Record the changed request and revise the agreed scope before assigning more work. Automatic word-count pricing is not implied.
Can clients receive only the reviewed file?
A Drive external link shares a specific version while keeping internal file conversations private.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
