ThisCalculator

Everyday

Strike Back Codes: Meaning & Use in Cricket

Updated · Standard formula, shown below

The calculator for this page is switched off while it is checked. The formula is below, and the worked example in the article shows how to use it by hand.

Strike back codes are a set of predefined numeric or alphanumeric signals used in cricket to communicate fielding changes, bowling plans, and tactical instructions between the captain, bowler, and fielders without the opposing team understanding. You enter the code into the calculator below to convert it into a specific fielding position or bowling plan, and it returns the corresponding instruction and its meaning.

Formula

The calculator does not use a mathematical formula; it uses a lookup table that maps each code to a predefined tactical instruction. The table is created by the team management before a match and is unique to that team. The mapping is:

Code → Instruction

Where Code is the numeric or alphanumeric signal (e.g., 42, 7A, 3-2) and Instruction is the specific fielding change, bowling plan, or defensive/attacking adjustment it triggers. The calculator above uses a sample mapping for demonstration; in reality, each team has its own private table.

Worked Example

Using the default code 42 from the calculator, the lookup table returns:

  • Code 42 → Slip cordon to 3, mid-off back

This means the captain wants three slips (instead of the usual two) and the mid-off fielder to move deeper. The bowler sees the code, nods, and the fielders adjust accordingly. The calculator shows this exact instruction for the default value.

Background: Why Teams Use Strike Back Codes

Cricket is a game of constant tactical adjustments. The captain and bowler need to change field placements, bowling lines, and lengths based on the batsman’s strengths, the pitch conditions, and the match situation. However, openly discussing these changes at the bowling mark can tip off the batsman, who might adjust his stance or shot selection. Strike back codes solve this by allowing the captain to convey complex instructions with a simple hand gesture or a number shouted from the field.

The term “strike back” likely originates from the idea of “striking back” at the batsman with a surprise plan. The codes are typically agreed upon during team meetings before a match or series, and each player memorizes the table. They are used across all formats—Test, ODI, and T20—though they are more prevalent in the longer formats where field placements are more varied.

How Strike Back Codes Work in Practice

The system works through a simple process:

  1. Pre-match planning: The captain, coach, and senior bowlers decide on a set of codes and their meanings. For example, code 1 might mean “bowl a yorker,” code 2 might mean “bouncer,” and code 3 might mean “slip moved to gully.”
  2. Signaling: During the match, the captain or a designated fielder (often the wicketkeeper) gives the code as a hand signal, a number shouted, or a combination of both. The bowler acknowledges subtly, and the fielders adjust.
  3. Execution: The bowler delivers the ball according to the new plan. The fielders remain alert for any further changes.

The codes are usually simple numbers (1-9) or short alphanumeric strings (e.g., 2A, 3B) to avoid confusion. Some teams use colored wristbands or small boards held up by the coach on the boundary, but the most common method is verbal or hand signals.

How to Choose Your Own Strike Back Codes

If you are a club or amateur team looking to implement a similar system, here are some practical steps:

  • Keep it simple: Start with 5-10 codes that cover the most common tactical changes: fielding positions (slip, gully, short cover), bowling types (yorker, bouncer, slower ball), and fielding aggression (attack vs. defensive).
  • Use memorable numbers: Assign codes that are easy to remember. For example, 1 for slip, 2 for gully, 3 for short cover, etc. Avoid using numbers that could be confused with the score or over count.
  • Test in practice: Run drills where the captain gives a code and the fielders react. This ensures everyone is on the same page before using it in a match.
  • Change codes regularly: If you play the same opponents often, change the codes to prevent them from decoding your signals.

Remember, the codes are only effective if the team is well-drilled. A miscommunication can lead to a missed catch or a boundary.

Common Problems and Misconceptions

One common misconception is that strike back codes are a secret language known only to professionals. In reality, many amateur and club teams use simplified versions. Another issue is that codes can become predictable if used too often. Opponents may notice that code 7 always brings the field in, and they can adjust accordingly.

Technical problems also arise:

  • Mishearing: In a noisy stadium, a number shouted from the boundary might be misheard. That’s why many teams use hand signals in addition to verbal calls.
  • Overcomplication: Having too many codes can lead to confusion. A player might forget what code 15 means in the heat of the moment.
  • Opposition decoding: If the same codes are used for an entire series, opponents can decode them by observing patterns. This is why professional teams change codes frequently.

Strike Back Codes vs. Other Communication Methods

Strike back codes are just one of several ways cricket teams communicate. Other methods include:

  • Direct verbal instructions: The captain walks up to the bowler and talks openly. This is simple but can be overheard by the batsman.
  • Hand signals from the boundary: The coach uses a set of hand gestures from the sidelines. This is common in limited-overs cricket, but the batsman can also see these signals.
  • Wristbands: Some teams use colored wristbands that the captain wears; each color corresponds to a specific fielding plan. The bowler sees the wristband and knows the plan. This is less common but used in some professional teams.

Strike back codes are more covert than direct speech and more flexible than pre-set wristbands, making them a middle ground between simplicity and secrecy.

Safety and Fair Play Considerations

Strike back codes are legal under the Laws of Cricket, provided they are not used to waste time or to communicate with a player off the field in a way that violates the spirit of the game. The ICC (International Cricket Council) has regulations about on-field communication, but these codes are generally allowed as they are a form of tactical communication between the captain and players. However, teams must ensure that the codes do not involve any external signals from the dressing room, which is prohibited. Also, the umpires can intervene if they feel the codes are being used to slow down the game or to engage in unfair practices.

Frequently Asked Questions

What is the origin of the term “strike back code”?

The exact origin is unclear, but it likely comes from the idea of “striking back” at the batsman with a new plan. It has been used in cricket for decades, with teams devising their own systems. The term became more popular in the 2000s with the rise of T20 cricket, where tactical variations are frequent.

Can I use strike back codes in a casual game?

Yes, absolutely. Even in a friendly match, you can agree on a few simple codes with your teammates to change field placements or bowling plans. It adds a fun, strategic element to the game. Just ensure everyone remembers the codes.

How do I prevent the opposition from decoding my codes?

The best way is to change your codes regularly, especially if you play the same opponents often. Also, use a mix of verbal and non-verbal signals, and avoid predictable patterns like always using the same number for the same action.

Are there any official strike back codes in professional cricket?

No, there are no universal or official codes. Each team has its own private set, which they keep secret. The codes are part of the team’s internal strategy and are not regulated by cricket’s governing bodies.

What happens if a player forgets a code during a match?

In that case, the player can look to the captain for a repeat signal or use a fallback plan. Good teams practice enough that this rarely happens, but when it does, it can lead to a missed opportunity or a bowler bowling a different delivery than planned.

Related

Formula used
in code | Strike back code | - | 42 | 0
out meaning | Instruction | - | "Code 42: Slip cordon to 3, mid-off back" | 0

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.