Construction Weather Delay Log: What to Record

“Rain all day—no work” is too vague to explain a weather delay. It does not show how much rain reached the site, when conditions changed, which operation was planned, whether the work could safely or technically continue, what the crew actually did, or whether the event affected a controlling schedule path.

A useful weather record builds a factual chain. It records the measured weather, the resulting condition at the work face, the specific operation affected, the planned and actual labor and equipment, the stop and restart decisions, mitigation, contemporaneous evidence, required notice, and the schedule activity under review.

Use the Construction Daily Report / Log as the contemporaneous source record. Give the event a stable ID such as WX-018 and write the actual operation and effect: “Roof Area B membrane placement planned under activity R-410. Rain began 08:35; placement stopped and the edge was protected. Rain ended 10:20; substrate criteria still not met at 13:00. Crew moved to approved interior work.” The recordkeeping discipline in construction daily reports that stay useful a year later matters more than a label reading “weather day.”

The daily report should not decide contractual entitlement by itself. Weather observation, work disruption, schedule delay, excusability, compensability, and a time extension are different questions. The agreement, applicable law, timely notice, schedule analysis, causation, mitigation, and decision authority control the later determination. Documentorium is not a weather station, scheduling engine, or claim calculator; preserve the actual instrument and schedule records alongside its forms.

Quick Answer

For every material weather event, connect five things: measured weather, work-face conditions, the affected operation, the current schedule effect, and the pending contract determination. Identify the project, location, local time zone, observer, and data sources; record the weather variables relevant to the task rather than filling every possible field.

Show the planned activity, crew, equipment, and quantity beside actual work, stop and restart times, mitigation, and unaffected operations. Attach photos and measurements, identify other readiness constraints, and link the required notices and schedule review.

Use measured values where practicable and preserve the source and limitations. Connect the event to a defined operation and current schedule activity. Avoid conclusions such as “excusable day” or “owner-caused delay” unless the authorized contract process has made that determination.

Separate Five Layers of Evidence

The strongest logs do not jump from a cloudy sky to a claimed completion extension.

Preserve each layer even when a later determination rejects relief. A valid field observation remains useful for safety, quality, planning, and production history.

A Weather Log Is Not Automatically a Claim

Use the log as contemporaneous factual support. It may feed:

• the daily report;
• schedule update and narrative;
• weather calendar;
• safety record;
• quality or inspection record;
• delay notice;
• change or time-extension request;
• cost segregation;
• mitigation plan; and
• project closeout history.

It does not automatically prove:

• that the weather was unusual or unforeseeable;
• that all work stopped;
• that the affected task controlled completion;
• that the contractor was otherwise ready to perform;
• that no concurrent delay existed;
• that mitigation was impossible;
• that a full day should be added to contract time;
• that standby or inefficiency cost is recoverable; or
• that a notice requirement was satisfied.

Keep factual fields separate from analysis and determination fields. Label opinions, estimates, and pending conclusions.

Read the Operative Contract Before Documenting an Event

Weather treatment varies. Review:

• definition of adverse, abnormal, or unusually severe weather;
• anticipated weather allowance;
• calendar and lost-workday method;
• operation or critical-path requirement;
• notice trigger and deadline;
• required recipient and delivery method;
• required supporting detail;
• continuing and cessation notices;
• mitigation duty;
• schedule-update or time-impact-analysis procedure;
• concurrent-delay treatment;
• cost entitlement or exclusion;
• force-majeure provision;
• claim and dispute procedure; and
• record-retention requirement.

FAR 52.249-10 provides one federal fixed-price construction example. It lists unusually severe weather among possible unforeseeable causes beyond contractor control and includes a written-notice provision. That clause applies only when incorporated and does not create a universal ten-day rule for all construction. Other contracts use different language, baselines, proof, deadlines, and remedies.

FAR 52.236-15 is a separate federal example of schedule-submission and progress-reporting requirements when included in a contract. It does not set a universal schedule method for private projects.

Do not copy a federal, AIA, ConsensusDocs, state, or local method into a project that adopted something else. Obtain project-specific legal and schedule advice for material requests.

Define the Project's Weather Method

Before the first event, document:

• onsite station or manual instruments;
• instrument location and exposure;
• calibration or verification procedure;
• observation interval;
• local time standard;
• external reference station;
• distance and elevation difference;
• data archive method;
• operation-specific stop and restart criteria;
• who may suspend and resume work;
• photo and file naming;
• schedule weather-calendar treatment;
• anticipated weather baseline; and
• review and approval roles.

