Review Load Fairness
Pull Request Lifecycle
index
Scores how evenly review actions are distributed across team members.
💡 Like checking if only a few people always do the washing up, high fairness means everyone contributes, not just the most available or senior people.
What It Measures
Scores how evenly review actions are distributed across team members.
Why It Matters
Ensuring review duties are shared fairly
Identifying if review work is concentrated on a few people
How It's Calculated
Calculates 1 minus the Gini coefficient of actions per reviewer, clamped between 0 and 1, where 1 means perfectly fair distribution.
1 – GINI(actions_per_reviewer) (clamped between 0 and 1)Concrete Example
If your review load fairness score is 0.75, review work is fairly distributed, compare to a score of 0.3 where one or two people do most reviews.
What Does a Healthy Score Look Like?
Higher is better, aim for a score close to 1.0 (perfectly fair distribution).
Healthy
0.7 and above
Watch Out
0.4–0.7
Needs Attention
Under 0.4, review work is heavily concentrated
What Moves This Metric?
Goes up when…
Deliberate review rotation policies
Auto-assigning reviewers randomly across the team
Senior developers actively stepping back to let others review
Goes down when…
Seniority bias causing the same people to always be requested
Reviewers self-selecting only familiar code
No rotation system in place
Start Tracking Review Load Fairness
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com