How Translation Studio work moves
Translation Studio is the middle path between raw AI output and sending files to professional linguists: your own team does the human pass, in Taia, on top of the AI translation. This page explains the model behind the buttons.
Two things, not one
The part that trips people up is that a task and an assignment are separate objects.
- A task is the work: "post-edit the German translation of this file". It belongs to one language of one project, and it stays put.
- An assignment is one person's turn at that task. It belongs to a person, and it can be declined, expire, or be handed to someone else.
One task can have several assignments over its life. That's why a task someone declined isn't lost — it keeps its history and waits for a new assignment.
The loop
| Step | Who | What happens |
|---|---|---|
| 1 | AI | The translation completes and the job is ready to review. |
| 2 | Manager | Clicks Assign for Editing, picks a task type (Post-Edit AI Translation, Revision or Proofreading) and a person. |
| 3 | Taia | Creates the task, sends the assignment, notifies the assignee. |
| 4 | Assignee | Accepts — the editor unlocks. Or declines, and the manager reassigns, returning to step 3. |
| 5 | Assignee | Edits the segments. Work saves as they go. |
| 6 | Assignee | Clicks Submit. The manager is notified. |
| 7 | Manager | Reviews with Preview. If another pass is needed, back to step 2. |
| 8 | Manager | Clicks Download Updated Files to rebuild the documents. |
Statuses
An assignment moves through:
| Status | What it means |
|---|---|
| Awaiting Response | Sent, not yet answered. Expires if the response deadline passes. |
| Accepted | Taken. The editor is unlocked for this person. |
| Rejected | Declined. The task stays and can be reassigned. |
| Submitted | The assignee says they're finished. |
| Expired | The response deadline passed with no answer. |
A task separately shows Ready to Start, In Progress, Completed, or Blocked.
Two deadlines
Assignments carry two dates that are easy to confuse:
- Response Deadline — how long the assignee has to accept or decline before the assignment expires.
- Task Deadline — when the finished work is due.
Only the first one expires anything.
Who can do what
| Team Member | Team Manager | Org Manager | |
|---|---|---|---|
| Be assigned work | Yes | Yes | Yes |
| Accept, edit, submit | Yes | Yes | Yes |
| Create and assign tasks | — | Yes | Yes |
| Preview any job in the team | — | Yes | Yes |
| Reassign a declined task | — | Yes | Yes |
Limited Team Members can work only on tasks explicitly assigned to them and cannot create projects. External Linguists are outside vendors: they see their assignments and nothing else. See user roles.
What Translation Studio deliberately does not do
It is kept simple on purpose, and it helps to know where the edges are:
- There is no formal approval step. When an assignee submits, the work sits in Submitted. A manager reviews by opening Preview and, if it's good, downloading the files. There is no approve or send-back button.
- Tasks don't block each other. Stacking a Revision after a Post-Edit does not make the second wait for the first. Both assignees can be in the editor at once. If you need a strict order, wait for the first to submit before assigning the second.
- Submitting doesn't lock anything. An assignee can keep editing after they submit, and the status stays Submitted.
If you need enforced sequencing, formal sign-off, and managed linguists, that is Professional Localization, where a Taia project manager runs the workflow.