Eighty for one becomes 112 all out in under an hour. The commentary calls it a lack of application, the supporters call it a lack of character, and both explanations skip every mechanism that actually caused it.
Proper match analysis treats a collapse as a sequence with identifiable triggers, because almost every one follows a recognisable pattern once you know what to look for.
This guide explains what causes collapses, how to distinguish the different types, which evidence matters, and how teams work to prevent them.
What Counts as a Collapse
There is no official definition, but a usable one is losing a cluster of wickets for a small number of runs.
The common working threshold is four or more wickets for fewer than thirty runs, which separates a genuine collapse from the normal loss of a couple of wickets in a session.
Duration matters as much as the numbers. A collapse is compressed in time, typically occurring inside eight to twelve overs, which is why it feels different from a steady decline.
Position in the innings matters too. Losing the top order cheaply and losing the tail cheaply are different events with different causes, and conflating them produces poor analysis.
The Main Categories
| Type | Trigger | Typical signature |
|---|---|---|
| Conditions-driven | Ball movement or surface change | Multiple edges, similar dismissals |
| Bowling-driven | An exceptional spell | One bowler takes most of the wickets |
| Pressure-driven | Scoring dries up | Loose shots after long quiet periods |
| Tactical | Chasing an unrealistic rate | Dismissals attacking, spread across bowlers |
| Structural | Weak middle order | Same collapse recurs across matches |
| Sequencing | Two set batters out together | Several new batters in at once |
The sequencing collapse is the most misunderstood. When two established batters are dismissed within a short period, the side suddenly has two players at the crease who have faced almost no deliveries, which multiplies the risk for the following overs.
Structural collapses are the most serious because they recur. If the same four positions fail repeatedly in similar circumstances, the problem is selection or technique rather than circumstance.
Evidence Worth Examining
Several specific pieces of information separate real analysis from assertion.
Check the dismissal modes. Five caught behind suggests movement; five bowled or leg before suggests the ball keeping low or turning; a mix of modes suggests pressure rather than conditions.
Check who bowled. If one bowler took five of the six, the collapse was a spell. If six wickets were spread across four bowlers, the batting side caused it.
Check the scoring rate before the collapse began, since a long period without boundaries very often precedes the first wicket in a pressure-driven sequence.
Check what the other side did on the same surface, because a comparable total elsewhere in the match removes conditions as the explanation entirely.
How Collapses Are Prevented
Teams work on this explicitly, and the methods are more practical than the language around character suggests.
- Agreeing a plan to survive a specific bowler’s spell
- Rotating strike to break bowling rhythm
- Avoiding two new batters at the crease together
- Taking a deliberate pause after a wicket falls
- Having a designated rebuilder in the middle order
- Practising scenarios from a poor position in training
- Reviewing whether a target remains realistic
- Protecting a set batter’s strike against the dangerous end
The deliberate pause is the simplest and most effective. Sides that slow the game down after losing a wicket concede noticeably fewer follow-up wickets than those who carry on at the same tempo.
Reading the Dismissal Pattern
Dismissal modes carry more diagnostic information than any other single piece of evidence on a scorecard.
| Pattern | Most likely cause | What to check next |
|---|---|---|
| Caught behind or in the slips | Lateral movement off the surface or in the air | Weather and ball age |
| Bowled and leg before | Low bounce or sharp turn | Day of the match, pitch wear |
| Caught in the deep | Attacking under rate pressure | Required rate at the time |
| Caught at short leg or bat-pad | Spin with extra bounce | Which end, and the footmarks |
| Mixed modes, no pattern | Accumulated pressure | Dot-ball sequence beforehand |
| Run outs among the wickets | Panic and poor communication | Match situation and time remaining |
Run outs appearing inside a collapse are the clearest indicator that the batting side has lost composure rather than simply faced good bowling, because no bowler causes them.
A completely mixed pattern with no common mode is the signature of pressure. When the deliveries causing dismissals are unrelated to each other, the problem is in the decision-making rather than in the conditions.
Conversely, four identical dismissals in quick succession almost always indicate a conditions or bowling explanation, and criticism of the batters in that case is generally misplaced.
Frequently Asked Questions
Are collapses more common now?
They appear more frequent in the long format, largely because batters trained in attacking methods are less practised at absorbing pressure over extended periods.
Is a collapse always the batting side’s fault?
No. Conditions-driven and bowling-driven collapses reflect good bowling or a difficult surface, and treating every one as a failure of application is simply inaccurate.
Why do collapses happen after a long partnership?
Because the batting side has only two set players, and losing both leaves the rest of the order exposed at once with no established partner.
Can statistics predict them?
Partially. Teams track dot-ball sequences and scoring droughts, both of which correlate with wicket probability, but no model predicts a specific collapse.
The Short Version
A collapse is typically four or more wickets for under thirty runs in a compressed period. Classify it by examining dismissal modes, which bowlers took the wickets and the scoring rate beforehand. Conditions, an exceptional spell, accumulated pressure, tactics and squad structure are the five main causes, and only some of them are the batting side’s fault.
Writing Up a Collapse Properly
Name the trigger, identify the type, and state what evidence supports the classification.
That produces an account someone can disagree with on the facts, which is more useful than a verdict about temperament that cannot be tested at all.
The Role of Pressure Build-Up
The most common collapse type is also the hardest to see while it is happening.
Pressure accumulates through dot balls rather than through wickets, and a long sequence without scoring changes a batter’s assessment of risk without anything visible occurring.
Teams track consecutive dot balls precisely because of this, and the probability of a wicket rises measurably once a batter has gone several overs without a scoring shot.
The mechanism is straightforward. A batter who cannot score begins looking for an opportunity, and the delivery they eventually attack is frequently not the right one.
Good bowling sides understand this and will set entirely defensive fields against a struggling batter, accepting that no wicket is likely for several overs in order to create one later.
The counter is equally well understood, which is to take a single at any cost, even a poor one, in order to reset the sequence and transfer the problem to a partner.
Why the Middle Order Matters Most
Collapses concentrate in specific positions, and the reasons are structural.
Openers face the hardest conditions but are selected and prepared specifically for them, and a top order dismissed cheaply by a moving new ball is an understood outcome.
The middle order faces a less obvious challenge, since those players may arrive at any point against any bowler in any situation, and preparation for that is much harder.
When a side loses three early wickets, the players arriving are frequently those with the least defined role, and if they have been selected for their scoring ability the situation does not suit them.
That is why squad structure appears so often in collapse analysis. A batting order with no designated rebuilder will collapse repeatedly in the same circumstances until one is selected.
Collapses by Format
The same word covers quite different events depending on the length of the match.
In the long format, a collapse usually costs the match outright, since there is time for the opposition to build a lead and no realistic way to recover two sessions of lost ground.
In fifty-over cricket a collapse is survivable, because a side with overs remaining can rebuild and still reach a competitive total, which is why the format retains its distinctive shape.
In the shortest format a collapse is frequently the result of correct decision-making, since a side chasing a high target must accept risk and several dismissals is the expected cost.
Judging a short-format collapse by the standards of the long format is therefore a basic analytical error, and it is made constantly in broadcast commentary.
The correct question in each case is whether the risk taken was appropriate to the situation, not whether wickets fell quickly.
What Teams Do in the Dressing Room
The response during and after a collapse is more systematic than it appears from outside.
During one, the usual instruction is to reduce tempo and survive a set number of overs, with scoring explicitly deprioritised until two batters are established.
Padded-up players are often told to prepare differently, taking longer over their routine so that they arrive settled rather than rushed.
Afterwards, analysts review each dismissal individually, identifying whether the delivery was good, the shot was poor, or the situation made the risk reasonable.
That review produces a classification rather than a verdict, and the same collapse frequently contains dismissals in all three categories.
Coaches then address only the genuine errors, because treating every wicket in a collapse as a mistake damages confidence without improving anything.
A Step-by-Step Method
For anyone wanting to analyse a collapse properly, the sequence below covers most cases.
Start by establishing the exact boundaries of the event, noting the score when the first wicket of the sequence fell and the score when it ended, along with the overs consumed.
List the dismissals in order with the mode and the bowler, which immediately shows whether one bowler or one type of delivery was responsible.
Note the scoring rate in the ten overs preceding the first wicket, since a drought beforehand points to pressure and a healthy rate points elsewhere.
Compare with the other innings on the same surface, as that single comparison resolves the conditions question faster than any amount of watching.
Check whether the same group of players has produced a similar sequence recently, which distinguishes an isolated event from a structural weakness.
Then state the classification and the evidence supporting it, and note explicitly what would have changed your conclusion, which is the step almost everyone skips.
Common Analytical Errors
A few mistakes recur in almost every public discussion of a collapse.
Attributing it to temperament, which is unfalsifiable and explains nothing, and which tends to be applied selectively to particular teams.
Ignoring the opposition, since a great spell of bowling is the most common cause and giving the bowler credit is frequently the correct analysis.
Treating the surface as constant, when pitches change materially across a match and a fourth-innings collapse may have nothing in common with a first-innings one.
Generalising from a single event, as every side collapses occasionally and one instance carries very little information about anything.
And judging the decision by the outcome, which is the most pervasive error of all, since a reasonable shot that gets a batter out remains a reasonable shot.
Why This Is Worth Doing
Collapses are the moments that decide most matches, and they are also the moments discussed least carefully.
Analysing one properly takes about ten minutes with a scorecard and produces a conclusion that holds up, which is more than can be said for most of what is said about them at the time.
It also changes how you watch. Once the warning signs are familiar, a scoring drought in the middle overs becomes genuinely tense, because you can see the sequence beginning before the first wicket falls.
That is the best argument for the effort. Understanding the mechanism does not reduce the drama at all, and it makes the twenty quiet overs before a collapse as interesting as the ten loud ones that follow.