An attempted return counts as being ready.

The BWF international baseline used here

This page applies BWF Statutes Section 4.1, Laws of Badminton, Version 5.0 (2), in force 26 April 2025, especially Laws 9.1–9.5, 13.1–13.2, 14 and 16–17. Match-control procedure is checked against BWF Statutes Section 4.1.1, Instructions to Technical Officials (ITTO), Version 8.0, in force 17 November 2025.

The core readiness rule is the BWF international playing-law baseline. The 25-second Time Clock procedure discussed below applies only when that tool is in use. National associations, schools, clubs and event organisers may appoint additional procedures, and the specific Para badminton technical-official instructions supersede the general ITTO where they contain a specific clause.

Readiness is judged before delivery

BWF Law 9.4 says the server shall not serve before the receiver is ready. Law 9.3 identifies delivery as the moment the racket hits the shuttle or the server misses it while attempting to serve. If delivery occurs too soon, Law 14.2.1 requires a let.

The Laws prescribe no countdown, mandatory hand signal or verbal formula for becoming ready. In an umpired match, readiness is therefore a point-of-fact judgment from the players' positions and actions. A receiver should communicate unreadiness clearly, but a raised hand or turned head is evidence to assess—not permission to create undue delay.

Contact with the shuttle is not required

Law 9.4 uses an attempt, not a successful return, as the decisive event. A receiver who makes a genuine racket action intending to play the delivered shuttle is deemed ready even if the racket misses. The receiver cannot wait to see whether the attempted return succeeds before choosing between a live rally and a let.

The law does not say that every flinch, step or racket movement is an attempted return. BWF's definition of a “stroke” turns on an intention to hit the shuttle; similarly, whether an observed action was an attempted return is a factual judgment. Movement to avoid being struck or to signal “wait” should not automatically be relabelled as an attempt without evidence of an intention to play the shuttle.

Reconstruct the service in order

1. Identify the correct players. Confirm the server, the designated receiver and their diagonal service courts.
2. Decide readiness. Was the receiver ready before the service was delivered?
3. Look for an attempted return. A genuine attempt deems the receiver ready under Law 9.4, even without contact.
4. If genuinely unready with no attempt, call a let. Law 14.2.1 ends the inquiry into the result of that uncounted play.
5. If ready, judge the service. Apply the server's and receiver's position, feet and all other Law 9 requirements.
6. Check for two faults. If server and receiver are both faulted during service, Law 14.2.2 makes it a let.
7. Apply the correct outcome. A single fault loses the rally; a let leaves the score and last server unchanged.

Preparation, start and delivery are different moments

Once the players are ready, Law 9.2 makes the first forward movement of the server's racket head the start of service. Law 9.3 makes racket contact—or a miss while attempting to serve—the delivery. The stationary-foot requirement and continuous-forward-racket requirement run from start to delivery.

Those definitions matter when reviewing slow motion. A receiver may adjust before the start without committing the Law 9.1.4 foot fault. Once service starts, some part of both of the receiver's feet must remain in stationary contact with the court until delivery. An attempted return proves readiness; it does not excuse a separate foot fault during that interval.

The receiver's protection is not a right to stall

Law 9.1.1 prohibits either side from causing undue delay once server and receiver are ready. Law 9.1.2 specifically treats a delay after completion of the server's backward racket-head movement as undue delay. BWF ITTO 5.10.3 adds that once the server is in position and ready, the receiver must not unduly delay getting ready for the next service.

Receiver delay does not authorise the server to deliver anyway and demand that the rally count. The umpire manages it: ITTO 5.10.9 calls first for a reminder that play must be continuous and, if necessary, application of Law 16.7. That law permits a warning, a fault after a prior warning, or an immediate fault for a flagrant breach; a fault loses the rally, and a faulted side is reported to the Referee, who has power to disqualify it.

Twenty-five seconds applies only when the tool is in use

BWF ITTO 5.10.8 creates a tournament procedure for a match using the Time Clock. The clock starts when the umpire enters the previous rally's score and expires after 25 seconds. The umpire checks that both sides are in position and ready before expiry, but the receiving side must be ready sooner if the server is already in position and ready.

This is not a universal “serve clock” for every badminton match and expiry does not automatically award a point. The umpire may stop the clock for matters such as extended court mopping, a dispute or an injury. A violation is handled through the reminder and possible Law 16.7 process; it does not erase Law 9.4 or permit an unofficiated quick serve.

Readiness does not legalise the service

Once the receiver is ready—expressly or because a return is attempted—the delivery still has to satisfy every applicable part of Law 9. A single server fault gives the receiving side the rally and point. A single receiver fault gives the serving side the rally and point.

Law 14.2.2 supplies a narrow different result when the server and receiver are both faulted during service: a let. For example, a server may breach the service-height rule while the ready receiver also lifts a foot completely after service starts. The receiver's attempted return is not itself a fault; it only answers the readiness question.

The score, server and service court do not advance

