Climate force majeure proof: how to prove it with auditable data (not with a weather app screenshot)
Mateus Lima
CEO
··5 min read
The delivery was delayed two days because the rain closed the highway. The client applies the contractual penalty. You respond with a screenshot of the weather forecast app and a news story about the storm in the region. The response comes in one line: a forecast is not a record of what happened, and the news story talks about another city.
This scenario repeats itself in transportation, storage, construction and critical asset operation contracts. Whoever has a contractual dispute needs proof, and most companies only start looking for that proof after the dispute has begun. This guide shows how to prove climate force majeure with a technical dossier that withstands challenge.
This text deals with technical evidence and data records. The legal qualification of an event as force majeure is up to your legal counsel.
What the counterparty questions in proving force majeure
The definition of force majeure in the Civil Code (art. 393) refers to a necessary fact whose effects it was not possible to avoid or prevent. In practice, the counterparty usually questions five points:
Location. Did the event hit the exact point of the operation or just the region? A weather station in another municipality does not answer this question.
Intensity. Was the rain or wind outside the pattern for that location and that time of year, or was it expected?
Predictability. If there was an alert, why wasn't the operation prepared? For this reason, the alert alone can work against whoever presents it. Together with the record of the action taken, it becomes proof of diligence.
Nexus. Did the delay result from the climate event or from another cause that coincided with it?
Source. Who produced the data, using what method, and can it be verified by a third party?
Climate report to justify delay: what works in a dispute and what doesn't
Not every document carries the same weight. In general, the ones that help the least are:
screenshots of forecast apps, which show what was expected and not what occurred;
generic news stories, without coordinates or time;
regional bulletins that cover an area much larger than that of the operation;
team accounts made after the fact, without a contemporaneous record.
A climate report to justify delay tends to better support the technical argument when it brings together:
meteorological history at the asset's exact point, with source, method and period stated;
comparison of the event with the historical series for the same location, showing whether it was atypical;
records made during the event: alerts received, decisions made, photos and messages with date and time;
data from official stations, such as those of INMET, when they are close enough to the asset, and weather radar images, which show where the rain passed and at what time;
a technical report that brings all of this together with a responsible party's signature.
Contractual climate risk management in logistics: record the event before it happens
The best evidence is assembled before the event. Four practices make the difference when the dispute arrives:
1. Register assets with coordinates. Distribution centers, yards, critical route stretches. Without coordinates, there is no way to prove that the event hit that point.
2. Archive alerts with timestamps. The alert shows when the company learned of the risk, which answers the question about predictability.
3. Record the decision made. If the company received the alert and acted, the record shows diligence. If the action was not enough, it shows that the effect could not be avoided.
4. Notify the counterparty early. Many contracts require notice within a defined period. A notification with the data attached, sent on the same day, is worth more than a dossier sent a month later.
Meteorological history for companies: from raw data to technical report
Meteorological history is available from several public sources. What separates raw data from evidence are three attributes.
Resolution
The most commonly used free historical data comes from stations, which can be dozens of kilometers from the asset, or from global reanalyses, with a grid of about 30 km. A summer storm, which forms quickly and covers a small area, can hit the yard and spare the nearest station, or the opposite. i4sea reconstructs conditions at a resolution of 1 to 3 km, which brings the data closer to the point where the operation stopped.
Source and method
The report needs to state where each number comes from. i4sea uses a proprietary 10-year reanalysis, covering 18 climate hazards, which makes it possible to compare the event with a decade of history at the same location and say whether it was inside or outside the pattern.
For very rare events, it is worth adding long series from official stations, because ten years is not enough to safely measure something that happens once every few decades.
It also matters to separate what is measured from what is estimated: stations and radar record what happened, while reanalysis is a model estimate. The counterparty may question the modeled data, so the strongest report combines both and makes clear where each value comes from.
Chain of custody
The counterparty will ask who extracted the data, when, and whether it was altered. The report must record the extraction date, the model version and the parameters used, so that an expert can reproduce the result.
Climate force majeure dossier checklist
Before sending the proof, check whether the dossier has:
coordinates of the affected asset or stretch;
exact period of the event, with start and end;
measured values (station, radar) or model-estimated values, such as accumulated rainfall, wind gust or visibility, always with the unit and indicating what is measured and what is estimated;
comparison with the history of the same location;
alerts received before the event, with timestamps;
record of the team's decisions and actions;
notification sent to the counterparty and the sending date;
source, method, resolution and extraction date of each piece of data;
identification of the technical party responsible for the report.
A complete dossier does not guarantee the outcome of the dispute. It guarantees that the discussion will be about what happened, and not about the quality of the evidence.
Start with the history of the event that affected your operation
i4sea reconstructs conditions at your asset's exact point, compares them with the 10-year series and reports, for each number, the source, the method and the resolution. It is this combination that supports a proof dossier.
Test it with a real event. i4sea's AI Climate Agent checks the location's history in conversation and shows what happened at the asset's exact point.
References
Brazil. Civil Code, Law No. 10.406/2002, art. 393.
i4sea. Product data: proprietary 10-year reanalysis, 1 to 3 km resolution, 18 climate hazards.
We use analytics cookies to understand how the site is used and marketing cookies to measure our campaigns. They are only enabled with your permission.