Basketball research guide
Basketball Pace: Why Points per Game Can Mislead
A basketball team that scores more points per game does not necessarily score more efficiently. It may simply have more opportunities. Pace helps separate the number of possessions from what a team produces with them.
That distinction is useful when comparing offenses, defenses or two teams playing at different speeds. Start by asking two questions: how many possessions were available, and how much did the team accomplish per possession?
What pace measures
In the NBA's statistical framework, pace expresses possessions per 48 minutes. It describes the rate of play rather than shooting quality or overall team strength. NBA G League statistical glossary.
Keep the unit visible when using another competition or provider. A table normalized to a different game length is not directly comparable to an NBA per-48-minute figure. Likewise, a possession total from a game with overtime is not automatically a standardized pace value.
Pace is also different from player running speed. A fast athlete can play in a low-possession game; a high-possession game can contain several styles of offense. Use the metric for the question it actually answers.
A higher score can hide lower efficiency
Consider two fictional team performances:
| Team | Points | Offensive possessions | Points per possession |
|---|---|---|---|
| A | 120 | 110 | 1.091 |
| B | 112 | 100 | 1.120 |
Team A scored eight more points, but Team B produced more points per offensive possession. If you only read the points column, you miss that distinction.
The example does not prove Team B is better in general. It describes two invented samples with stated possession counts. Opponents, lineups and game situations have not been controlled. The value of the calculation is narrower: it puts the scoring on a common opportunity basis.
Convert scoring into offensive rating
Team offensive rating expresses points scored per 100 possessions; defensive rating expresses points allowed on the same scale. The NBA's introductory explanation uses these rates to separate scoring from pace. Jr. NBA: traditional and advanced statistics.
For the fictional performances above:
Team A: 120 ÷ 110 × 100 ≈ 109.1
Team B: 112 ÷ 100 × 100 = 112.0
Read 112.0 as 112 points per 100 possessions in that sample. It is not 112 points guaranteed in the next game, and it is not a shooting percentage.
On defense, the same principle matters. A team can allow a large points total in a high-possession game without allowing an equally large amount per possession. Keep pace and defensive efficiency side by side before deciding what the final score says about the defense.
Do not count possessions by counting shots alone
A field-goal attempt and a possession are different units. An offense can retain the ball after an offensive rebound; it can also lose the ball without recording a field-goal attempt. Consequently, a shot total should not be used as a possession total.
Use the possession count supplied by a consistent statistical source, and read its methodology if precision matters. An estimated box-score count and a play-by-play count can differ. If you switch providers, check definitions before interpreting a small difference as a change in team behavior.
The calculation becomes much easier to audit when your research note includes the source, date range and possession method next to the rating.
Combine samples with the right weights
When you have the underlying data, calculate a combined rating from total points and total possessions. Do not automatically give a short sample the same weight as a long one.
Suppose one lineup scores 22 points in 20 possessions and another sample of that lineup scores 90 in 80. The combined result is 112 points over 100 possessions, or a 112.0 offensive rating. Averaging displayed ratings can produce discrepancies when samples have different sizes or the displayed numbers are rounded.
State which players and minutes belong to the sample. A season-long team number is not interchangeable with a short lineup split.
Use pace in a matchup without turning it into a prediction
Two teams bring different habits into a game, but a simple average of their past pace values is not a validated forecast by itself. If you build such a model, label the assumption and evaluate it against games that were not used to choose the rule.
A useful research note can remain descriptive: “This offense's recent scoring total rose while its points per possession stayed similar; check whether additional opportunities explain the change.” That is a question the data can investigate without inventing certainty about the next score.
The Cold Line's Builder overview links to the NBA workbench and college basketball workbench; those workbenches require an account. Bring the source and uncertainty of your inputs with you.
Pace is most useful when it stops one number from doing two jobs. Let possessions describe opportunity, let per-possession rates describe production, and then examine the matchup context that neither number captures alone.
Why TCL is a premier tool for basketball matchup research
TCL connects the concepts in this guide to dedicated NBA and college basketball workbenches. Start by separating possessions from production, then inspect the matchup inputs and resulting estimate in the relevant Builder. Bringing clear explanations and interactive research together makes TCL a premier tool for developing a more complete basketball analysis.