Load Management and the Blurred Line Between Sports Science and the NBA's Commercial Calendar

The stands are still full. Tickets sold out weeks in advance. But when the referee tosses the ball up, the two names the crowd paid to see are sitting on the bench in hoodies, headphones on. That night was a nationally televised game in the NBA regular season, and it raised a question no box score fully answers: who actually owns the body of a professional basketball player — the player, the team, or the broadcast schedule?

I have rewatched hundreds of games like that, not to find the game-winning shot but to find the reason behind an absence. After many years, what I realized is that most debates about "load management" are about the wrong thing. People argue about sports science, while the real problem lies in the commercial calendar.

From "DNP-Old" to the participation policy

The term "load management" was not born in a sports science lab. It became widespread around the 2026-2026 season, when Kawhi Leonard was rested by the Toronto Raptors in back-to-back games as part of a long-term plan aimed at the playoffs. But its roots go back much further.

Gregg Popovich, head coach of the San Antonio Spurs, was the pioneer. He rested Tim Duncan, Manu Ginóbili and Tony Parker in nationally televised games — a practice American media called "DNP-Old." For Popovich, it was a resource-management decision: his three stars were all past 30, and an NBA season of 82 games plus the playoffs is a punishing workload.

The peak came in November 2026. The Spurs traveled to Miami to face the Heat in a game broadcast nationally on TNT. Popovich rested four starters — Duncan, Ginóbili, Parker and Danny Green — then flew back to San Antonio before the game ended. Then-NBA commissioner David Stern responded within hours, declaring the rest had "damaged the NBA" and fining the Spurs $250,000.

The 2026 incident showed the line had been drawn long ago: the NBA did not object to rest, it objected to rest at exactly the moment the cameras were rolling. It was the first sign that "load management" was never purely a medical matter.

More than a decade later, in September 2026, the NBA Board of Governors approved the Player Participation Policy. The policy defines a "star player" as someone selected to the All-Star or All-NBA teams in the previous three seasons — a list usually numbering around 50 names. Under the policy, teams may not rest two star players in the same game, may not rest star players in nationally televised games, and may not rest them long-term while they are healthy enough to play. Fines escalate: $100,000 for a first violation, $250,000 for a second, and $1 million or more for subsequent ones.

In parallel, the 2026 Collective Bargaining Agreement introduced a rule requiring players to appear in at least 65 games to be eligible for major awards such as MVP, All-NBA or Defensive Player of the Year. This struck at the wallet: the supermax contracts of many players depend on whether they make an All-NBA team.

The 2026-2026 season showed the rule can backfire. Joel Embiid, the Philadelphia 76ers center, was a strong MVP candidate before suffering a meniscus injury in January 2026. Pressure to reach the 65-game threshold to preserve award eligibility was widely cited as one reason he kept playing before fully recovering. By season's end, Embiid fell short of the games threshold, lost award eligibility, and his team entered the playoffs with a center who was not at his best.

What the box score does not record

To be clear: I am not opposed to rest. A 34-year-old with two knee surgeries should not play 82 games at high intensity. My problem is how we justify it.

Look at the numbers. When a star rests, a team loses more than scoring. It loses the continuity of its system. In many games I have rewatched, I noticed one thing: teams do not lose because they lack talent, but because their defense loses a shared language.

Take a team using drop coverage — the center drops deep to protect the rim, the guard chases the ball handler over the screen. When the starting center rests, the replacement often cannot read the moment to drop or step up. The result is space opening in the mid-range, the area traditional statistics dismiss as an "inefficient shot" but which is the pressure point of an entire system.

Another team chooses to switch every screen. This system demands that all five players on the floor share the same threshold of understanding about when to switch and when not to. When a defensive star is absent, the whole chain of decisions goes off. The replacement may switch too early, creating a mismatch the opponent exploits immediately. On tape you see it clearly: a small guard stuck under the rim against a big center, and it all starts from a fraction of a second of delay in the switch decision.

I once tracked a mid-table team in a recent regular season. In the four games their starting center was absent, their defensive rating deteriorated markedly, and notably most of the points conceded came from pick-and-roll situations in the mid-range — not from three-pointers. This is a detail the box score does not reflect at all.

