Key takeaways
- Seasonal weather is predictable enough to be programmed for, so treating rain or heat as an unforeseen event is a commercial choice rather than a technical one.
- The trades most exposed to weather are the wet trades, external finishes, and anything requiring a dry substrate, and they should be sequenced with float rather than stacked end to end.
- A programme that assumes uninterrupted production will fail in the same weeks every year, which means the same disputes recur on every job the builder runs.
- Weather delays that are not documented contemporaneously are effectively invisible at the claim stage, regardless of how real the lost days were.
- Requirements such as BASIX commitments and bush fire protection measures interact with weather because they impose inspection and verification points that cannot be compressed.
Every builder in NSW knows the pattern. The same weeks every year produce the same lost days, the same wet subfloor, the same aborted concrete pour, the same argument with the client about who pays for the delay. Nothing about that pattern is surprising, and that is the point: seasonal weather is not an unforeseen condition, it is a known characteristic of the site and the calendar.
Yet most residential programmes are built as though production is continuous. Durations are lifted from a previous job, compressed to win the tender, and presented as a commitment. When the weather arrives on schedule, the programme collapses on schedule, and the builder is left explaining a delay that a competent scheduler would have priced in from the start.
This article is about planning for those predictable effects. It is not about any particular weather event, and it is not about how to claim an extension of time after the fact. It is about the decisions made before the first sod is turned that determine whether a wet month is a manageable nuisance or a commercial loss.
Why weather is a scheduling input, not an excuse
The reason weather gets treated as an excuse rather than an input is that excuses are free at tender stage and inputs cost money. If you allow realistic weather days in the programme, the completion date moves out, and on a competitive tender that can be the difference between winning and losing. So the allowance gets trimmed, sometimes to nothing, and the risk is transferred to a party who has no control over it.
The mechanism matters here. A construction programme is a model of dependencies. Each activity has a duration, each duration assumes a level of productivity, and productivity for external work is a function of weather. If you assume full productivity in a month that historically delivers partial productivity, you have not built a programme, you have built a hope. The dependencies still exist, the trades still follow each other, but the model no longer describes the site.
The commercial consequence is straightforward. Weather delays that were foreseeable are generally not recoverable as variations or extensions unless the contract says otherwise, and even where a claim is available, it depends on notice and records. A builder who programmed no weather allowance has effectively agreed to carry the risk, whether or not they understood that at the time.
The trades that actually stop when it rains
Not all work is equally weather-sensitive, and a programme that treats all trades the same wastes the flexibility that exists. The trades that stop are the ones that need a dry substrate, a stable temperature, or open ground. Earthworks, footings, slab pours, brick and block laying, render, external painting, waterproofing, tiling to wet areas before the roof is on, and anything involving excavation all fall into that group.
Internal fit-out is different. Once the building is dried in, electrical rough-in, plumbing, plasterboard, joinery and internal painting can proceed through a wet week with minimal loss. That is why getting the roof on is the single most valuable weather decision on the job: it converts an exposed site into a covered one and moves a large block of the programme out of the weather entirely.
The practical implication is that your sequence should be arranged to maximise the amount of work under cover as early as possible, and to place the weather-sensitive external trades where they have the best chance of a clear run. If you are still working out how to structure those dependencies, the guide to construction programme scheduling basics covers the underlying logic before you start layering weather on top of it.
Sequencing external work around the predictable wet and hot periods
- Site establishment and earthworksGet drainage, sediment control and access in before the ground turns, because a bogged site stops everything behind it.
- Structure and roof coverPrioritise getting the building dried in so internal trades are not exposed to the weather at all.
- External envelope and wet tradesRender, cladding, waterproofing and tiling need dry substrates and stable temperatures, so they sit in the best window you have.
- Fit-out and servicesInternal work is the buffer: it can absorb lost external days if the building is closed up.
- External works and landscapingDriveways, paving, fencing and turf are the last to go in and the first to be ruined by a late storm.
- Verification and handoverInspection and certification points need the work complete and accessible, which weather can delay independently of the build.
Building float into the programme rather than promising a date
Float is the slack between when an activity can finish and when the next one needs it to finish. A programme with no float is a programme with no capacity to absorb anything, including weather. Many residential programmes have effectively zero float because every trade is scheduled back to back and the completion date is fixed by a contract that was signed before the site was understood.
There are two honest ways to handle this. The first is to include a weather allowance as a visible line or as extended durations on weather-sensitive activities, so the completion date reflects reality. The second is to build genuine float into the sequence so that a lost week is absorbed without moving the end date. Most good programmes do both to some degree.
What you should not do is hide the allowance inside a trade duration and then present the date as fixed. That produces a programme where nobody can see where the risk sits, and when the delay arrives, the argument is about whose duration was wrong rather than about the weather that everyone knew was coming. Hidden allowances also break the moment a subbie works faster or slower than assumed, because there is no visible buffer to adjust.
Weather days versus weather risk
These are different things and they are often conflated. Weather days are the number of lost days you expect in a given period based on the site and the season. Weather risk is the possibility that the season is worse than expected. A programme should carry an allowance for the first and a contingency for the second, and the two should be separately identifiable. If they are merged, you cannot tell whether you are having a bad month or a bad job.
Sequencing to reduce exposure
Sequencing is where a builder has the most control and where the most value is created. The objective is to arrange the works so that the activities most vulnerable to weather are either done in the best window available or protected by work that has already been completed. This is not a novel idea, but it is frequently sacrificed to convenience, to subbie availability, or to a client who wants to see progress in a particular order.
A few principles hold across most residential jobs. Get the drainage and site works done early, because a site that does not drain will lose days long after the rain has stopped. Get the structure up and the roof on as fast as the approval and the trades allow, because everything after that is easier. Don’t schedule render, external paint or waterproofing immediately behind a trade that has no float, because a single lost day cascades straight into a missed inspection.
There is also a scheduling consequence that flows from the approvals themselves. Requirements imposed at approval stage, including the commitments that come with a BASIX certificate, create verification points that have to be satisfied before certain work can proceed or be signed off. If those points fall in a wet period and depend on external work being complete, they become weather-sensitive even though they are administrative. The NSW Planning Portal guidance on BASIX and planning approvals sets out how those commitments attach to the approval, and it is worth checking which ones your programme has made time-critical.
Where approvals and bush fire requirements change the calendar
Some sites carry requirements that make weather planning more rather than less important. Bush fire prone land is the clearest example. Measures required under Planning for Bush Fire Protection can affect construction detailing, access, water supply and the timing of inspections, and those elements often involve external work or site access that weather can disrupt. The NSW Rural Fire Service guidance on Planning for Bush Fire Protection is the reference for what applies, and it is worth reading before you commit a sequence on an affected site rather than after.
The scheduling point is this: any requirement that depends on an inspection, a verification, or a completed external element is exposed to weather in the same way a trade is. If you have not identified those dependencies, you will discover them at the moment you are trying to book an inspection and the work is not ready. That discovery costs days, and days cost money.
Modern methods of construction are relevant here too, because off-site manufacture moves work out of the weather and into a factory. The NSW Department of Planning, Housing and Infrastructure material on modern methods of construction covers the policy context, but the scheduling effect is what matters on a job: a panelised or modular approach changes which activities are weather-sensitive and which are not, and a programme that ignores that difference is wasting the main advantage of the method.
Documenting weather delays as they happen
The time to think about evidence is before the delay, not after. Weather delays are the most commonly claimed and most commonly disputed category of delay in residential work, and the reason is almost always records. A builder who can point to dated site diary entries, photographs, rainfall observations from a nearby station, and contemporaneous notices to the client is in a completely different position from one who reconstructs the story months later.
What good records look like is unglamorous. A daily site diary that notes the weather, the trades on site, what was stopped, and what was redeployed. Photographs with dates. Written notice to the client or superintendent within whatever period the contract requires, not at the end of the job. A note of which subbies were affected and what they did instead. None of this takes long if it is a habit, and all of it is impossible to manufacture convincingly afterwards.
The commercial reality is that the absence of records does not mean there was no delay. It means the delay is unproven, and an unproven delay is a cost the builder carries. That is the most expensive way to learn this lesson, and it is entirely avoidable.
The mistake that costs the most. Programming to a best-case season and then discovering, in the wet weeks, that no allowance was made and no records were kept — so the delay is real, the cause is obvious, and the claim fails for want of a diary entry and a notice.
What to check before you commit a date
Before a completion date is promised, someone needs to have looked at the site, the season, and the sequence together. That is not a formality. It is the difference between a programme that describes the job and one that describes an aspiration.
What to confirm before you commit a programme date
- The forecast window for the trades that cannot work wet, and whether the programme has float behind them.
- Whether the site drains, and where water sits after a normal storm rather than a once-a-year event.
- Which inspections or hold points depend on dry, complete or accessible work.
- Whether the contract allocates weather risk, and what the notice period is for a delay claim.
- Whether subbies have been told the sequence, not just the start date.
- Whether the client understands that the completion date assumes a normal season, not a perfect one.
- Whether the programme shows the weather allowance explicitly or hides it inside a trade duration.
The items on that list are not complicated, but they require a decision to be made and recorded. Which trades are exposed. Where the float is. How the contract allocates the risk. What notice is required. What the subbies have been told. If you cannot answer those questions, the programme is not ready to be issued.
A worked example: a builder in western Sydney
A builder in western Sydney takes on a single dwelling on a sloping site with a fixed completion date written into the contract. The tender programme was built from a previous job, with external trades scheduled back to back and no visible weather allowance. The building is dried in late, and the render, external paint and waterproofing all land in the same wet weeks. Two inspections slip because the work is not complete, and the tiling to the wet areas is held up behind the waterproofing.
The client points to the contract date. The builder points to the weather. The subbies point to a programme that told them to be on site on a date that was never realistic. By the time anyone looks at the records, the site diary is a few lines a week, no written notice was given within the required period, and the photographs are undated.
The cost of that job is not just the delay. It is the standing time for trades who arrived to find no work, the re-mobilisation charges, the client relationship, and the reputational damage when the client tells the story to the next three enquiries. None of it was caused by the weather, which behaved exactly as it always does. It was caused by a programme that assumed the weather away and a record-keeping practice that could not prove what happened.
The same job run differently would have had a visible weather allowance, a sequence that got the roof on earlier, float behind the render, a diary entry every day, and a notice to the client in the first week of the wet period. The delay would still have occurred. The difference is who paid for it.
How this connects to your obligations as a builder
Scheduling is not usually described as a compliance topic, but it sits underneath a lot of what is regulated. Contract administration, notice periods, inspection regimes, approval conditions and verification requirements all assume a programme that someone is actually managing. When the programme is unrealistic, the compliance failures follow, because inspections are missed, notices are late, and commitments made at approval stage are not met on time.
That is one reason the PointCPD guide to how NSW builder CPD works is worth reading even if you have been licensed for years. The categories of continuing professional development are structured around the things that actually go wrong on jobs, and programme management and contract administration are recurring themes. If you want to see what is available, the PointCPD course catalogue lists the current options, and the PointCPD home page is the starting point for NSW builder CPD generally.
The broader point is that weather planning is a professional skill, not a piece of luck. Builders who plan for it lose fewer days, argue less, and carry fewer unrecoverable costs. Builders who ignore it spend every wet season explaining a delay that they could have priced, sequenced, or documented from the beginning.
Practical steps for the next programme you write
Start with the site and the season, not with the completion date. Identify the weather-sensitive activities and place them deliberately. Make the allowance visible so that everyone, including the client, can see where the risk sits. Get the building dried in as early as the approvals allow. Keep a diary that would stand up if it were tested. Give notice when the delay occurs, not when the argument starts.
None of this guarantees a dry season. It guarantees that when the wet one arrives, you already know what it costs, who carries it, and how you will prove it. That is the difference between a weather delay and a weather loss, and it is entirely within the builder’s control.
Questions builders ask
Is weather delay a valid extension of time on a residential job in NSW?
It depends entirely on what the contract says and on whether the delay was foreseeable. Many contracts exclude weather that could reasonably have been anticipated, which is most seasonal weather. Even where a claim is available, it usually depends on written notice within a set period and on contemporaneous records. Read the contract before you assume you are covered.
How do I allow for weather in a programme without losing the tender?
Show the allowance explicitly rather than hiding it inside a trade duration, and explain it. A client who understands that the completion date reflects a normal season is easier to deal with than one who was promised a date that assumed no rain at all. If you must compete on programme, compete on sequence and float rather than on pretending the weather will not happen.
Which trades should I sequence first to reduce weather risk?
Site drainage and earthworks first, then structure and roof cover, because getting the building dried in moves the largest block of work out of the weather. External render, paint, waterproofing and cladding come next, with float behind them. Internal fit-out is the buffer that can absorb lost external days once the roof is on.
What records do I need if a weather delay turns into a dispute?
A daily site diary noting weather, trades on site and work stopped, dated photographs, rainfall observations from a nearby station, and written notice to the client or superintendent within the period the contract requires. The key word is contemporaneous. Records created after the fact carry far less weight than ones made on the day.
Do BASIX or bush fire requirements affect scheduling?
They can, because they impose verification and inspection points that depend on work being complete and accessible. If those points fall in a wet period, they become weather-sensitive even though they are administrative. Check which commitments attach to your approval and identify any that are time-critical before you commit a sequence.
Does using modern methods of construction remove weather risk?
It changes which activities are weather-sensitive rather than removing the risk. Off-site manufacture moves a large part of the work into a factory, but site preparation, footings, connections and external finishes are still exposed. A programme that treats a modular job the same as a traditional one wastes the main scheduling advantage of the method.
Sources
- BASIX · NSW Planning Portal
- BASIX and planning approvals · NSW Planning Portal
- Modern methods of construction · NSW Department of Planning, Housing and Infrastructure
- Planning for Bush Fire Protection · NSW Rural Fire Service
Published 29 August 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
