Weather Delay Log Template: Free Excel Weather Record (NEC4)
A ready to use Excel log for recording daily weather measurements and the work they delayed, built to feed the NEC4 clause 60.1(13) one in ten year comparison. Built by quantity surveyors.
Will Doyle
Founder and CEO, Gather · Chartered QS · Last reviewed 23 July 2026
A weather delay log is a daily record of the weather measurement at site (rainfall, temperature, wind, or whichever measurement is stated in Contract Data) alongside the work it delayed. Under NEC4 clause 60.1(13), a weather compensation event exists only where a recorded measurement, within a calendar month and before Completion, is shown by comparison with the weather data to occur on average less frequently than once in ten years at the stated weather station.
The log itself is not the compensation event. It's the contemporaneous evidence that lets a QS run that comparison when a wet month or a cold snap looks like it might qualify.
What a good weather delay log covers
Most sites record weather as a one line note: "heavy rain, works delayed." That's not enough to support a clause 60.1(13) compensation event, because the clause turns on a specific measurement compared against historical weather data for the stated station, not on a general impression that it rained a lot. This template records the actual measurement every day, so the comparison can be run properly when a month looks unusual.
| Field | Why it matters |
|---|---|
| Date and weather station | Must match the station stated in Contract Data for the comparison to be valid |
| Measurement type and value | Rainfall, temperature or whichever measurement Contract Data specifies, recorded as a number not an impression |
| Work affected and hours lost | Ties the measurement to an actual delay to a specific activity |
| 1 in 10 year comparison value | The historical threshold for that measurement and month, entered once and compared automatically |
| Threshold exceeded (calculated) | Flags any day where the measurement is worse than the one in ten year value |
| Evidence reference | Points at photos, met office data or other supporting records |
How to complete the log
Five steps, every day the weather affects the works. The whole point is that the measurement is captured as it happens, not reconstructed at the end of a month that turned out to be wet.
-
Record the weather station
Use the weather station stated in Contract Data for every entry. A measurement from any other station will not support the comparison.
-
Record the daily measurement
Log the measurement type and value stated in Contract Data, such as rainfall or temperature, as a number rather than a description.
-
Record affected work and hours lost
Note the activity affected and the hours lost to the weather, so the measurement ties to a real delay rather than sitting on its own.
-
Compare against the 1 in 10 year value
Enter the historical one in ten year comparison value for that month and let the template flag any exceedance automatically.
-
Reference supporting evidence
Attach photos or third party weather data that support the recorded measurement, so the entry stands up if it is challenged later.
The template, field by field
| Date | Measurement | Recorded value | 1-in-10yr value | Status |
|---|---|---|---|---|
| 04 Mar | Daily rainfall | 38mm | 32mm | Exceeded |
| 11 Mar | Daily rainfall | 18mm | 32mm | Within range |
| 19 Mar | Wind speed | — | — | Not measured |
Scroll the table sideways to see every column.
The Weather Delay Log tab is where the daily measurement and affected work are entered against the station and measurement type stated in Contract Data; the Dashboard tab rolls that up into a monthly view showing how many days exceeded the one in ten year comparison. The How to use tab explains every column with a worked example.
Download the free template
The Excel file with daily weather measurement logging, the one in ten year comparison column, and a monthly exceedance summary.
Download the template (.xlsx) Free download. No email needed. Yours to use and share with your team.Worked example: a wet March against the one in ten year threshold
On 4 March, 38mm of rainfall is recorded at the weather station stated in Contract Data, against a one in ten year value of 32mm for that month at that station. The log records the measurement, the affected groundworks activity, and the hours lost the same day. Later in the month, the QS pulls the log to check whether March as a whole supports a clause 60.1(13) notification, and the 4 March entry, recorded contemporaneously with the actual figure rather than a note that "it was very wet," is what makes that comparison possible.
Compare that with 11 March, where 18mm falls: within range, no event, correctly excluded rather than lumped in with a vague "wet month" claim that wouldn't survive scrutiny.
How Gather automates this
A weather delay log is only useful if the measurement gets recorded every day, in the right units, against the right station, whether or not that day turns out to matter later. Most sites only start logging weather properly once a month already looks unusual, by which point the early days of it are gone.
Gather's AI QS reads every daily record as it comes in and flags the events, delays and instructions that turn into money later, so the entitlement is captured while the evidence is still fresh.
See how the AI QS reads your site diaries A 30 minute call. No commitment. See if it fits how your team already works.Frequently asked questions
What makes weather a compensation event under NEC4?
Under clause 60.1(13), a weather measurement recorded within a calendar month, before the Completion Date for the whole of the works, at the weather station stated in Contract Data, must by comparison with the weather data occur on average less frequently than once in ten years.
What should a weather delay log record?
The date, the weather station, the measurement type and value stated in Contract Data, the work affected and hours lost, the one in ten year comparison value for that month, and whether the threshold was exceeded.
Is a general note that it rained heavily enough to support a claim?
No. Clause 60.1(13) requires an actual recorded measurement compared against historical weather data for the stated station and month, not a general impression of bad weather.
Does this log replace the compensation event notification?
No. The log provides the contemporaneous measurement evidence. The compensation event still needs to be notified within the clause 61.3 eight week time bar once the team becomes aware the threshold has been met.
.webp)
