Does It Make Sense To Sign Jordan McRae Now?

Jordan McRae tweeted last night that he was leaving Australia and on his way home.

Does that mean he’s on his way to Philadelphia to play for the Sixers? Not necessarily.

McRae’s team, Melbourne United, had their season end on February 22nd as they failed to reach the playoffs. McRae could, literally, be headed home now that his season is over.

The Sixers could attempt to sign McRae now and have him play for the remainder of the season, something the team has indicated before could be an option. But would it make sense?

The natural reaction is not to lose a year of team control for only a few months of playing time, and it’s one that makes sense. Sam Hinkie has shown a desire to get young players under a cheap contract for as many years as possible, usually with team options or non-guaranteed years in the latter half of the contract.

The Sixers, since they are under the salary cap, are free to offer McRae any contract they desire with that cap space. They are, however, limited to a maixmum of 4 years, as the only way to sign a player to a 5-year deal is if you have bird rights, which the Sixers do not with McRae.

If the Sixers sign McRae to a contract now, they will essentially lose over a half a season of control. Is that a factor in Sam Hinkie’s decision on what to do with McRae now? Absolutely. In fact, it might just prevent them from signing the scorer out of Tennessee.

But there’s another factor.

That other factor is evaluation. The one reason I could see Sam Hinkie and the Sixers giving up a year of salary control is if they feel like now is an opportunity to evaluate McRae. With the Sixers in a unique position where they don’t really care about wins and losses and have minutes available for young players, Hinkie might want to maximize McRae’s availability during this period.

This phase of the Sixers rebuild is likely to extend through the 2015-16 season, but an extra couple of months to evaluate McRae in an environment where he can play early on in his career might be more important than that extra year of control. The odds of a 58th pick in the draft sticking with a team for 4 years is, after all, low, and prioritizing that 4th year of control over even just a few months of player evaluation might be putting the cart before the horse.

The available minutes are not quite what they used to be, with Hollis Thompson and Jason Richardson having worked their way back from injury. And the roster cuts are getting tougher and tougher to make, especially if you’re under the assumption that the Sixers are desirous to give recently acquired Thomas Robinson a look, that they want to give Furkan Aldemir an offseason to get into the shape that Brett Brown wants, and that the lack of point guard depth would keep Ish Smith, or a replacement point guard, taking up a roster spot.

Sam Hinkie might very well keep McRae off the roster for the remainder of the season and maximize how long they can keep him under control. I just wouldn’t say that’s the only consideration, either.

Sixers Draft Pick Tracker – February 25th, 2015

Only a few games last night, but some big impact on the Sixers ability to get the OKC pick.

Sixers pick (Currently slotted 2nd):

  • No changes here, as the Sixers were idle, as were New York, Minnesota, Lakers, and Orlando. Sixers still have the 2nd worst record, 1.5 games behind New York for the worst record, and 0.5 up on Minnesota, 2.5 up on the Lakers, and 6 up on Orlando, who have won 3 in a row.

Lakers pick (top 5 protected, currently 4th):

  • Once again, no real action here. Detroit and Indy both lost, which there’s 8.5 games of separation between them and the Lakers, so no real games of consequence.

Miami’s pick (top 10 protected, currently 16th):

  • Detroit lost (bad?): I keep going back and forth on whether I want Indy and Detroit to lose. Again, all 4 of Charlotte, Indy, Detroit, and Brooklyn passing Miami would be bad, but 3 out of 4 of them passing Miami would be great. I’m counting on Indiana and Detroit to pass Miami. It’s a bit of a gamble, but I’m willing to gamble on that pick to get it as close to the top 10 as possible.
  • Indy lost (bad?): Same situation as Detroit. In fact, Indiana and Detroit are both tied at 23-33, 2 games behind Miami. You kind of don’t want Miami to fall off of a cliff, as the more they struggle, the more chance that even more teams, such as Utah (21-34), and Boston (21-33) come into play. So Indy and Detroit winning, and Miami playing slightly below average ball, is probably the best hope here.

Thunder’s pick (top 18 protected, currently 18th):

  • OKC won (good): Oklahoma City beat Indiana. They’ve now won 7 in a row and 9 of their last 10, even as Durant continues to miss time.
  • Washington lost (good): Tough draw for Washington, as they played Golden State tough for most of the game, but the loss, combined with OKC’s win, pulls OKC to within a game of the 19th slot, and thus conveying the pick to the Sixers.

