Last week, I promised a look back at an earlier version of Principle 12, foreshadowing that it has evolved significantly over the past 25 years. That topic is still coming.However, the direct comments on last Wednesday’s post were unusually lively. The discussion that followed raised an excellent point that deserves attention.
Out calls reversed. A player who calls a ball out must reverse the call if the player becomes uncertain or realizes that the ball was good. The point goes to the opponent and is not replayed. However, when a receiver reverses a fault call on a serve that hit the net, the server is entitled to two serves.
USTA Friend at Court 2026 , The Code, Principle 12
Readers pointed out something I had overlooked. My explanation that the serve became a let works perfectly when the reversed call occurred on a first serve. However, it falls apart when the let happens on the second.
Rule 22 in the main body of the ITF (I guess World Tennis now) Rules of Tennis is clear. A service let does not erase a previous fault. If a first serve is missed and the second serve clips the net before landing in the proper service box, the server receives another second serve, not two serves.
Yet Principle 12 of The Code explicitly awards two serves after a receiver reverses an incorrect fault call on a serve that touched the net. That means something more than a simple let is taking place. Another reader pointed out that the answer lies in the interruption itself. That comment reflects my own perspective on that situation.
When the receiver immediately calls, “Fault” after a second serve, the disruption creates a break in the psychological flow. The server spends a brief moment processing the point as a double fault. If the opponent subsequently decides the ball actually landed in and reverses the call, it is occurring from a different state than if the let had been immediately granted.
The key point is that the server did not create the interruption. Rather, it was generated by the receiver’s incorrect call.
Throughout the Rules of Tennis and The Code, responsibility for interruptions generally follows the player who caused them. When the server interrupts play through a fault, delay, or other error, the consequences belong to the server. When the receiver interrupts play through an incorrect call, it would be inequitable for the server to lose the benefit of a normal service sequence because of an error they did not make.
Viewed within that framing, awarding two serves is not really about the let at all. The let explains why the original fault disappears. The additional first serve recognizes that the receiver’s erroneous call interrupted the server’s routine and effectively forced them to experience a double fault that never actually occurred.
Psychologically, that matters. Serving is one of the most rhythm-dependent skills in tennis. Recovering from what you believe is a double fault is very different from preparing to hit another second serve. Principle 12 acknowledges that reality by restoring the server to the position they occupied before the interruption occurred.
The discussion following last week’s topic led me to spend a little more time on Principle 12. The injection of this additional post into what was initially planned feels emblematic of the point it establishes. Reconsidering an initial conclusion in light of better information is exactly what it has been teaching us all along.
- Friend at Court: The Handbook of Tennis Rules and Regulations, USTA, 2026
- Friend at Court: The USTA Handbook of Tennis Rules and Regulations, USTA, 2001. (Hardcopy.)
I know you’ve signed up for USTA Coaching. Not sure if you’re aware, but they recently uploaded three new courses on the rules and regulations of tennis that appear to be officiating courses. (Digression: they also appear to be older. Not sure if they’re migrating course content to add to the library on the Coaching website or they’re in the process of adding an officiating curriculum there too.)
In any event, Rules and Regs Course No. 3 deals with the Code, and in completing the course, I was reminded of Principle 30 of the Code. I think this scenario is just a simple extension of the application of that principle, and we were all (myself included) probably just overthinking it in your prior post. Not that your conclusion here is wrong (the opposite, in fact, since it flows from the same basic idea underlying Principle 30), but that the answer might be expressed more simply as just the Code working holistically.