How to Allocate Cricket Grounds and Slots

A ground allocation is a set of promises: which teams play, where, when, and what happens if the day falls behind. A spreadsheet with every minute filled is not automatically a usable fixture plan. It has to survive changeovers, team rest and a match that overruns.

Use this guide with the free fixture and duration calculator. It uses CricketOrganizer's fixture generators for match counts, then applies a separate, disclosed planning model for grounds and rest. The calculator estimates a minimum. It does not book a ground or assign a live venue in the product for you.

Turn a ground day into usable slots

Start with a slot ledger for each ground, not one total for the whole event. A slot includes match play, the time needed to close that match, and the changeover before the next start.

For example, a 90-minute allocation with 15 minutes for result entry, teams leaving and officials resetting creates a 105-minute slot:

Only count slots that the ground manager, officials and teams can genuinely use. A listed 18:00 slot is not available if the lights, access gate or umpire cover ends at 17:30. Record those limits against that ground instead of applying one optimistic number to every venue.

Calculate the capacity bound first

The first check is straightforward:

minimum days by capacity = ceiling(total matches / (grounds × matches per ground per day))

An eight-team single round robin needs 28 matches. With two grounds and three matches per ground per day, the ground capacity is six matches a day:

ceiling(28 / (2 × 3)) = 5 days

Five days is a capacity bound, not a finished schedule. It says the grounds have enough slots in aggregate. It does not say Falcons can play a morning fixture on Ground A and an afternoon fixture on Ground B without an unreasonable turnaround.

Check the rest bound before you publish dates

The calculator models the competition as sequential rounds. For a round robin, an eight-team league has seven rounds. With one rest day between a team's matches, the round sequence requires 13 days:

7 rounds + (6 gaps × 1 rest day) = 13 days

In this example, 13 days wins over the five-day ground-capacity calculation. Booking a third ground does not solve a team-rest constraint.

To reproduce those planning numbers:

1. Open the fixture and duration calculator.
2. Choose Round robin.
3. Enter 8 teams, 2 grounds and 3 matches per ground per day.
4. Enter 1 under Rest days and leave home-and-away off.
5. Read both bounds in the result panel: 28 matches, 5 days by ground capacity, 13 days by rest, and 13 days recommended.
6. Change only the number of grounds or rest days to see which constraint actually changes the finish date.

The match count is generator-backed. The day count is a planning model, so use it to test your calendar before saving fixtures, not as a claim that the app has reserved those dates.

Place fixed commitments before ordinary league matches

Once the bounds fit, place the things that cannot move:

1. Ground closures, local curfews and lighting cut-offs.
2. The final and any ceremony that has a fixed time.
3. Semifinals or qualifier matches that must finish before the next stage can start.
4. Teams with a documented travel constraint, if the competition rules allow it.
5. Ordinary league fixtures in the remaining slots.

Then trace each team's route across the grid. Check date, start time, ground and the time between appearances for every team, not only the daily total. A full-looking Ground B cannot repair an impossible path for the two teams advancing from a semifinal.

Use CricketOrganizer's scheduler for the work it actually does

On the organizer Matches page, the current Smart scheduler builds either a round robin or home-and-away round robin. It lets you set a first and last date, permitted days of the week, start times, matches per day, rest days and whether a team may have simultaneous matches. It shows a preview before saving and reports fixtures it could not fit into the rules.

Use it in this order:

1. Open Matches and choose Smart scheduler.
2. Select Round robin or Home and away.
3. Set the first and last match dates, eligible days and start times.
4. Choose Matches a day and Rest between a team's matches.
5. Keep Never clash a team with itself enabled unless your event has an explicit reason not to.
6. Select Preview schedule. Inspect the date and time of every fixture that matters, plus any count the dialog says could not be fitted.
7. Select Save fixtures only after the preview has a workable answer.

There is an important ground boundary in the current Smart scheduler: its visible dialog does not ask for grounds. The underlying scheduling code can carry a venue, but Smart-scheduled fixtures are saved with a blank ground. Do not tell captains their ground is confirmed until you add it yourself.

Add or correct the ground on each saved fixture

CricketOrganizer stores a date, start time and ground on each fixture, and the organizer can create a one-off fixture by hand or edit an existing one.

For a fixture the scheduler did not cover:

1. On Matches, select Add match.
2. Choose the home and away teams.
3. Add the date, start time and Ground. Those three fields are optional in the form, so treat a blank field as unfinished planning, not a confirmed slot.
4. Save the fixture as Scheduled.

For an existing row, use its edit action and update Ground, Date and Start time together when a move affects all three. The public schedule sorts fixtures by date and time, groups them by day, and displays the ground for an upcoming fixture when one is present. Updating the row is the product's source of truth. Sending a separate message is still sensible, but it should not contradict the published row.

Keep a delay policy that matches the table

Leave at least one recovery slot in each half-day where the consequence of a delay is serious. Then publish a short operations rule:

If a fixture cannot start by [time], the organizer may move it to [reserve slot].
The organizer records any shortened, tied, no-result or abandoned outcome in the fixture list.
Captains receive the revised ground and start time through [channel].
The published schedule is updated before the revised call time.

The current points table only processes fixtures whose status is Completed. A completed result with no winner and a result description containing “tie” gives both teams a tie point. A completed result with no winner and no “tie” text becomes a no result. An Abandoned fixture does not affect the table until you decide and record the relevant completed outcome. The points-table and tiebreaker guide shows the exact result-entry behavior.

Publish one schedule, then maintain it

Before registrations close, make sure the league structure, slot capacity and team-rest rule agree. Tournament formats compared helps choose the structure. The cricket fixture generator hub covers the product's schedule flow. If player availability genuinely changes your calendar, collect only that information in the registration-form field guide.

The useful schedule is not the one with the most fixtures squeezed into a day. It is the one every team can read, every ground can host, and the organizer can still repair after the first delay.