Tonight’s games:

  • Sixers @ Milwaukee: Big not only for the Sixers positioning, but for the OKC positioning as well, as the Thunder are 0.5 games ahead of Milwaukee for the 18th spot. It’s kind of a win-win, but the Sixers pick is more important than the OKC pick.
  • Miami @ Orlando: I suppose you want to root for Orlando to win, although if they do, their ability to remain out of the top 10 concerns me a little bit.  Orlando has won 3 in a row.
  • Knicks @ Boston: Boston’s in that 8-10 range where they’re really not in play to impact anything, unless Boston really goes on a run or Miami really goes on a slide. But the Knicks winning would not only help the Sixers pick, but also help the Heat pick, pushing the Celtics one game further away from Miami.
  • Brooklyn @ New Orleans: Brooklyn is at 15th, 0.5 games from Miami. At this point, I’m hoping Brooklyn wins and passes Miami.
  • Charlotte @ Chicago: Charlotte is the team I’m kind of counting on to falter down the stretch and *not* pass Miami, thus preventing Miami from falling to #10, and giving the Sixers a 97%+ chance of keeping that pick.
  • Washington @ Minnesota: Minnesota winning here could help the Sixers in two ways: it could put some space between Minnesota and the Sixers in the race for that #2 slot, and it could help push Washington away from that 19th spot, and thus help the OKC pick convey.
  • Lakers @ Utah: A Lakers win would be huge, not only to increase the (slight) chance the Lakers pick can fall outside of the top 5, but also to put some space between the Lakers and Sixers in a race for a top pick. This is a game you’d typically think the Lakers would have a chance, but the Jazz are coming off wins against the Spurs and Blazers in their last two games.
  • Memphis @ Sacramento: Sacramento (and Orlando) are the teams the Lakers would have to pass in order to fall out of a top 5 slot. Odds are really low, but they’re there.

Sixers Draft Pick Tracker – February 24th, 2015

Following up on last night’s NBA action and how that impacts the Sixers upcoming draft picks:

Sixers pick (currently slotted 2nd):

  • Sixers lost to Miami (good): I’m putting this one in the good category, because the value of the Sixers likely top-5 pick is more important than Heat’s pick. Even beyond that, the Heat putting some distance between themselves and Charlotte (10th slot, now 1.5 games up of Miami in the lottery standings) isn’t the worst thing in the world. The loss pulls the Sixers to within 1.5 games of the Knicks for the worst record in the league, and puts them 2.5 up on the Lakers (4th) and 5.5 up on the Magic (5th). Not a whole lot happened in terms of the teams around the Sixers, however, as New York, Minnesota, Lakers, and Orlando were all inactive.

Lakers pick (top 5 protected. Currently slotted 4th):

  • Nothing really to report here, outside of the Sixers win. NYK, Min, LAL, and Orlando were all inactive.

Heat’s pick (top 10 protected. Currently 16th):

  • Heat won (bad / kinda): The Heat won, which could be either good or bad, depending on your viewpoint. The Heat can have 3 out of Charlotte, Detroit, Indy, and Brooklyn pass them. All 4 passing them and the odds are the Heat keep their pick. 3 out of 4 pass them and the Sixers have very good odds of ending up with the 11th pick. Charlotte, Detroit, and Indy are now in a virtual tie at 22-32, 23-33, and 23-33, respectively, putting them all 1.5 games up on Miami.
  • Brooklyn beat Denver (bad / kinda): Brooklyn beat the Nuggets 110-82, with newcomer Thad Young scoring 15. This is good in that 3 out of 4 of the aforementioned teams need to pass Miami, but bad in that I think Brooklyn is one of the teams more likely (along with Charlotte) to falter. The Denver loss pulls the Nuggets to within 5.5 games of the Lakers. The Nuggets are bad, but so are the Lakers, and that’s a ton of ground to make up in 26 games.

