Workload per person
Check how many hours each person has assigned against their capacity, adding up this project, other projects and agile boards.
On this page
The Workload view shows, day by day or week by week, how many hours each person on the project has assigned and how many they can work according to the calendar. It adds up what they have in this project, in other projects and on agile boards, so you can see if someone is overallocated before it shows up as delays.
Before you start
You only need to be able to see the project desk.
For a task to add hours, it must have an Assignee, Effort (hours) and dates, and no Actual finish. See Build the plan in the list.
Steps
Go to the project and choose Workload.
Choose the range:
With From and To, or
with a quick range: 2 weeks, 4 weeks or 3 months, starting on Monday of this week. When you open it, 4 weeks are shown.
Choose how to group: By day or By week. The 3 months quick range is shown by week.
Review the table and click a cell with hours to see where they come from.
The range can be up to 92 days (about 3 months). If you choose a longer one, the view shows "Could not load the workload: The range cannot exceed 92 days."; shorten the dates.
How to read the table
Person: each desk member with the Lead or Member role, and each person who has a project row assigned. If a person has overallocated days, a tag like 3 d over appears. People with the most overallocated days come first.
One column per day or per week: the hours assigned that day or week. In the day view, non-working days look lighter.
Hours: the total hours assigned in the range.
Capacity: the total hours the person can work in the range, according to the project calendar's schedule. Non-working days and holidays have zero capacity.
Cell statuses
Status | Color | When |
|---|---|---|
Free | No color | No hours assigned |
With slack | Green | Less than 85% of capacity |
Nearly full | Yellow (in the legend, 85% or more) | Between 85% and 100% |
Overallocated | Red | More hours than capacity, or any hours on a day with no capacity |
If there are people with overallocated days, a message like "2 people with overallocated days. This is only a warning: reassign or move tasks in the Gantt." appears above the table. Elion ITSM doesn't redistribute the work on its own: the decision is yours.
See the source details
When you click a cell with hours, the details appear below the table, for example "Ana Pérez · 2026-10-14: 10 h of 8 h", with the list of items that add up those hours and the desk of each one. Click a number to open its record. If there's no source information, it says "No source details.".
Where the hours come from
Source | How it's spread |
|---|---|
Tasks from this and other projects | The task effort is spread across its working days, from start to finish |
Items in an active sprint (Scrum) | The remaining (or estimated) hours are spread from today to the end of the sprint |
Agile items in progress or in QA that aren't in an active sprint (for example, on a Kanban board) | The remaining (or estimated) hours are spread from today at 8 hours per working day |
Only the desks you can see count. Finished tasks and finished agile items don't add hours.
What to do about overallocation
Move one of the tasks in the Use the Gantt to days when the person has slack.
Lengthen the task's duration to spread the same effort over more days.
Split the work: create another task with another assignee and lower the effort of the original.
The table updates on its own when tasks or assignments change.