Bureau Works supports multiple workflows designed to optimize the translation and localization process. Each workflow consists of a predefined sequence of steps that dictate the progress of a project, ensuring efficiency and consistency.

Bureau Works workflows are built using three primary types of steps: Translation, Review, and External Processing.

With over 20 different available steps, users have the flexibility to configure workflows tailored to their needs. However, to maintain consistency and streamline processes, understanding each step’s function and placement is crucial.

The Translation step is the foundation of any workflow.

It involves rendering text from the source language into the target language, either manually by a linguist or through machine translation.

A Translation task can be opened in the Bureau Works editor, where the target text may either be empty or pre-filled with content from pre-translation. Translators have full access to editor functionalities, depending on their permissions, allowing them to modify segments, leverage translation memories, apply termbase suggestions, and use machine translation assistance if enabled. A task can only be delivered once all segments are confirmed, ensuring completeness and quality control.

Review steps are used to refine translations, ensuring accuracy, consistency, and adherence to project guidelines.

Currently, review steps function identically regardless of their label—the assigned name is purely an identifier and does not alter functionality.

Like the translation step, they open in the Bureau Works editor, but with key differences. The target text is always pre-filled with the content from the previous step—either the translation or another preceding review. However, review steps remain in read-only mode until the previous step is completed, preventing premature modifications. Once unlocked, reviewers have full access to the editor (based on their permissions), enabling them to refine translations. Additionally, if the review unit is configured for categorization, reviewers can expand fields to justify changes and categorize modifications, ensuring a structured feedback process.

External processing steps involve work conducted outside the Bureau Works editor. These steps do not open within the platform; instead, Project Managers (PMs) can download the latest translated files from the last completed step and share them externally with linguists or specialists responsible for tasks like desktop publishing (DTP), quality assurance (QA), voiceover, or sworn translations. Once the external work is completed, the processed files can be sent directly to the client.

In Bureau Works, workflow steps follow a predefined sequence. While users have the flexibility to select which steps to include in their workflow, the order in which they appear remains fixed. For example, it is possible to configure a workflow with Translation, Review, and In-Country Review (ICR) or one that includes Translation and DTP, but it is not possible to place DTP before Review. The system automatically arranges steps according to a structured sequence to ensure consistency and efficiency in project execution.

While steps can be arranged freely, Bureau Works also allows for Custom Workflows, where predefined sequences of steps can be assigned based on file extensions and project preferences. This feature enables users to streamline project setups by automatically applying a preferred step sequence when a new project is created. For more details on setting up custom workflows, refer to our Managing Your Custom Workflows article.