AACE Recommended Practice 84R-13 addresses planning and accounting for adverse weather and is guidance rather than a substitute for contract terms. Use the applicable agreement and project schedule procedure to select the method.

Identify the Event and Work Face

Assign a stable event ID such as WX-018. Record:

• project and contract;
• event date and local time zone;
• building, elevation, grid, station, roadway segment, or work zone;
• observer name and role;
• onsite weather source;
• external station ID;
• linked daily report;
• affected schedule activity IDs;
• linked look-ahead tasks; and
• related notices or prior event IDs.

Weather can vary across a large site. “Project site” may be too broad when one elevation is exposed to wind, a trench collects runoff, and interior work remains unaffected.

Record a Time-Stamped Weather Timeline

Capture conditions at meaningful points:

• pre-shift observation;
• planned task start;
• threshold approach;
• stop decision;
• peak or material change;
• periodic checks during stoppage;
• attempted restart;
• end-of-shift condition; and
• next-shift readiness check.

Use local timestamps and retain raw instrument exports when available. Do not enter a single daily summary if the operation stopped for a two-hour storm and resumed afterward.

Example timeline fields:

Capture Measured Conditions and Source

Select variables relevant to the planned operations. Possible fields include:

• ambient temperature;
• surface or material temperature;
• relative humidity;
• wet-bulb globe temperature or another required heat measure;
• dew point and temperature spread;
• sustained wind, direction, and gust;
• precipitation type, amount, intensity, start, and end;
• snow depth, accumulation, or drifting;
• visibility;
• lightning observation or detection status;
• warning, watch, or advisory;
• cloud cover or solar exposure when relevant;
• soil moisture or ground condition;
• standing water or drainage condition;
• frost or frozen substrate;
• roof, coating, masonry, concrete, or other substrate condition; and
• indoor microclimate when enclosure work is affected.

Record units and method. “Wind 25” is ambiguous without miles per hour, knots, meters per second, sustained or gust, height, and source.

For heat-related stop and restart decisions, follow the employer's site-specific controls and OSHA's heat hazard guidance, then record how those controls affected the planned task.

Preserve Instrument and Station Limitations

An external airport station may corroborate a regional event while missing the exact jobsite condition. Record:

• station identifier and operator;
• distance and direction from the work;
• station elevation versus site elevation;
• observation interval;
• daily-summary time basis;
• missing or flagged data;
• sensor type when material;
• whether data are preliminary or certified; and
• known sheltering, terrain, urban, roof, or waterfront differences.

The National Weather Service describes ASOS as an automated network measuring items such as wind, temperature, precipitation, and visibility, primarily at airport locations. NCEI datasets such as GHCN-Daily and Synoptic Summary of the Day (SSOD version 2, the successor to GSOD) have their own reporting periods, quality controls, and completeness rules. Do not present a nearby station's total as though a gauge measured it at the work face.

SSOD uses a UTC calendar day; GHCN-Daily reporting periods follow the contributing service's observation conventions. Neither necessarily matches the site's local shift. Record the dataset version and reporting period before comparing totals. NCEI also cautions that SSOD precipitation can be underreported and its temperature extremes may miss the true daily extremes; it recommends GHCN-Daily for the most accurate daily rainfall and maximum/minimum temperature reports. Use appropriately timed observations to establish when work was affected rather than inferring the event timeline from a daily total.

Onsite readings also need context. An anemometer behind a trailer may understate roof wind. A thermometer in shade does not represent radiant roof exposure. A clogged rain gauge does not become accurate because its value supports a request.

State the Operation-Specific Threshold

There is no universal “rain day.” Weather affects operations differently.

For each planned task, identify the governing criterion from:

• contract specification;
• approved product data;
• manufacturer instructions;
• safety plan or applicable standard;
• inspection and test plan;
• approved work plan;
• permit or authority requirement;
• quality-control procedure; or
• reasoned field determination by the responsible role.

Record the exact source, revision, and threshold. Examples may involve:

• substrate dryness;
• minimum or maximum material temperature;
• wind limit for equipment or handling;
• lightning stop and restart rule;
• visibility for traffic control;
• rain intensity affecting placement;
• frozen ground;
• heat exposure controls;
• humidity or dew-point relationship; or
• cure and protection duration.

