Running the play clock...making sure I got things right in my mind...

[Official_21]

I just want to make sure I got this right before what is only my 2nd time on the play clock this season. In a nutshell, the play clock runs at 40 seconds (including after a touch down), unless the following occurs:

1. Any Administrative stoppage, which then causes the 25 second play clock to be used
2. With less than 40 or 25 seconds left on the game clock, only when the game clock is stopped

Do I have this right?

[ilyazhito]

Yes. 1st downs are also 40-second play clock, because the flow of the game does not stop, only the game clock stops.

[Official_21]

Yes. 1st downs are also 40-second play clock, because the flow of the game does not stop, only the game clock stops.

Almost forgot about that...thanks for the reminder.

[TxBJ]

And following a free kick it is always 40 if no administrative stoppage. It doesn’t matter if returned, fair caught, a touchback, or it team A gets it. A lot of play clock operators around here don’t understand that.

[ElvisLives]

And following a free kick it is always 40 if no administrative stoppage. It doesn’t matter if returned, fair caught, a touchback, or it team A gets it. A lot of play clock operators around here don’t understand that.

Not just around there.  Pretty much everywhere.  This Jackhiny PCO at the local "big" stadium refuses - let me emphasize, REFUSES - to visit with us before the game.  As a retired official, he thinks he knows everything.  'No need to talk to us.  All the same as we've done the previous 9 games - right?'  So, we had an onside kick recovered by A.  He sets it to 40 and starts it.  I think, "Great.  He knows this."  I look up and it is now at 25 and holding.  Rather annoyed, I begin signaling 40 and finger wind (don't want to use full arm wind, so the game clock operator doesn't get confused and start the game clock).  Nothing.  More pumps and finger winds.  Nothing.  More pumps and finger winds, and the clock goes to 40, but holds.  More finger winds, and he finally starts it. 

I have to figure out how we get this issue resolved (locally).