New planning features in Tempo: examples

This article covers the following:

  • Planning for individual users on the Team Timeline
  • Planning on non-working days
  • Workload and team membership
  • Exporting plans

Planning for individual users on the Team Timeline

You now plan work for individual team members using fixed hours, instead of as a percentage of their workload.

When creating a user plan on the Team Timeline for a given period, you can now specify the number of hours per day, or the total number of hours to assign to the issue, project or component.

If you select total time, the total is divided by the number of days in the planned period. For example, a plan with a total of 9 hours over a period of 3 days will record 3 hours per day.

If you select hour per day, then the number of hours is multiplied by the number of days.

Note: This option is only available when you create a plan; once created, all planned work is is stored as hours per day. If you add days to the plan, the total time increases accordingly, and you can only edit planned work on a per day basis.  

Planning on non-working days

You can now opt include non-working days directly from the Create Plan dialog.

If you specify a period of time that includes any non-working days, an “Include non-working days” option appears in the Create Plan dialog. If selected, it adds additional working days to your plan.

If you extend your plan in the timeline and then opt to include non-working days in Plan Details, the number of hours recorded as Planned time per day is added to your plan. It is simply adding additional working days to your plan.


Similarly, if you reduce the number of working days in your planned period, the number of planned hours is reduced.

Workload and team membership

When planning work for a team member, their workload scheme and the percentage of their time allocated to a team are factored in.

For example:  25% of Eric’s time is allocated to Team A, and his daily workload is 8 hours per day. When you create an individual plan for him, Tempo Planner will suggest 2 hours per day for Eric (25% of 8h). This initial suggestion, however, does not account for any existing plans, thus Eric may end up with a workload that exceeds his daily hours.

The initial suggestion also considers a workload scheme with different working hours per day. In our example below, Summer is allocated to the team at 100%, but has a workload of 5h on Fridays. Creating an individual plan for her on a Friday will result in a default of 5 hours-per-day for that plan.


If the planned period includes days with different workloads, Tempo Planner will suggest a plan based the working hours for the first day of the selected period. E.g., a 2-day plan for Summer that starts on Thursday and ends on Friday will suggest a default planned time per day of 8 hours (as Summer has a workload of 8 hours on Thursdays), while a plan starting on Friday will suggest 5 hours of planned time per day (as Summer has a workload of 5 hours on Fridays).


In the above example, adding the individual plan for Summer reduces the available planned time for the team to 50,8 hours. This happens because Summer’s availability to the team has been reduced when creating the individual plan. Summer has a commitment to the team of 50% and a workload of 8 hours for the Thursday and 5 hours for the Friday, therefore the team plan has been reduced by 0,5x8h + 0,5x5h = 6,5 hours (57,3h - 6,5h = 50,8h).

Exporting plans

Exporting plans to a CSV file has been improved. You will notice that several new columns have been added to the CSV export.


To reflect both existing plans and plan new plans (after the update), the column ”Planned time (fraction of each working day)” refers to existing plans and the column “Planned time per day (hours)” refers to newly created plans. The total planned time for each single plan is displayed in the column “Planned time (hours)”.

Additionally, the export sheet includes more detailed information on when plans were created and when they have been updated. This helps to maintain an integration with 3rd party planning applications.

Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.