Do not invent a technical limit after the event. If no numeric threshold applies, document the observable condition and responsible decision basis.

Use the Construction Submittal Form to preserve the approved product data, manufacturer instructions, work plan, or test procedure that supplies the project criterion. If the documents conflict or do not identify a usable threshold, use the Construction Request for Information for the exact product, operation, references, observed condition, and question. An RFI response may clarify the technical basis; it does not decide weather entitlement.

Record Planned Work Before Describing Loss

The log should show what was credibly planned for the weather-affected period.

Capture:

• schedule activity and current update;
• look-ahead task;
• exact location;
• planned operation;
• planned start and finish;
• planned quantity;
• crew by employer, craft, and count;
• planned labor-hours;
• equipment and planned hours;
• required material;
• predecessor readiness;
• planned inspection or handoff;
• available float or path status from the current schedule; and
• alternate work identified before the event.

If the drawing, material, access, or predecessor was already missing, disclose it. Weather may have occurred without being the cause that prevented work.

Use the Construction Work Order to establish the released operation before the event. State the schedule activity, exact area, planned quantity, current documents, crew, equipment, start criteria, finish condition, alternate work, exclusions, and authorization. For WX-018, a useful instruction is: “R-410 Roof Area B membrane placement; dry-substrate criterion per approved product data; flashing preparation is approved alternate work; no placement outside Area B.”

Record Actual Crew, Equipment, and Quantity

Compare planned resources with actual deployment.

For labor, show:

• personnel onsite by employer and craft;
• regular and overtime hours;
• time on the planned operation;
• time on protection or mitigation;
• time on alternate productive work;
• time waiting, moving, or demobilizing;
• early release or reassignment; and
• reason for each material variance.

For equipment, show:

• asset or type;
• planned use;
• actual operating hours;
• weather protection or standby period;
• reassignment;
• demobilization; and
• operator status.

For production, show:

• planned quantity;
• quantity completed before stop;
• accepted quantity;
• quantity protected;
• quantity damaged or requiring rework;
• remaining quantity; and
• revised production assumption.

Do not label every difference a recoverable “lost hour.” The log records what occurred; cost and entitlement require separate analysis.

Explain the Causal Chain

Use a concise chain:

Measured weather → work-face condition → governing threshold → operational decision → actual effect

Example:

Onsite rainfall began at 08:35 and wetted the exposed deck. The current work plan requires a dry substrate before membrane placement. The roofing supervisor stopped placement, protected the open edge, and moved available personnel to eligible flashing preparation. No membrane placement resumed because documented substrate checks remained outside the project criterion.

Avoid:

Bad weather caused a full-day critical delay.

The first statement preserves facts and basis. The second skips readiness, mitigation, duration, and schedule analysis.

Distinguish Stop, Restrict, and Continue Decisions

Weather rarely affects every operation identically. Categorize work as:

• stopped for safety;
• stopped for quality or technical criteria;
• restricted to a reduced rate;
• moved to another area;
• converted to protection or recovery;
• performed offsite;
• continued normally; or
• not planned that shift.

List unaffected crews and work. This improves credibility and helps evaluate whether reasonable resequencing existed.

For lightning, follow the employer's safety program and applicable guidance. Use the Safety Inspection Checklist to record the actual warning or observed condition, affected area and equipment, shelter or access control, responsible role, corrective action, and recheck. The National Weather Service's lightning guidance for outdoor workers identifies construction and heavy-equipment work among exposed occupations and emphasizes advance warning and access to safe shelter. It advises workers who hear thunder to stop and seek shelter in a substantial building or a hard-topped metal vehicle. Record the stop decision and the basis for any later restart under the site's safety program. The weather record documents implementation of the plan; it does not replace it.

Document Mitigation Contemporaneously

Mitigation may include:

• temporary cover or enclosure;
• drainage, pumping, snow removal, or deicing;
• heaters, ventilation, or dehumidification under an approved plan;
• alternate means or sequence;
• shifting crews to interior or offsite tasks;
• protecting completed work and materials;
• reserving a replacement inspection;
• extending a shift when safe and authorized;
• adding resources;
• securing equipment before high wind;
• accelerating dry-out; and
• revising delivery or work-face plans.

For every action, record:

• proposer and approver;
• start and finish;
• labor and equipment used;
• result;
• constraint or risk introduced;
• reason an alternative was rejected; and
• effect on remaining work.

