Scoring
Ten minutes that prevent a wrong target in the chase: totals, wickets, extras, bowling quotas, and who will open.
By CricMatch Editorial · Updated 2026-08-17 · ~641 words
If first innings is 162 on the app and 166 in the umpire’s head, the second innings is a different match for each camp. The innings break exists to make those numbers the same before anyone pads up again.
Do not use the break only for tea. Use it as a data checkpoint. Captains will forgive a slow restart. They will not forgive a target that changes at 18 overs.
Agree runs, wickets, overs, and extras with both umpires. If extras do not add up to the gap between batters’ runs and the total, find the missing wide now. Check fall of wickets if a captain disputes a dismissal time.
Read the numbers out loud: “164 for 7 in 20 overs, extras 14.” If someone disagrees, they must disagree immediately.
If the second innings might be reduced, recompute max overs per bowler before the first ball of the chase. If it is a full innings, still glance at who has overs left in case of a split innings or a super over later.
Maidens and wides in bowling figures should match the extras column closely enough that a human can believe both. Perfect accounting is the goal; “off by one because of a missed wide” should be fixed now.
Target is usually first-innings runs plus one, unless rain math says otherwise. Confirm DLS or reduced-overs target if weather already intervened. Write the target on paper and on the live page.
Select opening striker, non-striker, and opening bowler before you go live again. A chase that starts with the wrong striker for two overs poisons strike rates and “who faced the hat-trick ball” folklore forever.
Update status to innings break, then to live when the first ball of the chase is about to be bowled. Fans hate a frozen first-innings total with no explanation. A single line—“Chase: 165 in 20 overs”—is enough.
CricMatch live pages show overs left and required rate when the chase is on. Those numbers are only helpful if the first-innings total was closed properly. The checklist is how you earn those features.
Both umpires, both captains or their deputies, and the scorer. A spectator with a strong opinion is not a fifth official. Read the numbers. If someone disagrees, identify the over, not the vibe.
If you cannot agree, you still need a working target to restart. Log the dissent, pick the umpires’ figure, and continue. Re-litigate after the match if the committee demands it — not at 14.2 of the chase.
Before you go live again: names of two batters, bowler, target, overs. Then one public sentence. If the page still shows first-innings batters as “not out” in a way that confuses fans, that is a display issue to fix in the product — the book must still be right.
CricMatch chase views (runs needed, overs left, required rate) are only as good as this checklist. Skip it and the pretty numbers lie.
“They scored 164 for 7 in 20. Target 165. Openers A and B. Bowler C. Twenty overs, four per bowler.” If rain reduced, replace the overs and cap in the same breath.
Write it on paper even if the app shows it. Paper survives a phone restart. Then tap the app to match the paper, not the other way around, if you just agreed with umpires.
Only then tell the public. A live page that starts the chase while the huddle is still arguing extras is how fans screenshot the wrong target.