Localization Jobs
Write back to drafts
Accepted translations must be written back to Kit drafts before merging: preview comparisons across three texts before confirming.
Requester
Accepting a delivery round does not immediately update the Kit. Write-back is the final step: aligning delivered translations with your active draft and committing them to the shared draft.
When write-back is needed
- After a requester clicks Accept in reviews, the job moves to "Write-back pending".
- If the draft bound to this job is no longer the active shared draft, write-back is blocked until you restore the original active draft—translations are never written into unrelated drafts.
How to write back
- 1
Open editor
On the job details page, click More → Open editor to open the read-only editor as a requester.
- 2
Click Accept
Click Accept in the header. The system runs a write-back preview, comparing text across three states: Issued, Current draft, and Delivery.
- 3
Resolve conflicts per segment
The preview highlights differences. For conflicting entries, choose your resolution: Use delivery (apply delivered text), Keep current (retain draft value), or Skip (do not write back this entry).
- 4
Confirm write-back
Once all conflicts are handled, click Confirm write-back. Translations apply to the draft, and the job completes.
Write-back rules
- Write-back only modifies the draft, without generating a version or signifying a release or LQA sign-off. Publishing externally still requires committing and releasing a version.
- Keys no longer present in the draft can only be skipped; they are not recreated.
- If source text or context changed after issuing, accepting preserves current source/context while writing translations; confirm prompts segment by segment.
- If the draft changes after preview generation, you must re-preview before confirming—write-backs never overwrite changes you haven't reviewed.