Reactions about Chris Culliver being cut?

[KI Skins Fan]

Originally Posted by Alvin Walton

Not sure I understand the future dating part.
Maybe they did it to give him more time to find a new team.

It also gives CC and his agent time to look around for a good deal, fail to find it, and then come back to the Redskins for much less money, if that's what both sides decide to do.

[WillH]

Is there another move they are trying to make? What do we need $8mil in cap space for? Maybe they're hoping for a shot at a C, NT, or RB that will be released?

[Schneed10]

Originally Posted by That Guy

he was released with post june 1 per kien (espn blog)

Ah you're right, so it is.

For those wondering how this works, here's the rundown.

When you release a player, you have to recognize any money you paid to him on your cap in the year you released him. In Culliver's case, we paid him a $5M signing bonus up front when he signed him to his 4 year deal. That $5M was to spread evenly to the cap over the course of the 4 years, meaning that each year on the roster the signing bonus was to count $1.25M each season (four seasons x 1.25M = $5M signing bonus).

He played one season for us, meaning we carried the first year's portion of that bonus last year. We still have 3 more years of it that still need to hit our cap books. When we released him, we're forced to carry all the rest of it, which is the remaining $3.75M.

The rules used to be that if you released a player after June 1, you could recognize one year's portion of the signing bonus on your cap this year, and the rest would go on the next year's cap. So if we released him after June 1, we would carry $1.25 on the 2016 cap, and then the remaining $2.5M on the 2017 cap.

But the NFL Players Association thought it was shitty that the player would hit the free agent market on June 1, when most teams had their rosters set. It meant the player wouldn't have much of a market. So they said how about we let you designate players as a post-June 1 release for cap purposes, but you can go ahead and release him now before June 1 so that he can hit the market and try to get the best deal. So they did that.

So Culliver gets released now, but for cap purposes only they treat him as being released after June 1. So the Redskins save his $9.25M salary this year, and carry $1.25M of dead cap money this year, thus freeing $8M in cap space in 2016.

They then will carry $2.5M in dead cap space for him in 2017.

There you have it, clear as mud. I would have preferred they take the full cap hit now, but it's of little consequence in the end.

[Skinzman]

Originally Posted by WillH

Is there another move they are trying to make? What do we need $8mil in cap space for? Maybe they're hoping for a shot at a C, NT, or RB that will be released?

Given that you can carry over any cap excess from year to year, I think this move has a much to do with that than anything. If it looks like he will rarely play, there isnt much reason to have his salary on the books. Given Norman and Breeland will be starters, and they dont want to expose Fuller or Dunbar, its probably better long term to go ahead and do it. Its 8 mil against the cap, and since it can carry over, you make the move even if no other move is planned.

Without cap space being allowed to be carried over, it now makes these moves more common. Prior to that, it was only a question of whether cap space was needed this year. Now its about more than that. I think it also diminshes the pre/post june 1 cuts also. As long as a team is smart with the cap, then saving 8 mil this year for Culliver as opposed to 5.5 mil doesnt matter as much. Carry 2.5 mil over and have 2.5 mil dead cap next year is equal to carrying nothing over and not having 2.5 mil in dead cap next year. It all evens out in the long run (as long as your actions are cap conscious to begin with).

[That Guy]

they probably wanted the space now in case there's someone else to sign (like pierre thomas). you want at least 3m free going into sep 1st for mid season injury signings etc, and we needed to free up some space for the rookies anyways.

[WillH]

Originally Posted by Skinzman

Given that you can carry over any cap excess from year to year, I think this move has a much to do with that than anything. If it looks like he will rarely play, there isnt much reason to have his salary on the books. Given Norman and Breeland will be starters, and they dont want to expose Fuller or Dunbar, its probably better long term to go ahead and do it. Its 8 mil against the cap, and since it can carry over, you make the move even if no other move is planned.

Without cap space being allowed to be carried over, it now makes these moves more common. Prior to that, it was only a question of whether cap space was needed this year. Now its about more than that. I think it also diminshes the pre/post june 1 cuts also. As long as a team is smart with the cap, then saving 8 mil this year for Culliver as opposed to 5.5 mil doesnt matter as much. Carry 2.5 mil over and have 2.5 mil dead cap next year is equal to carrying nothing over and not having 2.5 mil in dead cap next year. It all evens out in the long run (as long as your actions are cap conscious to begin with).

Oh I didn't realize that. Is that a newer rule?

[That Guy]

Originally Posted by WillH

Oh I didn't realize that. Is that a newer rule?

well, as of the last cba, so not that new, but yeah.

[Defensewins]

Originally Posted by WillH

Is there another move they are trying to make? What do we need $8mil in cap space for? Maybe they're hoping for a shot at a C, NT, or RB that will be released?

I believe it is to have flexibility just case another good player becomes available from now to beginning of season. As it always happens. If not then we use it for next year. Rookies need to be signed.

[Chico23231]

Originally Posted by WillH

Is there another move they are trying to make? What do we need $8mil in cap space for? Maybe they're hoping for a shot at a C, NT, or RB that will be released?

I think you are correct. I would strongly suspect another vet addition is coming most likely to the D-line or RB.

I think we are willing to roll with Kory L and Grimace at Center. Spencer Long most likely isn't moving because of his positive play at Guard. Its really ashamed we couldn't get a center because our running game seemed to really suffer from the lack of inside push.

Thomas is a strong candidate for RB, but their are other options out there as well.

[TheMalcolmConnection]

I read somewhere that Scot is planning to use those picks he acquired next year to pick up needs THIS year if someone is available. Wondering if a 4th could pry a decent center from someone. Love that we have those since he can wheel and deal THIS year without worrying about wasting our original picks.

[KI Skins Fan]

Originally Posted by TheMalcolmConnection

I read somewhere that Scot is planning to use those picks he acquired next year to pick up needs THIS year if someone is available. Wondering if a 4th could pry a decent center from someone. Love that we have those since he can wheel and deal THIS year without worrying about wasting our original picks.

Really? Did Scot actually say that? Anyone else know more about this?

[Chico23231]

Originally Posted by KI Skins Fan

Really? Did Scot actually say that? Anyone else know more about this?

McCloughan may use extra 2017 picks to deal for players this year | CSN Mid-Atlantic

[Schneed10]

At the risk of fanning the flames of unfounded internet rumors...

Kam!

[DesertHog]

The Guy was always hurt and the Skins need the money for Josh. Im ok with and not surprised

[Evilgrin]

2nd ACL tear.... Who else had 2 and looked really bad, also at a young age