How to read Span's "/ week" metrics
Last updated: October 29, 2026
Many Span metrics are rates per week, such as Deployments / week, PRs merged / week, Commits / week, and Weighted PRs / week. A "/ week" metric is an average rate, not a total, so it stays comparable whether you look at 2 weeks or 6 months, and, for per-person metrics, whether a team has 3 engineers or 300.
Why it matters
Window length: the value is normalized by the days in your date range, so a 30-day view and a 90-day view compare directly.
Team size and time off: per-person rates divide by the days people actually worked, so they reflect output per contributor rather than headcount, and vacations don't drag them down.
How it works
There are four families of "/ week" metrics.
Family | Formula | Examples |
|---|---|---|
Calendar-week rate (team cadence, not per person) | events ÷ calendar days in range × 7 | Deployments / week, Incidents / week |
Per-active-contributor rate | count on active days ÷ active contributor-days × 7 | PRs merged / week, Weighted PRs / week, Commits / week, Commit days / week, PR reviews / week, Unique PRs reviewed / week, Comments authored / week |
Per-person issue rate | count ÷ non-OOO person-days × 7 | Issues completed / week (and by type), Estimate completed / week |
Per-person weekly time | hours on weekdays ÷ active person-weekdays × 5 | Focus time, Fragmented time, meeting hours |
Active contributor-days. A person counts for a day when all four hold:
They're marked Contributor under Code Contribution in Settings > People management.
The day falls between their start date and termination date.
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.
They weren't out of office (OOO) that day.
When a day is OOO. Span marks each weekday as OOO or not; there are no partial days. With the 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 it a full active day. With the HRIS source, every weekday inside an absence is OOO. Weekends are never OOO.
Weekends count. Every calendar day is in the denominator, including Saturdays and Sundays, and weekend work counts in the numerator. That's why code and issue rates multiply by 7. Calendar time metrics use weekdays only and multiply by 5.
Team values pool the totals. A team's rate is the team's total count ÷ the team's total days × 7. It isn't an average of each person's rate, so people who worked more days weigh more.
Weighted PRs / week works the same way, but each merged PR counts for a weight between 0 and 2 instead of 1. The weight is an AI complexity score (0.1–1) plus a size score from lines changed on a log scale (about 0.5 at 32 lines, capped at 1 from 1,000 lines). Lines in files matching your ignore patterns don't count. A weight of 1 is roughly one PR of about 32 lines with medium complexity.
Setup
Mark people who don't write code, such as most managers, as Non-contributor in Settings > People management.
Connect an OOO source (calendar or HRIS) so time off leaves the denominator.
To see totals instead of rates, use the matching "Total …" metric, such as Total PRs Merged.
Things to know
Worked example. A team of four over two weeks has 56 person-days. One person was OOO for 5 weekdays, leaving 51 active days. The team merged 34 PRs, 2 on the OOO person's OOO days. PRs merged / week = 32 ÷ 51 × 7 = 4.4. Dividing the team total by headcount and weeks instead (34 ÷ 4 ÷ 2) gives 4.25. If that person had instead blocked only 1pm to 5pm (4 hours) on those 5 days, none of them would be OOO, and the rate would be 34 ÷ 56 × 7 = 4.25.
What leaves the numerator. PRs merged, commits, and PR comments on a person's calendar OOO day leave the count. PR reviews and issues completed on an OOO day stay in.
It's an average, not a running total. Multiplying a weekly rate by the number of weeks won't reproduce the total, because the denominator counts active days, not whole weeks.
Reviewers keep people active. Someone who only reviews or comments stays in the denominator for 30 days, which lowers PR and commit rates.
New hires enter on their first code activity, not their start date.
Issue rates use a wider denominator. Issues completed / week and Estimate completed / week divide by every non-OOO day for every person in scope, contributor or not, active in code or not.
Company holidays count as active days unless they show as OOO.
The weekend setting doesn't apply. Settings > Metrics > Cycle & Response Times: Weekends changes durations such as PR cycle time, not "/ week" rates.
Dividing by 5 working days gives a higher number than Span when people work weekends. For a team that never works weekends, Span's × 7 over 7 days equals × 5 over 5 days.
Weighted PRs / week won't match PRs merged / week. One counts each PR as 1; the other weights each PR. A big refactor barely moves Weighted PRs because the size score is capped.
Related articles
How to setup weekend exclusion for metrics
Need help?
Contact your Span account team or reach out to support@span.app.