CricPulse
Declaration Calculator
Enter the overs left in the match, your lead, and how fast you are scoring. See the run rate you would leave the opposition to chase — declaring right now, or at your recommended declaration point.
Scoring a Match? Let the App Keep Count
CricPulse scores ball by ball and keeps run rates and player stats up to date as you go. Free on iOS and Android.
What the Declaration Calculator Does
Declaring is entirely the batting captain’s judgement call, and it always trades two things against each other: runs you could still score, against overs your bowlers need to take ten wickets. This calculator does the arithmetic behind that trade-off. Enter the overs left in the match, your current lead, and how fast you’re scoring, and it shows the run rate you’d leave the opposition to chase — both if you declare this instant, and at the point where you’ve batted as long as possible without cutting into your bowlers’ minimum overs.
New to the rule itself? Read how declaration and forfeiture work under Law 15 first — this tool assumes you already know when a declaration is legal and focuses purely on the timing decision.
The Two Scenarios, Explained
- If you declare right now: uses your current lead and the overs left in the match after subtracting what you’ve already faced this innings. This is your position exactly as it stands.
- Recommended declaration point: projects your score forward at your current run rate for as long as you can bat while still leaving your chosen number of overs for bowling, then shows the required rate at that later, higher score.
The Core Formula
Required run rate for the opposition = your lead ÷ overs you leave them to bat
Everything else — the projected extra runs, the projected lead, the “fully safe” lead figure — is built from that one relationship, just evaluated at two different points in time (now, and at your recommended declaration).
A Worked Example
Say there are 60 overs left in the match, you want to leave your bowlers a minimum of 20 overs, your team currently leads by 30 runs, you’ve scored 120 for the loss of a few wickets in 20 overs this innings (a run rate of 6.00/over), and you estimate the opposition could realistically chase at 5.5 runs/over on this pitch. You have 20 more overs available to bat before you must declare to protect the 20-over bowling minimum. Batting those out at your current rate adds roughly 120 more runs, pushing your lead to 150 — which the opposition would then need to chase at 7.50 runs/over in the 20 overs you leave them. That clears your 5.5 runs/over estimate comfortably, so the calculator marks it safe.
Track Your Run Rate Automatically with CricPulse
CricPulse keeps your live score, overs faced and run rate visible ball by ball while you score a multi-day or timed match, so the numbers this calculator needs are never a guess. It also supports hit wicket as a dedicated dismissal type, correctly crediting the bowler the moment it happens. Score your match with CricPulse — free on iOS and Android.
Related Tools
Setting up a run chase once the declaration lands? Check the required run rate calculator or the win probability calculator. Wondering whether the follow-on applies instead of a declaration? Try the follow-on calculator.
Frequently Asked Questions
How do I decide how many overs to leave for bowling? +
There's no universal rule — it depends on your bowling attack and the pitch. Many club declaration leagues and representative fixtures work on a rough guide of leaving at least 18-20 overs to bowl out a recognised batting line-up, but a weaker or more defensive opposition may need fewer. Enter your own judgement in the "overs to leave for bowling" field rather than treating any single number as fixed.
What counts as a "safe" run rate to leave the opposition? +
It depends entirely on the opposition's batting depth and how the pitch is playing. A rate the calculator marks "safe" (at or above your own chase-rate estimate) means the opposition would need to bat better than you consider realistic for them to win outright — it does not mean they can't bat out the overs for a draw, or that a genuinely strong batting side couldn't still chase it.
Does this work for limited-overs cricket? +
No. Declarations only exist in Law 15 of the Laws of Cricket, which applies solely to matches where each side is scheduled to bat in two innings — traditional timed cricket, first-class and Test matches. In a fixed-overs league match, the innings ends when the overs run out or the side is bowled out, so there's nothing to declare.
What does "your team's current lead" mean if this is your first innings? +
If the opposition hasn't batted yet, your "lead" is simply your own total, since there's nothing yet to compare it against — enter your current score as the lead. Once both first innings are complete, your lead becomes your team's total runs scored across the match minus the opposition's, which the calculator uses as the starting point for the second-innings declaration.
Why does the calculator show two different scenarios? +
The "declare right now" card tells you where you stand at this exact moment. The "recommended declaration point" card projects forward using your current scoring rate to show what happens if you keep batting up to the point where you'd still leave your chosen number of overs for bowling. Comparing the two shows whether batting on actually improves your position or just eats into bowling time for no real gain.
Can the opposition chase a target the calculator marks "risky"? +
They still have to actually do it — a low required run rate makes a chase realistic, not automatic. Wickets, required-rate pressure as overs run down, and a collapse can all still turn a "risky" target into a game you win. Treat a risky verdict as a signal to reconsider your declaration timing, not as a guaranteed loss.
Score Your Next Match with the App
Ball-by-ball scoring, live stats, offline support, and instant sharing. Free to download on iOS and Android.