Unique PRs Reviewed / Week

Last updated: October 27, 2026

Unique PRs reviewed / week shows how many different pull requests (PRs) a typical active contributor reviews in a week. Compare it with PR reviews / week: a big gap means reviewers make many passes on the same PRs.

Why it matters

  • Review breadth: shows how widely review work is spread, separate from how many review rounds happen.

  • Workload balance: highlights reviewers who cover many PRs and teams where few people review.

  • Back-and-forth: many reviews on few unique PRs points to long review loops.

How it works

Unique PRs reviewed / week = distinct PRs reviewed ÷ active contributor-days × 7

  1. Span starts from the same reviews as PR reviews / week: submitted reviews by people marked Contributor, without self-reviews, ignored repositories and branches, or ignored Git usernames. Any review state counts, including "commented".

  2. Span counts the distinct PRs among the reviews submitted in the period.

  3. Denominator: active contributor-days: days a person marked Contributor wasn't out of office (OOO) and had code activity (a commit, merged PR, PR review, or PR comment) that day or in the 30 days before it. Weekends count.

  4. Span divides and multiplies by 7. The value shows to one decimal place.

Where to find it: Insights > Productivity > Quality > Code review, team and person Code review tabs, and custom dashboards, with percentile ranks.

Setup

  1. Connect your version control system.

  2. Mark people who don't write or review code as Non-contributor in Settings > People management.

  3. Connect an OOO source (calendar or HRIS) so time off leaves the denominator.

Things to know

  • Worked example. In one week, a reviewer reviews PR 101 twice and PR 102 once, over 5 active days. Unique PRs = 2, so 2 ÷ 5 × 7 = 2.8. PR reviews / week for the same week shows 3 ÷ 5 × 7 = 4.2.

  • Distinct within the group you view. At team level, a PR two teammates reviewed counts once. In a per-person breakdown it counts once for each person, so person values add up to more than the team value.

  • Distinct within the period. A PR reviewed in two different weeks counts in each week of a weekly chart, but once in a monthly view.

  • Reviewers keep people active. Someone who only reviews stays in the denominator for 30 days after that activity.

  • OOO days leave the denominator.

  • Bots and dev agents: unmapped bot accounts drop out, and report pages hide dev agents by default.

Related articles

PRs Reviewed / Week Report

Comments Authored / Week

How to read Span's "/ week" metrics

Need help?

Contact your Span account team or reach out to support@span.app.