How to create a cricket tournament fixture list.

The seven steps

1. Lock the team list. Fixtures cannot be built against a team count that might change. Close entries, confirm payment, and treat the list as final before generating anything.
2. Choose the format from the match count. Compute the match count for each candidate format and discard any that does not fit your slots. A single round robin of 12 teams is 66 matches and will not fit two weekends.
3. Inventory real venue slots. One slot is one ground for one match length plus changeover. Count usable light, not booking hours, and leave the last slot of the day free of knockout matches.
4. Assign matches to slots with rest intervals. Keep at least one slot between a team’s consecutive matches, and rotate teams across grounds where you have more than one.
5. Mark knockout rounds as qualifier placeholders. Publish the bracket shape with slots and venues named but team positions shown as qualifiers, so teams can plan travel against real dates.
6. State the withdrawal rule, then publish. Decide in advance whether a withdrawn team’s matches are voided or awarded as walkovers, write it into the fixture release, and publish at least two weeks out.
7. Freeze changes and route them through one person. After release, every change goes through the organizer and is re-published in full. Teams working from three different versions of a schedule is worse than a schedule with a flaw in it.

Why the order matters

Each step constrains the next, and doing them out of order means redoing work. Choosing a format before counting slots produces a schedule that does not fit. Publishing before the team list is locked produces a schedule that changes. Assigning venues before knowing the match count produces a venue booking that is either short or wasteful.

The arithmetic behind steps two and three is on the fixtures guide, including the match-count table and slots-per-ground figures by match length.

The rest-interval rule

At least one full slot between a team’s matches. This is the constraint most hand-built schedules violate, because it is invisible when you are filling a grid ground by ground rather than team by team.

Two matches back to back is tolerable in short-format box cricket. Three is not. A side playing its third match of the day in fading light has a legitimate grievance about the schedule rather than the result, and that is the kind of complaint that stops a team entering next year.

Handling a withdrawal after release

Decide the rule before you publish, then apply it without discussion. The two defensible options:

• Void all matches involving the withdrawn team. Cleanest for standings, because no team gains from an opponent’s absence. Costs the remaining teams a fixture each.
• Award walkovers. Keeps everyone on the same match count. Requires a stated rule for whether the walkover affects net run rate, and the clean answer is that it awards points but is excluded from net run rate entirely.

What is not defensible is choosing after the withdrawal, because by then it affects a known qualification race and whichever choice you make will look like favouring someone.

Skip the manual pass

Steps two through five are mechanical and the fixture generator does them: enter teams, format, venues and slots, and the list comes out with byes placed and rest intervals respected. It is worth doing by hand once to understand what it is producing, and then never again.

Steps one, six and seven are judgement and process, and no tool does them for you. They are also the ones that actually determine whether the tournament runs smoothly. The planning checklist puts them in sequence with the rest of the six-week plan.