Reporting

Content Velocity Reports

This article is for Account Owners and Project Managers.

The Content Velocity by Workflow Report and the Content Velocity by Locale Report provide insight into the average amount of time that a word or a string spends in a particular workflow step.

The difference between the two reports is how the data is visualized.

These reports help you monitor translation speed, as well as determine possible unnecessary workflow step(s). For example, if content sits in the validation step for six days without changes made, perhaps that step can be removed from the workflow.

Access the Reports

  1. To access the reports, go to Reports.
  2. From the drop down menu, select Content Velocity by Workflow or Content Velocity by Locale.
  3. Expand Filters and select them:
    • Authorization Date: Date in which content is authorized to move to the first step in the workflow. (We filter on this because occasionally, content can pass through workflows more than once.)
    • Project: The name of the project for which you'd like data.
    • Workflow: The name of the workflow step for which you'd like data.
    • Target Locale: The translated language for which you'd like data.
    • Include Weekends (yes/no)?: Whether or not to include Saturday and/or Sunday in the data.
  4. Click Run.

Content Velocity by Workflow

In the Content Velocity by Workflow Report, the data is grouped by workflow (as seen on the y-axis of the charts). Each color represents a different workflow step. Hover over the colored bar to see more info.

Content Velocity by Workflow data is shown in 4 charts:

  • Hours Spent in Workflow Step (per string)
  • String Counts by Workflow Step
  • Hours Spent in Workflow Step (per word)
  • Word Counts by Workflow Step

Content Velocity by Locale

In the Content Velocity by Locale, the data is grouped by locale (as seen on the y-axis of the charts). Each color represents a different workflow step. Hover over the colored bar to see more info.

Content Velocity by Locale data is shown in 4 charts:

  • Workflow Average Time to Process (per string)
  • String Counts by Workflow Step
  • Workflow Average Time to Process (per word)
  • Word Counts

Content Velocity Calculation

Data is generated based on the following:

  • The time a string spends in a workflow step is based on a comparison between when the string leaves the step versus when it entered the step.
  • The per word velocity of a string is calculated by dividing the time a string spends in a workflow step by word count of the string. Time spent in a step is cumulative for every instance when a string is moved back into the step (via rejection, for example). The velocity at string level is then aggregated across strings for reporting, as needed, weighted by the number of words in each string.

Download Data

Hover over the top right of each chart. Click the more icon and select Download Data.

Was this article helpful?