In Review Time
Task Cycle Times
business days
Measures the average weekday duration tasks spend in the "In Review" state.
💡 Like a manuscript waiting for an editor. In Review time is completely in the hands of the reviewer, not the author.
What It Measures
Measures the average weekday duration tasks spend in the "In Review" state.
Why It Matters
Identifying review bottlenecks in your workflow
Understanding how long tasks wait for and undergo review
How It's Calculated
Calculates the mean business days tasks spend in "In Review" before moving to the next state.
AVG(business_days_in_review WHERE completed_at BETWEEN measure_from AND measure_to)Concrete Example
If tasks spend an average of 1.5 business days in In Review, that means reviewers are responding within a day and a half, solid but there's room to improve.
What Does a Healthy Score Look Like?
Lower is better, review time is usually pure waiting time for the author.
Healthy
Under 1 business day
Watch Out
1–3 business days
Needs Attention
Over 3 business days, review is a bottleneck
What Moves This Metric?
Goes up when…
Reviewers handling too many PRs simultaneously
Large or complex changes requiring deep review
Review requests going to busy or unavailable teammates
Goes down when…
Faster reviewer response through team agreements on review SLAs
Smaller PRs that require less reviewer time
Review rotation ensuring no single reviewer is overwhelmed
Start Tracking In Review Time
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com