You can automatically lock segments that should not be modified, preventing translators from changing reviewed and approved translations. Segment locking is initiated through workflow.

You can design a workflow that adds a Lock Segments automatic action, which prevents translators from changing certain segments. For example, if a segment has already been translated and approved, you might want to prevent further changes to the segment. The Lock Segments action either locks all segments or in-context matched (ICE) segments only. After you create a project that uses this locking workflow, when the translator opens a task in a WorldServer translation workbench, all segments with 100% in-context matches are locked (by the first automatic step). That is, the translator cannot change any segment that has been previously translated in that exact context. A lock icon indicates which segments are locked. Locking should be set to static for the translator (in the Advanced setting of the Translate step), meaning that this user cannot change the status of a lock.

When the translator completes the translation of the task, if you have a lock step after the translate step, all segments in the task are automatically locked. The reviewer then manually unlocks any segments that require translation changes. Locking should be set to dynamic for the Review step (in the Advanced setting of the Review step), meaning that this user can change the status of a lock. If there are no corrections to be made (in this locking workflow), the reviewer accepts the translation, and the task workflow is complete. If there are corrections required, the reviewer rejects the translation, an automatic step checks to make sure that at least one segment is unlocked (so that the translator can correct it), and then sends the task back to the translator for further work.