Running Between Wickets: The Yes, No, and Wait System
How the yes/no/wait calling system works between batting partners, who has the primary responsibility for calling on each side of the wicket, why miscommunication is the most common cause of run-outs, the role of backing up (the non-striker moving before the ball is bowled), the call hierarchy when both batsmen are calling simultaneously, and how elite partnerships develop running between wickets as a skill.
The Three Calls
Running between wickets operates on three calls. 'Yes' means: complete the run — both batsmen sprint. 'No' means: do not run — the batsman who has struck the ball or is nearest to the call-side has judged the fielding situation unfavourable. 'Wait' is the holding call — hold your position, do not cross, I am assessing whether a run is available. 'Wait' should be followed by either a 'yes' or 'no' as quickly as possible once the fielding situation clarifies. The danger of 'wait' is that the hesitation can leave both batsmen stranded mid-pitch — the batting partnership should default to quick, committed calls that eliminate wait wherever possible. A slow, uncertain call (that resolves to 'no' after 2 seconds) is often worse than an early 'no' because it takes both batsmen away from their safe ground without the commitment needed to complete a run.
Primary Calling Responsibility
The conventional responsibility for the primary call is: the batsman who has struck the ball is responsible for calling on the off side (when the ball goes to the off side — toward cover, point, or extra cover); the non-striker (the batsman at the other end) is responsible for calling when the ball goes behind the striking batsman (behind square on the leg side, or behind the stumps). The reasoning: the striking batsman can see the off side clearly as they play the shot; the non-striker has a view of what happens behind the striking batsman that the striker cannot see. When the ball goes straight or to mid-off/mid-on, the striking batsman takes primary responsibility as they can see the fielder's movement clearly.
Backing Up
Backing up refers to the non-striker moving forward (away from their crease) as the bowler delivers — anticipating a run and reducing the distance to be covered. A non-striker who backs up well can convert a marginal run into a comfortable one by starting the running movement before the ball is played. The legal requirement: the non-striker cannot leave their crease before the ball leaves the bowler's hand — leaving early is the act that allows a Mankad (run out of the non-striker by the bowler). Good backing up stays within the legal boundary (leaving as the bowler delivers, not before) while gaining the maximum ground advantage. A backing-up non-striker who sees a 'no' call from their partner must scramble back to their crease — the farther they have backed up, the more scrambling is required on a 'no' call.
Frequently asked questions
What happens if both batsmen call simultaneously?
When both batsmen call simultaneously (both saying 'yes' or both saying 'no' at the same moment), the batting partnership must have a pre-agreed hierarchy for resolving the conflict. The convention is that the striker's call takes precedence for off-side deliveries (the striker can see the off side); the non-striker's call takes precedence for deliveries behind the striker. If both call 'yes' when one should have called 'no', the result is often a run-out — the batsmen are crossing mid-pitch when the fielder's throw arrives. Most batting partnerships develop their calling conventions through experience — the understanding of who defers to whom becomes automatic in established partnerships.
How important is running speed to between-wickets success?
Running speed matters significantly but is less important than decisiveness and calling quality. A slow runner who calls early and commits fully to the call will complete more runs than a fast runner who hesitates. The time lost in hesitation (the fraction of a second both batsmen spend assessing the situation after a 'wait' call rather than already sprinting) is often more costly than the speed advantage of a faster runner. Elite fielding sides exploit hesitation specifically — fielding quickly enough that the batsmen's delay (not their running speed) becomes the margin for the run-out. This is why 'back your call' is one of the most repeated instructions in batting coaching: a committed wrong call (where both batsmen sprint immediately) sometimes succeeds where a correct call hesitated over results in a run-out.
Are there penalty runs for slow running or not grounding the bat?
There are no penalty runs specifically for slow running between wickets — the only consequence is potential run-out if the batsmen are too slow to complete the run before the stumps are broken. However, a batsman who does not ground their bat (or body) behind the crease line before the stumps are broken at that end is run out — the bat must cross the crease line before the wicket is broken, not the batsman's body. The traditional instruction 'run your bat in' (sliding the bat along the ground toward the crease to ensure it crosses the line as early as possible) is the technique to maximise the distance advantage in close run-out decisions. A batsman who dives with their body crossing the line but their bat in the air is run out if the stumps are broken at that moment.