Construction weather platforms: which type do you need?

Four types of platform — one name for all of them

Search for "construction weather software" and you will find a broad range of products that use similar language but serve fundamentally different purposes. Some are field workability apps designed for trade supervisors deciding whether to mobilise a crew. Some are hardware stations that mount on a site fence and record local conditions. Some are enterprise alert systems that push notifications to many sites at once. And some — a smaller category — are contractual workflow platforms designed to support the programme, commercial and legal functions of a construction project.

None of these is the right answer for every project, and several categories frequently overlap in their marketing. The purpose of this guide is to describe each category honestly, explain what each one is genuinely good at, and help you match the right tool to the actual problem you are trying to solve.

This is not a product ranking or a competitive review. It is a description of four distinct approaches to weather risk in construction — with the honest tradeoffs that come with each.

The four categories

Each category is well-suited to a different audience and a different moment in the project lifecycle. The challenge for buyers is that marketing language often conflates them — "weather intelligence for construction" can describe any of the four.

Category 1: Field workability apps — and what they are actually for

Field workability apps emerged to solve a real and immediate problem: the site supervisor standing in the rain at 6am trying to decide whether to mobilise a 20-person crew. Traditional general-purpose weather apps were not designed for this. They give you temperature and cloud cover for the city centre, not rain intensity and gust speed at the specific site location.

The best field apps address this with location-specific forecasts, trade-relevant indicators and a simple, fast interface usable on a phone in PPE. They are genuinely useful for the decision they are designed to support: go or no-go, today.

Where they typically fall short is at the project management and commercial level. A field app is designed for today's decision, not last month's claim or next year's tender. When a project director needs to benchmark last quarter's weather against the historical norm for an EOT claim, or a contracts manager needs to issue a formal early warning notice with the correct contractual language, a field workability app is not the right tool — even a good one.

The notification records generated by field apps can sometimes be used as supporting evidence in a weather delay claim, but they were not designed to carry contractual weight and typically lack the structure — historical benchmarks, threshold analysis, programme linkage — that a formal claim requires.

Category 2: On-site hardware stations — when local measurement matters

On-site weather stations record conditions at the exact site location, rather than interpolating from nearby meteorological stations or forecast models. For some projects and some operations, this matters a great deal: a high-rise tower in an urban canyon may experience significantly different wind conditions from the regional airport 8km away, and craneage is exactly the kind of operation where that difference is safety-critical.

The practical limitations of hardware stations are less often discussed. They only record from the date of installation — there is no historical record before the station was placed. This creates a gap at exactly the moment it matters most: when a contractor needs to benchmark the project weather against the historical norm to establish whether conditions were exceptional.

A station installed at project commencement will have recorded, say, eight months of data. To establish whether those eight months contained "exceptional" weather by the standard of the contract, the contractor still needs a long-term historical dataset for the same location — and the station itself cannot provide that. Hardware and historical data services are typically used together for this reason.

Hardware stations also require physical installation, calibration and maintenance. On a long-run infrastructure project this is routine. On a six-month residential development it may be disproportionate — particularly if a quality historical data service covers the location adequately.

Category 3: Enterprise alert systems — portfolio monitoring at scale

Enterprise weather alerting platforms are built for organisations managing weather risk across many sites simultaneously — a principal contractor with 40 live projects, a crane hire company monitoring lifting operations across a region, or an insurer tracking exposure across a construction portfolio.

These platforms typically integrate with the organisation's broader systems, provide configurable alert rules by site and condition, and push notifications through email, SMS or integrated channels. They are genuinely well-designed for the problem they solve: ensuring that no site in a large portfolio misses a weather event that should have triggered an alert.

The tradeoff with enterprise alert systems is depth versus breadth. They are optimised for monitoring at scale — not for the detailed contractual workflow of an individual project. They typically lack tender-stage historical analysis, trade-specific advisory frameworks referenced against published standards, and the document generation capability needed for formal contractual notices and EOT evidence.

For a large contractor, an enterprise alert system and a contractual workflow platform can be complementary rather than competing. The alert system ensures the portfolio is monitored; the workflow platform provides the contractual infrastructure for individual projects where formal notices and evidence are required.

