One underpriced weather allowance can cost more on a single project than PreDelayIQ ever will. It takes about five minutes to turn 30 years of Australian climate data into a delay number you can actually defend — at tender stage, or in an EOT claim.
"I'm an estimator. I started allowing for weather delays in tender programs and realised there was nothing to base it on except habit and hope. So I built a way to calculate it properly — using historical BOM data — for my own tenders first. PreDelayIQ is that tool, now available to other estimators."
— James, Founder
PreDelayIQ estimates likely weather-related delay from long-term historical climate averages. It does not predict the weather on your specific project, and it is not a promise of any particular outcome. Actual weather in any given year may be better or worse than these figures — that's what the P20–P90 range above is actually telling you.
It does not replace formal Extension of Time processes required under your contract, professional programming or estimating judgement, or your own knowledge of the site. Validate results against your own conditions before relying on them for tendering or pricing.
"We usually add two weeks" isn't a methodology — it's a habit, carried from the last job, in a different season, at a different site. When it's wrong, it's wrong in one direction: your margin absorbs it.
Weather delay claims are also hard to defend precisely because most companies can't show their working. PreDelayIQ exists so the number in your tender has a real, citable source behind it.
Postcode, program start date, duration, and the phases that make up the job.
Rain, heat, frost — whichever thresholds are relevant to your trades.
An instant estimate, or the full P10–P95 probability range if you want to see the whole picture.
CSV, Excel or MS Project. PreDelayIQ maps activities to construction work types and calculates weather exposure against when the work actually occurs.
A full Monte Carlo probability range, not a single averaged guess — so you can see exactly how confident the number is.
A branded report and a print-ready weather risk register — documents you can actually attach, not just a number to copy out.
PreDelayIQ runs a genuine statistical simulation — thousands of independent runs per calculation, built on real historical data, not a single averaged guess dressed up as precision. Every figure traces back to a real source and a documented method. Where something is an estimate rather than a direct measurement, it says so.
An instant deterministic estimate, or a full Monte Carlo probability range when you need a defensible confidence level.
Bring in an existing program, export it back out with the weather allowance built in — MS Project XML or a readable HTML file.
A properly formatted, fully explained summary report — with your own company logo alongside PreDelayIQ's.
See which phases are genuinely unpredictable, not just which one has the biggest number.
A standard, recognisable compliance document — ID'd, rated, and ready for tender submission.
A ready-to-paste paragraph explaining exactly how the allowance was calculated.
PreDelayIQ was developed around the way Australian contractors actually price and manage weather risk at tender stage. Climate inputs are sourced from SILO, built from Bureau of Meteorology observations across 95 reference locations covering every state and territory — with distance-weighted multi-station blending to better represent the actual project location, not just the nearest single gauge. The calculation methodology is documented throughout the application, so nothing about the number is a black box.
On a commercial project, one additional day can mean extended preliminaries, supervision, plant hire, temporary facilities — and, where the contract carries a liquidated damages clause, LDs on top. PreDelayIQ Pro is $799 once, not per project.
PreDelayIQ doesn't stop delays — it puts you in a stronger position when they happen. A defensible weather allowance at tender stage means the risk is priced in, not guessed at. A documented methodology behind an Extension of Time claim means a genuine weather delay has a real case behind it, not just an assertion. Either one, once, easily justifies the cost of the tool.
Illustrative example — replace with a real project once you have one on file.
This isn't a claim that 24 days is "correct" — it's what a defensible, documented number looks like instead of a round figure carried over from the last job.
Buy once, use it on every project after. Core gives you the number — a complete, genuinely useful tool on its own. Pro adds the polished, client-facing outputs built from it, plus access to future climate data refreshes as they're released.
Price your next tender's weather risk with real data behind it, not a round number.