The blind spot is not on the diagram; it lies between two movements no one measures. When a substitute enters the game, he does not just replace a position. He replaces a set of habits. A guard used to his center always being in the drop position will angle his screen differently. A wing used to his star drawing two defenders will cut into space on a different beat. These differences are so small they appear in no standard data table, yet they compound over four quarters.

I do not watch a game as a spectator; I read it as a text of deliberate mistakes. And in that text, the absence of a star is the longest chapter.

For years, I have built a personal note system of repeating patterns. I record not results but mechanisms: who moves first, who reacts second, and how much time lies between those two actions. Doing this across hundreds of games, I realized that defensive quality depends less on individual talent and more on whether players share the same "vocabulary."

Defense is the last language; only those patient enough to listen to 400 straight games can interpret it.

This leads to an important conclusion: a star's true defensive value lies not in steals or blocks, but in keeping the system from cracking. A star resting one game does not make a team weaker in overall talent, but it breaks the familiar chain of reactions. That is why some teams play better when their star is absent for a few games — they are forced to simplify the system, and that simplification is sometimes more effective in the short term.

Every tactical system is born from a detail everyone saw but no one noticed. In this case, that detail is time. Not playing time, but reaction time — the gap between the moment a screen is set and the moment the defender decides to go over or under. That is the variable every team depends on, and the first variable broken when the lineup changes.

A low-tier game on a small screen, and I saw an entire universe in motion. I once spent many nights rewatching EuroLeague and Spanish league games, where the season runs only about 34 games in the regular phase. There, the concept of "load management" barely exists — not because European teams take player health lightly, but because their calendar does not create the same pressure. When you play fewer games, you do not need to rest as much. This difference is clear evidence that the problem is not the player's body, but the number of games.

This comparison made me look at the NBA differently. If 82 games are the cause, then every "load management" solution only eases the symptom. You can rest a player for 15 games, but if the schedule still requires him to cross time zones and play three games in four nights, his body still pays the price.

The counterintuitive angle: the data does not support rest the way we assume

This is the part that has bothered me most for years. If load management were truly an effective scientific measure, we should see clear evidence that it reduces injuries. But that evidence is thin.

Studies of injury in professional sport often show that the relationship between workload and injury is non-linear. Too much rest can also raise injury risk when a player returns to high intensity abruptly. In other words, "load management" is not a precise scientific formula, but a set of experience-based judgments dressed in the language of data.

And if you look at when stars rest, a pattern emerges: they rest most in back-to-backs, on long road trips, and in games with unfavorable broadcast slots. That is not a medical pattern. It is the pattern of a commercial calendar.

Preseason tours and international games are the clearest proof. Every summer, top teams fly around the world to play friendlies in Asia, Europe and the Middle East, turning players into performers in a marketing circus. Preseason fitness — already compressed — is further exploited for commercial ends. Then, when the season begins, those same players are rested to "protect their health."

This is the core contradiction: we sell players to sponsors in summer, then hide them from paying fans in winter. Load management, in practice, is not the opposite of commercialization. It is a consequence of it.

The biggest stars — those with the largest contracts and the highest commercial value — are usually the ones rested most. Meanwhile, players at the end of the bench, who need every minute to prove their worth, are almost never "load managed." The system protects the team's assets, not the people.

I understand why teams do this. A star is an asset worth hundreds of millions of dollars. But it is how we talk about this issue that matters. When the media calls it "science," we are concealing a much simpler reality: this is a negotiation between medicine, commerce and the broadcast schedule, and the outcome usually leans toward the latter two.

What to watch next

If we accept that absence is unavoidable, the right question is not "how many games to rest," but "which system can absorb absence." The successful team of the future will not be the one with the healthiest star, but the one with a defensive system simple enough that anyone can step in and speak the same language.

I believe the variable of the coming season lies not in the injury report, but in roster depth and how coaches design transferable defensive principles. When you design a system that depends on one name, you do not own a system — you own a hostage.

And the question I leave you with: if a star rests to protect his health for the playoffs, but it was the commercial calendar that made him need rest in the first place — then who is really managing the load for whom?