The problem
Teams paste contracts, packets, and scans into generic translators and lose layout, page order, and any link back to the original file. The translation then lives in a chat thread instead of the matter or the shipment it belongs to.
How the workflow runs
Extract the source text
The first step reads the upload so the translator works from the document body, including text that needs OCR, rather than from a copy someone pasted.
Translate into English
The translate step targets English and keeps formatting. Change the target language on the canvas when a workspace needs a different language.
Return the result
The hosted translator shows run status and the finished translation next to the source document so reviewers can compare them.
What the hosted app shows
Users upload a file, add notes about the target language, and download or read the translation from the results page. The same app can be shared with operators who should not see the workflow canvas.
Who it is for
Operations, legal, and customer teams that receive documents in another language and need an English version tied to the source file.
Questions
The starter translates into English. Set a different target language on the translate step when you need another language.
The translate step is configured to preserve formatting. Complex scans may still need a quick visual check against the source file on the results page.
Yes. Add the translate step to a contract, RFP, or portal workflow when only part of the packet arrives in another language.