Lightning Delay Rules: When to Stop, Reset the Clock, and Resume Activity

When lightning is close enough to hear thunder within 30 seconds of the flash, outdoor activity needs to stop right away. The delay lasts a minimum of 30 minutes after the last strike, and any new lightning within that window resets the clock back to zero. 

It’s a common situation – and because lightning can be unpredictable, applying that rule across more than one field, site, or crew can be tricky. Below, we share more about lightning delays, including when to stop activities and give the all-clear, and how organizations can turn this rule into a repeatable process across every location they manage.

Key Takeaways

• Suspend outdoor activity if thunder follows a lightning flash within 30 seconds; wait at least 30 minutes after the last strike before resuming.
• The 30-30 rule relies on human observation and reaction time; while real-time detection technology identifies threats sooner and more reliably.
• Multiple locations can’t rely on a single named weather-safety official. Consistency requires real-time detection and simultaneous alerts across every site.

What are lightning delay rules?

Lightning delay rules suspend outdoor activities if thunder is heard, or if lightning is detected within six to ten miles of an outdoor event. While different organizations have different lightning safety plans, all include participants moving to a designated safe shelter while conditions are monitored by officials. If no safe shelter is present, hard-topped metal vehicles provide adequate protection. Because electrical charges can stick around in clouds after a thunderstorm has passed, officials should wait at least thirty minutes after the last thunder clap before resuming outdoor activities. 

Organizations usually formalize this into a written policy, and pair it with weather monitoring systems and lightning detection networks to clearly determine when a delay begins and ends.

What resets a lightning delay?

A lightning delay is reset by any observed lightning strike or clap of thunder. This begins a new thirty minute countdown. This is where manual tracking usually breaks down – during a long, drawn-out storm, competing priorities can make resetting timers difficult. Automated tracking logs each strike and calculates the time activities can resume automatically, without relying on a single observer’s memory of what happened.

What is the 30-30 rule?

The 30-30 rule is the traditional way for organizations to determine the threat of lightning in an area, and it relies on the acoustic relationship between lightning and thunder. Count the seconds between seeing a flash and hearing the thunder that follows it. If the gap is less than 30 seconds, cease activity. Thirty minutes should pass with no further lightning or thunder before anyone leaves shelter.

The 30-30 rule isn’t the best way to determine the duration of a lightning delay, especially with multiple locations. It reacts to visual and auditory cues, and isn’t the same as relying on real-time atmospheric data that allows coaches, directors, or operational staff to account for the first strike. For facilities where safety is paramount, an estimate is no longer sufficient. Detection technology tells you sooner and more reliably.

How long is a lightning delay?

A lightning delay can last well over 30 minutes. The National Weather Service recommends staying in shelter for at least 30 minutes after the last thunder you hear. At venues that use a lightning detection radius, each new strike within that radius can restart the countdown under the venue’s policy. Pulling from over 390,000 strikes captured by Perry Weather stations across the United States, the median recorded lightning-zone delay was 63 minutes, and about one in four lasted more than two hours.

How do you keep the lightning call consistent across multiple fields, sites, or departments?

A single-site lightning safety policy is straightforward. Designate one weather-safety official, grant that person the authority to call and respond to a delay, and then defer to their judgement for the duration of the storm. Of course, that model becomes unreliable once an organization has to operate more than one location simultaneously. A park system with six fields, a school running games across three sites, or a campus with multiple practice areas cannot accurately apply the 30-30 rule. To keep lightning calls consistent across multiple fields, sites, or departments, it’s important to detect and track lightning in real time with advanced alert systems that account for the unpredictable behavior of lightning. 

This is where several organizations have moved to a shared detection and alerting system rather than site-by-site observation. Prince William County Public Schools, a 97-school district in Virginia, consolidated onto one lightning detection and warning system so that every athletic trainer and coach across the district makes the same call at the same time, without relying on separate apps that produced inconsistent decisions. Northern Texas PGA saw a similar problem across golf: staff managing junior tournaments across three cities used a single dashboard to monitor lightning status at every location simultaneously rather than checking each site separately. 

In both cases, the fix wasn’t a stricter policy or more observers. Instead, it was replacing several independent judgement calls with one source of data that every site can act on simultaneously.

How to document the decision of a lightning delay

Lightning safety plans should specify one person in charge of monitoring the weather for lightning. Every delay call should also be recorded, and information like when it started, what triggered it, when it was lifted, and who made the call should be written down. 

That documentation matters – if there’s ever an incident, or if a parent or employee disputes it after the fact, a clear record of the delay can be used to defend the decision. Reviewing past delays can also help identify where a policy consistently breaks down, whether that’s an inadequate shelter or a threshold that gets applied inconsistently across sites. 

To document the decision of a lightning delay, create a manual log maintained by the designated weather monitor, or rely on automatic timestamped logs from your weather detection system. These logs can be used for liability and compliance purposes, or be kept on file to refer to in the event of a postponed or canceled activity. 

How can organizations enforce lightning delays?

Good intentions only go so far once multiple locations, multiple observers, and real time pressure is involved. To enforce a lightning delay, it’s important to have a written policy in place. Set trigger radiuses, designate a weather monitor, develop an evacuation plan, and make sure you and your team have clear criteria for suspension and resumption of play.

Different settings carry their own specific requirements. School athletic programs, for example, need to account for practice schedules, multiple teams, and parent communications. Construction and other outdoor worksites have to abide by OSHA’s general duty clause. Golf operations carry their own considerations – from member communication during a delay to rescheduling around tournaments.

Enforcement also relies on how quickly a detected strike becomes a notification, and how uniformly that notification reaches every relevant site. A policy that’s technically correct but manually applied still leaves room for the same inconsistency described above: one location suspending activity while another, monitoring independently, has not yet registered the threat.

The bottom line

Lightning delay rules are simple in principle: stop when thunder follows a flash within 30 seconds, wait 30 minutes after the last strike, and reset the clock on any new activity within that window. But applying that rule reliably is the harder problem, particularly for organizations managing multiple fields, sites, or departments. Combining a clearly documented policy with real-time detection and simultaneous alerting software like Perry Weather can close that gap and turn a written standard into one that’s actually enforced the same way, at every location, every time.