Thunder’s pick (top 18 protected. Currently 18th):

  • Milwaukee lost (good): Milwaukee’s 87-71 loss to Chicago, their 2nd straight defeat, puts them in a tie with Oklahoma City, bumping OKC to the 18th slot, the last slot where they would keep their pick. All that’s left would be OKC passing Washington (2 games between the two) in order for the Thunder to convey the pick to the Sixers. In theory, you would prefer the Bulls to lose, as they’re currently slotted 22nd and are in theory a team that the Thunder could pass for that 19th spot, but with Milwaukee also being a team that OKC has to pass, it’s more important for Milwaukee to lose than for Chicago to do so.
  •  San Antonio lost (good): If the Sixers get the OKC pick, the odds point to OKC passing Washington for the 19th slot. However, after the Spurs surprising 90-81 loss to the Jazz, the Thunder are only 3 games behind the Spurs.
  • Los Angeles Clips lost (good): Again, a team the Thunder have an outside shot of passing, as the Clips are 37-20, 5.5 games up on OKC and in the 23rd slot. Extreme far shot, but any time one of those teams gets closer to OKC, it just increases the number of ways the end of the season can shake out with the Sixers getting the pick. That being said, the goal is for the Thunder to ultimately *just* pass one of Washington, San Antonio, Cleveland, Chicago, or LAC, not all of them. So eventually these “long shots” getting closer become a negative.

Tonight’s games:

  • Golden State @ Washington: The Thunder are 2 games behind the Wizards for the 19th slot and conveying their pick to the Sixers.
  • Pacers @ Thunder: ^– Same as above. An OKC win and a Wiz loss and the Thunder could be within a game of #19. That being said, the Pacers losing would push them further away from Miami for a conveyable lotto pick. This game is really a win-win.
  • Cleveland @ Detroit: Impacts the Miami pick. At this point, I think you’re hoping for Detroit to win and pass Miami, pushing the Heat pick closer to the coveted #11 draft slot, although there’s obvious risk in doing so should all 4 of the EC teams between 10 and 15 pass the Heat.

Sixers Draft Pick Tracker – February 23rd, 2015

The Sixers have picks — a lot of picks. The Sixers could have a total of 4 1st round draft picks in the 2015 NBA draft, if losses and ping pong balls go their way. 3 of them, however are protected: the Sixers will only get the Lakers 1st round pick this year if it falls outside of the top 5, they will get the Heat pick as long as it doesn’t fall in the top 10, and will get Oklahoma City’s pick if it’s 19+.

So, I will use this space here to track the status of these picks, and how the games from the previous night impact the Sixers upcoming draft picks.

The Sixers own draft pick:

  • Sixers lost (good): The Sixers losing to the Magic last night was key, at least for their own draft pick. Orlando, who currently has the 5th worst record at 19-39, is 3.5 games ahead of the Lakers and 5.5 games ahead of the Sixers. The Lakers catching the Magic is an extreme long shot, so the Sixers getting one more game towards locking themselves into a top-4 lottery positioning was big. The loss also puts the Sixers a half-game up on idle Minnesota for the 2nd most ping pong balls, and 2 games behind New York, who lost to the Cavs.
  • Knicks lost (bad): The Knicks predictably lost to the Cavs, 101-83. The loss extends the Knicks losing streak to 7 games, and puts them 2 games “up” on the Sixers and 2.5 games up on Minnesota. They have to be the frontrunners for the worst record, at this point.

The Lakers pick (top 5 protected):

  • The Lakers won (good): The Lakers beat the Celtics in overtime, which keeps them 3.5 games behind the Magic for the 5h slot and 5.5 behind Sacramento for 6th. The Sixers would have a ~17% chance of getting the pick if the Lakers finish with the 4th worst record, which is about as good as the Sixers chances could realistically hope for. More likely, however, is the Lakers finishing with the 2nd or 3rd worst record, and any Lakers win to prevent that from happening and put more space between the Sixers and the Lakers is a good thing. The Lakers are currently 2 games up on the Sixers, and with how poorly the Lakers had been playing of late, that win last night was big.

