Price each outdoor crew pause as paid or unpaid time, and check whether it also moves the calendar. A storm, a heat problem, and a long wait for wet ground each stop work for a different reason, and each touches labor cost in a different way. Some stops keep the crew on the clock. Some send the crew home. Some keep everyone paid while cutting the productive part of the day.
This post covers the three outdoor pauses that come up most often on job sites: lightning, heat, and weather waits. For each one, you will see what it does to crew hours, when the time is usually paid, and where it lands in the hourly labor cost. The method is the same for all three. First, work out what the crew is doing during the pause. Second, decide whether that time is paid or unpaid. Third, decide whether the pause also moves the calendar, because a longer schedule costs money even when no extra labor is paid.
Lightning comes first because it is the most sudden. Heat comes second because it changes output without always stopping work. Weather waits come last because they are the most frequent, and they only make sense once the other two are sorted.
Before you start, settle the cost model, since most pricing errors come from mixing up the kinds of cost a pause creates. A pause can add paid hours. It can add calendar days with no paid hours. Or it can leave the paid day alone and cut the productive output inside it. Each effect belongs on a different line. Labor is paid hours times the loaded hourly rate for each worker. Calendar days feed equipment rental, site overhead, and supervision. Lost productivity makes a task take more paid hours, which feeds back into the labor line.
If you price these pauses in a spreadsheet, keep one row for each pause and one column each for paid hours, unpaid hours, and calendar days. The structure matters more than the software. A row that mixes labor and calendar cost is hard to check later, while separate rows are easy to audit when a job runs long.
1. Lightning: price the move, the wait, and the restart
Lightning is the pause that stops everything at once. When thunder is heard, the crew moves to a safe building or vehicle and stays there until the storm has passed. Estimators often treat this as a small adjustment. It is not small, and it is not one block of time either. Each storm creates three parts, and each belongs on its own line: the move to shelter, the wait, and the restart when the crew returns and puts equipment and the work area back in order.
For the wait, the National Weather Service advises: "Wait 30 minutes until after the last rumble of thunder before going back to the campsite." The 30-minute figure is a planning number for estimating, and your safety lead should confirm what your company requires on site. The wait counts from the last rumble, so it starts again if thunder returns. Source: National Weather Service, "When a Safe Building or Vehicle is Nearby".
The move depends on crew size. The same page adds: "If you're in a large group, you'll need extra time to get everyone to a safe place." That is why the move cannot be a fixed number in your estimate. A small crew working close together can reach shelter quickly. A larger crew spread across a site needs more time, and that time grows with the distance from the farthest work position to the nearest shelter and with the number of vehicles or buildings the crew must split between.
Walk the site before you bid it. Mark each work position on the site plan, mark the nearest safe shelter for each position, and measure the walk. Then size the move for the largest crew you expect, not the smallest. Estimators who price the move for a two-person crew and then staff the job with eight people will find the number wrong on the first storm.
Decide the trigger in advance as well. Write down who can call a lightning stop, what they look for, and who calls the all-clear. A vague trigger produces a pause that runs longer, is less predictable, and is harder to bill for. The site lead should be able to stop work without waiting for the office, and the office should price that authority into the job.
Next, decide whether the time is paid. Ask one question: is the crew on the clock and under your direction during the move and the wait? If yes, the time is paid and goes into the labor line. Idle time in a truck while the foreman waits for the all-clear can be paid, partly paid, or unpaid, depending on your pay policy and how idle time is set up. Whether release is allowed, and what your pay rules require after a crew reports, depends on company policy and local wage requirements. Check them before you commit to an unpaid assumption.
Pricing paid lightning time is straightforward. Take the paid pause hours, multiply by crew size, and multiply by the loaded rate. Keep the move and the wait on separate lines so you can see how much of the total comes from crew size rather than from the storm itself.
Unpaid lightning time still costs you. The crew is not paid, but the job calendar moves. Equipment rental keeps running, and so does site overhead. A crane, a trench box, or a generator billed by the day will charge for a day it did not run. Price those as calendar costs per day, not as labor, and make sure the estimate shows where the delay lands.
Documentation matters for paid lightning time. Record when the storm was called, when the crew moved to shelter, and when they returned. A sign-in or timecard note with a cause code such as "lightning" keeps the paid time traceable at payroll and gives you evidence if a client questions the bill. A record kept at the time is worth far more than a reconstruction after the job closes. For a fuller list of times to log, see Lightning wait costs: 3 times to log for each stop.
Storms also come back. On a multi-day job, the cost recurs with each storm day, so price it for each storm day rather than once for the whole job. A job that gets two storms in one week carries two moves, two waits, and two restarts. A single lump for the job hides that repetition, and the first bad week will expose it.
Finally, the restart. After a storm, the crew does not resume at full speed. They re-stage materials, check that the work area is safe, and often recheck work done just before the storm. Put a restart allowance in the estimate as paid hours, even when the storm was short. It is easy to leave off a bid and easy to forget on the job, so write it into the line from the start.
2. Heat: price the breaks, the water, and the slower pace
Heat differs from lightning in one important way. The crew usually keeps working, but at a lower pace, with planned rest breaks and a steady water supply. A heat pause is often partly paid and partly productive, so the estimate has to show both parts instead of one lump.
Heat rules vary by place, so do not price heat from a general sense that breaks are normal. Look up the heat rules that apply where the job is, and check how your company's written procedures handle breaks, water, and shade. Build the estimate from that schedule. The breaks you price should be the breaks you will actually schedule, not an optimistic version of them.
Whether scheduled rest breaks are paid depends on your pay rules, so confirm that before you price them. If they fall inside the hours you are paying for, they need no separate labor line. What changes is output. A crew that takes a scheduled break every hour during the hottest part of the afternoon finishes less work in those hours than a crew that does not. Model this as a productivity factor on the affected tasks. Lengthen the task duration for the hot hours, then recalculate paid hours for that task.
Here is how to set up the adjustment for one task. Take one task that normally runs for a set number of paid hours. In the afternoon heat, the same task runs longer because the crew works slower and takes its scheduled breaks. The estimate should show the original duration, the adjusted duration, and the reason for the change, so a reviewer can see that the extra time came from the heat and not from a scope change.
Lengthen the task, and do not also add break minutes as paid time on top of it. Doing both counts the same minutes twice, and a client who reviews the estimate will spot it.
Water and shade are direct job costs. Price them like supplies: for each worker, each day, in a non-labor line. The cost comes from the water itself, the containers and coolers used to carry it, and any shade structures or cooling equipment you provide. Use your own supplier prices. Do not carry a figure from another job without checking that the crew size and season match. For a short checklist of heat costs, see Heat checks: 3 costs to include in crew hours.
Heat-driven stops are a separate case. Sometimes a supervisor stops work for the hottest hours, or sends the crew home mid-afternoon. If the crew is released, whether those hours are paid depends on your policy and local rules, so check before you assume they are unpaid. Some policies pay a minimum period after a crew reports. If those hours are unpaid, put the lost time into the schedule as a calendar cost, the same way as unpaid lightning time. If the crew stays clocked in during a heat-driven stop, price that time as paid labor at the loaded rate instead.
Shifting start times earlier is a common way to avoid the worst heat. It moves work into cooler hours without adding a pause at all. Before you assume the hours cost the same, check overtime, shift premiums, and any local limits on start times. An early start can change what you pay even if total hours stay flat. Price the change rather than assuming it.
Heat also varies by task. Heavy lifting, digging, and work in full protective gear slow down in heat more than light tasks do. Set the productivity factor task by task, not as one rate for the whole job. A single rate hides the difference and can underprice the heavy work.
Track conditions by day as you go. If the estimate assumed a certain number of heat-affected hours, log the actual hours each day against it. The log shows whether your factor was right for that crew, that season, and that type of work. Over a few jobs, the log becomes the best source for the next estimate.
The first hot days of the season deserve their own look. A crew that has spent the winter indoors often works slower in the first heat than it will a few weeks later. Price a ramp-up for the early days, and let the estimate fall back to the normal factor once the log shows the crew has settled in.
3. Weather waits: price rain, wind, and wet ground by paid status
Weather waits are the least dramatic of the three and the most frequent. Rain stops roofing. Wind stops a crane lift. Wet ground stops trenching or a concrete pour. The crew sits in the truck for an hour, or the foreman sends everyone home for the afternoon. The pricing question is the same as before: is the crew on the clock and under your direction?
Weather waits happen often and in small pieces, so they add up quietly. Price them from history, not from a guess. Pull the last several jobs of the same type, in the same season, and count the scheduled days when rain, wind, or ground conditions stopped work. Divide that count by the scheduled days. The result is a rate of lost days for that kind of work at that time of year. Apply the rate to the crew-days in the new estimate, and show the result as its own line so it is visible and can be adjusted.
Then split the result the same way as before.
Paid waits happen when the crew is clocked in and held on site, ready to work. Nobody has released them, and the foreman expects them back when conditions change. The time is paid and goes into the labor line at the loaded rate.
Unpaid waits happen when the crew is released and not required to stay. Unless a minimum paid period applies, this time carries no labor cost, but the schedule slips. Put the slipped days into calendar costs: equipment rental, site overhead, and any supervision you carry on the job whether or not the crew is working that day.
Some situations mix the two. If part of the crew is released and part is kept on site, price each group separately, because the two groups have different paid status. The same applies to a crew kept on site for part of the day and released for the rest. Split the day at the release time and price each part on its own line.
When a crew is released and called back, the return is also a cost. The crew may need to re-mobilize: reload materials, reset equipment, and re-check the work area. Those hours belong in the paid line when the crew is paid for the return, and in the calendar line when the return pushes work into the next day.
Forecasts are a scheduling input as well as a risk. When rain or wind is likely, the cheapest move is often to reorder tasks so the crew works on items that can proceed in poor conditions. Rescheduling can cost something of its own, though. Equipment booked for a specific day may carry a change fee, and crane or subcontract bookings can be hard to move on short notice. Read the rental and subcontract terms before you price a move, and count any change fee as a non-labor cost.
Timekeeping should carry the cause of each wait. Use a consistent cause code such as rain, wind, or ground, so that the next time you pull history you can count the days directly instead of reconstructing them from memory. This is the step many estimators skip, and it is the one that makes the historical rate reliable. For the wider paid-time picture, see Crew hours: 3 paid-time and overtime costs to price.
Contracts matter too. If the contract includes a weather clause, read what it gives you before you decide how much of the historical wait to carry. A clause that extends the schedule but says nothing about cost leaves the cost of the wait on your side of the bid. A clause that pays for standby changes the picture. Price the part you actually carry, and state the assumption in the estimate so the client sees it.
Some pay policies include a minimum paid period when a crew reports and is sent home. Check whether yours does, because that minimum can turn a short weather wait into a paid one even when the crew does no work.
Once the job closes, compare each of the three lines against the timecards and the calendar. Where the actual paid hours, unpaid days, or lost productivity differ from the estimate, note the cause next to the line. Those notes are what make the next estimate for the same kind of work more accurate.
Related guides: Ladder setup: 4 figures to check before crew hours.