Redskins

Quick Links

Need to Know: How much cap space do the Redskins need to sign their draft picks?

screenshot-2015-03-17-05-52-16.png

Need to Know: How much cap space do the Redskins need to sign their draft picks?

Here is what you need to know on this Tuesday, March 17, 44 days before the Washington Redskins go on the clock at the NFL draft.

Question of the day

A few days a week I’ll give an in-depth answer to a question submitted by a fan on my Twitter feed, via the Real Redskins Facebook page, or in the comments section here. On Twitter address the questions to me at @Rich_TandlerCSN with the #NTK hashtag. There will be a comment thread set up on the Facebook page and if you’re asking your question here, put “for NTK” at the start of the comment.

Today’s question is from the Real Redskins Facebook page:

As we discussed here yesterday, the Redskins had $11.73 million in salary cap space. That was before they signed safety Jeron Johnson. We don’t have the details on that deal yet (reported to the for two years and $4 million) so we don’t know what the 2015 cap hit will be. But we can estimate they have about $10.5 million left and be close enough for our purposes here.

The Redskins will need a chunk of that money to pay their draft picks. As of now, they have seven picks, their own selection in each round. Thanks to the rookie slotting system that came into effect with the current CBA in 2011, the 2015 cap hit for each those draft picks can be determined now.

Washington has the fifth overall pick in the draft. That player, regardless of what position he plays or what he may have accomplished in college, will get a contract with a 2015 salary cap hit of $3.41 million per Over the Cap. Here are the hits for the Redskins other picks, rounded to the nearest $1,000.

Round-Cap hit

2-$970,000
3-$606,000
4-$554,000
5-$487,000
6-$464,000
7-$451,000

The total cap hits for rounds one through seven comes to $6.943 million. At first glance, if you subtract that from the $10.5 million they currently have it looks like the Redskins are getting very low on cash to spend.

But you don’t subtract nearly that much from the remaining cap space due to the Rule of 51. That rule applies during the offseason, from the start of the league year in March until Week 1 of the regular season. Teams have to be under the NFL salary cap of $143.28 million during that time, but since they can carry up to 90 players on the roster they can’t count everyone towards the cap. So the rule is that only the top 51 cap hits on the roster count towards cap during the offseason.

That means that when you add a player into the top 51 you drop the player with the lowest cap hit. So when the Redskins sign their first-round draft pick, Phillip Thomas, who has a cap hit of $510,000, will drop out of the top 51, so you subtract his money from the cap. So that $3.41 million deal counts a net of just $2.9 million.

It happens that the Redskins have a bunch of players with cap hits of $510,000, which is the third-year minimum salary, so when you knock Thomas off of the list of 51, he’s replaced in 51st place by another player making the same amount. So when you sign picks from rounds two, three, and four, you add their cap hits but you take off someone making $510,000 when you do. In all, picks 1-4 have total cap hits of $5.54 million. But with the Rule of 51 the net effect is a subtraction of $3.5 million from available cap space.

And since the picks in rounds five, six, and seven make less than $510,000 they don’t even count against the cap for the time being. So you wind up with a net cap hit of $3.5 million for the draft class of 2015.

As Keith noted in his questions, this could change with a draft trade but trades of picks for picks in the same draft don’t usually have a major effect on the cap consequences. The Redskins can figure on accounting for about $3.5 million in cap space for the draft regardless of how much wheeling and dealing Scot McCloughan may do.

Timeline

—It’s been 79 days since the Redskins played a game. It will be about 180 days until they play another one.

Days until: Redskins offseason workouts start 34; 2015 NFL Draft 44; Redskins training camp starts 135

If you have any questions about what's going on at Redskins Park, hit me up in the comments. And I'm always on Twitter @Rich_TandlerCSN.

Like Real Redskins on Facebook!

Follow Real Redskins on Instagram @RichTandler

In case you missed it

Quick Links

Kirk Cousins breaks down the terribleness of FedEx Field grass

usatsi_10433251.jpg

Kirk Cousins breaks down the terribleness of FedEx Field grass

For years, the Redskins struggle with their home field as the fall turns to winter. It's been happening so long it's become an expected passing of the seasons, like the transition from Halloween jack-o-lanterns to Christmas lights dotting people's front yards. 

