Rain Delay Playbook for Tournament Directors

Weather does not wait for pool play to finish. The directors who look calm on a Saturday storm are not guessing — they have a sequence.

1. Decide once, then publish it

Pick a single source of truth (diamond status + a public status board). Do not let each diamond umpire invent a different restart time. Coaches will trust a late-but-consistent call over three conflicting texts.

2. Use the 30-30 rule, then add buffer

If the time between lightning and thunder is 30 seconds or less, suspend play. Wait 30 minutes after the last lightning or thunder before resuming. Restart the clock on every new strike. Add a 10-minute “get back to the dugout” buffer so the first pitch is not a scramble.

3. Protect the next four games, not just the current one

A 40-minute stoppage is not one delayed game. It is a cascade: the on-deck matchup, travel between parks, umpire crews, and a team that already played at 8 a.m. Shift the next four games on that diamond (or complex) as a block. Isolated “we will start at 2:15” notes are how you get two teams at the wrong field.

4. Tell coaches before you tell social

Order of operations:

1. Update diamond status (delayed / closed).
2. Push the new first-pitch times to coaches (SMS + the team link they already use).
3. Then update the public board and social.

Parents will refresh the board. Coaches need the slot, not a vibe.

5. Know when to cut, not compress

If you are still sliding games after 8 p.m., you are borrowing tomorrow’s pitching. Drop a consolation, shorten innings, or move a pool game to a spare diamond before you stack four 9:00 p.m. starts. A clean Sunday is worth more than a heroic Saturday.

Dugout Desk’s status board and schedule grid are built for this loop: change the diamond, shift the block, notify the next teams. The playbook is the same whether you run it on paper or in the command center.