Declaration and Forfeiture in Cricket: The Run-Chase Bargain, and What the Scorer Must Record

Most cricketers can explain a declaration in one sentence: the batting captain closes the innings early. Far fewer can explain forfeiture, mostly because it is rare enough that a lot of players go a whole career without seeing one. The two get lumped together constantly, and the confusion is understandable — both end an innings without the normal ten wickets falling, both require the captain to tell someone, and both exist for the same underlying reason: time is a resource in cricket, and sometimes making a match happen at all means one side deliberately giving some of it up.

This guide covers what Law 15 actually says, the practical mechanics of the “forfeiture bargain” that turns a rain-wrecked weekend into a finish, a genuine example of each mechanism from first-class cricket, why almost none of this applies to your Saturday 40-over league match, and — the part no rules page covers — precisely what a scorer records when an entire innings is given up before a ball is bowled in it.

Two Different Things, One Law

Law 15 of the Laws of Cricket covers both mechanisms, and the distinction between them comes down to timing: a declaration ends an innings that has already started, while a forfeiture gives up an innings that has not started yet.

Both require the captain to notify the opposing captain and the umpires, and in both cases the decision is final the moment it is announced — a captain cannot declare, watch the opposition struggle, and then withdraw the declaration. The same applies to forfeiture: once notified, it cannot be reversed.

One restriction matters more than any other: Law 15 applies only to matches in which each side is scheduled to bat in two innings. It does not apply, in any form, to limited-overs cricket. That single sentence explains why this entire topic feels unfamiliar if the only cricket you play is a weekly 40- or 50-over league match — more on that below.

Why a Captain Declares

A declaration is a time-management tool for the batting side. The usual reasons:

• Setting a target with enough time to bowl the opposition out. A team batting first in a two-innings match does not need all ten wickets to fall — once the captain judges the total is competitive and there is enough time left in the match to dismiss the opposition twice (or once, in the second innings), continuing to bat is just eating into the time available to win.
• Weather or an interruption compressing the time left. If the match has lost sessions to rain, a captain may declare earlier than planned simply because there is no longer time to bat out a normal-length innings and still force a result.
• Managing the second innings of a lead. A side batting last in its own second innings may declare to leave itself the maximum bowling time against a target it considers unreachable.

None of this requires the other captain’s agreement. Declaration is entirely one-sided — the batting captain’s call, and the batting captain’s alone. It is a genuine captaincy decision in the same family as the choice covered in our toss decision framework — reading conditions, time, and the state of the match rather than following a fixed rule.

Why a Captain Forfeits — The Run-Chase Bargain

Forfeiture is different in exactly this respect: on its own, it looks like giving away half a match for nothing. It only makes sense as part of an agreement between both captains, and the agreement is almost always the same shape. Rain has taken enough time out of the match that a normal finish — bat, bowl, bat, bowl — is no longer possible. Both sides would rather have a competitive run chase in the time remaining than a match that fizzles into a draw because nobody could complete two full innings each. So the two captains strike a deal: one side forfeits an innings it was never going to have time to use anyway, and the game is restructured into a single run chase.

A genuine example, cited widely as the clearest modern illustration of the mechanism at its most sporting: in May 2015, Kent and Glamorgan’s County Championship match at Canterbury had been so badly affected by rain that a normal finish was impossible. Both captains agreed to “sporting declarations” to manufacture a chase — Glamorgan declared their second innings closed on 64 for 3, and Kent declared in reply on 60 for 1, setting Glamorgan a target of 304 to win in the time left. No forfeiture was needed there; both sides simply declared early by mutual understanding. That is the lighter-touch version of the same idea, and it happens far more often than a formal Law 15 forfeiture.

The formal version — an actual forfeited innings — is rarer, and the most famous instance carries a warning alongside the explanation. In the fifth Test between South Africa and England at Centurion in January 2000, three days were lost to rain. To engineer a finish, South Africa’s captain Hansie Cronje declared South Africa’s first innings on 248 for 8, England’s captain Nasser Hussain then declared England’s first innings at 0 for 0 — effectively forfeiting it — and South Africa forfeited their second innings, leaving England to chase 249. England got there, winning by two wickets. At the time it was celebrated as a wonderful piece of sportsmanship that saved a dead match. It later emerged that Cronje had arranged the result for a payment from a bookmaker, a revelation that became central to the match-fixing scandal that ended his career. The cricketing mechanism he used was entirely legal under the Laws — plenty of forfeiture bargains before and since have been exactly as sporting as they looked. That one specific match simply was not, and it is worth knowing the full story before citing it as an example of good spirit.

The practical lesson for club cricket is the ordinary one: neither captain can be forced into a forfeiture bargain. It is an offer, not an obligation, and a captain who thinks the proposed target is unfair — or who is happy to settle for a draw — is entitled to simply say no.

Timed vs Limited-Overs Club Cricket — Why This Rarely Comes Up on a Saturday

If your own cricket is a weekly 40-overs-a-side league fixture, you have almost certainly never seen a Law 15 declaration or forfeiture, and there is a simple reason: Law 15 does not apply to limited-overs cricket at all. A standard club league match — the format covered in our guide to league bonus points — is single-innings and overs-limited by its own competition rules, not by a captain’s discretion. There is nothing to declare, because the innings ends when the overs run out or the side is bowled out, not when a captain decides it has.

