Effort is small. Waiting is expensive.
Most conversations about code review focus on effort: how long it takes a reviewer to read a change. For a typical pull request that number is modest. The bigger cost is the time it spends waiting: for a first look, for the author to respond, for the re-review and for the merge.
While a pull request waits, the author has moved on to something else, the branch drifts away from main, and the context that made the change easy to reason about fades. None of this shows up on a timesheet, which is why it is so easy to underestimate.
How waiting compounds
Waiting sets off a chain of smaller costs that add up quickly:
- Context switching. Each slow round trip forces the author to put the work down and pick it up again.
- Bigger pull requests. When every review costs a day, developers batch more into each change, and bigger changes get slower, shallower reviews.
- Drift and conflicts. Long-lived branches collide with main, sometimes visibly and sometimes in subtle ways that still merge cleanly.
- Reviewer fatigue. Long queues lead to marathon review sessions where the last pull requests get the least attention.
Put a number on it
The paper includes a simple, transparent model that estimates the weekly cost of review latency for your team. You enter your own inputs: pull requests per week, context-switch cost, how often feedback lands late, how often branches conflict, and your loaded hourly rate. Every assumption is visible and labelled, so you can adjust it to fit your team rather than rely on someone else’s benchmark.
Even with conservative inputs, the model shows how small costs per pull request become a significant weekly total once they are multiplied across a whole team.
Measure it, then shrink it
You can’t manage latency you don’t measure. The paper defines the metrics that matter: time to first review, review rounds, time to merge, pull request size and post-merge fixes. It explains why you should track distributions rather than averages. It then sets out a practical playbook, from first-review targets and smaller pull requests to automating the mechanical first pass so it never waits for a human. A one-page checklist lets you see where your team stands today.
Download the full paper
The full 11-page paper includes the anatomy of a waiting pull request, the worked cost model, the metrics table and the checklist. It’s free. Fill in the form to download the PDF and share it with your team.