NBA DFS Research: How To Project Minutes, Usage & Pace
July 19, 2026
NBA DFS Research: How To Project Minutes, Usage & Pace
Winning daily fantasy basketball does not start with the biggest projected total on the slate. It starts with a process, and the process is always the same three moves, run in the same order: project the minutes, adjust the rates, then find the games with the pace and the total to reward all of it. Everything else in NBA DFS research is a footnote to those three tenets. Get the order right and a projection stops being a number you copy off a screen and becomes something you actually understand, including the one loose injury update that could double it.
This guide walks that process end to end, the same way I do it before I build a single lineup. Each step feeds the next. Minutes are the foundation. Rates are the multiplier that a lineup change quietly resets. Pace and total are the environment that decides how much all of it is worth.
TL;DR: The NBA DFS Research Process
- Project Minutes First. No minutes, no production. Use season averages for a baseline, recent games when a role is changing, and game logs to learn a coach's substitution pattern.
- Adjust Usage And Rebounding Rates When Someone Is Out Of The Normal Lineup. A starter ruled out redistributes possessions — and the swing on a high-usage, high-rebound, or high-assist teammate can be enormous.
- Target High Pace And A High Vegas Total. More possessions plus a higher total means more fantasy points on the table for every player in the game.
- Do It In That Order. Minutes are the base, rates are the multiplier, pace and total are the environment. Skipping a step is how you end up rostering a projection you cannot defend.
Watch The Video
The full walkthrough of these NBA DFS research concepts is on YouTube:
Step 1: Project The Minutes
Minutes are the foundation of every counting stat in basketball. A player who is not on the floor cannot score, rebound, or assist, so before you look at a single efficiency number you have to answer one question: how long is this guy actually playing tonight? There are three places to build that estimate, and you use them in combination, not isolation.
| Data Source | What it gives you | When it wins |
|---|---|---|
| Season Averages | A baseline read on how often a player is on the floor | Stable roles with a full sample of games |
| Recent Playing Time | The current trend when a role is shifting | A player climbing from the bench into the starting lineup |
| Game Logs & Substitution Patterns | The coach's actual rotation, sub by sub | Anytime you need to know how the minutes accumulate |
Start with season averages for a quick read on how often a player is simply on the floor over a full sample. The average alone can mislead you, though, because it flattens out the games at the extremes. Take a big like Mitchell Robinson: he might play anywhere from 14 minutes to 28 depending on foul trouble, and a raw average lands somewhere in the low-to-mid 20s. That mid-20s figure is more representative of his true range than either the 14 or the 28, but you only know to distrust the single number once you have seen how wide the spread is. The row worth pausing on above tells the story: the season average is a baseline, not an answer.
Recent playing time is where you catch what the season average misses. When a player started the year on the bench and has slowly worked his way into the starting lineup, his season average drags him down and hides the fact that he is now a 30-minute player. Looking at his last handful of games projects that trend forward instead of anchoring to stale data. Whenever a role is changing, recent games beat the season line.
Game logs and substitution patterns are the final layer, and the one that separates a good minutes projection from a great one. Read the logs to see exactly when a player checks in and checks out, and you start to learn the coach's rotation: who plays with whom, which units close, when the starters get their rest. Understand the substitution pattern and your NBA DFS minutes projections get noticeably more accurate, because you are no longer guessing at a total. You are mapping how the total actually gets accumulated.
Once every player on the slate has a minutes number you trust, you have the base of the projection. Now comes the move that quietly rewrites it.
Step 2: Adjust The Rates When Someone Is Off The Floor
Here is the number that resets every projection on the slate: rate stats change when the lineup around a player changes. Once your minutes are set, the next step is to adjust the rates, usage rate and rebounding rate in particular, for any player who is out of his normal starting five because a teammate is in or a teammate is out.
This is not a perfectly scientific process. There is genuine wiggle room, and different players respond differently when specific teammates sit. That is exactly why you lean on on/off tools, which show you how a player's rates shift with a given teammate on or off the floor. The goal is to replace a guess with a range you can defend.
The classic example of an NBA DFS usage rate swing is James Harden. Back when Harden and Russell Westbrook shared a backcourt, Harden's usage rate would skyrocket whenever Westbrook was off the floor, climbing all the way up to nearly 50% usage. That is a massive change to a baseline projection, and it was knowable in advance simply by seeing that Westbrook was ruled out. A player carrying that kind of usage swing is a different projection depending on one name on the inactive list, and the whole point of research is to catch it before the field does.
The effect matters most for players who already command a lot of a possession or a rebound. Recall the minutes work from Step 1: a big man like Mitchell Robinson lives on rebounding rate, so a high-usage or high-rebound teammate going out sends his numbers moving, not just his minutes. The larger a player's usage, rebounding, or assist rate, the larger the swing when you swap a high-rate teammate for a low-rate one. And because everyone's shots and boards come out of the same fixed pool, that swing has a trickle-down effect through the rest of the lineup.
| Rate To Adjust | Who it moves most | The signal to watch |
|---|---|---|
| Usage Rate | High-usage scorers and ball-handlers | A primary creator or shot-taker ruled out — usage flows to whoever inherits the offense |
| Rebounding Rate | Bigs and high-rebound wings | A frontcourt teammate out leaves boards on the floor for the next man up |
| Assist Rate | Lead guards and playmaking hubs | A co-creator out concentrates the passing load in one set of hands |
The row that pays the bills is the top one. A usage-leader going out is one of the biggest levers in NBA DFS research, because those shot attempts and creation chances have to be redistributed to someone, and usage is what tracks where they land. When you see a primary scorer ruled out, your first job is to find whose usage inherits the vacated possessions, because that player is often underpriced, at least until his salary catches up to the new role. If you want the tool that surfaces those on/off rate swings, minutes, and ownership on one screen, that is exactly what the NBA DFS projections, ownership and stacks in the DataHub is built to do. For a full column-by-column read of those numbers, our guide to using NBA DFS data breaks each one down.
Step 3: Identify High Pace And High Total
Minutes give you opportunity and rates give you the share of it, but the last step decides how much that opportunity is worth in the first place. This is where pace and total come in, and they work together.
The Vegas game total is the market's estimate of how many points the two teams will combine to score. You do not have to treat it as gospel, but the relationship is simple and reliable: the higher the total, the more fantasy points you should expect out of that game. A high total is a rising tide.
Pace is the other half of the NBA DFS pace-and-total read. Pace is how many possessions exist in a 48-minute game, and more possessions means more chances for everyone on the floor to rack up fantasy points. High pace plus a high total is the environment you are hunting. A fast game with a lot of expected scoring hands every player in it extra opportunities on top of the minutes and rates you have already projected.
You can estimate a game's pace before tip with a quick calculation. Take one team's pace, multiply it by the pace of the specific opponent they are facing (the actual matchup, not a random team), and divide by the league-average pace. That gives you a workable estimate of how many possessions the game will hold.
Pace estimate: (one team's pace × the opponent's actual pace) ÷ league-average pace = the projected possessions for that specific matchup.
One caveat worth respecting: early in the season, pace and total figures are noisy, and it takes time for that noise to wash out of the numbers. In the opening weeks you are often better off leaning on league averages, giving a slight bump where the matchup clearly warrants it, rather than trusting a five-game pace sample. Later in the year, once the sample has settled, the estimate above earns its keep.
A Worked Example: Putting The Three Tenets Together
Return to the James Harden and Russell Westbrook spot the video calls out, and run the full sequence on it in order:
- Minutes. Confirm Harden is in his usual heavy-minutes starter role. His minutes are stable, so the foundation of the projection is not the question here. The lineup around him is.
- Rates. Westbrook is ruled out, and that inactive is the trigger. With Westbrook off the floor, Harden's usage rate climbs toward that near-50% figure, because more of the offense runs through him. Callback to the lever from Step 2: usage is the engine of scoring, so this is the swing that matters most, and the on/off data is what tells you how far it moves.
- Pace and total. Now check the game environment. If Harden's team is in a high-total game against a fast opponent, those spiked-usage minutes are being spent in a scoring environment that rewards volume. The same usage bump in a grind-it-out, low-total game would be worth noticeably less.
Stack all three and you have a projection you can defend: stable minutes, spiked usage from a confirmed inactive, in a game built to produce fantasy points, and often a value before the salary catches up to the new role. That is the whole process in one player, and it is why the order matters. Miss the minutes and the usage means nothing. Miss the pace and the usage is being spent in the wrong game.
Where The Research Lives In Our Tools
You can run this entire process by hand, and understanding it by hand is what makes you dangerous. The Stokastic NBA Sims and DataHub are built around these same inputs, so they are the place to check your work: projected minutes to compare against your own, usage and rebounding context to read against who is on and off the floor, and pace and totals for the slate all on one screen. If you want the deeper reads behind those columns, the NBA DFS projections guide shows how they turn into lineups, and our breakdown of Sims vs. optimizers explains why simulations beat a flat projection for this kind of research. For the wider slate approach, the full NBA DFS strategy guide ties it all together. When news breaks, the same reads feed straight into today's NBA DFS picks hub.
Run the research faster. The Stokastic NBA Sims and DataHub put projected minutes, on/off usage rates, ownership, and pace-aware projections on one screen. Use code NBARESEARCH10 for 10% off at stokastic.com/pricing.
Frequently Asked Questions
What is the most important step in NBA DFS research? Projecting minutes. A player who does not see the floor cannot produce, so minutes are the foundation every other number sits on. Build your minutes projection from season averages, recent games, and the coach's substitution pattern before you look at anything else. A useful rule of thumb: when a role is actively changing, weight the last five to ten games over the full-season average, since that recent stretch reflects the rotation the player is in now.
How do injuries change my NBA DFS projections? A starter ruled out redistributes usage, rebounding, and assist opportunity to teammates. The biggest swings come on high-usage scorers, high-rebound bigs, and lead playmakers. Use on/off data to see how far a specific teammate's rates move. For example, a primary ball-handler out can send a backup's usage rate soaring.
Why does pace matter in NBA DFS? Pace is the number of possessions in a game. More possessions mean more scoring, rebounding, and assist chances for everyone on the floor, so a high-pace game inflates fantasy production across the board. Pair a high pace with a high Vegas total and you have the best scoring environment on the slate.
How do I estimate a game's pace? Multiply one team's pace by their actual opponent's pace, then divide by the league-average pace. That gives a workable estimate of the possessions in that specific matchup. Early in the season, when the sample is noisy, lean on league averages with a small bump instead.
Do I have to use the highest Vegas total on the slate? No, but the total is a reliable tailwind. The higher the total, the more combined scoring is expected, and the more fantasy points are on the table. Use it alongside pace and your minutes and usage reads rather than as a standalone reason to roster a player.
In Summary: The Three Tenets Of NBA DFS Research
- Project The Minutes First. Start with season averages, correct with recent games when a role is changing, and read game logs to learn the coach's rotation. No minutes, no production.
- Adjust The Rates When The Lineup Changes. Use on/off tools to move usage, rebounding, and assist rates for anyone out of their normal five — the swing on high-usage players like a Harden-with-Westbrook-out spot is the single biggest lever in the sport.
- Find The Pace And The Total. More possessions and a higher Vegas total mean more fantasy points for everyone in the game. Estimate pace from the specific matchup, and lean on league averages early in the season.
- Respect The Order. Minutes are the base, rates are the multiplier, pace and total are the environment. Run them in sequence and every projection you build is one you can actually defend.
