Rework Rate
Pull Request Lifecycle
%
Shows the percentage of merged pull requests that needed multiple review cycles.
💡 Like revisions on a document, some editing is expected and healthy, but if every draft needs major rewrites, the initial quality needs improving.
What It Measures
Shows the percentage of merged pull requests that needed multiple review cycles.
Why It Matters
Monitoring quality of initial submissions
Identifying if PRs typically require significant rework
How It's Calculated
Divides the count of merged PRs with 2 or more cycles by total merged PRs and multiplies by 100.
100 × COUNT(prs WHERE cycles ≥ 2 AND status = merged) ÷ COUNT(prs WHERE status = merged)Concrete Example
If 30% of your merged PRs required 2 or more review cycles, nearly a third of your work needed significant iteration before it was accepted.
What Does a Healthy Score Look Like?
Lower is better, high rework rate signals issues with quality or communication.
Healthy
Under 30% of PRs need 2+ cycles
Watch Out
30–50% of PRs need 2+ cycles
Needs Attention
Over 50%, most PRs require significant back-and-forth
What Moves This Metric?
Goes up when…
PRs submitted before thorough self-review
Unclear requirements leading to different implementations
Reviewers having inconsistent or shifting standards
Goes down when…
Authors doing thorough self-review before submitting
Pair programming or early feedback sessions before formal review
Clear team conventions reducing subjective feedback
Start Tracking Rework Rate
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