Workflow

Deliver and export approved localization

Delivering turns reviewed localization into a controlled final version that is ready to use outside Localizethat.

Only markets that have completed the required review should be delivered.

Check what is ready

Different markets do not need to finish review at the same time.

Netherlands

7 of 7 approved

Ready to export

Sweden

7 of 7 approved

Ready to export

Germany

5 of 7 reviewed

Still in review

Approved markets can be delivered without waiting for unfinished markets.

Unfinished markets remain outside the delivered output.

Run final checks

Before delivery, Localizethat checks the localization for unresolved workflow and context issues.

  • All content items approved
  • No unresolved comments
  • Claims valid
  • Terminology consistent
  • Required wording preserved

Some checks may block delivery while others may require the user to review a warning.

The approved version

Approval creates the approved version of that localization.

The approved version should preserve who approved the content and when it was approved.

Once approved, the output is treated as the approved revision.

If approved content is edited later, it should become a new draft rather than silently changing the approved version.

Export it where you need it

After approval, export the approved localization in the format that fits your workflow.

Export approved content: the market list with approval counts, what is ready for export, and Download spreadsheet (CSV) and Copy approved translations actions.
Only approved wording is exported, and each market is exported on its own.
Download spreadsheet (CSV)Copy approved translations

Export only the market's language when you need a clean final document, or include source and market language when a side-by-side format is useful.

Default final exports should not contain internal comments or review signals.

What happens to unfinished markets?

A localization can contain both delivered and unfinished markets.

Only markets that have completed approval should be included in delivered output.

If a market is no longer required, it can be explicitly excluded rather than blocking the rest of the project.

Delivery is not where the value stops

Approved content can also become useful input for future localization.

Terminology decisions, preferred wording and other approved choices can be saved as reusable Brand Context.

See how Localizethat learns from approved decisions

Turn approved language into reusable knowledge.