09-30-2015, 01:22 PM
(09-29-2015, 08:23 PM)fredtoast Wrote: 1. Using time outs is not poor "clock management". There are many good reasons to use a timeout other than to stop the clock in the final minute of a half.
2. Deciding not to risk trying to score at the end of a half is not poor "clock management". It is a tactical decision.
The only time I can really complain about poor clock management is when there is actually poor clock management. Marvin may have been guilty of that a few times, but it is not a serious problem. In fact I can not remember that last time it really hurt us.
Opening week vs. Bears in 2013. We get the ball at our own 12 with 1:38, 1 TO, Bears have 1 TO as well.
1st and 10 (1:38) - rush for -4, let clock run down
Okay, at this point if you want to go in the half no prob. Not very likely you can march 60+ yards in that time with one TO. Bears are fine with that too and are not using their TO.
2nd and 14 (approx 1:04) - incomplete pass, clock stops
Why would you pass now after burning half a minute off the clock?
3rd and 14 (1:00) - short pass completion for 7 yards
So now you've decided to not go for it again, but take the risk of passing the ball and possibly stopping the clock?
Bears now take final TO since it is 4th down and the Bengals managed to stop the clock for them already.
Bears get punt on own 44 with 44 seconds left, proceed to march down the field and kick field goal.
Bengals end up losing game by 3.
You can make a defensible argument to just run out the clock back on 1st down on your own 14. You can make a defensible argument to try to get down the field for a score with 1 TO left. You cannot make any defensible argument to run the ball on 1st down to bleed the clock, and then all of a sudden decide to start throwing it and go down the field when you're already in 2nd and long. Absolutely impacted the game.
