Reviews Count is the total number of PR reviews a single team member submitted during the selected period. It measures peer engagement in code review and helps identify how review labor distributes across the team.
What it measures
The count of pull-request review events submitted by this member. The period selects PRs by when they were merged, not by when the review was submitted — a review written inside the period on a PR that merges later does not count until the period that contains the merge.
How Leanmote calculates it
reviews_count = count(reviews where reviewer = member, on prs merged in period)
Includes approvals, change-requests, and substantive comment-only reviews.
Empty approvals or rubber-stamps can be excluded based on configuration.
Bot accounts are excluded from the count.
How to interpret it
Healthy distribution: most active engineers contribute reviews within ±2× of the team median.
Concentrated reviews (one or two members carrying most of the load) is a fragility signal — investigate before it becomes burnout.
Very low Reviews Count with high PRs Created may indicate someone authoring without reviewing peers' work.
What to do about it
Distribute reviews via auto-assignment or rotating reviewer rotas.
Pair under-reviewing members with mentors so review skills spread.
Surface review activity in 1:1s — peer review often goes invisible.
Related metrics
Review participation
Review latency
Activity distribution
PRs Created (per member)