Do not promise unsafe or noncompliant acceleration. Do not imply that mitigation eliminates a valid notice. Follow both operational and contractual processes.

Use Photos as Located Evidence

Each photo should have:

• event ID;
• unique image number;
• original capture timestamp;
• photographer;
• exact location and direction;
• subject;
• scale or reference where useful;
• related measurement;
• annotation status;
• original-file preservation; and
• privacy or access restriction.

Photograph both the weather effect and the work state:

• rain gauge or instrument display;
• wet or frozen substrate;
• standing water and drainage;
• snow or ice accumulation;
• protected materials;
• stopped equipment;
• safe shelter or closure controls;
• installed quantity before stop;
• unaffected work continuing; and
• later restart condition.

A dramatic sky without a location or operation proves little. Use the overview, location, and detail sequence in photo requirements on every work order, and tie every image back to WX-018, the work face, and the relevant observation time.

Send Contractual Notice Separately

The log may be an attachment, but do not assume a daily report satisfies a formal notice clause.

Track:

• notice trigger;
• contract provision;
• deadline calculation;
• required recipient;
• required delivery method;
• initial notice ID;
• continuing update requirement;
• estimated cost and schedule effect, if required;
• mitigation statement;
• cessation notice;
• proof of receipt; and
• reservation or waiver language reviewed for the project.

Send the required notice and its weather-record attachments with the Construction Transmittal only when that delivery route matches the contract. Name the notice, event ID, attachments, sender, authorized recipient, purpose, issue time, and receipt evidence. A transmittal records what was sent; retain delivery or receipt confirmation separately. It does not create entitlement or replace a different notice method. The principles in schedule-change notices for service and construction jobs help keep facts, forecast effects, and requests distinct.

Use careful language while facts develop:

WX-018 records a potential weather-related impact to Activity R-410. Schedule and cost effects remain under evaluation. This log does not replace Notice N-027 or the contract's time-extension procedure.

Do not wait for the final schedule analysis if the contract requires earlier notice. Do not state a universal deadline in the template.

Link the Event to the Current Schedule

Record:

• affected activity ID and description;
• schedule update and data date;
• calendar;
• actual start status;
• remaining duration before event;
• predecessor and successor;
• path or float status before event;
• work period affected;
• revised remaining duration;
• resequencing;
• mitigation activity;
• path or float after the schedule update; and
• milestone forecast.

Weather can reduce production without delaying completion. It can delay a noncritical activity within available float. It can affect a longest-path activity and still be absorbed by mitigation. It can also combine with another cause.

If the authorized contract process ultimately grants a time, price, or scope adjustment, record that result in the Change Order with the event and notice IDs, exact adjustment, schedule effect, revised total, and signatures. Do not use the change order to rewrite the contemporaneous weather observations.

GAO's Schedule Assessment Guide emphasizes logically linked, regularly statused schedules that forecast effects on downstream work. Use schedule calculations and narrative—not a count of rainy dates—to evaluate time effect.

Compare Anticipated and Actual Weather Correctly

Some contracts build anticipated weather into calendars or monthly allowances. If so, preserve:

• baseline source and period;
• selected station;
• monthly allowance;
• weather-sensitive activities and assigned calendars;
• actual qualifying days under the contract definition;
• activity path status;
• work possible for part of the day;
• prior use of the allowance; and
• remaining or exceeded amount.

UFGS 01 32 17.00 20 illustrates one project-specific method using anticipated adverse-weather days and activity-path tests. Its definitions and thresholds are tailored to the applicable federal project; do not assume its “lost day” test applies elsewhere.

Historical normals and actual-event evidence serve different purposes. A normal helps plan expected exposure. It does not prove what happened on a particular roof. An event log shows current facts. It does not by itself prove the event exceeded the contractual baseline.

Identify Concurrent and Preexisting Constraints

For the affected activity, review whether any other condition independently prevented progress:

• design information missing;
• submittal not approved;
• material unavailable;
• predecessor incomplete;
• access unavailable;
• crew or equipment not mobilized;
• safety plan incomplete;
• inspection not booked;
• owner hold;
• changed condition;
• contractor sequencing choice; or
• another delay event.

Record the facts without making an unsupported legal conclusion about concurrency. A schedule or claims professional may need to analyze the timing and effect under the governing law and contract.

Continue the Event Through Restart

A storm ending does not always make work ready. Track:

