Avg. to first review

The average amount of time it takes for a pull request to receive its first review after being created.

High: Less than 24 hours – show strong review triage and availability at scale. Typically reflects clear code ownership, auto-assignment/rotations, CI that surfaces changes quickly, and well-scoped PRs. Watchouts: rubber-stamping or superficial reviews—use checklists and spot audits to protect quality.
Medium: Between 24 and 72 hours – a healthy enterprise norm. Balances time zones, reviewer load, security/compliance checks, and deeper feedback. Signals workable processes: reliable CI, defined SLAs, and predictable handoffs. Keep it steady with reviewer rotations, small PRs, and async feedback before meetings.
Low: More than 72 hours – suggests bottlenecks: too few qualified reviewers, heavy approval chains, flaky/slow CI blocking pickup, oversized PRs, or cross-team dependencies. Improve by splitting PRs, enabling draft PRs early, widening/backup reviewer pools, adding escalation rules & SLAs, reserving “review hours,” and stabilizing CI.

High: Less than 2 hours - very responsive team, quick review initiation, may indicate rushed reviews or insufficient depth. Verify review quality and thoroughness.
Medium: Between 2 and 8 hours - good balance between responsiveness and thoroughness, common for well-functioning teams. Monitor for consistency and trends.
Low: More than 8 hours - slow response may indicate bottlenecks. Potential Issues: too few reviewers available, reviewers are overloaded, process inefficiencies, team communication issues, time zone differences.

Don't forget you can anytime include any metric in your Custom Dashboards.

Updated 2 months ago