LIST OF SUGGESTED PICKLEBALL RULE CHANGES FOR PREVIOUS YEARS

Rule Change Process

Rule Submission TitleSomething to the effect of better saying the score clearly, slowly, and loudly. . Also, a two second pause between the last number spoken and the beginning of the serve motion. Also the correction of the score
USAP Board Vote ReasonFailed
USAP Rules Committee Vote ReasonFailed. Unnecessarily cumbersome. Overkill.
Existing Rule #In the area of 4.K Wrong Score Called. and 4 D. Calling the Score
Proposed Rule Change

Something to the effect of saying the score clearly, slowly, and loudly.  Also, a two second pause between the last number spoken and the beginning of the serve motion.

I think the ultimate way to REALLY resolve this on-going perpetual problem would be too have the server, say before the serve, to the receiver, "I believe the score is," and "say it" and then look at the receiver and ask, "Agree?"  Then the receiver would either nod their head for YES, or shakes it for NO.   Yes, meaning "I agree, please serve the ball."  NO, would mean, "Let's stop and talk about the score"  Then reach an agreement about it, and then serve the ball.   That's pretty simple and right.  That alone puts some onus on the server to say the score loud, slow and clear every serve, or have to break into a discussion about it.  As is, these fast talking mumbling bumpkins are not held accountable much of all, and just rip off a serve without any agreement or accuracy.  Then the opponents have to often go through a long rally, thinking about the darn score, said wrong, when they should only have to think about playing the game.

Original Rule Text

The rules concerning what happens if the score is called wrong.   And  and how the score shall be called.

Reasoning Behind Suggested Change

Pickleball is most often played in loud settings and if the full score is not said, clearly, slowly and loudly the opponents can not hear it in full.  A two second pause between the end of the score being said and  before the beginning of the serve motion gives everyone a chance to at least minimally absorb what the serving has said, and prevents the 'fast serve' where opponents are caught not ready to play.  There is "NO TIME" for players to ask for a correction by the speed freaks.  Often that can be deliberate. Is TWO SECONDS asking too much?  Get it right BEFORE the serve is made!

So so often, the score is confused, said wrong, not heard, or in doubt.  So why is that?  Well, how about explaining how it should be said, so that much of this problem can be alleviated.  Left without some explanation as to how the score should be said, and some absorption time, we will continue to waste even more time later discussing what the heck the score is. It's really better to get it resolves BEFORE any serve motion in made.

I think the ultimate way to REALLY resolve this on-going perpetual problem would be too have the server, say before the serve, to the receiver, "I believe the score is," and "say it" and then look at the receiver and ask, "Agree?"  Then the receiver would either nod their head for YES, or shakes it for NO.   Yes, meaning I agree, please serve the ball.  NO, would mean, let's stop and talk about the score - make an agreement about it, and then serve the ball.   That's pretty simple and right.  That alone puts some onus on the server to say the score loud, slow and clear every serve, or have to break into a discussion about it.  As is, these fast talking mumbling bumpkins are not held accountable much of all, and just rip off a serve without any agreement or accuracy.  Then the opponents have to often go through a long rally, thinking about the darn score, said wrong, when they should only have to think about playing the game.

But, if we want to continue this rude time consuming confusion - just keep it all as is.  Let the havoc and confusion continue to abound.

Scenarios In Which the Rules Applies

The server saying the score and how it is said and corrected if need be.

Rule Book Year2023
Rule Change ID286
Date CreatedMarch 16, 2022
View Comments View Comments