Documents
Part of Translation management software: workflow fit
Testing version changes in a multilingual content project
Use a controlled source change to check translated versions, review status and the next multilingual content delivery.
Test a source change by updating a small, already translated project and tracing each target language and review step. The decision is whether the team can identify the current source, preserve unaffected work, recheck changed translations and keep an old target version out of the next delivery.
Build a controlled change set
Use fictional or cleared content: an unchanged paragraph, a sentence whose meaning changes and a heading that is removed. Give each unit a stable identifier. Save the original source, translations and review states before editing.
Write the expected outcome for each unit. The unchanged paragraph should remain recognisable. The changed sentence should be assigned for translation and review. The removed heading should be absent from the next delivery.
Add a late correction while a reviewer has the job open. Check which source version appears after a reload.
Change / Question to answer
- Sentence edited
- Which target text and review state now need attention?
- Unit added
- Who receives it, and in which languages?
- Unit removed
- Is it absent from the delivered output?
- Reviewer active
- Is a reload required to see the new source?
- Delivery repeated
- Which source and target versions were used?
Check the update route
In Lokalise Expert, an updated-key workflow responds to changes in base-language translation values; metadata and tag edits do not trigger it. The workflow start step includes options for monitored language, target languages and monitored key type, so check how those options apply to the change set.
Inspect the generated tasks. For file downloads, check the branch, file format and selected languages: downloads are branch-specific, and a new file is generated on export. Compare the exported text with the intended release.
In Phrase TMS, the manual Update source tool updates a previously imported file with a new source file and overwrites the older version. In continuous jobs, unchanged segments are carried forward to the updated file.
Workflow steps have a hierarchical order: edits in one step propagate to a higher step, and once a segment is edited or confirmed in the higher step, changes from lower steps are not propagated. Check the actual job and step statuses before release.
Lokalise vs Phrase TMS Update Behaviour
- Trigger for WorkflowLokalise: only base-language changes; Phrase: manual update or continuous jobs
- File ExportLokalise: branch-specific, new file on export; Phrase: overwrites older version
- Unchanged SegmentsPhrase: carried forward in continuous jobs; Lokalise: not affected by metadata/tag edits
- Workflow HierarchyIn Phrase: higher steps override lower ones; once confirmed, lower changes are not propagated
Reconcile the next delivery
After updating, ask someone who did not edit the source to identify the current source version, target text in each language and remaining review work. Export or synchronise a safe sample and compare it with the expected outcomes. Pay particular attention to the removed heading and changed sentence; a completion label alone does not establish which content was reviewed.
Keep a separate copy of the original source and delivery before an overwrite operation. If a correction cannot be traced to the delivered target, hold that release while the team resolves the gap. Repeat the check after a connector or workflow change.
Post-Update Delivery Verification
- Verify current source versionAsk non-editor to identify source version used in delivery
- Check target texts per languageCompare exported sample against expected outcomes
- Validate removed contentEnsure removed heading is absent from delivered output
- Confirm review status accuracyCompletion label alone does not confirm which content was reviewed
- Retain original backupKeep copy of original source and delivery before overwrite