The Miami Heat’s Draft Pick (top 10 protected):

  • Charlotte lost to Dallas (good): The Heat currently sit at 23-31, in the Eastern Conference playoffs and currently slated to draft 16th. They can miss the playoffs and still (be likely to) convey the pick, as Indiana (11th), Detroit (12th), and Brooklyn (15th) can all pass the Heat and the Sixers still have a 97% chance of keeping the pick. The problem comes in if 4 Eastern Conference teams pass the Heat, and with the Bobcats sitting at the 10th slot at 22-32, only a game worse than Miami, there are a lot of teams really bunched up. Indy and Detroit are playing pretty good basketball of late, at 7-3 and 6-4 in their last 10, respectively. With Bosh out for the rest of the year, them passing Miami has a decent chance of happening, so the Sixers need one of Charlotte or Brooklyn to stumble. The Hornets on a 5 game losing streak could be big for the Sixers.
  • Indiana won (unknown): I’m listing this as unknown because it could be either really good or really bad. As I mentioned, if the 3 out of 4 of Charlotte, Indiana, Detroit, and Brooklyn pass Miami, the Sixers could have a very good chance of getting the 11th pick. If all 4 of them pass Miami, that could be bad for the Sixers. My hunch says Indy passes the Heat eventually, so this is a positive. But it would be nice if one of those 4 teams could fall back and put some separation between them and Miami.
  • Detroit won (unknown): A surprising win by Detroit over Washington. Detroit is 6-4 in their last 10 and continues their strong play of late. Their situation is the same as Indy above: could be really good if 3 out of 4 pass Miami, really bad if all 4 do.

Oklahoma City pick (top 18 protected):

  • Oklahoma City won (good): Oklahoma City, without Kevin Durant, beat a pretty bad Denver team. The win wasn’t all that surprising, but the play of newcomer Enes Kanter was a positive sign. Kanter dropped 20 points, 12 rebounds, and 3 assists for the Thunder’s balanced attack, which also included 20 points from Ibaka, 21 points, 17 assists, and 8 rebounds from Westbrook, and 17 points from Dion Waiters off the bench. The win pushes Oklahoma City to 31-25, only a half game behind Milwaukee for the 18th spot, and only 2 games behind Washington for the 19th spot with 26 games left to play. As long as Kevin Durant isn’t out too long, I think there’s a far better chance that the Oklahoma City pick conveys than the 30% chance Sam Hinkie gave at the deadline. The Thunder have won 6 straight and are rolling.
  • Milwaukee lost (good): Milwaukee lost to Atlanta, which is good. This was one of those losses, between them playing Atlanta and MCW not playing yet, that you kind of figured would happen. However, with their loss and OKC’s win. that puts OKC ever-so-closer to conveying that pick. The Sixers would *really* prefer to get the pick this year, as the 19th or 20th pick would be much better than the expected 27th-or-so pick OKC will convey if they’re healthy for a full season.
  • Washington lost (good): Again, the Wizards losing to the Pistons was good for 2 reasons: it puts the Pistons closer to passing the Heat (which could be either good or bad, depending on what Charlotte, Indy, and Brooklyn do as well), and also puts the Wizards one game closer to the Thunder. Washington is a good team, so the Sixers could use every Wizards loss they can get.
  • Cleveland won (bad): The Cleveland win puts them at 35-22, a full 3.5 games ahead of the Thunder for the 20th slot. After Milwaukee and Washington, OKC starts chasing some very good teams, including Cleveland, San Antonio, Portland, and Dallas, which puts even more pressure on OKC catching Washington. I don’t expect OKC to be able to catch Cleveland, but this win is still not good for the Sixers chances.

Dario Saric’s Contract Situation

Just days before the 2014 NBA Draft, Chad Ford reported that Dario Saric had signed a three-year contract with Turkish club Anadolu Efes, where he will join former NBA players such as Zoran Planinic and Nenad Krstic.

The contract, while for a total of three years, includes an out after two years (frequently cited as a “2+1″ contract), should Saric wish to come over to the NBA then. Saric did say (in very broken English) at both Media Day and on Draft night that he would come over after 2 seasons.

“I will come to the NBA for sure, 100 percent in two years and that’s all.” — Dario Saric

Continue reading

Arriving at the Minimum Team Salary – A look at the NBA’s CBA

A few people have asked me about the loophole in the minimum salary calculation that I described the other day. The main point of contention has been an article from Mark Deeks of ShamSports where he states that team payroll, not team salary, is used when determining whether a team has reached the salary floor.

“when calculating a team’s proximity to the minimum salary threshold, it is payroll that is used, not team salary. “

