Match centreLoading fixtures…
Two fictional batters run hard between the wickets during an evening chaseStumpScopeIndependent cricket coverage

Rankings & Guides · Global / English

What Is the Best Strategy for Chasing in Cricket?

Stay close enough to the rate that later hitting remains realistic, while spending wickets only where the expected scoring return justifies the risk.

01A chase is managed with four live resources: runs needed, legal balls left, wickets left and future bowling difficulty.
02Cricket notation 7.2 means seven overs and two balls, not 7.2 decimal overs.
03Required run rate is incomplete unless read beside wickets, batter quality and bowlers remaining.
04A phase target should specify both runs and an acceptable wicket cost.
05The weakest over on paper is useful only when a batter at the crease can exploit its matchup.
06After a wicket, the side should recalculate rather than automatically stop scoring or attack immediately.
07DLS uses both overs and wickets as resources, so live official par information matters during rain risk.
08The best finish leaves a task matched to the batters and bowlers actually remaining, not an arbitrary last-five-over number.

The StumpScope answer is to keep the chase inside the scoring range of the resources still available. Track runs needed, legal balls left, wickets left and the difficulty of the bowlers remaining. Score steadily enough that the finish suits the batters you expect to have at the crease; spend wickets when the matchup return justifies the risk; and recalculate after every over, wicket, bowling change or interruption. A chase plan is a moving allocation problem, not one fixed required-rate line.

The short answer

Start with exact arithmetic. The target is one more than the opposition's completed total unless a competition rule or revised target applies. Runs needed equal target minus current score. In standard six-ball cricket, required run rate equals runs needed multiplied by six, divided by legal balls remaining. Cricket notation is not decimal: 7.2 overs means seven completed overs and two balls, or 44 legal balls. Wides and no-balls add to the score but do not use one of the six valid balls under MCC Law 17, so a chase can gain a run without losing a delivery.

Know the exact chase state

Required rate describes speed, not difficulty. Eight an over with nine wickets and several favorable matchups is different from eight an over with three wickets and the best bowlers returning. Add three columns to the scoreboard: recognised batting resources, boundary options against the current bowler and overs still owed by each bowler. A rising rate can be acceptable when weaker overs are reserved; a flat rate can be dangerous when the strongest death pair remains. Wickets have value because they permit risk, but that value expires when balls run out.

Required rate is not the whole problem

Map the bowling inventory before the chase begins and update it at every change. Record each bowler's overs left, likely phase, stock ball, field and matchup against current and incoming batters. The best bowling order in cricket tries to preserve high-control overs for pressure, so a chasing side must not assume relief will arrive automatically. If the leading seamer has two overs left and the fifth bowler has one, the next partnership can decide whether to absorb, rotate or attack. The greatest fast bowlers of all time reduced scoring options; survival against them mattered only if another over offered a real return.

Map the bowlers still to come

Divide the chase into review blocks, not rigid mini-matches. Each block needs a run range and a maximum acceptable wicket cost. In a 50-over chase, five-over checks may be useful; in T20, two- or three-over checks react faster. A target of 28 to 34 runs with no more than one wicket is more informative than 'win the powerplay.' If the pair scores fewer but faces the opponent's strongest overs, the plan may still be healthy. If it scores the number through uncontrolled edges and loses two batters, the headline rate hides damage.

Set phase targets with wicket budgets

Partnerships work best when roles are complementary and temporary. One batter may attack pace while the other targets spin; one may protect a difficult over while the partner preserves strike for the next matchup. Both still need scoring options, because a permanent anchor can push all risk onto the other end. The greatest batsmen of all time had broad methods, but a chase still rewards the option that fits today's bowler, field and target. Decide who attacks the current field, how strike should be managed before the over, and what changes after a boundary or wicket. Running hard converts good placement into twos and prevents the field from controlling the pair without a risky shot.

Build partnerships with different roles

Use the powerplay to acquire runs at a wicket cost the target can afford. A modest chase does not require reckless boundary hunting, but a large T20 target cannot be rescued by keeping ten wickets while falling far behind. Read the best powerplay field settings: gaps inside and only the permitted riders create scoring options, but the new ball may also swing or seam. Choose shots against the bowler's actual length. The best T20 fast bowlers punish premeditated aggression; the response is selective intent, not passive survival.

How to use the powerplay

In the middle overs, prevent dot-ball clusters and choose attack windows. Rotation changes strike, disrupts a bowler's line and keeps the required rate from compounding, but singles are not automatically enough. Compare the next four overs: which bowler, boundary side and batter matchup offers the highest expected return? Take lower-risk runs from the stronger over and press the weaker or less favorable matchup before the fielding captain can hide it. The best way to set a cricket field is designed to deny these options, so batters must notice ring depth, protected boundary arcs and the fielder with the weaker pickup or throw.

