Clock management on our last drive
Posted: Sun Oct 14, 2012 7:47 am
I was watching the game on firstrow so no clock or downs to reference to but I heard the commentators mention this and wondered the same.
Why was June not running the clock down on our last drive and waiting for the entire play clock to wind to 1 before snapping it? It was around 2 minutes and if we milked the clock a little more than we did, Tulane doesn't have enough time to get a score. I'm also confused as to why he would throw on that drive especially with how much success we were having feeding the ball to our beast Line. He should've just kept running the ball and I know that Line was looking tired at the end so he could've put in Seeker for a few snaps. He could've faked a GG run like we did earlier which worked great. The clock management was just horrible on that last drive. Anyone have an ideas what the hell June was thinking?
Why was June not running the clock down on our last drive and waiting for the entire play clock to wind to 1 before snapping it? It was around 2 minutes and if we milked the clock a little more than we did, Tulane doesn't have enough time to get a score. I'm also confused as to why he would throw on that drive especially with how much success we were having feeding the ball to our beast Line. He should've just kept running the ball and I know that Line was looking tired at the end so he could've put in Seeker for a few snaps. He could've faked a GG run like we did earlier which worked great. The clock management was just horrible on that last drive. Anyone have an ideas what the hell June was thinking?