<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Brandon Lloyd Cut</title>
	<atom:link href="http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/</link>
	<description>Thoughts and Analysis of the Washington Redskins and the NFL. Indepth game previews, statistical analysis and opinion pieces featuring the Redskins</description>
	<lastBuildDate>Sun, 01 Jan 2012 18:47:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Bill</title>
		<link>http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/comment-page-1/#comment-24284</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/#comment-24284</guid>
		<description>Actually, I stand corrected; the Redskins handled this the stupidest way possible, at least according to the Post.

They have released Lloyd, all right, but designated him a June cut.  That&#039;s what I originally thought they would do; however, they released him in February, instead of waiting until June.

While Lloyd could easily have been told that his services were not required and he could look elsewhere, doing the cut this way means that they MAY be on the hook for a Roster bonus (which they were trying to get out of paying by announcing the cut now) OR may have screwed up the computations for the Cap for this season by announcing it too early; it&#039;s as if the Redskins are trying to have it both ways.  That&#039;s going to get them a grievance with the NFLPA; my guess is that the Redskins are going to end up having to pay Lloyd the additional $1.5 mil that they were trying to avoid because they&#039;re trying to get cute, which means that if we DO start making signings, all of a sudden, we&#039;re going to have to take a second hit on the Cap.

It&#039;s like going into a Chinese restaurant and being told &quot;You can choose one from Column A and one from Column B&quot; and saying &quot;Great, I&#039;ll have A3 and A7&quot;.</description>
		<content:encoded><![CDATA[<p>Actually, I stand corrected; the Redskins handled this the stupidest way possible, at least according to the Post.</p>
<p>They have released Lloyd, all right, but designated him a June cut.  That&#8217;s what I originally thought they would do; however, they released him in February, instead of waiting until June.</p>
<p>While Lloyd could easily have been told that his services were not required and he could look elsewhere, doing the cut this way means that they MAY be on the hook for a Roster bonus (which they were trying to get out of paying by announcing the cut now) OR may have screwed up the computations for the Cap for this season by announcing it too early; it&#8217;s as if the Redskins are trying to have it both ways.  That&#8217;s going to get them a grievance with the NFLPA; my guess is that the Redskins are going to end up having to pay Lloyd the additional $1.5 mil that they were trying to avoid because they&#8217;re trying to get cute, which means that if we DO start making signings, all of a sudden, we&#8217;re going to have to take a second hit on the Cap.</p>
<p>It&#8217;s like going into a Chinese restaurant and being told &#8220;You can choose one from Column A and one from Column B&#8221; and saying &#8220;Great, I&#8217;ll have A3 and A7&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/comment-page-1/#comment-24279</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 27 Feb 2008 14:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.theredskinreport.com/2008/02/26/brandon-lloyd-cut/#comment-24279</guid>
		<description>By cutting Lloyd now, the Redskins are free of him for 2009; that&#039;s a good thing, but it hurts here and now.  It also means that he&#039;s less of a total Cap hit over the next two years; making him a June cut would have cost the Redskins an extra 1.5 million between the two years.

This actually bodes well for resetting up for the future, although not necessarily well for a &quot;quick fix&quot; in 2008.  It&#039;s a good way to get back to sanity in the way the Redskins do their offseason contracts.  As I said before, I&#039;m good with this; I&#039;m surprised (the Redskins were tight, and this was the more expensive option now) but it just means no splashy signings this offseason, and a bit of belt tightening.</description>
		<content:encoded><![CDATA[<p>By cutting Lloyd now, the Redskins are free of him for 2009; that&#8217;s a good thing, but it hurts here and now.  It also means that he&#8217;s less of a total Cap hit over the next two years; making him a June cut would have cost the Redskins an extra 1.5 million between the two years.</p>
<p>This actually bodes well for resetting up for the future, although not necessarily well for a &#8220;quick fix&#8221; in 2008.  It&#8217;s a good way to get back to sanity in the way the Redskins do their offseason contracts.  As I said before, I&#8217;m good with this; I&#8217;m surprised (the Redskins were tight, and this was the more expensive option now) but it just means no splashy signings this offseason, and a bit of belt tightening.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

