A four-state diverging load chart — every person measured out from their own capacity line, over-allocation running one way and idle headroom the other on one shared scale, with a tolerance band, an aggregate meter that the per-person picture argues against, and a greedy plan naming who to move work from and to.
Preview in your theme
Loading preview…
This component is part of Pro
The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.
status: ready · 8 people. The squad is booked to 96% of capacity and still has 23h that must move: Priya sits at 144% of her own week while Ren sits at 38% of his, so the aggregate is balanced and the people are not. 31h of headroom absorbs all 23h; the greedy plan needs five moves and prints the three largest. Select a name to pin their numbers and highlight the moves they are in.
Platform squad · sprint 34
Week of 24 Aug · assigned hours against remaining capacity
Workload balance: Platform squad · sprint 34. 8 people: 3 over capacity, 2 balanced, 3 with room to spare. The team as a whole is booked to 96% of capacity. 23h sits above somebody's capacity. 31h of headroom across 3 people can absorb all of it. Priya Raman carries the most surplus, 14h over. Jonas Weber has the most room, 11h. Median utilisation 98%, spread 38% to 144%. Suggested moves: 11h from Priya Raman to Jonas Weber; 6h from Marco Adeyemi to Leila Haddad; 3h from Priya Raman to Leila Haddad; and 2 more.
23hto move off 3 people31h of headroom across 3 people can absorb all of it.
98%median utilisation38% to 144% across the roster
Team total · booked to 96% of capacity86% booked · 14% headroom · 10% over
Platform squad · sprint 34 — every member with the work assigned to them, their capacity for this window and the difference. Bars run right when someone is over their own capacity and left when they have room to spare, both arms on one shared scale reaching 15h of headroom and 15h over.
Member
←headroomover capacity→
Against capacity
Backend · 11 items
14h over46h of 32h · 144%
Frontend · 9 items
6h over38h of 32h · 119%
Design · 6 items
3h over33h of 30h · 110%
Backend · 7 items
on capacity30h of 30h · 100%
QA · 12 items
on capacity29h of 30h · 97%
Data · 4 items
10h spare14h of 24h · 58%
Mobile (part-time) · 2 items
10h spare6h of 16h · 38%
Frontend · 5 items
11h spare21h of 32h · 66%
15h10h5h0h5h10h15h
Select a name to pin their numbers and their suggested moves.
Suggested moves · 5 moves clear 23h
Priya Raman→toJonas Weber11h
Marco Adeyemi→toLeila Haddad6h
Priya Raman→toLeila Haddad3h
and 2 smaller moves
Each bar is the distance from that person's own capacity, and both arms share one scale — a headroom bar and an over-allocation bar of the same length are the same number of h. Anything within 5% of a person's capacity counts as balanced and is marked on the line instead of measured out from it. Suggested moves are greedy, deepest surplus into widest gap, and know about capacity only — skills, on-call and time zones are not in this data.
status: empty · a valid payload with nobody on the board — told apart from “loading” and from “the fetch failed”.
Platform squad · sprint 34
Week of 24 Aug · assigned hours against remaining capacity
Nobody is on this board yet
Give each person the work assigned to them and the capacity they have for this window, and this shows who to move work off and who has room to take it.
status: loading · the headline, the team meter and a diverging wedge of skeleton rows, aria-hidden with an sr-only role=status beside them. No timers are involved, and the pulse stops under prefers-reduced-motion.
Platform squad · sprint 34
Week of 24 Aug · assigned hours against remaining capacity
Loading workload balance
status: error · the source did not answer. “Try again” appears only when onRetry is passed, and pressing it switches this card to ready.
Platform squad · sprint 34
Week of 24 Aug · assigned hours against remaining capacity
Couldn’t load this board
The data source didn’t respond.
Nadia is on parental leave: capacity 0, but 12h never left her queue. Nothing can be divided by her capacity, so the row reports “no capacity” instead of ∞%, and the 12h still counts as work that has to move. The team total is booked to exactly 100% of capacity — the sharpest version of the argument this card makes.
Payments squad · sprint 34
Week of 24 Aug · one week into parental leave
Workload balance: Payments squad · sprint 34. 6 people: 2 over capacity, 2 balanced, 2 with room to spare. The team as a whole is booked to 100% of capacity. 14h sits above somebody's capacity. 14h of headroom across 2 people can absorb all of it. Nadia Okoro carries the most surplus, 12h over. Hana Yildiz has the most room, 10h. Median utilisation 100%, spread 64% to 106%. 1 person has no capacity in this window, so no percentage of capacity can be computed for them. Suggested moves: 10h from Nadia Okoro to Hana Yildiz; 2h from Nadia Okoro to Mei Chen; 2h from Ivan Petrov to Mei Chen.
14hto move off 2 people14h of headroom across 2 people can absorb all of it.
100%median utilisation64% to 106% across the roster
Team total · booked to 100% of capacity90% booked · 10% headroom · 10% over
Payments squad · sprint 34 — every member with the work assigned to them, their capacity for this window and the difference. Bars run right when someone is over their own capacity and left when they have room to spare, both arms on one shared scale reaching 10h of headroom and 15h over.
Member
←headroomover capacity→
Against capacity
Platform (on leave) · 4 items
12h over12h of 0h · no capacity
Backend · 8 items
2h over34h of 32h · 106%
Frontend · 9 items
on capacity30h of 30h · 100%
QA · 7 items
on capacity24h of 24h · 100%
Backend · 6 items
4h spare28h of 32h · 88%
Design · 5 items
10h spare18h of 28h · 64%
10h5h0h5h10h15h
Select a name to pin their numbers and their suggested moves.
Suggested moves · 3 moves clear 14h
Nadia Okoro→toHana Yildiz10h
Nadia Okoro→toMei Chen2h
Ivan Petrov→toMei Chen2h
Each bar is the distance from that person's own capacity, and both arms share one scale — a headroom bar and an over-allocation bar of the same length are the same number of h. Anything within 5% of a person's capacity counts as balanced and is marked on the line instead of measured out from it. Suggested moves are greedy, deepest surplus into widest gap, and know about capacity only — skills, on-call and time zones are not in this data.
A board that really is balanced: five people, every one inside the ±5% band, so no bar is drawn at all and each row is marked on the capacity line instead. Two of them are an hour off zero — letting that wobble set the scale would have shrunk the axis to ±1h and painted half-track bars under rows that read “on capacity”.
Growth squad · sprint 34
Week of 24 Aug · after Monday's planning session
Workload balance: Growth squad · sprint 34. 5 people: 0 over capacity, 5 balanced, 0 with room to spare. The team as a whole is booked to 100% of capacity. Everyone sits within 5% of their own capacity for this window. Median utilisation 100%, spread 97% to 103%.
0hto move — every person is inside their own bandEveryone sits within 5% of their own capacity for this window.
100%median utilisation97% to 103% across the roster
Team total · booked to 100% of capacity99% booked · 1% headroom · 1% over
Growth squad · sprint 34 — every member with the work assigned to them, their capacity for this window and the difference. Nobody falls outside their own tolerance band, so no bar is drawn: every row is marked on its capacity line.
Member
Against capacity
Design · 9 items
on capacity31h of 30h · 103%
Backend · 8 items
on capacity30h of 30h · 100%
Data · 6 items
on capacity30h of 30h · 100%
QA · 10 items
on capacity30h of 30h · 100%
Frontend · 7 items
on capacity29h of 30h · 97%
Select a name to pin their numbers and their suggested moves.
Each bar is the distance from that person's own capacity, and both arms share one scale — a headroom bar and an over-allocation bar of the same length are the same number of h. Anything within 5% of a person's capacity counts as balanced and is marked on the line instead of measured out from it. Nobody falls outside that band in this window.
Not an imbalance at all: the team is booked to 121% of capacity, so 39h sits above somebody's line and exactly one person has any room. The plan can place 2h of it, and the card then says outright that the remaining 37h has nowhere to go rather than drawing moves that pretend to fix it.
Release train · week 35
Week of 24 Aug · release week, nothing deferred
Workload balance: Release train · week 35. 6 people: 5 over capacity, 0 balanced, 1 with room to spare. The team as a whole is booked to 121% of capacity. 39h sits above somebody's capacity. 37h of that has nowhere to go: this team is over capacity in total, not just unevenly loaded. Lena Fischer carries the most surplus, 12h over. Theo Lambert has the most room, 2h. Median utilisation 123%, spread 93% to 140%. Suggested moves: 2h from Lena Fischer to Theo Lambert.
39hto move off 5 people37h of that has nowhere to go: this team is over capacity in total, not just unevenly loaded.
123%median utilisation93% to 140% across the roster
Team total · booked to 121% of capacity99% booked · 1% headroom · 22% over
Release train · week 35 — every member with the work assigned to them, their capacity for this window and the difference. Bars run right when someone is over their own capacity and left when they have room to spare, both arms on one shared scale reaching 2.5h of headroom and 12.5h over.
Member
←headroomover capacity→
Against capacity
Backend · 10 items
12h over42h of 30h · 140%
Backend · 9 items
10h over40h of 30h · 133%
Frontend · 8 items
8h over38h of 30h · 127%
Platform · 11 items
6h over36h of 30h · 120%
Design · 7 items
3h over33h of 30h · 110%
QA · 6 items
2h spare28h of 30h · 93%
2.5h0h2.5h5h7.5h10h12.5h
Select a name to pin their numbers and their suggested moves.
Suggested moves · 1 move clears 2h
Lena Fischer→toTheo Lambert2h
Each bar is the distance from that person's own capacity, and both arms share one scale — a headroom bar and an over-allocation bar of the same length are the same number of h. Anything within 5% of a person's capacity counts as balanced and is marked on the line instead of measured out from it. Suggested moves are greedy, deepest surplus into widest gap, and know about capacity only — skills, on-call and time zones are not in this data.
Fourteen people in story points rather than hours, from a fixed seed. Past twelve rows the bars thin themselves, the axis drops tick labels rather than letting them collide, and the plan prints its three largest moves and counts the four smaller ones. A three-letter unit takes a space before it, where a one-letter unit hugs the number.
Platform department
Sprint 34 · committed points against team velocity
Workload balance: Platform department. 14 people: 5 over capacity, 4 balanced, 5 with room to spare. The team as a whole is booked to 97% of capacity. 28 pts sits above somebody's capacity. 36 pts of headroom across 5 people can absorb all of it. Christie Mann carries the most surplus, 9 pts over. Otilia Collins has the most room, 13 pts. Median utilisation 98%, spread 57% to 129%. Suggested moves: 9 pts from Christie Mann to Otilia Collins; 5 pts from Aric Murray to Brionna Monahan; 4 pts from Aric Murray to Otilia Collins; and 4 more.
28 ptsto move off 5 people36 pts of headroom across 5 people can absorb all of it.
98%median utilisation57% to 129% across the roster
Team total · booked to 97% of capacity90% booked · 10% headroom · 7% over
Platform department — every member with the work assigned to them, their capacity for this window and the difference. Bars run right when someone is over their own capacity and left when they have room to spare, both arms on one shared scale reaching 15 pts of headroom and 10 pts over.
Member
←headroomover capacity→
Against capacity
Paradigm · 10 items
9 pts over40 pts of 31 pts · 129%
Identity · 12 items
9 pts over49 pts of 40 pts · 123%
Implementation · 7 items
5 pts over29 pts of 24 pts · 121%
Assurance · 5 items
3 pts over19 pts of 16 pts · 119%
Web · 5 items
2 pts over21 pts of 19 pts · 111%
Interactions · 10 items
on capacity38 pts of 38 pts · 100%
Configuration · 7 items
on capacity28 pts of 28 pts · 100%
Interactions · 6 items
on capacity22 pts of 23 pts · 96%
Creative · 7 items
on capacity29 pts of 30 pts · 97%
Assurance · 4 items
2 pts spare14 pts of 16 pts · 88%
Usability · 2 items
6 pts spare8 pts of 14 pts · 57%
Branding · 7 items
6 pts spare29 pts of 35 pts · 83%
Accountability · 8 items
9 pts spare31 pts of 40 pts · 78%
Identity · 6 items
13 pts spare23 pts of 36 pts · 64%
15 pts10 pts5 pts0 pts5 pts10 pts
Select a name to pin their numbers and their suggested moves.
Suggested moves · 7 moves clear 28 pts
Christie Mann→toOtilia Collins9 pts
Aric Murray→toBrionna Monahan5 pts
Aric Murray→toOtilia Collins4 pts
and 4 smaller moves
Each bar is the distance from that person's own capacity, and both arms share one scale — a headroom bar and an over-allocation bar of the same length are the same number of pts. Anything within 5% of a person's capacity counts as balanced and is marked on the line instead of measured out from it. Suggested moves are greedy, deepest surplus into widest gap, and know about capacity only — skills, on-call and time zones are not in this data.
Contract refusal: two rows carry the id “priya”. They would collide as React keys and shadow each other in the rebalance plan, so the component names the offending id instead of quietly dropping a person from the roster.
Platform squad · duplicated feed
Week of 24 Aug · assigned hours against remaining capacity
Zyeon UI