I want to get this out of the way: I think Mark Deeks is a tremendous writer, and I have a ton of respect for him. In terms of authorities (who comment publicly) on the salary cap, he is right up there with Larry Coon in terms of go-to resources.

That being said, I think that he is wrong in this instance.

First, I will refer to Larry Coon’s FAQ, which is just a treasure trove of information for us lay-people, as he does a great (and thorough) job of translating the legalize in the Collective Bargaining Agreement to human-consumable terminology.

In question #15 of his FAQ, Coon describes the condition for when a team is penalized for not reaching the salary cap floor as:

“Teams with a team salary below the minimum are surcharged for their shortfall, with the money distributed among the players on that team.”

Team salary there is the key word, as that is a term that has a strict definition.

Moving back to question #14 in his FAQ, which goes into what is included in team salary, we have:

“The full season salary of any players the team acquires in midseason trades.”

So, that seems pretty cut and dry: the league uses team salary when determining whether a team has reached the salary cap floor, and a players full season salary is included in that calculation, not how much a team actually pays that player.

Still, to be safe I like to go back and take a look at the actual Collective Bargaining Agreement when I can. The NBA and NBPA do a great job of making the CBA publicly available, if you have the time and patience to wade through the nearly-400 page document.

In the CBA (Article I), the minimum salary is defined as:

(jj)
“Minimum Team Salary” means the minimum Team Salary a Team must have for a Salary Cap Year as determined in accordance with Article VII, Section 2(b)

The fact that Team Salary is a proper noun in this instance is important, as it generally indicates that there is a relatively strict definition in place.

As such, the CBA also defines Team Salary in Article I:

(nnn)
“Team Salary” means, with respect to a Salary Cap Year, the sum of all Salaries attributable to a Team’s active and former players plus other amounts as computed in accordance with Article VII, less applicable credit amounts as computed in accordance with Article VII.

This more or less solves the debate, as it establishes that Team Salary, not payroll, is used in the determination of a teams position with regards to the Minimum Team Salary. Still, let’s take a look at what the CBA says with regards to acquired players (Article VII Section 2):

“(c)
Assigned Contracts.
For purposes of calculating Team Salary, with respect to any Player Contract that is assigned, the assignee Team shall, upon assignment, have included in its Team Salary the entire Salary for the then-current Salary Cap Year and for all future Salary Cap Years”

(The CBA refers to players who have been traded as having been “assigned to another team”).

It is the above information that I used to arrive at the conclusion that Team Salary is used when determining whether or not a team has reached the minimum salary, and that a players full season salary is used when calculating Team Salary.

Resources:

Update – November 13th, 2014

The rule was changed during the latest iteration of the Collective Bargaining Agreement, which came out in late 2011. Before that, team payroll was used. After that, total team salary was used. That explains the discrepancy, as Deeks likely simply forgot that the rule was changed.

How the Sixers did — and didn’t — turn a profit last year

thabeet

It has been known for quite some time now that the Sixers, despite finishing the season 29th out of 30 NBA teams in attendance, turned a profit last year.

This has led some to speculate that they did so by gaming the system by just barely meeting the league’s minimum salary requirements, then turning a profit on the backs of the league’s revenue sharing program.

Last year the NBA was projected to redistribute over $231 million to its needy teams through their revenue sharing program, a huge jump from the $40 million or so that was distributed under the previous CBA, which came entirely from luxury tax payments. Two teams were scheduled to receive in excess of $20 million each to help them remain competitive financially, with an additional 5 teams scheduled to receive $17 million each.

Except, the Sixers weren’t one of these 7 teams. In fact, the Sixers are not eligible to receive one cent from the league’s revenue sharing program, a fact first reported by Zach Lowe of Grantland, and one that John Gonzalez followed up on.

The exact details of who is eligible for revenue sharing are clarified by Larry Coon, where he states that teams with more than 2.5 million TV households cannot receive a revenue sharing payment.

This list, according to the Nielsen group, would include teams in the New York, Los Angeles, Chicago, Philadelphia, Dallas, and San Francisco media markets.

Beyond that, since teams contribute to the revenue sharing pool an amount equal to a percentage of their revenue, the league actually makes teams accountable for hitting revenue benchmarks based on market size. If a team falls short on revenue they have to make up that difference. While I don’t have the exact figures of the Sixers revenue sharing contribution, it stands to reason that the Sixers didn’t hit their revenue benchmarks, and thus ended up sending a higher percentage of their revenue towards the league’s revenue sharing program than they normally would have, while getting nothing back from it.