How to manage the middle overs

Plan the finish backward from bowlers and batters, not from an arbitrary last-five-over target. Ask what rate your likely finishing pair can realistically score against the specific death skills remaining. If the final three overs belong to yorker specialists, the chase may need to move earlier against middle-overs pace or spin. If two weaker overs remain late, preserve a batter who can exploit them. The best death overs field settings protect the planned ball's main arcs, so a finisher needs straight, square and running options rather than assuming every full ball can be hit for six.

How to plan the finish

After a wicket, pause for information rather than surrendering momentum. Recalculate runs, legal balls, wickets, bowler inventory and incoming batter matchup. Set a short recovery block—perhaps the next 12 balls—with a minimum scoring floor and one clear boundary option. A new batter can rotate while the set partner attacks, or reverse roles if the bowler matchup says so. Two quiet balls to read conditions can be rational; two quiet overs by habit may make the required rate unmanageable. The goal is restored control, not the appearance of calm.

What to do after a wicket

ODI and T20 chases spend resources differently. An ODI gives more time for partnerships, bowling spells and surface change, but dot-ball pressure can accumulate across longer middle phases. T20 leaves less recovery time, so maintaining a viable rate earlier is more important and one high-return over can reshape the equation. The best ODI fast bowlers may attack with a new ball twice under the format's ball arrangements, while T20 attacks concentrate four-over quotas. Use the current competition conditions rather than importing one format's phase plan into another.

How ODI and T20 chases differ

A Test chase adds time and draw probability. The team may need to choose among winning, drawing and avoiding defeat as pitch behavior changes. Runs needed and wickets remain central, but overs available, light, weather and the ability to survive particular bowlers can dominate. A fourth-innings rate that looks low in limited-overs terms may be difficult on a deteriorating surface. The best spin bowlers of all time made time itself part of the pressure. Set session goals with wicket costs, then reassess when the ball, pitch or result boundary changes.

How a Test chase differs

When rain threatens a limited-overs chase, follow the official DLS target and par information. ICC material explains that overs and wickets interact as resources; a side at the same run rate can be in a different position after losing wickets. Know the minimum-over requirement and monitor the scoreboard, but do not publish or act on a guessed par score. If an interruption looks imminent, losing a wicket can materially change the official position, yet freezing completely can leave the score short. The current batter pair needs the exact live number from officials and scorers.

Rain, DLS and live par scores

Common mistakes include treating required rate as the only variable, saving wickets beyond the point they can be used and attacking the nominal weakest bowler with the wrong batter. Teams leave every boundary for the final overs, ignore remaining bowler quotas, or react to one dot with a low-percentage shot. They confuse 12.3 overs with a decimal, fail to update after wides and no-balls, and use a pre-match phase target after wickets or rain has changed the chase. Another error is copying a famous finisher's tempo without that player's options, surface or matchup.

Common chasing mistakes

Use a seven-part check at the end of every over: exact runs and legal balls; wickets and batting depth; current required rate; next two bowlers and their remaining quotas; current pair's best matchups; the next review-block run and wicket range; and any DLS or weather change. Before each ball, reduce it further: expected delivery, safest scoring zone, boundary option and running call. The best strategy for chasing in cricket keeps the future task realistic without wasting present opportunities. Finish the target when it is available; do not save resources for balls the Laws will never return.

FAQs

Frequently asked questions

What is the best strategy for chasing in cricket?

Keep the required rate within the scoring range of the batters and bowlers still to come, while preserving enough wickets to use the final overs. Recalculate after every over, wicket, bowling change and interruption.

How is required run rate calculated?

For six-ball overs, multiply runs needed by six and divide by legal balls remaining. Use balls, not decimal over notation, and read the result beside wickets and remaining bowlers.

Should a chasing team save wickets for the end?

Only while the future rate remains realistic for the batters and bowlers left. Saving wickets while the required rate moves beyond the team's scoring range wastes those wickets.

How should a team recover after losing wickets in a chase?

Recalculate the rate, identify the next attackable bowler, assign one batter to stabilise and one to keep scoring, and set a short recovery block. Do not let rebuilding become several overs of avoidable dots.

How does rain change a cricket chase?

DLS can revise targets from overs and wickets as resources. Follow the official live target or par score, protect wickets when an interruption is near, and never rely on a guessed par calculation.

Editorial note

This report summarizes named sources in original language. It does not reproduce proprietary commentary, imagery or score feeds.