PoolSolve
Menu
Features Free tools Formats Sports Guides Help

Free tools

Browser-only schedule generators - no account needed; team names you type never leave the device.

Tournament day checklist

Tournament day rewards preparation and punishes improvisation. Everything below is organised by when it happens - the week before, the morning of, during play, and after the final - so you can work top to bottom. It assumes a typical one-day event like 8 teams, 2 fields and 20-minute matches, but the same shape holds for anything up to a full weekend.

The week before

  • Confirm the venue in writing. Field access hours, changing rooms, toilets, water, parking, wet-weather policy. A booking email beats a memory when the gates are locked at 09:00.
  • Publish the schedule to every coach, not just on a noticeboard. A live schedule link means the same URL stays current through every later change; if you are still finalising the grid, generate it with the tournament schedule generator first - see how to schedule a tournament for the full planning flow.
  • Brief referees and duty teams. Who referees which rounds, the conflict rules, and the escalation path when a call is disputed. The patterns are in assigning referees fairly.
  • Collect what you need upfront. Squad lists, contact numbers for one responsible adult per team, any medical or safeguarding requirements, entry fees still outstanding.
  • Print the paper backups. A hard-copy fixture list, scoresheets, and a spare pen per field. Phones die; a laminated schedule does not.

Morning of the event

  • Arrive 60-90 minutes before check-in. Walk the fields: line markings visible, goals or equipment safe, corner flags or cones out, any hazards dealt with before the first team arrives.
  • Set up a visible results point. One table or board where scoresheets come in and standings go up. Everyone should know within ten minutes of arriving where results are reported.
  • Check in teams against a list, confirming the coach's phone number works - it is your fallback channel for every delay announcement.
  • Hold a five-minute coaches' briefing covering the schedule link, rest and substitution rules, how disputes are handled, and the weather plan. Put the weather plan in words: "if lightning stops play, we hold 20 minutes, then call it" - decided now, not argued later.
  • Start on time. A 10:00 first match that begins at 10:15 costs one slot; on a 14-round day that slot comes off the buffer you will want at 16:00.

Roles to delegate

You cannot run the day and referee it and fix the scoreboard at once. Four roles cover a two-field event:

  • Organiser (you): decisions and disputes only - format rulings, weather calls, appeals. If you are carrying cones, nobody is carrying the authority.
  • Results desk: collects scoresheets, enters results, updates standings. One person, one table, no other jobs.
  • Field marshals: one per field, keeping the next two teams staged and the changeover under a couple of minutes. They are your schedule buffer made flesh.
  • Float: a spare pair of hands for the problems you have not thought of yet - lost property, a missing referee, a first-aid run. Small events merge the float into the results desk; do not merge the results desk into anything.

Brief these people together for ten minutes before check-in opens, share one phone number for the day, and you have a crew instead of a crowd.

During play

  • Collect every score immediately. Scoresheet in after each match, results entered, standings updated. Falling three rounds behind on results is how wrong teams show up for semifinals.
  • Watch the clock, not just the games. Compare actual finish times to the plan each round; if you are running two slots behind by lunch, shorten the afternoon changeovers rather than discovering it at the semifinal.
  • Handle delays as one edit. A postponed match should move in the schedule and republish to everyone's phone, not get shouted across a car park. The tournament management tooling exists for exactly this, and handling postponements and rescheduling covers the policy side - which games get priority, which get dropped.
  • Track referee no-shows against the duty list each round; substitute from the named spares, not whoever happens to be standing nearby.
  • Log incidents while they are fresh. Injuries, disputes, carded players - two lines per incident written at the time beats reconstruction at 18:00.

Contingencies to have decided in advance

  • Team no-show: how long you wait (10-15 minutes is common), what the result stands as (typically a recorded default win), and whether the opponent then takes an empty slot or a friendly.
  • Weather: the stop-and-hold threshold, the abandonment threshold, and what happens to unfinished rounds - completed matches stand, or the round replays.
  • Running long: your pre-agreed cuts, in order - shorten ceremony, shorten changeovers, drop a consolation round. Never silently drop matches that affect qualification.

After the final

  • Verify results before trophies. Standings and tiebreakers resolved, then presentations - not the other way round. The rules in season standings and tiebreakers apply to one-day tables too.
  • Return the venue as found and settle the same day: fees, deposits, equipment signed back.
  • Send the wrap-up within 24 hours. Final standings, thanks to volunteers, and the date of the next one while goodwill is high. A post-event note is also where you record what to change next time - which slot ran long, which rule got argued - so the second edition starts from experience rather than from scratch.

None of this is glamorous, and that is the point: checklists exist so the unglamorous parts happen on time and the actual tournament - the games - gets all the attention it deserves.

Generate it now

Try the steps in this guide with a free generator - no account needed, nothing to install.

Open the free generator

Related guides

Put it into practice

Build your first schedule in minutes - every feature is free.

Create a free workspace