In short, the Sixers did not turn a profit based on the league’s revenue sharing program.

(Note: All teams do, however, receive roughly $31 million per season as part of the league’s national television deal, which is an 8 year, $7.5 billion deal between the NBA and ESPN/Turner that expires after the 2015-16 NBA season. The national TV deal is separate from the revenue sharing program, and all teams, regardless of market size, receive a portion of this. The value of the next national TV deal could increase substantially.)

Salary cap floor

The salary cap floor is a  topic that comes up frequently in Sixersland.

The league mandates that each team must spend 90% of the salary cap towards player salaries. With a salary cap set at $63.065 million for the 2014-15 season, that means a team must pay at least $56.759 million in team salary for the season.

With the Sixers currently at just around $32 million in committed salary, that sounds like a potential issue.

Except it’s really not. The “penalty” for not hitting the salary floor is virtually non-existent, as the Sixers would just have to distribute the amount they’re under the floor to the players on roster. So, should the Sixers be $20 million under the floor at the end of the season, the players on roster will get a significant bonus.

The goal of the floor, and of the penalty, is that teams will essentially pay a fixed minimum amount to players, even if team salary falls below there.

But there is a loophole.

First, the teams salary is calculated at the end of the season. The team being below the salary cap floor at any point before then is irrelevant.

Second, team salaries are calculated based off of the full season salary of all players on the roster at the end of the season, even if that player was acquired during the season.

So, let’s say the Sixers acquire, oh, I don’t know, Danny Granger and his $13 million salary at the NBA’s trade deadline, and that salary brings them over the salary cap floor. Granger’s impact on team salary would be $13 million, even though the amount that they have to pay him is based on the amount of time he’s with the team (or, in this case, amount of games after he was waived), or roughly 1/3 of the season. So Granger’s cap hit would be $13 million, but the Sixers would only be on the hook to pay for roughly $4.3 million of that.

In theory, this discrepancy between how much Granger counted towards the Sixers end-of-year salary calculation and how much the team actually paid him could be considered a loophole to save money, although with how many lawyers looked over the NBA’s CBA, it’s hard for me to believe that this wasn’t a scenario they predicted would happen, and something that was intentional and accounted for.

Still, the longer the team goes into the season with upwards of $24 million between them and the salary floor, the potential cost savings grow. With the offseason virtually wrapped up there doesn’t seem like there will be all that many opportunities to add gobs of salary until the trade deadline, where a situation could present itself where a roughly $8 million expenditure could prevent the team from spending $24 million in salary floor penalty.

Now, is turning a profit why the Sixers aren’t using their salary cap space? I’m not sure I believe that. I think Sam Hinkie values salary cap flexibility immensely. I think that he wants to keep himself in a position where he can pounce on an opportunity if one presents itself, and the deals that have been presented to the Sixers thus far have simply not been worth giving up that flexibility for, in his mind. I think that this inability to find many opportunities has largely been influenced by the rising salary cap (which increased by over $4.3 million this summer) along with teams decreasing willingness to part with quality first round picks.

I also think that Sam Hinkie is not likely to make moves that add long term salary yet, thus limiting the amount of moves that he could make with that cap space. I think the Sixers brass realizes that, as the team is not yet a destination, luring players is going to be a difficult proposition. Using that cap space on stars is not feasible, and in order to use it to acquire complementary pieces they’re likely going to have to considerably overpay for their services. And they don’t want to start that process until they know what superstars those players are going to be complementing.

So, I think that at this point the salary cap flexibility is going to be largely kept in Sam Hinkie’s back pocket, used to facilitate deals by taking on short term contracts, while gaining relatively small assets in return.

Now, if the team is sitting at the trade deadline and no opportunity to acquire assets has presented itself, might they then look to take on enough salary to reach the salary cap floor rather than pay out the difference to their players, thus spending, in essence, $8 million rather than $24 million? This is when I believe the salary cap floor becomes relevant. But I do believe the Sixers lack of moves at this point in the offseason is because an opportunity hasn’t presented itself that is good enough to lose cap flexibility, rather than a desire to maximize their savings potential by using this loophole in the salary cap floor and team salary calculations.