Category 4: Contractual workflow platforms — the tender-to-claim lifecycle

Contractual workflow platforms occupy a different part of the market from the categories above. They are designed for the programme, commercial and contracts functions of a construction project — the people who price the tender, manage the programme, issue formal notices and assemble delay evidence.

The core capability that distinguishes this category is historical data combined with structured contractual output. Where a field app answers the question "can we work today?", a contractual workflow platform answers a different set of questions:

• How many weather-affected days should we allow per trade operation in the tender programme?
• Does the forecast for the next 14 days trigger the contractual obligation to issue an early warning notice?
• How does last month's actual weather at this location compare with the ten-year historical benchmark — and did any days qualify as exceptional under the contract?
• Can we produce a formatted EOT evidence document that tests the actual conditions against the contract's specific threshold wording?

The primary audience for this category is not the site supervisor — it is the contracts manager, QS, project manager, or commercial director. They use it at the desk, in the project office and in the dispute resolution process, not on the site fence in PPE.

This category is smaller and less visible than field apps or hardware because the problem it solves is less immediately visible. A crew standing in the rain is an obvious problem. A weather EOT claim that was never made, because the evidence was never assembled, because the notices were never issued, because nobody was tracking the contractual position — that is a much quieter failure, and it typically only becomes visible in the final account.

Choosing the right fit — a plain comparison

Most projects do not need all four categories. The table below summarises which capabilities fall naturally within each category and which require a different tool.

Three questions that identify the right category

Rather than starting with a shortlist of products, start with the problem the project actually needs to solve. Three questions narrow it down quickly:

Many projects will benefit from tools from more than one category. A field app and a contractual workflow platform are not competing choices — they serve different users at different stages of the same project. The field supervisor uses the app at 6am to decide whether to mobilise the concreters. The contracts manager uses the workflow platform at month end to generate the early warning notice and build the benchmark.

Where Construction Weather fits

Construction Weather is a contractual workflow platform. It is not a field workability app, a hardware station or an enterprise alert system — and it does not try to be.

The platform is designed for the commercial, contracts and programme side of construction weather risk: pricing allowances at tender, interpreting the 14-day forecast in operational and contractual terms, issuing formal early warning notices when the forecast triggers the obligation, and generating EOT evidence benchmarked against historical data when weather delay needs to be formally established.

The tools in the platform follow the sequence of the project lifecycle:

• Tender Planning — calculates average weather-affected days per trade operation per month using 10 years of historical data at the project location, so weather risk is priced into the tender rather than absorbed as margin erosion during delivery.
• 14-day trade forecast and advisories — interprets forecast conditions against standards-referenced thresholds for over 30 trade operations, so the team can see whether the forecast affects the planned work — not just whether it will rain.
• Early Warning Notices — generates a formal, editable contractual notice in Word format using project details, forecast conditions, affected operations, anticipated impact and proposed mitigation. The notice is ready to issue; the barrier to doing the right thing is removed.
• EOT Evidence Generator — benchmarks a selected project month against 5 or 10 years of historical data, identifies qualifying weather days by condition type, and produces a formatted evidence document structured around the actual contract clauses supplied by the project team.
• Historical weather data — provides access to past conditions at the project location for any date range, with export for supplementary records.

Construction Weather is currently in open beta and free to use. It is not the right tool for every project or every user — but for the contractor who has experienced a weather delay that was never properly claimed, or the QS who needs to price weather into a tender without guessing, it occupies a space that general-purpose weather apps and field tools do not cover.

Conclusion — match the tool to the problem

The construction weather technology market is more fragmented than it appears. Products that share the same category label often serve fundamentally different purposes, and the one most prominently marketed is not necessarily the one that solves the actual project problem.

The framework is simple: identify the primary user, the project stage and whether weather is a contractual risk event. Those three questions point reliably to the right category — and the right category makes the specific product decision much more straightforward.

Weather risk in construction is manageable. The challenge is usually not the weather itself — it is matching the right tools to the right moment in the project lifecycle, and ensuring that the commercial and contractual infrastructure is in place to protect entitlement when adverse conditions do occur.