Weather-day policy for concrete subs

"Weather day" sounds simple. In practice, it's one of the most contested concepts on a job site. The GC's super wants to push the call (every weather day slips their schedule). You want to make the call early (concrete doesn't cure in rain). The estimator wrote vague contract language a year ago. Now it's 5 PM Thursday and you're trying to decide whether to cancel tomorrow, and you know there will be a billing argument either way.

The teams that get this right share two habits: their contracts define weather days specifically, and their cancellation documentation is automatic, not reconstructed later.

What "weather day" should mean in your contract

Vague version: "Contractor may delay performance due to adverse weather conditions."

That language gives the GC infinite room to dispute. A better version names specific thresholds:

Variations: some subs prefer hour-based windows (e.g., "between 4 and 10 AM"). Some adjust temperatures based on local climate. The key is specific, NWS-referenced thresholds, not "adverse conditions."

When to call a weather day

The 6 PM rule

Make the call by 6 PM the day before. Why:

• Ready-mix dispatch can release your trucks
• Pump operator can route their truck elsewhere
• Crew has time to make childcare/transport arrangements
• You have time to notify GC's super while they're still at the office

Earlier is better. Later than 6 PM and you're paying for at least short-load fees + pump no-show minimums even if the weather actually hits.

The 50% threshold

If NWS forecast probability of measurable precip is >= 50% during your pour window, call the weather day. Yes, sometimes you'll cancel and the rain doesn't materialize. The math: a false-positive cancellation costs you a day of rebooking; a false-negative (pour gets rained on) costs you the pour, plus the surface defects in the slab, plus the GC's confidence in your judgment.

The pour-type modifier

Cold weather + footing: usually OK with proper protection.
Cold weather + decorative finish: cancel.
Rain + interior slab in a closed building: usually OK.
Rain + exterior flatwork: cancel.

The contract language should accommodate this with phrases like "subject to pour type and protection plan." Don't just write a one-size-fits-all temperature threshold and then realize Tuesday that you painted yourself into a corner.

How to document a weather day so the GC can't dispute it

The reason most disputes happen is that the documentation gets reconstructed weeks later from memory. The GC's super swears you canceled "because of light drizzle"; you swear the forecast called for 1.5 inches. Without contemporaneous records, you both lose.

1. Save the NWS forecast at the moment you decide

Screenshot the forecast (or use a tool that captures it automatically) when you make the call — not later. Include the timestamp, the location, and the specific forecast values that triggered your decision.

2. Send written notice immediately

The 6 PM written notice to the GC super should reference the contract clause + the specific forecast values. Example:

3. Capture the cancellation log automatically

Every notification you send — to ready-mix, pump, GC, owner's rep, crew — should be archived in one place with timestamps. If a dispute arises three months later, you pull up the pour record and there it all is. If it's reconstructed from your sent-mail folder, you're going to lose pieces.

4. Track weather-day frequency as a contract metric

If a project has 18 weather days in a 12-month schedule, that's a contract overrun indicator the GC's PM wants to know about — and it's a fact you control because you have the records. Frequency matters for billing arguments at closeout.

The cost of getting this wrong

Three failure modes, in order of expense:

1. Don't cancel; rain hits. Lost pour + surface defects + crew + ready-mix + pump cost. $5,000-50,000 depending on scale.
2. Cancel poorly (late, ambiguous, undocumented). Short-load fees, pump minimums, billing disputes, GC relationship damage. $500-5,000.
3. Cancel correctly but get billed for it. Liquidated damages because the contract language was vague and the GC's lawyer won the argument. $1,000-25,000.

The contract language + documentation discipline above eliminates #3 and most of #2.

How a pour-scheduling tool helps

The contract language is on you. The documentation is where Place & Finish Hub earns its keep:

• A rolling 10-day forecast on every pour row, pulled from each project's ZIP and color-coded good / hedge / hold with a severe-weather flag — no manual lookup, so the call is in front of you when you make it
• One-click cancellation notifications with the reason logged (Weather, with a sub-kind of Rain, Cold, Heat, Snow/Ice, Wind, or Other) — email to every contact (SMS coming soon), every timestamp
• Audit log of who declared the weather day, when, and what notifications fired
• Cancellation history per project for closeout reporting

The getting-started guide covers setting each project's ZIP so the forecast lights up.