What is a handcuff in fantasy football?

Why running backs, and not other positions

Running back is the position where opportunity transfers most cleanly. When a lead back is out, his carries and goal-line work have to go somewhere, and most teams hand the bulk of them to one player. A receiver’s targets tend to scatter across the whole offense when he is out, and a backup quarterback rarely matters outside of deep leagues. That is why the word handcuff almost always means a backup running back.

The name comes from the original use: you drafted a star back and then “handcuffed” him by also rostering his backup, so an injury could not sink your season. Today most managers treat handcuffs more broadly. You can hold the backup to someone else’s starter just as easily as your own, and that is often the better bet.

What a handcuff hit looks like

Two well-known seasons show the upside. In 2017 Kansas City’s Spencer Ware injured his knee in the preseason; rookie Kareem Hunt took over the backfield and led the NFL with 1,327 rushing yards. In 2018 Le’Veon Bell sat out the entire season in a contract dispute; James Conner started in his place, finished with 1,470 total yards and 13 touchdowns, and made the Pro Bowl. In both cases the back who benefited could be had for almost nothing shortly before the news.

Those are the best outcomes, not the typical one. In most weeks most handcuffs do very little, because most starters play. Our own track record shows that plainly: the hit rate in any one week is low, and the value comes from owning the right back in the week it finally matters.

What separates a good handcuff from a name on a depth chart

• A clear line of succession. The best handcuffs would take most of the starter’s work by themselves. If the team would split the job three ways, no single backup inherits enough to matter. We label those backfields as shared.
• A valuable job to inherit. The backup on a run-heavy offense with a good line is worth more than the backup on a team that throws on every down. The size of the role matters as much as the odds of getting it.
• The skills to keep the role. A back who can catch passes and handle pass protection stays on the field in every situation. One who cannot will lose third downs to someone else even as the nominal starter.
• His own availability. A handcuff who is hurt himself is not insurance. Check the running back injury report for both the starter and the backup.
• A starter with some risk attached. Age, a heavy workload and injury history all raise the chance the backup is needed. They raise it; they do not predict it.

These are the same factors behind the scores in our handcuff directory, which names one preferred backup for every backfield. The methodology page explains how they are weighed.

Should you handcuff your own starter?

Sometimes. Holding your own starter’s backup lowers your risk: if he goes down, you keep the production. Holding another team’s backup raises your ceiling: if that starter goes down, you gain a starting running back you did not have. With a short bench, the second kind of stash usually does more for your team, because it adds points instead of only protecting them.

The case for handcuffing your own back is strongest when the succession is clear, the job is valuable, and you have the bench space. It is weakest in a committee backfield, where your starter’s absence would not make anyone a reliable play.

When a handcuff is a wasted roster spot

A bench spot has a cost. A handcuff is a poor use of it when you need that spot to cover bye weeks, when the backup would only inherit a share of a weak job, or when your league has so few bench slots that every one has to produce now. Stash value and start value are different things: do not start a handcuff because his score is high. His appeal depends on something that has not happened.

One way to lower that cost is to stop holding the same backup all season and rotate a single bench slot through the best available stash in each game window. The rotating bench slot strategy explains how.