Excusable vs. compensable delay: how weather is handled in your commercial contract

In late July a developer called us about a retail pad near the Borderplex that was running behind. His contractor had stopped work for most of a week during a monsoon stretch, then sent a letter asking for both more time and more money. The owner wanted to know which one he actually owed.

That is the right question, and almost nobody asks it until the rain has already cost them. The answer lives in two words buried in your contract: excusable and compensable. They sound interchangeable. They are not. One costs you calendar days. The other costs you cash. Knowing the difference before you sign is how you keep a normal El Paso monsoon from turning into a fight.

Excusable versus compensable, in plain terms

Every weather delay falls into one of three buckets, and the contract decides which.

• Non-excusable. The delay was the contractor's fault, poor planning, slow crews, a missed order. The contractor eats both the time and the cost. You owe nothing.
• Excusable but non-compensable. The delay was outside anyone's reasonable control. The contractor gets more time to finish but no more money. Normal weather lives here.
• Excusable and compensable. The delay was caused by the owner or someone the owner controls, a late design decision, a stop-work order, an owner-furnished item that showed up late. The contractor gets both more time and added money.

Weather almost always lands in the middle bucket. When a monsoon cell parks over your site and the crew cannot pour or roof, that is nobody's fault. The standard outcome is a time extension, not a check. The contractor absorbs the idle day, you absorb the later finish date.

Why ordinary monsoon rain does not pay

The legal idea underneath this is foreseeability. A contractor bidding a job in El Paso is expected to know it rains here in the summer. Monsoon season runs roughly July through September. That is not a surprise, it is a calendar.

Because it is foreseeable, the cost of normal rain is supposed to be built into the bid and the schedule from day one. The contractor cannot stop work for a typical afternoon storm and then bill you for the lost hours as if it were a shock. Under the common industry contracts used across Texas and New Mexico, including the standard American Institute of Architects and ConsensusDocs forms, abnormal or unusually severe weather is grounds for a time extension only. The money side stays with the contractor unless your contract was specifically negotiated otherwise.

The word that matters is abnormal. A normal monsoon does not earn anything. Weather that meaningfully exceeds the historical norm for that month is what opens the door to a time extension.

The weather-day baseline decides everything

This is the part owners skip and later regret. A good commercial schedule does not assume zero rain days. It assumes a baseline.

A weather-day baseline is the number of lost-work days the schedule already bakes in for each month, drawn from local climate records. For the Borderplex, that means the schedule should carry meaningful rain-day allowances in July, August, and September and very few the rest of the year. National Weather Service and similar climate data for El Paso give a defensible monthly average to anchor those numbers.

Here is why it matters to you. Only days that exceed the baseline count as a delay that earns more time. If your contract assumes four lost days in August and the job loses four, the schedule already accounted for it and you owe no extension. If the job loses nine, the five days beyond baseline are what gets evaluated for a time extension.

Without a baseline in the contract, every argument becomes a fresh fight with no reference point. With one, the math is simple and both sides know the rules before the first cloud shows up. Insist that your contract names a monthly weather-day baseline. It is the single most useful clause for keeping weather claims honest.

Notice requirements will sink a valid claim

Here is the trap that catches good contractors and surprises owners. A weather delay can be completely legitimate and still get denied because nobody gave notice in time.

Almost every commercial contract requires written notice of a delay within a set window after the event, commonly a few days up to roughly two weeks. Miss that window and the claim can be waived no matter how real the rain was. The clause exists for a reason. It lets the owner verify the weather while the records are fresh and decide whether to adjust the plan.

So whichever side of the table you are on, the discipline is the same. Notice goes out in writing, promptly, every time. Not bundled into a single letter at the end of the job when the contractor suddenly wants forty days back. As an owner, a contractor who sends timely, specific weather notices is showing you they run a real schedule. One who saves them all for the final pay application is building a claim, not managing a job.

What real weather documentation looks like

A time extension stands or falls on proof. "It rained a lot" is not proof. When a weather claim is handled well, the file contains specific, day-by-day records.

• Daily reports that log the weather, the work planned, the work actually performed, and the crews sent home, signed and dated as the days happen.
• Objective weather data for the site, from the nearest National Weather Service station or an on-site gauge, showing actual rainfall against the baseline.
• Schedule impact analysis that shows the delayed activity was on the critical path. A rained-out task with float did not move your finish date. A rained-out task on the critical path did, and the schedule has to demonstrate it.
• Site photos time-stamped, showing standing water, saturated caliche subgrade, or conditions that genuinely prevented the work.

That last point separates a real claim from a reflexive one. If the crew could not pour a slab because the subgrade was a soup of saturated caliche, that is a documented impact. If they were tiling an interior the rain never touched, the weather did not delay anything on the critical path and no extension is owed. The schedule, not the storm, proves the impact.

What to lock down before you sign

You do not need to be a scheduler to protect yourself. You need a handful of clauses defined in writing before the contract is executed, not argued over in August.

• A stated weather-day baseline by month, anchored to El Paso or Las Cruces climate data.
• Clear language that ordinary weather is excusable and non-compensable, time only.
• A defined notice window and the requirement that notice be in writing.
• A requirement that any weather claim include daily reports, weather data, and a critical-path impact analysis.
• Agreement on whose weather data governs, so you are not arguing sources later.

Get those five settled up front and a monsoon becomes a scheduling event you both understand, not a dispute. Leave them vague and every rainy week becomes a negotiation you will probably lose.

If you have a contract or a bid set in front of you and you are not sure how it handles weather, send it to our team for an honest read. We will tell you whether the weather-day baseline is realistic for the Borderplex, whether the notice and documentation language protects you, and where a normal monsoon could quietly cost you time or money. Win the work or not, you will know exactly what you are signing.