![]() |
Quote:
|
Quote:
I know I am patient once the ball is spotted. I'll look to both wings and the box to make sure they're all set, which takes about 3-5 seconds. The chain crew was slow last night and they commented on my pace on first downs, which is no different than any other down. They were just slower. I do know that I got a compliment at halftime from someone working in the press box saying that we had very good pace out there. At the end of the day, the teams adapt to the crew. We've not had a DOG in 4-5 weeks on Friday night. And with a 35-20 game last night (8 touchdowns) with homecoming (20 minute halftime), we still finished the game in 2:10. |
RFP is three ticks from when the ball is set. Huddle, no huddle, hurry-up, makes no difference.
|
Quote:
|
Quote:
|
Quote:
It is a crew effort. It requires that the HL makes sure the chain crew (particularly the box) is doing their job and that the umpire, SJ and BJ do their jobs in a manner that doesn't create a delay. |
Consistently assessing that a crew is doing their job, " in a manner that doesn't create a delay" is clearly an appropriate objective. Assuming a specific time interval can be set as an overriding requirement, seems like a dangerous and unnecessary requirement.
There are all sorts of common occurences that can affect that interval; a slow(er) chain crew, a player an Umpire has decided needs a special word of guidance, a reasonable, appropriate question from a coach to a wing official. Under "normal" circumstances a specific time interval may be attainable, but the circumstances are what should decide the interval, not the other way around. |
I've never been concerned with or counted the number of seconds after the ball became dead for the ball to be declared RFP. I signal RFP when it is READY FOR PLAY. No sooner nor later. The moment the ball is placed on the ground AND I see that my crew and the chains are ready, I declare it RFP. This time will vary, I am sure.
|
All times are GMT -5. The time now is 04:41pm. |