Foreman
Connection

Connect Foreman and the weather record

Your diary says work stopped and why. The weather archive independently confirms the conditions. A delay supported by both is a different proposition.

Updated 30 August 2026 4 min read
Foreman brings
The site record: who was on the job, the hours, the photos, the inductions and the dates.
the weather archive brings
Current conditions, forecasts and decades of Australian historical weather, by location and date.

You do not connect these to each other. You connect both to the same AI assistant — Claude or ChatGPT — and then just ask it, in your own words, for something that needs the two of them. The assistant is the bit in the middle. There is nothing to install and no code to write.

The technical detail, if you want it

Assistants reach outside tools through something called MCP. Foreman runs its own, the weather archive has one too, and it is built on Bureau of Meteorology data. Make sure you pick an Australian one: the most widely copied option runs on the US weather service and returns nothing useful here.

Rain is the single most common reason a job runs late, and the diary entry that says so is usually the only record of it. What that entry cannot do on its own is prove it rained.

Connect the weather archive and it can.

Practical ways to use Foreman and the weather record

Corroborate a delay for an extension of time claim.

"On 17 March we lost two and a half hours to rain at Pacific Avenue. What was the weather doing that afternoon?"

This is the strongest use of the pair. Your diary entry, written on the day, says work stopped and why. The archive independently confirms the conditions at that location. A claim supported by both is a different proposition to one supported by your word.

Count what the weather actually cost you this year.

"How many days did I lose to weather across all jobs in the last twelve months, and on which sites?"

Most builders estimate this. Very few can answer it from records.

Check whether the delay you recorded was really weather.

"Show me every delay I logged as rain where it did not actually rain."

Uncomfortable, useful, and the kind of thing worth knowing before someone else checks.

Plan around the pour.

"The slab pour at Beach House is booked for Thursday. What is the forecast, and have I got a wet-weather note in the diary for that site recently?"

Build the weather record for a claim period.

"Give me the conditions for every day we were on site at Kingsley Street in February, next to what the diary says we did."

Make sure you get Australian weather

That sounds obvious, and it is the thing most likely to trip you up. There are several weather options an assistant can use, and the most widely copied one runs on the United States weather service. Ask it about Miami on the Gold Coast and you will get nothing back, or worse, Miami in Florida.

So pick one built on Australian data. The good ones draw on Bureau of Meteorology observations and carry decades of history.

Other than that it is the usual pair: an assistant, Claude or ChatGPT, and Foreman connected from API and integrations in your account. If you are not sure which weather option to choose, ask us and we will point you at one.

Foreman stores no weather at all. The diary has a free-text description where a builder might mention it, and nothing structured. Everything on this page comes from the archive, joined to your dates and project addresses.

Why this beats the built-in version

Several construction apps stamp today's weather onto a diary entry automatically. That is convenient, and it is also only ever about today.

The claim you have to defend is eighteen months old. What matters then is being able to check a long history against your own delay records, for that site, on that afternoon. The Australian options reach back decades, and that is the part that actually settles arguments.

Is a site diary a legal requirement in Australia? covers why contemporaneous delay records matter so much, and how to keep a site diary covers writing the entry that this is joined to.

Want a hand setting this up?

Most builders get this working in about ten minutes, and you do not need to be technical to do it. But if you would rather not work it out on your own, tell us what you are trying to get out of the weather archive and we will set it up with you — on a call, at no cost, whether or not you are paying us anything.

Ask us to set it upTell us which tools you use. We will reply with the steps for your setup.

Sources

Every regulatory statement on this page traces to one of these. We recheck them when we update the page.

Frequently asked questions

Does Foreman record the weather?
No. The site diary has a free-text description where a builder might mention it, and nothing structured. Everything on this page comes from a weather archive joined to your dates and project addresses.
How does this help an extension of time claim?
Your diary entry, written on the day, records that work stopped and how long you lost. The archive independently confirms the conditions at that location on that date. A claim supported by both is stronger than one supported by your recollection.
Other apps stamp the weather on automatically. Isn't that better?
It is more convenient, and it only ever tells you about today. The delay you have to defend is eighteen months old by the time anyone argues about it, and that is a question for an archive. Australian servers built on Open-Meteo go back decades.

The delay record is the half worth keeping.

Foreman logs what stopped, why and for how long, on the day it happened. Free on your first project.