Skip to main content

Team level utilization

Configure team-level utilization with custom formulas and scoped team assignments for precise tracking

K
Written by Katarina Dakic
Updated this week

Team level utilization has a formula first approach and that means that: Admins can create custom formulas and assign teams to the right formulas. This allows multiple teams to share a formula where appropriate, while ensuring different functions are measured by criteria that fit their work.

This Team level utilization empowers Admins only with formula creation and assignment, establishing a scalable foundation for accurate, flexible and trusted utilization insights.

Both organizational and team-level formulas are managed in a single place. Admins can quickly view formula type, assigned teams, authorship and edit history-making governance and oversight easier.

When formulas are updated, historical utilization data is automatically recalculated, this ensures reporting remains accurate, relevant and trusted across the organization even as teams evolve.

When you want to add a new formula, click on the upper right button Add New Formula and you will see a popup where you can choose which Type of formula you want:

  • Standard Hours

  • Scheduled Hours

  • Work Hours

  • Active Hours

Once the type is selected, the next step is Edit.

Actual is all the time that employees are actually going to spend, and these times are placed above the line. Productive time is always mandatory, all other times are optional.

The Standard Hours formula is the only type that allows precise definition of expected working hours. 'Expected' represents the total number of hours a team is required to work.

Configuring work expectations

Admins can define the expected total time—i.e., the total number of productive working hours required per day—applicable only within the Standard Hours formula. This can be a whole number of hours or include both hours and minutes. This number will be used as the denominator in the formula.

Setting the expected number of working hours per day is required.

Admin can also Define expected working days during the week. For example, employees will not have utilization expectations for weekends, if Saturday and Sunday are not selected. As a result, the utilization score will not be calculated for those days, and "N/A" will appear in the utilization column on Timesheets.

Specifying which days of the week are considered standard working days is required.

Admin can also set a minimum amount of work required for a day to be considered a working day. For example, if employees log less than 30 minutes of work in a day, utilization expectations will not apply. As a result, the utilization score will not be calculated, and "N/A" will appear in the utilization column on Timesheets.

N/A applies across all utilization scenarios. For example:

  • In the work time scenario, if an employee has 0 work time in the selected period, their utilization will show as N/A.

A threshold represents the minimum amount of work required for the day to count as a working day.

Next Step is Scope & Conformation where you can enter custom Formula Name and Team/Teams to the scope.

Once you click Save, you'll see an overview of the changes: the Current Setup and New Setup.

After adding a new formula, a pop-up will appear: Utilization data is being recalculated. Editing is temporarily disabled, you'll be notified once it's done.

During the recalculation process, users can only use the 'View' option to review the formulas. Once the process is complete, a notification will appear in the top-right corner, indicated by the bell icon.

  • Organizational formula cannot be deleted but Team Utilization formula can be deleted.

  • A single team can be assigned to only one utilization formula at a time — either at the organization level or the team level.

In the upper left corner, you'll find the Add Filter button, which allows you to filter by Author, Formula Type, or Teams.

  • Team-level formulas are not assigned by default, but a single team-level formula can be applied to multiple teams.

  • When an employee transfers between teams, historical utilization remains based on the original team.

  • When viewing aggregated data across multiple teams, employees, or longer time periods (where team transfers may have happened), utilization is always based on the following:

    • For employees - based on the team (and their active formula) they belonged to at each point in time.

    • For teams - based on the active team-level formula at the moment.

Did this answer your question?