Quick Links

June 1 has come and gone

June 1 has come and gone

I know that many of you out there are hoping for help for your favorite National Football League team coming from a wave of talent hitting the free agency market after June 1.

I hate to tell you this, but you should look elsewhere. As far as the NFL is concerned, June 1, for the most part, has come and gone.

No, you do not need to adjust your calendar. It says it's late May. But the NFL's June 1 came over two months ago.

The whacky calendar is due to a change in the collective bargaining agreement. Prior to 2006, a team could release a player after June 1 and have most of the salary cap implications of the release come in the following year rather than accelerating immediately into the cap.

The players didn't necessarily mind being cut; it frequently gave them the opportunity to collect a little more signing bonus money.

However, they were hitting the market at a bad time, after most team's free agent budgets were shot. In addition, they frequently were in an awkward position. In many cases it was well known that a player would be a June 1 cap casualty, but he had to go to his current team's facility to work out and participate in minicamps and OTA's.

And the teams became increasingly concerned about the risk of a player getting injured while working out at the team facility. If that were to happen, the team would be liable for the player's entire salary for the upcoming season.

These issues were addressed in the '06 CBA extension. Teams now are allowed to release up to two players as soon as the league year begins (the start of free agency) and designate them as post-June 1 cuts. The players get their freedom immediately, so they can pursue employment while the market still is hot.

While the teams don't get any salary cap relief until June 2—the players' salary for the coming season still is counted against their cap number until then—they don't have to have dead men walking around their facilities and their exposure to issues due to workout injuries is greatly reduced.

Since the rule creates such a win-win situation, teams have taken advantage of it. Most, if not all, of the players who would have been released post-June 1 in the past already have received their pink slips.

There are a couple of reasons why a team might choose to wait to release a player it intends to cut under the June 1 cap rules. If they have three or more players to release, they would have to wait until the date actually passes to get the cap relief. This would be highly unusual as few teams would want to dump that much dead cap money into the following season. I don't have complete list, but I don't think that any team designated more than one player.

An organization also might want to hold on to a veteran to see if they can draft his replacement and see how the rookie performs in a minicamp or two before deciding whether or not to cut the vet.

Again, this would be an unusual situation and if you're at that point, you might as well let the battle for the position and the roster spot go all the way to training camp. You get the same cap benefits if the veteran is cut on September 1 as you do on June 1.

The bottom line is that the free agent pickings on the morning of June 2 will be just about as slim as they are today. If you're hoping that your team can pick up some help then, don't hold your breath. The time for doing that was back in March.

You can reach Rich Tandler by email at rich.tandler+bleachers@gmail.com. His Redskins blog archive is located here.

Quick Links

3 reasons why Redskins promoting Matt Cavanaugh to offensive coordinator makes sense

3 reasons why Redskins promoting Matt Cavanaugh to offensive coordinator makes sense

Championship Sunday produced a flurry of Redskins news. A pair of internal promotions erased the team's vacant coordinator positions, as Greg Manusky landed the defensive coordinator spot and Matt Cavanaugh will take over as offensive coordinator. When Sean McVay left to coach the Rams, many expected Cavanaugh to take over his spot. Here are three reasons why:

  1. If it ain't broke, don't fix it - There was plenty to criticize from the Redskins the last two seasons, but not much of it came on offense. Cavanaugh joined the organization in 2015 as quarterback coach, and the offense has consistently improved in those two seasons. Though the team struggled to score TDs in the Red Zone, the 2016 version of the Redskins moved the ball at a team-record clip and ranked among the top offensive teams in NFL yardage. When something is working as well as the 'Skins offense, it's not wise to change it dramatically.
  2. Impressive work - Cavanaugh began coaching QBs for the Redskins in 2015. Kirk Cousins took over as Redskins starting quarterback in 2015. In two years working together, Cousins twice broke the Redskins franchise passing record and is now poised to get a mega-contract in free agency. Talking after the 'Skins loss to the Giants earlier this month, Jay Gruden said, "I think [Cousins'] really improved his game a lot in the last couple years. And a lot of it has to do with Matt Cavanaugh and Sean McVay."
  3. Make the call - The biggest question remaining for the Redskins - outside of the HUGE unknown surrounding Cousins - will be about play calling. All indications are that Jay Gruden will return to calling the plays from the Washington sideline, and obviously, that's a situation Cavanaugh understands. For two seasons now, Cavanaugh along with McVay, Gruden and offensive line coach Bill Callahan have had input on play calling. With McVay gone, Cavanaugh and Callahan will likely contribute even more in support of Gruden. 

RELATED: 2017 NFL MOCK DRAFT 1.0

Want more Redskins? Check out @JPFinlayCSN for live updates or click here for the #RedskinsTalk Podcast on iTunes, here for Google Play or press play below. Don't forget to subscribe!

Quick Links

Poll: What is your approval rating for the Manusky hire?

Poll: What is your approval rating for the Manusky hire?

Hit the poll and then come back here to comment or just replay on Twitter. Thanks!