A scorer's guide to box and open cricket

Agree the scoring rules before the toss

Box cricket and open-ground tournaments often use different rules for walls, roofs, nets, declared scoring zones, maximum wickets and no-ball or wide penalties. The scorer needs one written version before play begins. Confirm overs per innings, balls per over, squad and playing-team size, allowed dismissals, retirement rules, free hits, penalty runs and how a tied match is resolved.

A declared zone run is an award defined by the local competition. Agree whether it is credited to the batter, treated as completed running, counted as a boundary or recorded separately. SableApps can record declared zone runs, but it cannot decide which local interpretation is correct. The umpire's signal and tournament rules remain authoritative.

Enter every participating player separately. This produces meaningful batter, bowler and dismissal records. Check team names and the batting-first selection before starting, because correcting basic setup after many deliveries is harder than fixing it at the toss.

Build a repeatable routine for each delivery

Watch the umpire, then record the delivery after the signal is clear. For a normal ball, choose dot, one, two, three, four or six. Confirm the striker shown before recording the next ball. Odd completed runs normally change ends; the end of an over also changes strike. Unusual crossed-end decisions should follow the umpire, using strike correction where necessary.

Keep the live total, wickets and legal-ball count visible. Announce the score at the end of every over and compare it with the umpire or a second scorer. A quick verbal check is easier than reconstructing several overs later. Use undo immediately when an entry is wrong, then record the corrected delivery.

The current Scorebook supports one limited-overs innings per team. It does not automatically calculate DLS, multi-innings cricket, pairs-cricket deductions or super overs. Those formats need a separate agreed procedure.

Separate the automatic penalty from additional runs

A wide or no-ball commonly adds an automatic penalty, but teams may also complete runs or receive a boundary on the same delivery. Record the extra type and enter only the additional runs in the additional-runs field when the interface already applies the automatic penalty. Confirm whether the ball counts under the local rules; wides and no-balls normally do not count as legal balls.

Byes are runs completed after a legal delivery without contact with the bat or batter. Leg-byes require the umpire's signal and are not credited to the batter. Penalty runs are awarded by the umpire and may affect the current innings, an earlier fielding total or a later chase depending on when they occur. Do not use a batter run button merely to make the total look right, because that distorts player figures.

For box rules, distinguish physical running from a declared zone award. If the tournament says a roof hit is two runs without changing ends, record it according to that rule rather than assuming ordinary strike rotation.

Record the dismissal and the next batter carefully

Wait for the umpire's decision, select the dismissal type and confirm the dismissed batter. Run-outs can involve either active batter, so check the name rather than assuming the striker. A wicket on a no-ball is restricted to dismissal types allowed by the laws and local rules. Free-hit handling also depends on the competition's adopted rules.

After the wicket, select the incoming batter and check which end each batter occupies. Retired hurt is different from a completed dismissal and may allow the player to return. If a competition uses last-player-standing or pairs cricket, the current tool does not automate those special cases; the scorer must use the tournament's separate procedure.

Bowler figures should change only for runs and wickets attributed to the bowler. Byes and leg-byes affect the team total but not the bowler's conceded runs. Reviewing player figures at over breaks helps expose a wrong extra type quickly.

Close each over and innings with a reconciliation

At the end of an over, compare total runs, wickets, over count, striker, non-striker and bowler with the field. At the end of the first innings, confirm the final total and target before starting the chase. A target is one more than the first-innings total unless the tournament applies an adjustment outside the scorebook.

At match completion, verify the result wording, batter totals, extras and bowling figures. Export the available result and download a backup before clearing or replacing the match. Browser storage belongs to that browser profile; clearing site data can remove it, and a different device will not automatically see the match.

Scorer's checklist

• Local rules and declared zones are written down.
• Both playing teams are entered player by player.
• Extras use the correct category and legal-ball treatment.
• Dismissed batter and incoming batter are confirmed.
• Score, wickets and strike are checked each over.
• The target, result and exports are reviewed before closing.