# Cutting PR review time is really changing where review happens > Source: > Published: 2026-09-14 00:15:07+00:00 Atlassian reports its Rovo Dev AI reviewer cut PR cycle time by up to 45% internally and 32% for customers ([primary source](https://www.atlassian.com/blog/rovo/how-we-cut-pr-cycle-time-with-ai-code-reviews), Jan 2026). That figure gets quoted as proof that AI review saves review time. Read what the reviewer is described as doing and the number is mostly about routing. The post says the reviewer enforces engineering standards and Jira acceptance criteria before a person opens the PR. Mechanical checks run first, so most of the read-and-re-read cycle is gone before a human touches the change. What falls is the calendar time spent waiting on machines and re-reading the mechanical parts. The part that does not fall is the decision. The Real-SWE benchmark ([Specific Labs, Sept 2026](https://withspecific.com/benchmarks/real-swe)) has the best agent resolving 38.8% of its tasks on licensed enterprise codebases. At that acceptance rate the expensive step is deciding whether a given change is actually correct. Shortening the pipeline around it does not shorten that step. It moves the step. So the useful target is not "reduce PR review time." It is "spend human attention only where a machine cannot decide, and decide faster." Baseline checks, standards matching, acceptance-criteria checks all automate cleanly. The person keeps one yes-or-no question with a reason to back it. Teams that only speed up the reading part find the queue moves faster while the wrongness volume stays the same. The teams getting honest cuts are the ones that changed the order: machine decides the mechanical layer, person decides the change itself.