Loading page…
Why salary comparisons start with the cap
Nominal dollars hide how a contract sits inside the NBA economy of its season.
The Contract Value Model begins with documented salary and the season salary cap. That makes cross-season comparisons more legible while keeping contract terms and missing fields explicit.
The question
What can a salary comparison establish when cap levels change and contract terms are not uniformly documented?
Context
A $20 million salary does not carry the same league-wide meaning in every season. Cap share provides a stable first comparison, but it is not a complete valuation of a player or a front office decision.
Data
- Documented salary and contract rows from the repository's Basketball-Reference adapter.
- Season salary-cap reference records.
- Player and season joins used by the contract analytics surface.
Method
The analysis follows the method path shown below; each step is a boundary on what the note can establish.
- 01Salary is divided by the season salary cap to produce cap share.
- 02The result is kept separate from player-quality estimates and is presented as contract context.
- 03Unsupported options, guarantees, supermax details, trades, and apron restrictions are not inferred.
What the method establishes
- Cap share gives the contract surface a common denominator across seasons.
- The public model card supports descriptive comparisons, not a free-agent price forecast or a front-office grade.
- When a contract field is not documented, the product keeps it unavailable.
Interpretation
The model answers where a documented salary sits relative to that season's cap. It does not answer whether the deal was good in hindsight without a separately validated value estimate and a defined counterfactual.
Limitations
- Coverage follows the public source adapter and can be incomplete.
- Contract mechanics that are not present in the source remain unknown.
- Calibration against realized contracts and historical holdouts is not published.