PR Cycle Time Benchmark Tool
See where your pull request velocity sits against DORA Elite, High, Medium, and Low performers. Pinpoint whether your bottleneck is review lag, post-review delays, or PR size — and get a clear fix.
Your PR Metrics
Use last month's numbers for the most accurate result.
Total pull requests merged across all repos your team owns.
From PR opened to the first substantive code review comment or approval.
From first review to the PR being merged (including back-and-forth and CI wait).
Number of engineers actively submitting PRs.
Enter your metrics and click Benchmark to see your result.
How the benchmark is calculated
Review lag (40%)
Time from PR open to first meaningful review. The biggest driver of cycle time loss — Elite teams review within 2 hours.
Merge gap (40%)
Time from first review to merge. Includes CI wait, re-review, and approval latency. Equally weighted with review lag.
PR volume (20%)
PRs per developer per month. Very low or very high throughput signals either low activity or oversized PRs — both carry risk.
Tier thresholds are derived from the DORA State of DevOps report (Elite / High / Medium / Low performer definitions) and corroborated by LinearB's engineering benchmark dataset. View the full benchmark data →