Lightning pauses on public jobs: 3 facts to log

• Label storm distance as an estimate and record how you judged it.
• Note conditions that limit what the crew can see or hear.
• Track thunder times alongside the work stoppage and release.
• Check your contract's delay and notice terms.

A crew can be standing on a clear roof, with sun overhead, while a storm builds miles away. The National Weather Service puts the scale of the problem plainly: each year, thunderstorms produce an estimated 20 to 25 million cloud-to-ground lightning flashes in the United States, and each one of those flashes is a potential killer.

If you run dispatch or own a small electrical or HVAC firm, you face two questions every time a storm rolls through. The first is safety: when is it safe for people to go back outside? The second is a record question: can you show later, to an owner, an inspector, or a contracting officer, why work stopped and why it restarted when it did?

This post covers three weather facts that belong in your log whenever outdoor work pauses on a public job. Nothing here replaces your own safety plan, your contract, or the rules of the agency that owns the job. Use these facts as the core of your entries, then add whatever your contract and company policy require.

The first fact is about distance. The National Weather Service states that "in general, a significant lightning threat extends outward from the base of a thunderstorm cloud about 6 to 10 miles." The rain you can see is not the edge of the risk. A storm that seems to be passing to the north, or that has not yet reached the job, can still put lightning over the site if it sits within that distance from the base of the cloud.

Base your decision on the storm's position relative to the site, rather than whether rain has reached the roof.

You will rarely know the exact distance from the job to the base of a cloud, so do not invent precision. Write what you knew at the time. A good entry says something like "storm visible to the northwest, judged inside the threat zone based on radar and what the crew could see." That tells a reviewer what you knew and how you reasoned, which is more useful than a number you cannot back up.

What to log for this fact:

• The time you first saw or heard the storm.
• The direction it was coming from and whether it was moving toward the site.
• Your distance estimate, labeled as an estimate.
• The source you used, such as radar, a weather app, or what the crew could see.
• The time you judged the site inside the threat zone and work stopped.

The second fact cuts the other way. The National Weather Service notes that "in clear air, and especially at night, lightning can be seen from storms more than 10 miles away provided that obstructions don't limit the view of the thunderstorm." It also says that "thunder can usually be heard for a distance of about 10 miles provided that there is no background noise," and that "traffic, wind, and precipitation may limit the ability to hear thunder to less than 10 miles."

For a dispatcher, the lesson is that the crew's senses are a poor filter. A storm you can see on a clear evening is not automatically a threat to the job, and a storm you cannot hear is not automatically gone. Quiet on a job site often reflects conditions, not safety. A running generator, a compressor, a radio, a truck with the windows up, a busy road beside the site, or a stiff wind can all hide thunder that is still rolling in. Heavy rain can do the same.

So the log should record conditions, not just observations. Write things like "generator running, wind from the west, rain on the north side of the building, night work under work lights." These notes explain why a silent site did not prove the storm had gone, and they show that the crew tried honestly to account for what it could and could not perceive.

What to log for this fact:

• Whether it was day or night.
• Whether buildings, trees, equipment, or terrain blocked the view of the storm.
• Background noise, including equipment, traffic, and wind.
• Precipitation at the site and whether it limited seeing or hearing.
• Anything heard, even if faint or uncertain, with the time.

If thunder reaches the site, treat it as a reason to act, not as a reading to argue about later. The log should show that the crew stopped, moved people to shelter as your plan requires, and recorded the time.

The National Weather Service explains that "because electrical charges can linger in clouds after a thunderstorm has seemingly passed, experts agree that people should wait at least 30 minutes after the last thunder before resuming outdoor activities."

Two parts of that sentence matter for dispatch. The wait is measured from the last thunder, not from the moment the rain stopped or the sky looked clear. A storm can look finished while charge still sits in the cloud. A dispatcher who restarts crews when the rain ends is using the wrong clock.

The word "last" matters too. If thunder comes again, the new thunder becomes the starting point, and the wait begins again. Your log should make that restart visible. Do not leave a single entry saying the storm ended and the crew went back out shortly after, when thunder was heard again later in the same period. The reviewer needs to see each thunder event and the restart it caused.

Be clear about the source. The National Weather Service wrote this guidance for outdoor activities and sports, and a construction or service crew does different work. Your safety plan can be stricter than the source.

What to log for this fact:

• The time of each thunder event, even if the exact moment is uncertain.
• The time work stopped.
• The time of the most recent thunder, updated every time new thunder is heard.
• The earliest time the crew was cleared to resume, calculated from the last thunder.
• The actual time the crew resumed and who gave the release.

