How to Organise a Local Cricket Match: Complete Checklist
By the Cricket Score Counter Editorial Team · Updated · 7 min read
Most local matches that go wrong do so before a ball is bowled: the ground is double-booked, two players drop out, or nobody agreed how many overs to play. This checklist walks an organiser through the week before a game and the match day itself, so the cricket is the only thing people argue about.
Key takeaways
- Fix the format, venue and start time first, then build everything else around them.
- Invite two or three more players than you need and set a firm cut-off for confirmations.
- Write the playing conditions down and share them with both captains before match day.
- Plan the day backwards from the scheduled start, allowing time for set-up and the toss.
- Appoint a scorer and agree who umpires before the first ball, not after the first dispute.
Decide the format before anything else
Every other decision depends on the format, so settle it first. A 20-over game with hard ball needs a proper pitch, a full day's daylight window of about three and a half hours, and eleven players a side. An 8-over tennis-ball game on a turf patch needs a fraction of that.
Be realistic about how long things take. A 20-over innings at local level usually runs 75 to 90 minutes once you allow for lost balls, field changes and new batters walking out. Add a 15-minute break between innings and set-up time, and a T20 easily fills four hours. If the ground is only yours from 2pm to 5pm, play 15 or 16 overs a side instead of hoping everyone hurries.
Book the ground and check what you are getting
Public grounds, school fields and private turf facilities all take bookings in different ways, and popular slots on Saturday and Sunday mornings go early. Book at least a week ahead and get the confirmation in writing, even if it is a WhatsApp message from the groundsman. Ask exactly which strip or net is yours, what time you must vacate, and whether another game is booked straight after.
For hard-ball cricket the pitch should be 22 yards between the stumps, with a properly marked crease. Ask whether the ground provides stumps and boundary markers, and whether spikes are allowed. If you are using a public park, find out whether a permit is required and whether there are rules about hard balls near walkways or play areas.
Visit the ground once if you have never played there. Note parking, shade, toilets, drinking water and which boundary is short. Those details shape your rule sheet later, especially if one side has a road or houses behind it.
Confirm players with a hard cut-off
Dropouts are the single most common reason local matches start late or end up as 8 versus 10. Send the invite with the date, venue, start time, format and the cost per head if there is one. Ask for a clear yes or no, not a maybe, and set a cut-off, ideally 48 hours before the match.
Invite two or three more people than you need. If you need 22 players, aim for 25 confirmations. Agree in advance how extras will be used: they can be named substitutes for fielding, or you can split them so one team plays 12 a side with only 11 batting. Whatever you choose, tell everyone before the day so nobody feels left out when they arrive.
The night before, send a short reminder with the location pin and the time players should arrive, which should be 30 to 45 minutes before the start, not the start time itself. That small gap is the difference between a punctual first ball and a 40-minute wait for the opening bowler.
Kit and equipment checklist
Decide who brings what and write names next to items. Shared kit has a habit of being everyone's job and therefore nobody's. For hard-ball games, safety gear is not optional: every batter facing a leather ball needs pads, gloves, a helmet and an abdominal guard, and the wicketkeeper needs pads, keeping gloves and ideally a helmet when standing up to the stumps.
A small first-aid kit with an ice pack, plasters and a bandage covers most knocks. Bring a spare ball or two, because a lost ball with no replacement can end a game early.
- Two sets of stumps and bails, or a spring-back set for tennis-ball games
- Match balls plus at least one spare of the same type and condition
- Boundary markers or cones (around 20 for a full ground)
- Shared batting kit: pads, gloves, helmets, abdominal guards
- Wicketkeeping gloves and pads
- First-aid kit, ice pack and plenty of drinking water
- A phone with charge for scoring, plus a backup power bank
- A coin for the toss and a measuring tape for the pitch if it is unmarked
Write the playing conditions down
Local cricket runs on unwritten rules, and unwritten rules are where disputes come from. Before match day, send both captains a short rule sheet covering anything that differs from normal Laws. It takes ten minutes to write and saves an hour of arguing. The table below lists what to include and a sensible default for a 20-over hard-ball friendly.
Once both captains agree, share the sheet with the whole group. On the day, read out the two or three rules most likely to cause trouble, such as leg-side wides and the boundary near the road, at the toss.
| Item | Suggested default | Why it matters |
|---|---|---|
| Overs per side | 20 | Fixes the finish time |
| Max overs per bowler | 4 (one-fifth of the innings) | Stops one bowler dominating |
| Wides | Any ball down the leg side passing the batter is a wide | Most common local dispute |
| Bouncers | One per over above shoulder height; above head is a no-ball | Safety with mixed abilities |
| No-ball for overstepping | Free hit on the next ball | Agree before the game, not after |
| Retirements | Batter retires on 30, may return at the end | Gives everyone a bat |
| Late start | Overs reduced equally, one over per side per 8 minutes lost | Keeps the end time |
| Ties | Super over, or shared result | Decide before you need it |
Plan the match day backwards
Work from the scheduled first ball back to the arrival time. Under the MCC Laws the toss takes place no earlier than 30 minutes and no later than 15 minutes before the scheduled start, and that is a sensible target for friendlies too. It gives the losing captain time to sort the batting order or field, and it forces everyone to be at the ground in good time.
Assign one person to own the clock. Their job is to keep the innings break to the agreed length, chase the next batter out, and call time on drinks breaks.
Umpires, scoring and handling disputes
Neutral umpires are rare at local level, so most friendlies use the batting side's players, often the next two batters in. That works if the rule is clear: the umpire's decision is final, and fielders do not stand around arguing.
Scoring matters more than people think. A miscounted over or a forgotten wide changes targets and starts arguments at the worst moment. Pick one scorer per innings and have them score ball by ball rather than writing totals at the end of each over. Cricket Score Counter lets the scorer record every delivery on a phone and share a live score link, so players on the boundary and friends at home can see the same numbers.
When a dispute does happen, give the two captains the final word, take a minute, and move on. If the rule sheet covers it, read the sheet. If it does not, agree a ruling for today and add it to the sheet for next time.
Money, safety and after the match
If there is a ground fee or ball cost, collect it before the toss. Chasing payments after the game is awkward and often fails. Keep a simple list of who has paid, and share the total cost and split openly so nobody wonders where the money went.
Before you leave, collect all stumps and markers, pick up bottles and litter, and check the ground is as you found it. Groundsmen remember teams that leave a mess. Share the final scorecard in the group the same day, while the game is still fresh. Saved match history in Cricket Score Counter makes it easy to look back at results and pick balanced teams for the next fixture.
Put it into practice
Score your next match ball by ball for free and share a live scorecard link with everyone watching. No sign-up needed.
Frequently asked questions
How many players do I need for a local cricket match?
A standard match is 11 a side, but friendlies work well with anything from 6 to 11 per team. Invite two or three more than you need, because last-minute dropouts are common.
How long does a 20-over local match take?
Plan for around three and a half to four hours including set-up, the toss, a 15-minute innings break and packing up. Each innings usually takes 75 to 90 minutes at local level. If your ground booking is shorter, reduce the overs before the day rather than rushing.
What should go on a local match rule sheet?
Cover overs per side, bowler limits, wides and no-balls, bouncers, retirements, what happens if the start is delayed, and how ties are decided. Add any ground-specific rules, such as a short boundary or a no-go area. Send it to both captains before the day and read the key points at the toss.
Who should umpire a friendly match?
Neutral umpires are best but rarely available. The common approach is for two players from the batting side to umpire, rotating as batters come and go. Whoever umpires, agree before the start that their decision is final.
What happens if we start late?
Agree a reduction rule in advance. A common approach is to remove overs equally from both innings, about one over per side for every eight minutes lost. That keeps the finish time fixed and avoids arguments about who lost out.
This guide follows the MCC Laws of Cricket and common competition playing conditions. Local leagues and friendly matches often use their own rules, so always agree them before the toss. Spotted something we should correct? Contact us.