View Single Post
Old 02-21-2017, 07:56 PM   #2058
sureLoss
Some kinda newsbreaker!
 
sureLoss's Avatar
 
Join Date: May 2004
Location: Learning Phaneufs skating style
Exp:
Default

Here is a better explanation:
http://www.broadstreethockey.com/201...ve-is-not-good
Quote:
Everyone knows Chris Pronger is never going to play again, so the Flyers have been, and will continue to rely on LTIR to get the cap relief they need to replace him. However, many fans mistakenly think LTIR just makes the cap hit disappear; or at worst, that it allows the team to exceed the ceiling, for effectively the same result.

That's not the case. When it comes down to it LTIR is bad. It has negative ramifications and if you don't have to use it, you shouldn't.

For the sake of keeping this piece short and sweet, I'll keep the discussion at a really high level. The salary cap is calculated on a daily basis, not a yearly basis. It's almost as if, every day the Flyers are given a chunk of money to use to pay their players for that day. If they don't use it all, they can pocket the difference, and use it later.

The simplest example of this is to think about it from a yearly cap space perspective. If you have $1 million in cap space. Once you are 50% of the way through the season, you can acquire a $2 million player. You can afford their $2 million daily cap hit because you only have to pay it for 50% of the season, and you've been saving up a little bit of a time for that first half of the season.

The Flyers however, do use all of that daily money. In fact, they use even more. LTIR allows them to spend even more than that daily allowed sum. The difference with LTIR though, is that if a team doesn't use all of their possible LTIR, they don't get to pocket the difference.

The end result is that a team will never be able to have buying power exceeding the cap hit of the player(s) on LTIR. Whereas a team that is truly under the salary cap can get more for their money later in the season.
sureLoss is offline  
The Following 4 Users Say Thank You to sureLoss For This Useful Post: