What's new
Fantasy Football - Footballguys Forums

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

**RUMOR** (1 Viewer)

It would be pretty surprising...that said, Rhodes was pretty much expected to get the axe to make room for Bush, but maybe they've decided that Jordan's back issues have rendered him a poor investment for the future. It's not like they didn't just sign Rhodes.

If Kiffin has made the decision to start Fargas or get Bush a lot of meaningful time, then that makes Jordan a really expensive backup. And if he refuses to go on IR...there you have a release situation.

 
ok but as a jordan owner...if he was released and he is ok to play...there are some teams that could REALLY use him, aren't there? for instance-don't the packers run a similar zone blocking scheme, for instance?

 
ok but as a jordan owner...if he was released and he is ok to play...there are some teams that could REALLY use him, aren't there? for instance-don't the packers run a similar zone blocking scheme, for instance?
I don't know why he would be cut mid-season if there wasn't something wrong with him. Perhaps someone can explain how this rumor makes any sense. Fargas is gone in my league so if this is true Bush might make for a sneaky pickup. Or Rhodes.
 
65 User(s) are panicking for nothing:

42 Members: SayWhat?, Vicktimized, RBM, Billy Ball Thorton, Pigskins, fo shizzle, Tom Baker, Keysersoze666, L-pipe, The Noid, Smarr, brobe4, yellowdog, NorrisB, LMF, Banger, Heaton, Neofight, Hawk, elpasotexan, stillaway, glock, The foo, Pocket Joker, dmack, TheWick, kbcrowe, 3C's, fatboyj711, dmac37, Mr. Sparkle, Winning IS Everything, bcr8f, drdgreenlove, greenline, The Carnage, seatownfavorite, HunterBear, Screamin' SphinX, BoomBoom, Warpig

 
65 User(s) are panicking for nothing:42 Members: SayWhat?, Vicktimized, RBM, Billy Ball Thorton, Pigskins, fo shizzle, Tom Baker, Keysersoze666, L-pipe, The Noid, Smarr, brobe4, yellowdog, NorrisB, LMF, Banger, Heaton, Neofight, Hawk, elpasotexan, stillaway, glock, The foo, Pocket Joker, dmack, TheWick, kbcrowe, 3C's, fatboyj711, dmac37, Mr. Sparkle, Winning IS Everything, bcr8f, drdgreenlove, greenline, The Carnage, seatownfavorite, HunterBear, Screamin' SphinX, BoomBoom, Warpig
I'm sure there are some people that are panicking but I think most owners are paying close attention to the situation. If this rumor has any legs, those who paid attention in the early stages would be able to snag Fargas/Bush/Rhodes/etc.
 
If his back is still bothering him, IR, maybe. I don't see them just releasing him. He's been productive in the very recent past, injury excepted. Culpepper hasn't helped anyone on the team, Jordan included. With Culpepper using the shotgun so much it's kind of hard to setup any sort of running game if the defense knows that when they aren't in the shotgun it's likely a running play. Either that or the running back is a few more yards away from the line when he gets the ball. That's more yards to cover just to get back to the line that don't show up on a YPC stat line. Bush may yet take over, but I'd see Rhodes as the likely candidate to drop should Bush start passing people on the depth chart.

 
Lamont was one of the better RB's in the league the first few weeks of the year (fantasy and reality).

must be a slow day over at that site

 
Wasn't Dominic Rhodes the guy who was supposed to get cut like a week ago? And now its Jordan. I'm not buying it. I do wish that i had the roster room to stash Bush just in case, but alas Travis Henry continues his battle to elude suspension.

 
Lamont was one of the better RB's in the league the first few weeks of the year (fantasy and reality). must be a slow day over at that site
Except that Jordan has never been healthy in his whole career , so they dont want to waste money anymore on a guy that gives you 8 games per year , and other teams in the NFL know about this so he would have teams rushing to sign him.Yes he is talented but he cant and has never stayed healthy .
 
Also... I thought NFL players were protected from being cut if injured, hence the injured reserve. Couldn't Jordan sue the Raiders?

 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.

 
Also... I thought NFL players were protected from being cut if injured, hence the injured reserve. Couldn't Jordan sue the Raiders?
I was thinking the same, but if they tried to IR him and he fought that, then he would be healthy enough to cut....edit to add..Couch Potato's post made more sense to me
 
Last edited by a moderator:
All of this news that I have posted is correct... If I had to pick ONE statement of mine that might not happen, it would be Lamont... Why? Well, either Rhodes or Jordan is getting cut. That's a FACT. But 94% of me knows it's Lamont... They have no reason to wait on cutting him, but since they already have to pay him for the week, they may just keep him until after the game... I'm not doubting myself, I know it's Lamont, but I'm just saying if I had to pick one topic, that's the ONLY one that could change SOMEHOW, but won't!
I got this from word of mouth from an insider in Oakland, no link. Take it for what its worth with a grain of salt. -Just don't be surprised if it happens.
\
 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:goodposting: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
 
I feel like I have to come on here to address a couple of things being said in this thread.First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
This is a great posting. The first scenario is exactly why Bettis faked his injury in training camp many years ago with the Steelers. He suspected that the team was about to cut him.
 
ummm, Lamont has played in EVERY game this season. Yet Oakland cant cut him because he is less than 100% healthy? :confused:

 
I feel like I have to come on here to address a couple of things being said in this thread.First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
Isn't the fact that Lamont is not injured right now though? He has been active and playing. His back might be a hinderance, but every player in the NFL has those. If you couldn't cut a player under those circumstances during the season, then no one would be cut.
 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:confused: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA

 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:goodposting: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA
You're reaching. If LaMont goes to the IR you should cut him in redrafts.
 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:confused: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA
You're reaching. If LaMont goes to the IR you should cut him in redrafts.
That's actually probably true given how late in the season this is.Plus... if he does get a settlement and signs with another team, thanks to the SP I'll probably be the first owner in my league to grab him off of the waiver wire again.

So...

In leagues where Jordan is my RB2, grab Fargas for immediate needs

In leagues where Jordan is my RB3-4, grab Bush for potential

If Jordan goes on IR, cut him.

Then check SP constantly til end of season like I have been doing.

Game plan set, thanks!

 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:confused: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA
I guess it's possible. I would think picking up his replacement in OAK would be much better move. I was really just trying to get some answers on NFL policy. This rumor honestly doesn't make much sense, at least if we are supposed to believe that Jordan will be outright cut. How often is a productive (allegedly healthy) starting player outright cut this late in the season? I could see him going to IR.

 
Last edited by a moderator:
I can see him going on IR and Rhodes being cut, but I can't see them flat out cutting Jordan.
Weren't there talks last year that Lamont's back problem was so bad that it could stop him from playing football again? Isnt this the same injury acting up again?
 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:shrug: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA
I guess it's possible. I would think picking up his replacement in OAK would be much better move. I was really just trying to get some answers on NFL policy. This rumor honestly doesn't make much sense, at least if we are supposed to believe that Jordan will be outright cut. How often is a productive (allegedly healthy) starting player outright cut this late in the season? I could see him going to IR.
New coach, young players waiting in the wings, 29 year old RB with injury concerns and a huge contract, a potential top 10 draft pick ahead, season going down the drain....just to name a few
 
I feel like I have to come on here to address a couple of things being said in this thread.

First of all, by league rule a team cannot simply cut a player because he is injured. That is what IR is for, and if he goes on IR they have to pay him. Or they can IR him and then work out an injury settlement and release him so he's free to sign with another team. But if they tried to cut him because of back troubles so they no longer had to pay him, the NFLPA would go crazy and the league would come down hard on them. So a release isn't going to happen as long as he's got back issues. Sorry.

Also, someone above mentioned releasing him if he refused to go on IR. Folks, a player doesn't have a say in that. If the team can justify it medically and chooses to IR a player, that's that. There have been lots of players unhappy about being moved onto IR with minor injuries, sometimes because the team wants to stash a young player, sometimes because they need to create roster room somewhere, and the player has no veto power whatsoever.
:shrug: Thanks for the info. In fact I remember an instance as in the bolded happened with the Bills last year with Troy Vincent. They wanted rookie Ko Simpson to play, so a mildly injured Vincent went on IR. He fumed about it to the press, but the team later gave him an injury settlement and he signed elsewhere later in the season.
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?

