A tennis player can hit several serves without the score changing. To follow the sequence, track which service is due and what the official call does to that attempt. Counting every ball struck as a new point quickly produces the wrong story.
This reading exercise follows one point at a time under the standard ITF service-let rule. Its fictional practice logs are designed by i8 Live. Check the event's published format before applying them, because an approved no-let alternative also exists.
Keep an attempt record beside the score
Imagine watching a clip that begins with a ball touching the net. Before deciding what happens next, ask whether this was the first service or the second. The same visible contact can occur at different stages of a point.
Make two separate notes: the score before the point, and the service currently due. Update the service note after a call; update the score only when the point has been decided. This simple separation helps when a replay shows several deliveries while the scoreboard remains still.
The ITF glossary describes a first-service fault as leading to a second service. Two faults in succession lose the point, commonly called a double fault. A fault on its own therefore needs its place in the sequence before you can interpret its effect.
Read a service let as a repeat of that service
Under ITF Rule 22, a serve that touches the net and is otherwise good is a service let. That delivery is repeated, and an earlier fault remains on the record. A second-service let consequently leaves the player due to serve a second service again.
Net contact alone is insufficient information. You also need the landing and the official decision. Do not label a net-touching ball a let merely because it made the familiar sound.
| State before delivery | Call and next step |
|---|---|
| First service due | Fault: second service due |
| First service due | Service let: first service again |
| Second service due | Service let: second service again |
| Second service due | Fault: receiver wins the point |
Use the table as an observation aid, rather than a substitute for a ruling in a disputed incident. It assumes the standard service-let procedure and that each call in the record is known. An incomplete broadcast clip may not establish either assumption.
Follow Maya through one fictional point
Maya is serving in an invented practice match, with Joel receiving. The clip includes every delivery and every call for this point. The example uses ordinary first- and second-service rules; it represents no real player, match or statistical feed.
- Maya's first delivery is called a fault. Write down that a second service is due.
- The next delivery is called a service let. Keep the same second-service note.
- The next delivery is also called a service let. Keep that note again.
- The following delivery is called a fault. Record a double fault and the point for Joel.
Four balls were served, but this record contains one completed point. The two lets explain why the sequence was longer than two deliveries. They did not give Maya two new points or restore a first service.
Now change only the final event in your worksheet: replace the fault with a good serve followed by a rally. At that stage the service sequence has moved into live play, and the eventual rally result is needed. A good second serve does not itself tell you who won the point.
Compare logs that finish differently
The following shorthand preserves order from left to right. Read each row from a new point with a first service due. These are deliberately small editorial exercises, so you can trace the next action without a crowded scoreboard.
| Fictional sequence | What the observer can record |
|---|---|
| Let, then fault | Second service is now due |
| Fault, then let | Second service is still due |
| Fault, then fault | Double fault; receiver's point |
| Fault, then good serve | Follow the ensuing play |
The first two rows end at the same service state through different histories. This matters when writing a recap: a state tells you what is due now, while a log tells you how it was reached. Keep both if the sequence itself is the question.
Try covering the right-hand column and writing your own next-step note. Then compare your answer with the table. If you treated every let as a fresh first service, return to the earlier fault rather than merely recounting the deliveries.
Distinguish a service let from replaying a point
ITF Rule 23 treats a whole-point let differently from the second-service let described above. Its example concerns another ball entering the court during play: when the whole point is replayed, the player receives a first service. The official decision and its scope matter.
For a viewing note, write either service repeated or point replayed only when the call supports it. A pause, a camera cut or a player collecting a ball does not by itself identify the ruling. If the relevant announcement is missing, mark the restart state as unconfirmed.
An observer's useful checklist is:
- What service was due before the interruption?
- What call was actually made?
- Was a particular service repeated, or was the whole point restarted?
- Does the next visible delivery agree with that record?
This is a way to describe what you saw, not a method for overruling an official from a short clip. Preserve an uncertainty note instead of inventing the absent first delivery or announcement.
Check whether the event uses no let
Appendix VI of the ITF rules includes an alternative without the usual net service let. The standard table above must therefore be paired with the format used by the event. A rule from a different competition is an unsuitable shortcut.
Before taking detailed notes, find the event's own rules or an official explanation of its format. Record the document and edition beside your log. If that information is unavailable, describe the standard-rule example as a learning exercise and leave the event-specific conclusion open.
Questions about serve sequences
Does a second-service let erase the first fault?
Under the standard rule, it does not. Keep the earlier fault in your sequence and repeat the second service. Maya's example shows why counting physical deliveries alone gives an incomplete account.
Can a clip beginning with a fault prove a double fault?
It needs the preceding state or a confirmed point-ending call. If you cannot establish what service was due, the isolated fault leaves a gap. Note that gap rather than assuming a first fault happened off camera.
Does a good serve complete the point?
It starts the playable sequence rather than establishing its eventual winner. Continue with the observed play and confirmed result. Keep the service-stage note separate from the final point record.
Sources and further reading
The standard-rule facts were checked on 18 October 2026 against the ITF 2026 Rules of Tennis, especially Rules 20, 22, 23 and 24, and Appendix VI. The ITF tennis glossary provides the introductory first-service and double-fault terminology. Maya and Joel, the ordered logs and the observation worksheet are original i8 Live teaching examples.
For a different scoring question, read points, games and sets in a tennis tie-break. When a clip or capture omits the surrounding sequence, use our sports screenshot source and date checks to record that limitation. The Malaysia sports directory guide explains the separate role of site navigation and match information.
Sources
- 2026 Rules of TennisInternational Tennis Federation · 2026-10-18
- Tennis glossaryInternational Tennis Federation · 2026-10-18