• precipitation end;
• drainage or snow-removal completion;
• dry-out or thaw;
• substrate test;
• access restoration;
• equipment inspection;
• material condition;
• safety-plan restart criterion;
• reinspection;
• crew remobilization;
• actual restart; and
• residual productivity effect.

Use one event with a timeline when the condition is continuous. Use linked events when separate storms or freeze-thaw cycles create distinct impacts. Avoid duplicating the same hours across multiple logs.

When restart depends on a physical acceptance criterion, use the Construction Inspection Report for the exact work face, governing requirement, test method, readings, photographs, observed condition, reviewer, disposition, and reinspection. Wording such as “Roof Area B substrate checks at three listed points remain outside the approved dry-substrate criterion; no membrane placement released” is stronger than “still wet.”

Check the Event File Before Review

Keep raw instrument exports and schedule calculations with the project records. The daily report, safety and inspection records, formal notice, and any approved change should share the event ID and refer to the same timeline.

Resolve conflicting timestamps, quantities, or resource totals before submitting the file. Preserve corrections transparently rather than rewriting the original observations.

Worked Example: Roof Membrane Area B

Assume Activity R-410 is planned for membrane placement on Roof Area B. The approved daily plan calls for five roofing workers, two welding units, and 1,200 square feet of completed membrane during an eight-hour shift.

The project-specific work plan requires a dry substrate. The site safety plan also establishes a 25-mile-per-hour gust trigger for the exposed setup. These are hypothetical project criteria for the example, not universal limits.

Record the Planned Resources

Planned roofing labor is:

5 workers × 8 hours = 40 planned labor-hours

Planned welder use is:

2 welding units × 8 hours = 16 planned equipment-hours

The current schedule update shows R-410 started, with two days of total float before the event. The log records that value as a schedule snapshot, not a permanent entitlement.

Record the Event Timeline

At 06:00, the onsite gauge shows no precipitation, the deck passes the documented dryness check, and winds are below the project trigger. Placement begins at 06:35.

Rain begins at 08:35. The roofing supervisor stops membrane placement, protects the open edge, and records the condition. The onsite gauge accumulates 0.62 inch before rainfall ends at 10:20. An onsite anemometer records a peak gust of 28 miles per hour during the event.

Substrate checks at 13:00 and 15:00 do not satisfy the project's dry-surface criterion, so placement does not resume that shift. Photos WX-018-P01 through WX-018-P06 show the gauge, wet deck, protected edge, completed quantity, drainage work, and later test locations.

The nearest selected ASOS station is nine miles away. Its archived values corroborate regional precipitation and wind but differ from the onsite totals. The log preserves both sources and does not substitute the airport reading for the work-face measurement.

Reconcile Labor and Equipment

The five-person crew places membrane for two hours:

5 workers × 2 hours = 10 direct installation labor-hours

After the stop, three workers perform eligible flashing preparation in a protected area for five hours:

3 workers × 5 hours = 15 alternate productive labor-hours

Two workers spend four hours protecting edges, managing drainage, and securing material:

2 workers × 4 hours = 8 mitigation labor-hours

The remaining planned labor-hour difference is:

40 − 10 − 15 − 8 = 7 labor-hours

The log allocates those seven hours from actual time records among transition, weather waiting, cleanup, and early release. It does not automatically label them compensable standby.

The two welders operate for two hours:

2 units × 2 hours = 4 actual operating equipment-hours

Their remaining status is recorded as secured onsite, not simply “12 hours lost.”

Reconcile Production and Schedule Effect

The crew completes and protects 300 of the planned 1,200 square feet, and the inspection record confirms that quantity is accepted:

300 square feet ÷ 1,200 planned square feet × 100 = 25% of planned quantity

The remaining quantity is:

1,200 − 300 = 900 square feet

The scheduler updates actual quantity and remaining duration after confirming dry-out and remobilization. With other logic unchanged, the current calculation shows one day of R-410 float remaining and no present movement to the contractual completion milestone.

The log therefore states:

• operation effect: membrane placement stopped and 900 square feet remained;
• current schedule effect: R-410 forecast moved and calculated float reduced in the cited update;
• milestone effect: none currently forecast;
• mitigation: flashing preparation and protection completed; and
• contract treatment: pending under the notice and schedule procedure.

It does not call the event a one-day compensable delay merely because the roof crew could not finish its original quantity.

