How to Chase a Big ODI Total Policy & Terms

A chase is a budget of two resources: overs and wickets. You have 50 overs (300 balls) and 10 wickets, and the target sets the required run rate (RRR): the runs still needed divided by the balls left. Chasing 320, that is 6.4 an over from ball one. The trap is that the number does not sit still. Every dot pushes it up for the overs that remain, and the engine recomputes it after every single ball.

The mistake beginners make is watching only the run rate. Wickets in hand are the resource that decides whether you can accelerate later, and inside the simulator they directly govern how hard your batters are willing to push.

On every delivery of a chase, The Chase looks at the required rate and at how many wickets you have left, and lets the two together decide how hard your side pushes. When the required rate climbs above a comfortable clip, a full batting card is allowed to attack hard and accept the extra risk that comes with it; a side down to the tail gets only a fraction of that licence, because slogging the last pair out loses the game outright. When the required rate falls well below a run a ball, the engine does the opposite: it dials scoring and risk down, so your batters protect wickets and knock the runs off in singles rather than holing out with the game won.

This is why the same RRR of 7 is a good chase with eight wickets in hand and a bad one with three. The number on screen is identical. The licence the engine gives you is not.

Powerplay (overs 1-10). The engine gives the batting side a flat scoring lift in the first ten overs, modelling the fielding restrictions and the hard new ball. You are not trying to win here; you are trying not to lose. Arrive at over 10 no more than a couple down and near the rate and every option stays open.

Middle (overs 11-39). No phase bonus, and this is where chases are quietly won or lost. Keep the required rate from climbing while losing as few wickets as possible. The engine also models a genuine consolidation effect: lose two wickets in quick succession and a strong, sensible batting side automatically cuts its risk and rebuilds, while a weaker side keeps crumbling.

Death (overs 40-50). Now the engine opens the throttle, but only in proportion to wickets in hand. A full card slogs hard and risks a lot, a side several down lifts only a little, and the tail barely lifts at all. In the closing overs, a side with wickets still standing finds an extra gear as the finish line nears. Spend your wickets early and there is simply nothing left for the engine to accelerate.

Drift through the middle overs a run below the rate and it feels fine, the scoreboard ticks. But every slow over is borrowed against the death, and the death only pays back if you kept the wickets to spend there. A required rate of 7 with eight in hand at over 40 is a chase you win; the same 7 with three in hand is one you lose, because the engine will not let a near-exposed tail take the risks the target needs.

Underneath the chase logic, every ball is a matchup between the striker's batting profile and the bowler's, resolved with a shared run-and-wicket model (see how a single delivery is decided). A miserly bowler builds dot-ball pressure that also fetches wickets; the surface rewards the bowler whose type suits it; and a batter's real pace-versus-spin aptitude tilts both survival and scoring. Elite batting line-ups even carry a soft floor that makes them very hard to bowl out cheaply, which is part of why the homepage asks whether you can chase 380 rather than 280.

Take the chase yourself in The Chase, and see the same run-and-wicket model at the other end of the format in can you chase 380?