Duración en proyectos con plantilla de planificación

If the project includes a project schedule, the task duration is calculated depending on several factors. Familiarize yourselves with all the scenarios before setting up your project schedule.

Scenario 1: All Human workflow tasks have a duration specified in the schedule template

Scenario 1.1. - The total duration of workflow tasks = project duration

The due date of each Human workflow task is calculated based on the task duration specified in the schedule template.

Scenario 1.2. - The total duration of workflow tasks < project duration

The due date of each Human workflow task is calculated based on the task duration specified in the schedule template. Because the project duration exceeds the duration of workflow tasks, the delta duration (the remaining time) is not redistributed among tasks.

Scenario 1.3. - The total duration of workflow tasks > project duration

The due date of each Human workflow task is calculated based on the task duration specified in the schedule template. Because the duration of workflow tasks exceeds the project duration, there will be cases where some or all Human workflow tasks will already be overdue by the time they reach the assignees.

Scenario 2: Only some Human workflow tasks have a duration specified in the schedule template

The due date is calculated for all the Human tasks that have durations specified in the schedule template. The remaining time (i.e. project duration - total duration of tasks which have a duration in the schedule template) is divided by the number of Human tasks which do not have a duration specified in the schedule template:
  • If the remaining time is a positive value (the project duration exceeds the total duration of the tasks that have a duration specified in the schedule template), then the tasks which did not have a duration specified in the schedule template get an equal duration.Remaining time is a positive value
  • If the remaining time is a negative value or 0 (the project duration does not exceed the total duration of the tasks that have a duration specified in the schedule template), then the tasks which did not have a duration specified in the schedule template get a duration of 1 minute.Remaining time is zero or a negative value

Scenario 3: A Human workflow task has different durations for its target languages

Human workflow tasks can have several target languages. Sometimes, the durations associated with each target language may differ. In this case, the due date of the next task in the workflow is calculated to start only after the end date of the target language with the maximum duration.

Let's consider the following example:
  1. The project has 2 target languages: DE-DE and FR-FR.
  2. The project includes a schedule template where the following durations are specified for the Translation task: DE-DE Translation duration = 2 days; FR-FR Translation duration = 3 days.
  3. The Translation task is followed by a Linguistic Review task, where the duration for both languages is 3 days.
Even though the due date of the DE-DE Translation task is set earlier than the due date of the FR-FR Translation task, the start date of both the DE-DE Linguistic Review task and the FR-FR Linguistic Review task will be calculated only after the duration of the FR-FR Translation task has elapsed.Task with different language durations

Scenario 4: Task due dates are recalculated if project due date is changed during Customer Quote Approval

Here is an example.
  1. At project creation, the project due date is set for the 15th of August.
  2. During the Customer Quote Review task, the due date (Delivery By date) is set on 18th of August.
  3. During the Customer Quote Approval task, the customer agrees on the 18th of August and approves the project.

The project due date is changed from the 15th of August to the 18th of August. The total project duration increases by 3 days. This change in project duration will also be reflected in the duration of the tasks, which are calculated according to the schedule.

Scenario 5: Limitations for file batches

If a project includes a schedule template, the schedule template runs once at the start of the project. If you add file batches after the project start, the due date of the project remains the same (it is not recalculated). However, you can choose to have the due date of all tasks generated for the new batch recalculated or not.
  • If you choose not to recalculate the due dates, the due date of all Human tasks involved in the localization of subsequent batches will be based on the duration specified in the schedule template. It is very likely that the due date of the tasks generated for subsequent batches to be set in the past. In other words, the tasks in the new batches will have the same due dates as the tasks in the first batch.
  • If you choose to recalculate the due dates, the following will be recalculated:
    • The due date of all Human tasks involved in the localization of subsequent batches
    • The due dates of all Human tasks from the initial batch which have not been generated yet
    The system checks how many days are left till the project due date. The remaining time is divided by the durations specified in the schedule template.

Scenario 6: Limitations for custom workflow templates

Custom workflows can have non-default branches, namely task sequences that may happen for a specific transition, and not for others. The due date for the tasks positioned on non-default branches is calculated only after the due date is calculated for the main branch.

Here is an example.

  • The project lasts between the 10th of May and the 19th of May.
  • The tasks that have a due date which is marked red (8 tasks) belong to the main branch.
  • The tasks that have a due date which is marked black (2 tasks) belong to the non-default branch. The due date for the tasks of the non-default branch is calculated only after the last due date of the main branch (Task no. 10) is calculated.
task due dates for custom workflow templates

Scenario 7: Limitations for tasks assigned to vendors

How is the task due date calculated if a task has 2 target languages and only one of them is assigned to a vendor?

The due date for target languages that are not assigned to vendors are calculated after the Project Planning task is completed.

Let us consider the following:
  • The DE-DE Translation task is assigned to a vendor, while the FR-FR Translation task is assigned to a user.
  • The schedule template specifies that the Translation task has a duration of 1 day.
  • For DE-DE, the Vendor Quote Review (VQR) task has a duration of 1h, and the Vendor Quote Approval (VQA) task has a duration of 1h.

The DE-DE Translation task is generated after the Vendor Quote Approval task and lasts 1 day.

The FR-FR Translation task is generated after the Project Planning task, and lasts 1 day.

Schedule calculation for vendor and non-vendor assigned tasks