Under Law 14.3, play since the last service does not count and the player who served last serves again. No side receives a point. Because the score is unchanged, the same right-or-left service court remains tied to the same score parity.

This is a replay of the service at the existing match state, not a “second serve” after a fault. If the replayed service is then faulty or loses a normal rally, that later service is scored in the ordinary way.

Readiness belongs to the designated receiver

In doubles, Law 11.1.4 identifies the player diagonally opposite the server as the receiver. Law 9.5 allows both partners to take any positions within their respective courts during delivery provided they do not unsight the opposing server or receiver.

Law 9.4 speaks of an attempted return by the receiver. A partner's movement is not automatically proof that the designated receiver was ready. If the service is live and the receiver's partner hits it, Law 13.2.3 makes that a fault. In an alleged early-service case, the umpire should first decide whether the designated receiver was ready and whether a Law 14.2.1 let had already occurred.

The umpire decides readiness; IRS does not

BWF ITTO 5.4.3 tells the umpire to watch the receiver especially when a Service Judge is appointed. The Service Judge's assigned service-law responsibility is the server's compliance with Laws 9.1.2–9.1.8; receiver readiness remains with the umpire.

Under Law 17.5 and ITTO 2.4, the responsible official's decision on a point of fact is final. The Instant Review System is for line-call challenges, not a replay review of readiness or racket movement. An appeal about how the law was applied must be raised before the next service; only an unsatisfied appeal on a question of law is referred to the Referee under Law 17.6.8.

A player may call the let in self-officiated play

Law 14.1 allows a player to call a let when there is no umpire. The receiver should stop immediately, identify unreadiness and replay with the same server. Playing an attempted return and waiting for the outcome is inconsistent with Law 9.4.

The BWF Laws do not prescribe a universal gesture or a special dispute procedure for informal play. If players cannot agree on the fact, use the competition organiser's appointed procedure; do not invent a point award that Law 14 does not provide.

The receiver is still towelling

Situation: the receiver is turned away at courtside, has not taken the receiving position and makes no attempt when the server delivers.

BWF Version 5.0 (2) ruling: let under Laws 9.4 and 14.2.1. The last server serves again at the same score. If the receiver was unduly delaying, the umpire can address that separately under ITTO 5.10 and Law 16.7; the server cannot cure the delay by serving early.

The receiver says “wait” but swings

Situation: the receiver gestures for more time, then makes a genuine return swing and misses a legal service that lands inside the service court.

BWF Version 5.0 (2) ruling: no receiver-not-ready let. The attempted return deems the receiver ready under Law 9.4, so the normal rally result counts and the serving side wins the point. The earlier gesture does not preserve a conditional claim.

Both players commit a service fault

Situation: the receiver is ready but lifts one foot completely after the server's forward racket-head movement begins. At contact, the whole shuttle is not below the standard 1.15-metre limit.

BWF Version 5.0 (2) ruling: let under Law 14.2.2 because receiver and server are both faulted during service. No point is scored and the last server serves again. This is not a receiver-readiness let.

The Time Clock reaches 25 seconds

Situation: in a BWF match using the ITTO Version 8.0 Time Clock, the receiver is still walking back from a towel break at expiry while the server has been in position and ready.

BWF ITTO Version 8.0 ruling: the umpire reminds the receiver that play must be continuous and applies Law 16.7 if necessary. Expiry is not an automatic point, and the server must still wait for the umpire's management rather than deliver to an unready receiver.

Six claims to avoid

• “The receiver must touch the shuttle to count as ready.” Law 9.4 requires only an attempted return.
• “Any movement proves an attempted return.” Intention and the observed action are factual questions; a flinch or avoidance movement is not automatically a stroke.
• “A raised hand guarantees a let.” It is evidence of unreadiness, but it does not excuse undue delay or override an actual attempted return.
• “The server may punish delay with a quick serve.” Delay is managed by the umpire under ITTO 5.10 and Law 16.7.
• “Every match has a 25-second serve clock.” The ITTO timing applies only when the Time Clock tool is in use.
• “A let changes the server or service court.” The score stays unchanged and the last server serves again.

Governing-body sources and effective versions

• Badminton World Federation — BWF Statutes Section 4.1, Laws of Badminton, Version 5.0 (2), in force 26 April 2025 — Definitions and Laws 9.1–9.5, 11.1.4, 13.1–13.2.3, 14, and 16–17.
• Badminton World Federation — BWF Statutes Section 4.1.1, Instructions to Technical Officials, Version 8.0, in force 17 November 2025 — Instructions 2.4, 5.4.3, 5.10.1–5.10.9 and 7.2 (BWF-issued document copy hosted by Badminton Denmark).

Checked on 25 August 2026 against the BWF playing laws and the later BWF technical-official instructions above. Standard rulings use Section 4.1 Version 5.0 (2); the 25-second procedure is limited to matches using the ITTO Time Clock. Competition regulations, a tournament prospectus, domestic rules and specific Para badminton instructions may supplement the baseline within their stated scope.