At minute 0, thunder is heard and work stops. Thunder is heard again at minute 5. Adding the 30-minute wait to that latest event gives minute 35 as the earliest possible release under this guidance, assuming no further thunder. Record both events, then record the actual release separately under the site's safety plan.

Weather notes matter after the day is over. On a public job, a stoppage can affect the schedule, the completion date, and sometimes whether the contractor can claim additional time. Whether that happens depends on the contract, so start by reading what it says about weather, delays, and notice.

For federal contracts, an excusable delay clause is one place to start. The clause at FAR 52.249-14, Excusable Delays lists examples of causes that include "unusually severe weather," along with items such as fires, floods, and strikes. It also says that if the contracting officer determines a failure results from one of the listed causes, "the delivery schedule shall be revised, subject to the rights of the Government under the termination clause of this contract."

Read that carefully. The clause does not say every lightning pause is excusable. It lists weather as a cause that can be considered, and the decision rests with the contracting officer under the contract's terms. The contractor's job is to show the facts, which is why a weather log matters. A note that says "rained a lot" carries little weight. A timed entry showing storm distance, conditions, last thunder, and restart time gives the contracting officer something specific to evaluate.

Other public contracts, including those from state, county, and municipal owners, may use different language. Those requirements are not covered here, and you should not assume a federal clause applies to your job. Pull the delay and notice provisions from your own contract and build your log to meet them.

Questions to answer before the job starts:

• What counts as a weather delay under this contract?
• Is written notice required, and within what time?
• Who must receive the notice, and in what form?
• What records does the owner expect to see?
• How does the contract revise the schedule after a delay?

A good log entry is short, consistent, and written at the time of the event. A phone form or a clipboard in the truck works. Each pause should use the same fields, so a dispatcher can compare events across the season and a reviewer can follow any single event from start to finish. Keep it with your dispatch handoff checklist.

• Date and job: the date, job name or number, and crew lead on site.
• First storm sighting: the time, the direction, and your distance estimate labeled as an estimate.
• Threat decision: the time you judged the site inside the threat zone, the basis for that judgment, and who made the call.
• Visibility and hearing: day or night, obstructions, background noise, and precipitation.
• Thunder events: each time thunder was heard, with the time, updated as new thunder comes in.
• Work stopped: the time work stopped and people moved to shelter.
• Earliest release: the calculated release time under the guidance you follow.
• Actual release: the time the crew resumed, who gave the release, and any conditions noted.
• Notes: anything unusual, including equipment problems, traffic, or a storm that returned.

The form asks for times more than opinions. Opinions have a place, and the form should leave room for them, but times make the record useful. A reviewer can check a time. A reviewer can only argue with a feeling.

Keep entries in one place, such as a binder, a shared folder, or a job management system. Entries should be dated and not rewritten later. If you need to correct one, add the correction as a new note with the date and reason rather than changing the original.

Recording a storm without a time leaves a gap. "Lightning around mid-afternoon" cannot be placed against the schedule, the restart, or the other events that day. Write the time you saw it, even to the nearest few minutes, and label it as approximate.

Writing the log at day's end from memory leaves observations unrecorded until later. A few seconds with a phone to note the time is worth more than a careful summary written later.

Treating the log as optional because the job is small creates another gap. A short entry costs far less than reconstructing a week of stoppages after an owner asks about the schedule.

A log only works if everyone knows what goes in it and when. Write a short site rule for lightning. It should say who can stop work, what threat zone you use, and how the wait applies. Keep the rule at least as strict as the guidance you follow, and say so in writing. If you choose a longer wait for roof or lift work, write that down too.

Make sure the dispatcher and every foreman know the rule. A rule that lives only in the owner's head will not survive a busy afternoon with two jobs and storms from two directions. Walk through a real example with the crew: what would they see, hear, and write down? The answers will show where the rule is unclear. Include this discussion in your emergency action plan review.

Review the log after each storm. Look for missing times, unclear distances, or restarts that do not match the thunder record. Fix the form or the training when you find a pattern. Keep the records with the job file, because the weather log becomes part of the project history. If a question about schedule, delay, or notice comes up months later, the entries written during the storm are the strongest evidence you have.

Set up the log fields above in your existing job file, then walk through the illustrative pause with the dispatcher and crew lead.

What should the log show if nobody hears thunder?

Record the observations and the conditions that could limit hearing. Silence alone does not establish that the storm has gone.

Does a lightning pause automatically qualify for extra contract time?

No, a lightning pause does not automatically qualify for extra contract time. Check the applicable delay and notice terms before making a claim.