Useful Weather-Record Calculations

Planned-to-Actual Production

Actual accepted quantity ÷ planned quantity × 100

Keep rejected or reworked quantity separate.

Direct Operation Utilization

Labor-hours on planned operation ÷ planned operation labor-hours × 100

Show alternate productive and mitigation time beside the result.

Work-Face Downtime

Restart-ready timestamp − stop timestamp

This measures elapsed time and may extend beyond active precipitation because drainage, dry-out, inspection, or safety criteria remain open. Separately identify the scheduled working periods affected. Overnight hours and nonworking days are not automatically lost working time, labor-hours, or compensable delay.

Weather Allowance Use

Qualifying actual weather periods − applicable anticipated allowance

Use only the definition and period established by the contract. A positive value alone does not prove milestone delay.

Forecast Quantity Remaining

Planned quantity for the defined work area and period − accepted quantity completed for that same scope

Recalculate remaining duration using a supportable production rate and current conditions rather than assuming linear recovery.

Common Mistakes

Writing “Weather Delay” Without Measurements

The record contains a conclusion but no evidence. Capture timed values, source, site effect, and operation.

Using Only a Distant Airport Station

Regional data may not represent roof wind, trench water, direct sun, or local precipitation. Use it as a disclosed reference and preserve onsite facts.

Claiming the Whole Site Stopped

Interior or offsite work continued. Separate affected, restricted, reassigned, and unaffected operations.

Omitting Planned Crew and Equipment

The log cannot show what deployment changed. Record the credible pre-event plan and actual allocation.

Counting Rainfall as Schedule Delay

Precipitation occurred, but the task had float or was not ready for another reason. Link weather to the operation and current schedule network.

Ignoring Conditions After the Storm

Rain ends, but wet substrate or flooded access prevents restart. Continue the event through documented readiness.

Treating a Daily Report as Formal Notice

If the contract requires a separate recipient or delivery method, the daily report may not satisfy it. Track formal notice independently.

Calling Every Hour Standby

Some crew members may shift to alternate work or protection, handle cleanup, or leave early. Reconcile actual time before cost characterization.

Hiding Concurrent Constraints

The material or design was already unavailable. Disclose every condition bearing on readiness.

Backfilling Identical Entries at Month End

Copied descriptions lose the event timeline and contemporaneous credibility. Record conditions as they develop and correct them transparently.

Record the Event Before Arguing the Remedy

Weather documentation is strongest when it remains specific and modest. Measure the conditions, show the affected work face, reconcile the planned and actual resources, explain why the operation changed, preserve mitigation, and connect the event to the current schedule.

That factual chain gives safety, quality, project controls, and contract reviewers something reliable to evaluate. A conclusion written without the chain gives them only a label.

Sources

1. AACE International — Recommended Practice 84R-13, Planning and Accounting for Adverse Weather, public sample, revised September 15, 2015; checked October 4, 2026. The sample does not contain the full recommended practice, and AACE notes that revisions may evolve.
2. U.S. Government Accountability Office — Schedule Assessment Guide, GAO-16-89G, published December 22, 2015.
3. Federal Acquisition Regulation — 52.249-10, Default (Fixed-Price Construction), clause dated April 1984; current text under FAC 2026-01, effective March 13, 2026; accessed October 4, 2026.
4. Federal Acquisition Regulation — 52.236-15, Schedules for Construction Contracts, clause dated April 1984; current text under FAC 2026-01, effective March 13, 2026; accessed October 4, 2026.
5. Whole Building Design Guide — UFGS 01 32 17.00 20, Cost-Loaded Network Analysis Schedules, May 2025.
6. NOAA National Centers for Environmental Information — Climate Data Online.
7. NOAA National Centers for Environmental Information — Global Historical Climatology Network Daily.
8. NOAA National Centers for Environmental Information — Synoptic Summary of the Day (SSOD version 2), successor to GSOD; reporting periods and measurement limitations checked October 4, 2026.
9. National Weather Service — Automated Surface Observing System.
10. National Weather Service — Lightning Safety on the Job.
11. Occupational Safety and Health Administration — Heat Hazard Recognition.

Disclaimer

This article provides general construction recordkeeping information, not legal, scheduling, engineering, meteorological, or safety advice. Contract terms, applicable law, project specifications, and site conditions control. Have qualified counsel, a scheduler or claims professional, and the site safety lead review material delay, notice, and stop-work questions.