Practical walkthroughs for WicketGrid’s Android app, with examples you can follow during a practice match. Start with match setup, or jump straight to the task you need.
Updated October 2, 2026 · Written for app version 1.0.6, now available on Google Play. These guides describe the app’s workflow; agree your competition’s rules with the organisers before play.
01 · Score your first match
Before starting, confirm the two teams, overs per innings and playing squads. A short practice match is a useful way to learn the controls before recording a real fixture.
Open Teams to create your teams and add players. Reusable squads save time when those teams play again.
Open Matches or Quick Start Match. Choose Team A and Team B, the format, overs and match rules.
Complete the toss and squad setup, then select the opening batters and bowler. Check which batter is on strike.
With Quick Mode off, choose a delivery result and tap Save Ball. Check the updated score before entering the next delivery.
At the end of an over, choose the next bowler. You can select an eligible previous bowler, enter a name, or use Continue Random for the next numbered system bowler.
Practice example
Record six legal deliveries: 0, 1, 2, 0, 4, 1. The team should have 8 runs after 1.0 overs, assuming no other events. Check the team total as well as the batters’ individual scores.
When to use Quick Mode
Quick Mode records ordinary runs and dot balls immediately when tapped. Leave it off while learning or when you want to review each entry first. Extras still open a delivery-details window; in Quick Mode, tapping Apply records that delivery.
To resume an unfinished standalone match, find it under Matches. Completed scorecards remain available there. Tournament fixtures are opened from their tournament.
Use the umpire’s decision to select the delivery type. Do not enter an extra as an ordinary batting run: the team total may look right while the batter and bowler records become incorrect.
WD — Wide
Open the wide details and enter any additional runs. WicketGrid’s WD+1 label means one additional run plus the automatic wide extra. A wide does not consume a legal ball.
NB — No-ball
Use the no-ball details to record the correct run breakdown, including runs off the bat where applicable. NB+2 means two additional runs plus the automatic no-ball extra. A no-ball does not consume a legal ball.
B and LB — Byes and leg-byes
Choose the appropriate extra and enter the runs in delivery details. These are team extras rather than runs credited to the batter. Review any other delivery conditions before saving.
Reading an over
If two legal balls have been bowled, a wide leaves the legal-ball count at 0.2 overs. The delivery still appears in the current-over record. The next legal ball advances the count to 0.3.
Recording a dismissal
Select the appropriate wicket type and complete the details. For a run-out, identify the dismissed batter, then choose whether the remaining batter or the new batter faces next. Check both the wicket count and the next striker before continuing.
If a delivery involves both extras and a dismissal, use its details rather than adding two separate deliveries. Confirm the umpire’s ruling before recording an unusual event.
Use Undo when you need to remove the latest recorded delivery. Use Score Amendment when an earlier delivery has the wrong run total and later play should remain recorded.
Open the match menu on the live scoring screen and choose Score Amendment.
Select the affected delivery when you know which ball was entered incorrectly.
Enter the corrected total for that delivery. This replaces the old value; it is not an additional amount.
Review the team total and the affected batter and bowler figures.
Replacing a six with two runs
If the team total is 40 and an earlier six should have been two, enter 2 for that delivery. The corrected team total becomes 36, provided nothing else changes. Do not enter −4 as the replacement delivery total.
If you do not know the delivery
The Not sure - add to previous over option lets you choose Increase or Decrease, enter the adjustment and select the batter whose record should change. It adjusts the previous over without changing its legal-ball count or the current striker. Use a specific delivery amendment whenever you can identify the ball.
If the next striker is wrong, use Set Current Batters from the match menu. An amendment confirmation also offers an immediate UNDO action; it may no longer be available after another delivery is recorded.
When both regulation innings finish level, WicketGrid offers Play Super Over and End match as tie. Choose the option agreed for your match or competition.
Choose Play Super Over, select which team bats first and tap Continue.
Select two opening batters and one bowler, then score the deliveries.
Each team receives six legal balls. An innings can finish earlier when two wickets fall or the chase target is reached.
Complete the other team’s innings and review the result. If the Super Over is tied too, choose another Super Over or finish as a tie.
A Super Over chase
If the first team scores 10, the other team needs 11 to win. Reaching 11 ends the chase. Finishing on 10 leaves another tie decision; the original regulation scores remain unchanged.
Super Over innings appear separately in the scorecard. Their runs and wickets do not count toward the normal player or tournament statistics. The final match result identifies the Super Over winner.
If you choose End match as tie, confirm the decision to complete the match without a winner. These are WicketGrid’s available controls, not a claim that every competition uses identical tie-break rules.
Create the participating teams and squads before building the tournament. Check the competition format and rules with the organiser so fixtures and qualification reflect the intended event.
Open Tournaments and create a tournament.
Enter the details, select existing teams and configure the competition rules.
Review the generated structure and fixtures before starting.
Open the tournament’s Matches tab, select a fixture and score it using the normal workflow.
After completing the fixture, check the standings and player/team statistics. Qualification and knockout fixtures follow the saved tournament rules.
Check one result before scoring the next
For example, after completing the opening fixture, verify the two teams, result and points-table entry. Discovering a wrongly selected team immediately is easier to resolve than finding it after several more fixtures.
Use Player Stats or Records to inspect Batting, Bowling and Overall lists. Open tournament fixtures from the tournament itself when they are not shown among standalone matches. Export a backup after a scoring session to keep a separate copy of the event’s records.
A backup is a portable copy of your local WicketGrid data. It is not automatic cloud synchronisation. Keep an exported copy outside the app before changing phones, resetting a device or removing app data.
Create a copy
Open Settings → Data & Backup, then select Create Backup or Share Backup.
If prompted, complete the rewarded video to unlock export. An unavailable video may require an internet connection and a later retry.
For Create Backup, choose where to save the .cricketbackup file. Share Backup lets you send a copy using another app, such as your preferred cloud storage service.
Check the destination contains the file. A Last Backup timestamp alone does not confirm that you kept a copy somewhere outside the phone.
Restore on a phone
Use Restore Backup from Settings or the Welcome screen and choose the exported file.
Review the backup details before confirming. Restoration replaces the current local records; it does not merge two phones’ match histories. Export any current data you want to keep first.
After restoration, open a known team and match to check their records. Restoring does not require a rewarded video.
Moving to a new phone
Export on the old phone, save the file somewhere accessible, then restore it on the new phone. Keep the old phone’s data until you have checked the restored records.
If restoration fails
Make sure you selected the original .cricketbackup file rather than a screenshot or another export. Try copying it again from the original source and check that the receiving app is up to date. Renaming an unrelated file does not make it a valid backup.
If the error continues, contact support with the app version and exact error message. Backup files can contain names and match data; do not post them publicly.