Well, on Thanksgiving night, the turf at FedEx Field again showed how bad it can be. On a second half interception returned for a New York Giants touchdown, replay showed that Kirk Cousins' foot got stuck on the dirt, and it played a role in his sailing a ball to the sideline. The bad turf was not the only reason for the interception, but it was definitely a reason. 

Beyond the pick, the field was just ugly. Twitter blew up making fun of the Redskins home grass, and the national broadcast showed just how unsightly the long brown patch between the hash marks looked. 

On Friday, the normally diplomatic Cousins opened up about the grass.

"It probably doesn't look like a professional NFL field should," the quarterback said on 106.7 the Fan (full audio here). "If you think the field is rough now on Thanksgiving, we've got two more home games in mid-to-late December. That's probably going to be a bigger challenge."

Asked about the field's impact on the interception on Thursday night, Cousins ignored it. But plenty of other players have suggested the field is a known problem in the second half, and something they just must deal with. 

"I don't know why it is that way or what causes it," Cousins said. "I've kind of learned to accept it and understand it's part of the deal. Playing here on the field has never been that great in the second half of the season for whatever the reason."

[h/t @BenStandig for the Cousins quotes]

Want more Redskins? Click here to follow JP on Facebook and check out @JPFinlayNBCS for live updates via Twitter! Click here for the #RedskinsTalk on Apple Podcastshere for Google Play or press play below. Don't forget to subscribe!

 

 

Quick Links

When Samaje Perine got going, so did the Redskins' offense

perine_vs_nyg_youngentob.jpg
Bob Youngentob for NBC Sports Washington

When Samaje Perine got going, so did the Redskins' offense

At halftime of the Redskins’ Thanksgiving night game against the Giants, Samaje Perine had three yards rushing and his team had three points. Washington had racked up all of 113 yards.

Coincidence? Not entirely. Although the Redskins are primarily a passing team they need to run the ball to pass effectively.

“We had to get the running game going,” said Jay Gruden after the game.

In the second half, Perine and the offense did get it going. Perine ran for 97 yards and Redskins put up 210 yards and 17 points. It’s safe to say that it wasn’t a coincidence.

The Redskins didn’t make any halftime adjustments to get the ground game in gear.

“We just had to stay the course,” said Perine. “We knew they were going to come out fired up, they just came off a big win. We just had to stay the course and then things started going our way.”

MORE REDSKINS: MUST-SEE PHOTOS OF THE WIN

Perine was more steady than spectacular. His longest run was 16 yards. He came out of the locker room and ran for six and 10 yards on his first two carries. Later in the third quarter the Redskins were backed up at their own 10. Perine ran four straight plays for 39 yards and the Redskins were near midfield.

Although they didn’t score on that drive they did change field position. That was part of the Redskins’ strategy playing with an injury-depleted offense.

“If you had to punt in a game like this and play field position, it’s not the end of the world because our defense was playing so good,” said Gruden.

Not only did the running game flip the field, it flipped the time of possession. In the first half, the Giants had the ball for 17:40 compared to 12:20 for the Redskins.

“We had to get on the field and control some of the clock,” said tackle Morgan Moses. “We had to give our defense a rest. Samaje put his foot in the ground and got extra yards when needed and we were able to move the chains.”

Moses wasn’t the only one enjoying seeing Perine pile up some yards.

“As a defensive player, you want to see that,” said safety D.J. Swearinger. “We say, keep running it. Keep running him. Let him keep getting those carries, put a dent in the defense. It was a good sight to see.”

RELATED: FIVE KEY MOMENTS IN RESKINS VS GIANTS

Swearinger got to watch a lot of Perine. The Redskins piled up 22:17 in possession in the second half, while Swearinger and his defensive mates had to defend for just 7:43.

Last night was the second time in four days that Perine has rushed for 100 yards or more; he had 117 in New Orleans on Sunday. No Redskin has rushed for 100 yards in consecutive games since Alfred Morris did it in November of 2013.

He will have a chance to extend that streak to three on Thursday against the Cowboys, who are ranked 17th in rushing defense. That would put him in some elite company in Redskins history, including Larry Brown (twice) and Stephen Davis.  A steak of three straight 100-yard games was last done by Morris in 2012.

It may be a little early to look forward, but the Redskins record is five straight 100-yard games, held by Clinton Portis (twice) and Ladell Betts.  

Stay up to date on the Redskins. Rich Tandler covers the team 365 days a year. Like his Facebook page Facebook.com/TandlerNBCS and follow him on Twitter @TandlerNBCS.