(If you’re interested in the parts of the CBA that make this possible, I took a look at that here).

The signing of Joel Embiid

Earlier this week, Joel Embiid announced that he had signed his rookie contract.

My initial reaction was one of surprise, as it came almost a full month earlier than when Michael Carter-Williams and Nerlens Noel signed during last years offseason.

Why the surprise? It has to do with the salary cap.

For 1st round draft picks, the NBA has a set rookie scale, which basically slots what an incoming rookie can earn during his rookie contract based on where he was drafted. Teams and players have a little wiggle room — 20% above or below the rookie scale — but, in practice, virtually every 1st round draft pick signs for 120% of the rookie scale. For the 3rd overall pick in the 2014 NBA Draft, the NBA has slotted a first year salary of $3,689,700.

However, before a rookie signs his contract the amount he counts against a teams salary cap is 100% of the rookie scale contract. So, before signing a contract, Joel Embiid would count $3,689,700 against the Sixers salary cap. After signing the contract, assuming the Sixers gave Embiid the customary 120% of the rookie scale, his cap hit would rise to $4,427,640.

In essence, the Sixers gain an additional $734k in salary cap space by delaying the signing of Joel Embiid.

Now, the Sixers have roughly $30 million in salary cap space, so adding another $734k might seem inconsequential. And it most likely will turn out to be so. But, for a general manager like Sam Hinkie to give up *any* flexibility, even if there’s almost no chance of it being used, without getting anything in return, came as a surprise.

And there really isn’t anything to be gained by signing Embiid now vs signing him in late September. NBA players do not begin receiving pay checks until November 15th, so it’s not costing Embiid anything at the moment. It’s not that Sam Hinkie used up $734k of the Sixers cap space that surprised me, it’s that he did it when there was no real reason to do so.

It turns out, my initial suspicions were correct.

Bob Cooney wrote that the team isn’t ready to announce Embiid’s signing yet, and a source confirmed to me that the Sixers have yet to put their name on the dotted line. The contract will not be filed with the league (and, thus, not increase the Sixers salary cap commitment) until both parties have signed.

The reason the contract is not yet official? Likely that previously mentioned $734k in additional cap space. I would guess that the contract becomes official about a week before training camp starts up, or right around the same time that Michael Carter-Williams and Nerlens Noel signed last offseason. To this point, Embiid is the only top 10 pick that has not yet officially signed, but don’t be alarmed: I would expect this to be a standard practice any year where Sam Hinkie has salary cap space.

The confusing Hasheem Thabeet acquisition

A few hours after Sam Hinkie held the conference call to discuss the Thaddeus Young trade, the Sixers GM made another bold move: acquiring former 2nd overall pick Hasheem Thabeet.

Okay, there was a little bit of hyperbole there. It really wasn’t bold. Or even really an acquisition.

The Sixers traded a top-55 protected 2nd round pick to the Oklahoma City Thunder for Thabeet on Tuesday, although they will reportedly release Thabeet once the trade becomes official.

Why?

Hasheem Thabeet signed a 3 year, $3.65 million contract with the Thunder in July of 2012, with $2.4 million in guaranteed salary. Thabeet earned $1.2 million in each of the previous 2 seasons, leaving his entire 2014-15 salary non-guaranteed, as long as he is released by September 1st.

So, Thabeet will cost the Sixers nothing.

But Oklahoma City could have also released him, leaving them with the same $0 hit on their salary cap. So why trade him to the Sixers so they could release him instead?

A traded player exception.

By trading Thabeet’s $1.25 million salary to the Sixers, while getting back $0 of salary in return, the over-the-cap Thunder got a free $1.25 million traded player exception for a player they were going to cut anyway. For the Sixers? They received $100k in cash for a player who will count $0 towards their salary cap.

All the other moving parts are moot. The Sixers will never actually give up the 2nd round pick in the deal, which would require them to finish with one of the 5 best records in the league this year. They just had to “send something back” in order for the trade to work under the CBA. Hasheem Thabeet’s salary is fully non-guaranteed, and he will never receive one cent from the Sixers, and will not count at all against their cap. It has absolutely nothing to do with reaching the salary cap floor.

This trade was, essentially, about the Thunder buying a $1.25 million trade exception for $100k.