Declaration and forfeiture belong to timed, two-innings cricket — traditional Saturday “friendly” fixtures where each side bats one long innings with no overs limit, school and university cricket, and first-class and Test cricket. Plenty of clubs still play this way, particularly for mid-week or representative fixtures, alongside their overs-limited league programme. If your club runs both formats, it is worth being clear with new players about which one applies on a given day — someone used to the league’s fixed-overs finish can be genuinely confused watching a captain declare with wickets in hand.

What the Scorer Must Record

This is the part every generic rules page skips, and it is where a scorebook actually earns its keep. If you need a refresher on how a normal innings appears on the finished card first, our guide to reading a cricket scorecard covers the standard layout that a declared or forfeited innings then has to depart from clearly.

For a Declaration

• The score and wickets at the moment of declaration, exactly as they stood — nothing is added or adjusted.
• The overs bowled in that innings, stopping at the point of declaration, not projected forward.
• ”Innings declared closed” against the total, with the time. This is what tells anyone reading the book later that the innings ended by choice, not by ten wickets falling.
• Not-out batters stay not out. A declaration does not create a dismissal — every batter still at the crease is recorded not out, and counts as such for their own batting average, exactly as they would if the innings had ended by close of play.

For a Forfeiture

• The innings is recorded as forfeited, with zero of everything — no runs, no overs, no balls bowled, no wickets. Nobody batted, so nobody’s figures are touched.
• No individual batting or bowling entries exist for that innings at all — not “not out,” not “did not bat” in the usual sense, but a whole innings that the scorebook shows as forfeited outright. This is the detail that trips scorers up the first time they see it: there is a genuine difference between a batter who didn’t get to the crease because the innings ended (recorded “did not bat”) and an innings that never happened because it was forfeited (recorded against the innings itself, not any individual).
• The time and method of notification — which captain forfeited which innings, and when the umpires were told. Once notified, it is irreversible, so this entry is the permanent record of the moment that happened.
• How the match result is then reached. With one side’s innings forfeited, the match usually becomes a straightforward chase of a target derived from the innings actually played — but the exact target-setting method, and how a resulting win, loss or draw is scored for league or competition points, is down to your competition’s own regulations. If your competition runs a points table alongside its two-innings fixtures, the same result feeds into it the way any other match would — the points table calculator can still rank the standings once the result is settled. Check your own regulations before assuming the professional-game pattern applies to your league or representative fixture.

The forfeited-innings distinction matters beyond the scorebook, too. If your club tracks end-of-season batting and bowling averages, a forfeited innings contributes nothing to anyone’s figures — it is not an innings played, so it cannot help or hurt a qualifying average the way a low declared score or a not-out innings would.

A Worked Example

Take a hypothetical two-day representative fixture. Team A bats first and reaches 180 before stumps on day one. Overnight rain wipes out the entire morning of day two, leaving barely enough time for a short run chase and nothing close to enough time for two more full innings. The captains agree a forfeiture bargain:

• Team A, first innings: 180 all out (or declared, if they chose to close it rather than lose all ten wickets) — recorded normally, in full.
• Team A, second innings: forfeited — recorded as forfeited, zero across the board, no player entries.
• Team B, first innings: forfeited — recorded as forfeited, zero across the board, no player entries.
• Team B, second innings: chasing 181 to win in the time remaining — scored as a normal innings, with the target and required rate tracked as the session goes on.

The scorebook ends up with two innings that read as a completed match’s worth of cricket, and two entries that read “forfeited” with nothing beneath them. Anyone reading the book six months later should be able to reconstruct exactly what happened and why from those four lines alone.

How CricPulse Helps

A forfeited innings is one of the easiest things to get wrong in a paper scorebook, precisely because nothing happens in it — there is no ball-by-ball prompt to remind anyone to write it down. CricPulse’s innings-transition flow makes forfeiture and declaration explicit choices rather than blank pages left for someone to interpret later, so the record is unambiguous the moment the captains agree it. Score your match with CricPulse and a forfeited innings is as clearly logged as a completed one.

Frequently Asked Questions

Can a captain be forced to accept a forfeiture bargain?
No. Forfeiture requires the forfeiting side’s own captain to choose it for their own side’s innings. Nobody can compel the other captain to offer or accept one — a side that would rather play on, or settle for a draw, is entitled to do so.

Does a forfeited innings count toward a player’s season average?
No. Because nobody bats or bowls in a forfeited innings, there are no individual figures to record against it, so it neither helps nor hurts anyone’s batting or bowling average for the season.

Is forfeiting the same as losing because your team didn’t turn up?
No. A forfeited innings is a deliberate, agreed decision made during an ongoing match that is otherwise being properly played. A side failing to field a team at all is a completely separate situation, usually covered by your competition’s own default/walkover regulations rather than Law 15.

Can you declare or forfeit in a standard club 40- or 50-over league match?
Not under Law 15 — it explicitly does not apply to limited-overs cricket. Some leagues build their own optional early-finish or mutual-agreement provisions into their playing conditions for extreme circumstances, but that is a competition rule, not a declaration or forfeiture in the Law 15 sense. Check your own league’s playing conditions rather than assuming either applies.

What happens if a forfeiture agreement falls through partway through the discussion?
Nothing is binding until a captain actually notifies the opposing captain and the umpires of a decision to forfeit. Talking about a possible arrangement commits nobody — but once the notification is given, it is final and cannot be withdrawn.

Why doesn’t declaration exist in T20 or ODI cricket?
Because the innings length is already fixed by the format’s overs limit rather than by the batting captain’s judgement. Law 15 is explicit that it does not apply to any form of limited-overs cricket, so there is nothing for a captain to declare — the innings simply runs until the overs or the wickets run out.