Warning: Cannot modify header information - headers already sent by (output started at /home/content/85/8979285/html/wp-includes/post-thumbnail-template.php:1) in /home/content/85/8979285/html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 62
Should you use “stacking” in season-long fantasy leagues? | The DC Times

The DC Times

A New Way to Look at the Cowboys, NFL, and Fantasy Football


Should you use “stacking” in season-long fantasy leagues?

Subscribe to The DC Times
Never miss a post again!

Stacking–pairing your quarterback with one or more of his receivers–is a popular strategy in the world of daily fantasy football. At RotoWire, I examined if you should stack in season-long leagues:

Is pairing your QB with his WR a good idea?

I’ve been playing a whole lot of daily fantasy lately because I think it’s really the wave of the future in the industry. Daily fantasy is all about assessing individual matchups, but a lot of the principles can be applied to season-long leagues. One of those is known as “stacking.”

In the world of daily fantasy sports, stacking is when you pair your quarterback with one or more of his wide receivers (or tight ends). This is done for a few reasons, the most important of which is that it increases your team’s ceiling. When your receiver scores, you get 10 points just for the touchdown (in four-point passing TD leagues). Daily fantasy owners typically stack their teams in tournaments where upside is required. What’s the point of fielding a team that can consistently finish in the top 25 percent, but not better, if you get paid only for a top-10 percent finish?

The downside of stacking is a reduced floor. If your quarterback has a lousy game, chances are your receiver will as well. Thus, the purpose of stacking is to create a dependent relationship in your lineup through which you can increase your team’s ceiling at the expense of possibly tanking in any given week.

Head over there for the full post.

Be Sociable, Share!

Leave a Reply

Your email address will not be published. Required fields are marked *