PRs Merged / Week

Last updated: October 27, 2026

PRs merged / week shows how many pull requests (PRs) a typical active contributor merges in a week. It's a per-person rate, not a team total, and it adjusts for time off so you can compare teams of different sizes and periods with different holidays.

Why it matters

  • Fair comparisons: dividing by the days people actually worked removes the effect of team size, vacations, and leave.

  • Early warning: a sustained drop often signals blockers, review bottlenecks, or capacity problems before delivery dates slip.

  • Onboarding: the Onboarding report shows PRs merged / week for each of a new hire's first three months.

How it works

PRs merged / week = PRs merged on active days ÷ active contributor-days × 7

  1. Numerator: merged PRs authored by people marked Contributor, after your ignore settings, minus PRs merged on the author's out-of-office (OOO) day. Reverted PRs don't count.

  2. Denominator: active contributor-days. A person counts for a day when they're marked Contributor, the day falls between their start and termination dates, they weren't OOO, and they had code activity (a commit, a merged PR, a PR review, or a PR comment) that day or in the 30 days before it.

  3. Span divides the totals and multiplies by 7. For a team, both sides are summed across all members first, so the team value isn't an average of each person's rate. People who worked more days weigh more.

  4. Each chart bucket (week or month) repeats the same calculation for its own PRs and days.

When a day is OOO: with a calendar source, a weekday is OOO when out-of-office events cover more than 4 hours between 8am and 6pm in the person's time zone. A block of 4 hours or less leaves a full active day. With an HRIS source, every weekday inside an absence is OOO. Weekends are never OOO.

Weekends: every calendar day counts in the denominator, weekends included, and weekend merges count in the numerator. That's why Span multiplies by 7. For a team that never works weekends, the result equals what you'd get by dividing by weekdays and multiplying by 5.

Where to find it: Insights > Productivity > Velocity > Delivery, first in the metric grid, with percentile ranks. It's also in team and person Metrics tabs, custom reports, and custom dashboards. Break it down by team, person, job level, or repository; the breakdown table shows values to one decimal place.

Setup

  1. Connect your version control system.

  2. In Settings > People management, set Code Contribution to Non-contributor for people who don't write code, such as most managers. Span recommends this; their PRs and days then leave the metric.

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

  4. Under Settings > Metrics, add repositories, branches, or Git usernames to ignore.

Things to know

  • Worked example. A team of four over two weeks has 4 × 14 = 56 person-days. One person was OOO for 5 weekdays, leaving 51 active days. The team merged 34 PRs, 2 of them on the OOO person's OOO days, so 32 count. PRs merged / week = 32 ÷ 51 × 7 = 4.4. If that person had instead blocked only 1pm to 5pm (4 hours) on those 5 days, no day would be OOO: 34 ÷ 56 × 7 = 4.25.

  • Reviewers count as active. Someone who only reviews or comments stays in the denominator for 30 days after that activity, which lowers the team's rate.

  • New hires enter on their first code activity, not their start date. A rate can dip the week after a big hire, before the new people merge anything.

  • Company holidays count as active days unless they show as OOO on people's calendars or in your HRIS.

  • Non-contributor applies to all history. Switching someone to Non-contributor removes their past PRs and days from every period.

  • Weekend exclusion doesn't apply. The Settings > Metrics weekend setting changes durations such as PR cycle time, not "/ week" rates.

  • Why your own math differs: team total ÷ team size ÷ weeks includes people on leave and Non-contributors, so it runs lower than Span. Dividing by 5 working days runs higher than Span when people work weekends.

  • HRIS OOO and the numerator. When your OOO source is your HRIS, OOO days leave the denominator, but PRs merged on those days can stay in the numerator, which nudges the rate up slightly.

Related articles

How to read Span's "/ week" metrics

Total PRs Merged

Weighted PRs/Week

OOO Person-Days

Need help?

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