The Team Workload report shows how the sprint commitment is distributed across individual team members — who has how many points, how many stories, and whether their commitment is within their available capacity. It is the key tool for catching imbalanced sprints before they start.
The report is most useful during sprint planning and in the first standup of a new sprint. By the time the sprint is halfway through, redistribution is harder — catching problems early is the goal.
Each row in the report represents one team member. The columns show:
Clicking a team member's row expands it to show all stories assigned to them in the sprint, with status, points, and due dates.
| Signal | Risk | What to do |
|---|---|---|
| One person carries more than 40% of sprint points | Concentration risk. If they are blocked or go on leave, a large part of the sprint stalls. | Redistribute stories before the sprint starts. Pair the overloaded person with a team member who has capacity. |
| A team member shows 0 committed points | Under-utilised or stories may not be assigned to them yet. | Check whether they have stories assigned with points. If none, confirm they're active this sprint and assign backlog items. |
| Committed points well above available hours equivalent | Over-committed. The person has more work than time. | Remove or reassign some stories before the sprint starts. Use the Capacity panel to calculate their realistic ceiling. |
| Committed points well below available hours | Under-committed. Buffer exists — may be intentional or may mean stories are missing estimates. | Check whether their stories have points assigned. If yes, consider pulling in a backlog item to fill the gap. |
| Stories assigned but showing as "unestimated" | Missing point values make workload assessment inaccurate. | Add story points to unestimated stories in the backlog before or during sprint planning. |
The workload report updates in real time as stories move through the workflow. Mid-sprint, use the status breakdown column to spot individuals whose stories have not moved out of "To Do" or who have all their stories in "In Review" (potentially blocked waiting on others).
If a team member completes their stories early, use the report to identify who is overloaded and reassign stories rather than asking them to pull from the backlog without coordination.
Click Export CSV on the Team Workload report to download the current view. The export includes all columns visible in the report plus story-level detail (one row per story). This is useful for sharing with stakeholders who don't have project access or for tracking workload trends across sprints in a spreadsheet.
The Team Workload report shows some team members but not others
The report only shows members who have at least one story assigned in the selected sprint. Team members with no assignments don't appear. This is intentional — use the Capacity panel (in the sprint detail view) to see all members including those without assignments.
The "available hours" column doesn't match what I expect
Available hours = (allocated hours/week × sprint duration in days ÷ 5) − (leave days × hours/day). Verify that allocated hours are set for each member in the Members tab, and that any leave days are entered in the sprint's Capacity panel.
I want to compare workload across multiple sprints
Use the sprint selector at the top of the report to switch between sprints. There is no side-by-side multi-sprint view — you'll need to note numbers from each sprint individually or export to CSV and compare outside Silverile.
A story is assigned to a member but not showing in their workload
Unestimated stories (no story points assigned) show in the story list under the member's name but contribute 0 to the point total. Add story points to the story and the workload total will update.
The report shows a team member's stories but they left the project
Stories assigned to a removed project member remain assigned to them. Reassign these stories to an active team member using the Story List filter (filter by assignee → former member).