---
title: "PR throughput"
canonical_url: "https://docs.getdx.com/reports/pr-throughput/"
md_url: "https://docs.getdx.com/reports/pr-throughput.md"
last_updated: "2026-06-18"
---

# PR throughput
PR throughput measures the number of merged pull requests divided by the number of contributing engineers over a specific period. This report excludes bot-authored pull requests as it focuses on the productivity of your developers as opposed to bots and other forms of automation.

Additional nuances are discussed below:

## What is TrueThroughput®?

TrueThroughput® uses AI to account for the complexity of pull requests, and thereby create a throughput metric that provides a truer measure of output (similar to a weighted GPA). For more information, please visit our dedicated article on [TrueThroughput®](https://docs.getdx.com/reports/truethroughput/).

## Who is considered a developer?

DX reports normalize activity metrics into a "per developer" format. To ensure these metrics are accurate, DX must determine which users should be counted as developers. Including non-developers in this calculation would artificially lower the metric.

For reporting purposes, a user is considered a _developer_ in DX if **both** of the following are true:

- The user has authored at least one pull request, and
- The user is not explicitly marked as a non-developer in DX

Users self-identify their role during the DX Snapshot by indicating whether they regularly write code. Workspace admins can override these designations manually if needed.

## How are team changes handled?

Each date increment includes developers who were active members (i.e., not deleted) of your organization and given teams for at least one day during the date increment.

In cases where a developer changes teams, joins the organization, or leaves the organization in the middle of a date increment, DX adjusts the denominator (i.e., number of developers) by prorating for the number of days in which the developer was a member of your organization or a given team.

Examples:

- James Williams, a developer, switches from Team A to Team B in the middle of January. James' pull requests will be assigned to Team A and Team B based on the date of the team change. For January, James will count as 0.5 developers in the denominator for both Team A and Team B.

- Isaac Noda, a developer, joins Team A in the middle of January as a new hire. For January, Isaac's pull requests will be included under Team A, and Isaac will count as 0.5 developers in the denominator.
---

## Sitemap

[Overview of all docs pages](/llms.txt)