Reviewer load
Spot when review work is too concentrated on one person.
What this shows
Reviewer load looks at how review work is spread across your team, two ways:
- Concentrated — one reviewer is handling more than their fair share of a Report's reviews (over 40% of distinct PRs reviewed in the last 30 days). This is the fairness picture — it tells you whether review responsibility is spread out or piling onto one or two people over time.
- Overloaded — one reviewer currently has too many pending review requests assigned at once (more than 5). This is the today's-delay picture — it tells you who's likely to become a bottleneck right now.
Both counts are based on distinct pull requests, not raw review activity — leaving three separate reviews on the same PR only counts once.
Review counts per reviewer over the trailing window.
When to act on it
A Concentrated reviewer is a staffing signal: consider rebalancing who gets requested for review, or adding another reviewer to the rotation. An Overloaded reviewer is a today problem: consider re-assigning some of their pending requests so the queue doesn't stall. The two rarely mean exactly the same thing — a reviewer can be Concentrated over a month without being Overloaded this week, or vice versa.
This view is scoped to a Report — see Team Reports if you haven't created one yet.