Add review cycles and time to adoption phases in the usage API

The Copilot usage metrics API now reports two additional code-review velocity metrics for each AI adoption phase, extending the adoption phase cohorts fields available in the enterprise and organization reports. Alongside the existing per-phase merge time and merge counts, you can now compare how quickly pull requests are reviewed and how many review cycles they take across your adoption cohorts.

What’s new

Each phase entry in the totals_by_ai_adoption_phase breakdown now includes two new fields:

• avg_pull_requests_minutes_to_review: The median time, in minutes, from when a pull request is created to its first review.
• avg_pull_requests_review_cycles: The median number of review submissions a pull request receives before it merges.

Both metrics are scoped to merged pull requests and attributed to each pull request’s merge day, so every pull request is counted exactly once. Pull requests that are reviewed but never merged do not contribute to either metric.

Why this matters

Review latency and review-cycle counts are leading indicators of engineering throughput. By breaking them out by AI adoption phase, you can see whether teams with deeper Copilot adoption get their pull requests reviewed faster and iterate through fewer review cycles. This helps quantify the downstream impact of Copilot on your review process and helps you target enablement where it moves the needle most.

Important notes

• These metrics appear in both the enterprise and organization 1-day and 28-day reports.
• Because they are scoped to merged pull requests, review latency and cycle counts reflect work that actually landed.
• Phase definitions and cohort assignment are unchanged. For details, see the adoption phase cohorts announcement.

Visit the Copilot usage metrics API documentation to get started.