Engineering Craft › Pull Requests & Code Review

Review Turnaround

How quickly reviews happen, and why it matters to team speed.

Also known as: time to review, PR wait time

Review turnaround is the time between a pull request being opened and the first meaningful review. A change that waits a day for review is a day it can’t reach users, and the author has usually moved on to other work. When they come back, they have to reload the context, which costs time too.

Small changes make fast reviews easier. A change of a few dozen lines can be read in a few minutes, while a thousand-line change tends to wait until someone has a large block of free time.

Waiting:  "Can someone review PR #412? It's been open two days."
Better:   Small PR, a clear description, and a named reviewer who has agreed to look today.

The trade-off is between quick approval and careful review. Fast reviews that skip the real reading defeat the purpose. The goal is a predictable response time, not a rushed one. Reviewers also need protected time to do the work, which competes with their own tasks.

The classic mistake is treating review as an interruption to be handled later, so PRs queue up for days. Agree on a response target, such as first feedback within a working day, and track how long reviews actually take. Routing with CODEOWNERS can help, but only if the owners are available. Teams that do this well often pair with a first-pass AI review to shorten the first round, though a person still has to approve.