Organizing
Shorter games, more fixtures, tired scorers. A practical plan for indoor nets, turf boxes, and corporate 6-a-side cups.
By CricMatch Editorial · Updated 2026-08-17 · ~687 words
A 6-a-side cup can finish 24 matches in a day. That is the appeal and the trap. If each game overruns by eight minutes, your 7pm final starts at 10pm and teams vanish. The organizer’s job is a timetable that assumes slightly slow over rates, not a fantasy of IPL pace.
Score every game, even the 5-over ones. Without a card, group ranking becomes a shouting match about who “batted well”. With a card, NRR or a simple quotient can separate teams who all won twice.
Typical pattern: 5 or 6 overs a side, 4–6 players on the field, last-player-stands or last-two-stand, one bowler maximum two overs. Decide last-player-stands before registration, because it changes batting order strategy and when an innings ends.
For indoor nets, define wall scoring: one bounce off side net as a single, straight hit as four, roof as out, and so on. Put those on a poster at the entrance. Visiting corporate teams will not have trained at your venue.
Pre-create all matches in the morning with teams, overs, and player lists. Do not type squads while the toss is happening. The scorer’s job between games is: close last match, open next match, confirm two batters and one bowler, start.
Use a second volunteer as “queue manager” so the scorer is not also hunting for the next captain. Box cricket fails when the scorer becomes the PA announcer.
Indoor cricket injuries are often ankle and finger injuries. Require non-marking shoes. Keep a first-aid kit at the scorer’s table so it is not locked in someone’s car. If a ball hits lights or a camera, have a dead-ball rule ready.
Time-wasting is real when a team is defending a small total. A standing umpire plus a table umpire (the scorer with a clock) helps. If you impose a “bowl the over in 4 minutes” guideline, actually enforce it once so it is not decoration.
Fans and office colleagues cannot attend every game. A live list of fixtures with scores turning from “next” to “live” to “result” is how a corporate cup feels like an event instead of a private nets booking.
On CricMatch, keep one tournament hub for the day. Share that hub in the company group at 8am, not twenty separate links. People will follow their team’s next match without asking you for updates while you are trying to find a missing bail.
If last batter stands, the innings may continue with a runner or with special out rules. Write whether a run-out of the runner ends the innings. Box cricket arguments cluster here. The scorer should know the end condition before 4.3 overs, not at 5.5.
Keep player names short on the card; indoor PA systems mangle them. Confirm spellings at registration, not during the final.
Five minutes is a luxury. Pre-open the next match, pre-list XIs if they were submitted, and have the next captains at the table while the previous teams leave the net. The scorer should not be the person retrieving the ball from the roof.
Publish a live “now playing / on deck” list so corporate teams hanging around the cafe know when to pad up. That list is operations, and it is also content fans can follow remotely.
You have about 18 minutes. Pre-select bowlers if captains will name them. Use large taps. Do not type long batter names mid-over — pick from the squad list you loaded at 8am. If a team is late, start the clock anyway or you will never play the final.
NRR in a 24-match day is how you separate three teams with two wins. If you do not score the 9am game because “it is only a group match,” you cannot rank at 6pm.
Publish results into the same tournament hub all day. Corporate Slack should get one hub URL at breakfast, not 24 separate links.