TIA
I guess it's possible. I would think picking up his replacement in OAK would be much better move. I was really just trying to get some answers on NFL policy. This rumor honestly doesn't make much sense, at least if we are supposed to believe that Jordan will be outright cut. How often is a productive (allegedly healthy) starting player outright cut this late in the season? I could see him going to IR.
This is assuming that someone beats the Jordan owner to the wire to grab the next Oakland RB. (which, at this point, isn't all that clear... Fargas will probably start it seems but he' doesn't seem like the long-term answer)I also already wasn't that excited about the Oakland schedule in the playoffs

Week 14 @GNB (11th, and in Green bay)

Week 15 IND (14th, but late in the season where the Colts could have more to play for)

Week 16 @JAC (15th, same logic as Indy above)

 
All of this news that I have posted is correct... If I had to pick ONE statement of mine that might not happen, it would be Lamont... Why? Well, either Rhodes or Jordan is getting cut. That's a FACT. But 94% of me knows it's Lamont... They have no reason to wait on cutting him, but since they already have to pay him for the week, they may just keep him until after the game... I'm not doubting myself, I know it's Lamont, but I'm just saying if I had to pick one topic, that's the ONLY one that could change SOMEHOW, but won't!
I got this from word of mouth from an insider in Oakland, no link. Take it for what its worth with a grain of salt. -Just don't be surprised if it happens.
\
Where did those last 2 quotes come from? FantasySharks? (I can't view that site from behind the firewall.)
 
Last edited by a moderator:
So what I'm taking away is this. (and please correct me if I'm wrong)If Lamont Jordan does go on IR, those of us who own him shouldn't be so quick to release him as he could still get a settlement and sign with another team later in the season? (possibly in a more favorable situation, or at least be a serviceable RB2-3, small chance, but possible)?TIA
Here are the IR rules as I understand themThe team decides that you go on IR - Matt Lienart didn't want to go on the IR this year with his Sholder injury.They have to pay you all of your SalaryThe salary counts against the capYou do not count toward the roster sizeIf the player and the team then reach an injury settlement, the player agrees to accept an amount of money (Usually less than the remainder of his current year salary) to get waived. The player would only agree to this assuming he could make up more than the difference playing for someone else. If Jordan goes on the IR, I guess he stays there, as no one will want to make up the million+ he is making this year. I could be wrong, but you can find better values on the waiver wire.If he doesn't go on the IR, He is a veteran player, so even if they waive him outright he gets all of his money for this year. The question I have is does he have to go through waivers? I remember discussions that Tiki Barber would have to go through waivers if the Giants renounced their rights before he became a free agent. Would Jordan? And if he did go through waivers and someone claimed him, would they now be responsible for the remainder of his salary?
 
All of this news that I have posted is correct... If I had to pick ONE statement of mine that might not happen, it would be Lamont... Why? Well, either Rhodes or Jordan is getting cut. That's a FACT. But 94% of me knows it's Lamont... They have no reason to wait on cutting him, but since they already have to pay him for the week, they may just keep him until after the game... I'm not doubting myself, I know it's Lamont, but I'm just saying if I had to pick one topic, that's the ONLY one that could change SOMEHOW, but won't!
I got this from word of mouth from an insider in Oakland, no link. Take it for what its worth with a grain of salt. -Just don't be surprised if it happens.
\
Where did those last 2 quotes come from? FantasySharks? (I can't view that site from behind the firewall.)
Yes, that's where those quotes came from.
 
All of this news that I have posted is correct... If I had to pick ONE statement of mine that might not happen, it would be Lamont... Why? Well, either Rhodes or Jordan is getting cut. That's a FACT. But 94% of me knows it's Lamont... They have no reason to wait on cutting him, but since they already have to pay him for the week, they may just keep him until after the game... I'm not doubting myself, I know it's Lamont, but I'm just saying if I had to pick one topic, that's the ONLY one that could change SOMEHOW, but won't!
I got this from word of mouth from an insider in Oakland, no link. Take it for what its worth with a grain of salt. -Just don't be surprised if it happens.
\
Where did those last 2 quotes come from? FantasySharks? (I can't view that site from behind the firewall.)
The Middle quote about paying him for the Week is wrong. He is a veteran player, and his full salary was gaurenteed when he was on the opening day roster. They have to pay him. The only thing that may happen is someone else claims him is now that new team has to pay him. But Jordan will get his money for this year.
 
OMG.....I'm going to cut him right now and pick up Michael Bush!!!
That post was as useless as the player your alias is named after. Please keep stuff like this out of here, there are enough Patriot threads littering the forums if you're looking for some place to be a tool.
Next time I will go out on a limb and create a rumor or take a chance with a more creative name like.........bob.
 
What are the benefits of cutting Jordan now?
None. (edit to add, there is one reason, and it's if they absolutely needed the roster space).He's guarenteed his salary for the year. If he's hurt they would IR him. If he's enough of a malcontent they'd suspend him before they cut him.
 
Last edited by a moderator:

Users who are viewing this thread

Back
Top