Multi-stage projects

A multi-stage project is a coordinated set of stages that allows users to achieve specific marketing objectives, such as a product launch. Multi-stage projects are used for complex workflows where time and resource management are important. A multi-stage project consists of a hierarchy representing a sequence of work and related dependencies. Stages can include milestones and each stage is defined in a similar way to a basic project, using any of the following:

In the following example, between the Review and Approval stage and the Localization Stage, a diamond shape identifies a milestone (Content Complete).

Multi-stage project example

Project overview

The Overview tab displays the content used in the project. By clicking a tile, you can open the corresponding details page, which includes the following sections:




Filename, title, description, and locale.

Localized from

Original file that was localized.

Localized to

List of files to which the asset, content, or fragment was localized to.

Version history

List of versions. You can set a particular version as the master, which means it is the version used by default. You can also view the asset or content details for a particular version, or add comments and annotations to a particular version.

Local reviews

Displays local reviews.

Parallel reviews

Displays parallel reviews.

Used as content

Displays the projects, stages, and jobs that use the asset, content, or fragment as content, as well as the status of each.


Displays the projects and stages that use the asset, content, or fragment as an attachment as well as the status of each.

Used in tasks

Displays the tasks that use the asset, content, or fragment as well as the status and users assigned.

Time overview

On the Timeline tab, you can see a list of all the stages in the project, with a progress bar showing the overall project progress. This lets you visualize the different stages and milestones, plus their dependencies, status, start and end dates, and duration. From here, you can add a new stage or milestone, edit the details of each stage, and modify dependencies. If delaying a stage causes the overall project to be delayed, that project is considered to be on a critical path. The critical path is a sequence of stages that must not be delayed if the project is to be delivered on time, and it represents the minimum total duration of the project. In the following example, critical paths are shown in red.

timeline showing critical path

Standard operations are available on project pages and you can use the Content Hub Search to find specific information.

Do you have some feedback for us?

If you have suggestions for improving this article,