Strength Of Schedule, Fantasy Football Positional SOS

By on August 24, 2012

2012 fantasy football stength of scheduleStrength of schedule is one of the most overlooked factors in fantasy football. Some people discount its value, but do your homework before you shove such data to the side, it is indeed relevant. In order to calculate SOS we use last years defensive data combined with off season moves to calculate fantasy points allowed for the 2012 season. We then run the numbers together to give you a numerical ranking for each NFL team based on their schedule. We also include SOS side by side our projected fantasy points, draft value (VBD), ADP and bye weeks in our draft guide based on your leagues points settings.

But, as they used to say in Reading Rainbow, “but don’t take my word for it“.

Last year we projected Seattle as having the easiest SOS at running back. Marshawn Lynch went on to have the best year of his career, posting 1204 rushing yards and 12 rushing touchdowns.



We also projected Detroit to have the easiest strength of schedule at QB. Matthew Stafford posted record numbers (for the Lions) in his first full season.

We projected KC to have the easiest WR SOS and Bowe had 1159 receiving yards with 81 catches and 5 TD (could have been 8 if not for his red zone drops), and then Seattle was supposed to have the easiest TE SOS, but they didn’t have a worthy TE to take advantage, or maybe no one told them to read my article last year, HA!

Aaron Rodgers had the 3rd easiest strength of schedule and posted his best passing stats to date.

The Eagles had the third easiest SOS at RB, McCoy posted 17 rushing touch downs and 1309 rushing yards.

I can play the name game for hours, point out how studs abused fantasy stats because they had an easy SOS and mere mortals became “fantasy relevant” because of easy SOS.

Are you still a nonbeliever in Strength of Schedule? 

Looking at the 2012 NFL Season here’s our strength of schedule projections.

The easiest schedule has the lowest number. The hardest schedule has the highest number.

So the number “1″ equals the easiest schedule and a number “32″ equals the hardest schedule. This is the same way we display the data in our customized draft package, except in the draft package the SOS is listed next to each players name, which is very handy when drafting.

Team QB RB WR TE
ARZ 14 30 4 29
ATL 1 1 8 12
BAL 28 19 27 25
BUF 27 23 19 32
CAR 4 6 12 7
CHI 6 18 3 19
CIN 32 27 32 22
CLE 29 20 29 15
DAL 26 8 25 11
DEN 17 9 22 28
DET 13 29 7 17
GB 11 28 6 27
HOU 12 15 15 1
IND 22 26 23 2
JAC 10 17 11 5
KC 9 3 21 14
MIA 24 12 17 16
MIN 15 21 13 8
NE 30 24 26 10
NO 2 2 10 4
NYG 25 16 24 18
NYJ 20 25 14 13
OAK 21 10 30 23
PHI 18 11 20 9
PIT 31 13 31 24
SD 23 4 28 26
SEA 7 22 1 30
SF 5 14 2 21
STL 8 31 9 6
TB 3 5 5 20
TEN 16 32 16 3
WAS 19 7 18 31

Of course you can use SOS for your fantasy football draft to help you make decisions when drafting similar positions. Or you can use it to highlight players now as “targets” for your draft, I like to do both!

Here’s some predictions and notable statements based on the positional strength of schedule listed above.

  • Steven Jackson has the 2nd hardest SOS (#31), which may explain his current ADP.
  • Chris Johnson, whom we feel will have a bounce back year, has the toughest SOS @ 32. Truly elite talent is normally not immensely impacted by tough SOS, but his SOS is worth noting when DeMarco Murray has the 8th easiest and Ryan Mathews..
  • Ryan Mathews has the 4th easiest SOS @ RB, which could help him like it helped McCoy last year.
  • Phillip Rivers has the 23rd hardest SOS
  • Vernon Davis has the 2nd easiest SOS, bounce back year?, I’ll draft him at his current ADP for sure!

 

  • You can get SOS listed next to each players name in our “come back dressing” cheat sheets.

 

 

around the web

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>