| Rule Submission Title | Serving before or during the score call. |
|---|---|
| USAP Board Vote | Disapproved |
| USAP Board Vote Reason | There is no compelling need for this change. The current rule is clear, unambiguous, and well understood. The current rule, along with referee hand signals, works fine. |
| Existing Rule # | 4.A.1 |
| Proposed Rule Change | 4.A.1. The entire score must be called before the ball is served. In officiated matches, the referee will call for a replay if the serve is made before or during the score call. In unofficiated matches, the receivers may call for a replay before the return of serve if the ball is served before or during the score call. |
| Original Rule Text | 4.A.1. The entire score must be called before the ball is served. |
| Reasoning Behind Suggested Change | The rules are not explicit about the impact of serving the ball before or during the score call. Since a service fault cannot be made before the ball is live, referees currently ask for a replay if the serve is made before they begin calling the score. Referees call a fault if the server serves while the score is being called. Although these actions are appropriate based on the rules, there is a common perception that theses actions are inconsistent, and that calling a fault is a 'gotcha' fault. If we assume that the primary purpose of the rule is to ensure that the server has appropriately waited for player readiness and does not serve in a way that confuses the receiver, this change still adheres to that purpose. Allowing for a replay in all situations removes the 'gotcha' fault and makes the results consistent, regardless of when the early serve occurs. The rule does not require recreational or un-officiated players to force the replay, but does put a time limit on when it can be called for. To be consistent with 4.K, I am suggesting that the time limit be the return of serve. |
| Scenarios In Which the Rules Applies | Early serves |
| Rule Book Year | 2026 |
| Rule Change ID | 2134 |
| Date Created | April 18, 2025 |
| View Comments | View Comments |
Recent Comments