Module · Scheduling · Adelaide & South Australia
A heat day or a wet week.
Right-click, and it’s handled.
An Adelaide build gets planned around a hot dry summer and a wetter winter, and an extreme heat day can pull trades off the tools as surely as rain. When a weather day moves a date, you right-click the task and reschedule, and the whole dependent chain moves with it. The affected vendor gets the new date as a two-way text conversation, the day is recorded automatically as a weather day, and Oryn prepares the Extension of Time ready to send to your client for signature. Oryn does the work, you act at speed. This is not a normal Gantt chart.
The Founding Builders Programme · Onboarding in small cohorts
01 / What it does
What this feature does
This is the scheduling module of VIABUILD, the Construction Operating System for residential builders, set out for how a South Australian build actually sequences. It is task-based with real dependencies, the connected core of residential construction scheduling. Lock a baseline when the plan is agreed and you can always see how far the job has drifted.
In practice Adelaide runs a Mediterranean split. Long dry summers give a reliable building stretch, but extreme heat days can stop work, and wetter winters shorten the window for external trades. When a heat day or a wet week lands you do not want to redraw a chart by hand. You want to right-click the affected task, reschedule, and have the whole chain move, the vendor told, the weather day logged and the Extension of Time drafted, in one move.
02 / Why it matters
Why builders need it
A weather day moves the work
A heat day pulls trades off the tools, a wet winter week holds up the externals, and everything behind them shifts. Right-click, reschedule, and the dependent chain moves with it.
The vendor hears by text
The affected subbie gets the new date as a two-way text conversation, not a notification buried in an app they never open. They reply straight back from the site.
Every weather day is captured
The delay is recorded automatically as a weather day, a heat day or a wet day, so the record that supports an Extension of Time is built as it happens, not reconstructed from memory months later.
The EOT is ready before you ask
Oryn prepares the Extension of Time from the weather day and the moved dates, ready for you to send to the client for signature. You act at speed.
Hot pours need care
Concrete cures fast in Adelaide heat and needs the right timing. Build realistic durations and early-start pours into the tasks so the program matches the conditions.
Milestones drive cash
Stage milestones line up with progress claims automatically. Keep the schedule current through a heatwave and the claims still follow the build, with no re-entry.
03 / The VIABUILD way
How VIABUILD handles it
Right-click, reschedule, and Oryn does the rest.
Build the schedule as tasks with real dependencies, set milestones for the stages that matter, including the ones that trigger a claim, and lock a baseline when the plan is agreed.
Then run the job. When a heat day or a wet winter week moves a date, right-click the task and reschedule. The dependent chain moves with it and you see the new finish immediately against the baseline. The assigned vendor gets the new date as a two-way text message conversation and replies straight back, no portal to log into and no in-app notification they will never see. The delay is recorded automatically as a weather day.
From that weather day and the moved dates, Oryn prepares the Extension of Time, ready for you to send to the client for signature. Marking a stage done is still a completion, not a sign-off, the distinction between approvals and completions that keeps the program honest. On site the same dates show up in ViaSite, and because South Australian builders carry building indemnity insurance obligations, a schedule that stays current makes those handover dates easier to hold.
- Right-click reschedule, the whole dependent chain moves
- Vendor notified by two-way text, not an in-app alert
- The delay recorded automatically as a weather day
- Oryn prepares the Extension of Time for client signature
- Baseline tracking to measure seasonal drift
- The same dates flow through to progress claims and the field
- Not a normal Gantt chart
04 / The workflow
How it runs, step by step
- 01
Build the sequence
Lay out tasks and dependencies the way an SA build runs, working the weather-exposed trades into the shoulders.
- 02
Lock a baseline
Capture the agreed plan so you can measure seasonal drift against it later.
- 03
Right-click to reschedule
When a heat day or a wet week moves a date, reschedule and the whole dependent chain moves with it.
- 04
The vendor is told
The affected subbie gets the new date as a two-way text conversation and replies from site. No portal, no in-app notification.
- 05
The weather day is logged
The delay is recorded automatically as a weather day, a heat day or a wet day, building the record behind any Extension of Time.
- 06
Oryn prepares the EOT
The Extension of Time is drafted from the weather day and the moved dates, ready to send to the client for signature.
- 07
See the drift
Compare current vs baseline to know exactly how far the conditions have moved you, and act early.
05 / FAQ
Common questions.
You right-click the affected task and reschedule. The whole dependent chain moves with it, the assigned vendor gets the new date as a two-way text conversation, the delay is recorded automatically as a weather day, and Oryn prepares the Extension of Time ready for you to send to the client for signature. One move, not an afternoon of admin.
By a two-way text message conversation. The vendor gets the new date as a text and replies straight back to the task, so the conversation lives next to the work. There is no portal to log into, no app to install and no in-app notification they will never open.
Yes. When a delay is logged as a weather day, a heat day or a wet day, Oryn prepares the Extension of Time from that record and the moved dates, ready for you to send to the client for signature. The supporting record is built as the delay happens rather than reconstructed later. See the guide on extensions of time and delays for the wider process.
Yes. Stage milestones in the schedule line up with stage-based progress claims, so as the build hits each stage your claims follow the work with no double entry, even when a heatwave or a wet week has moved the program.
06 / Keep reading
Related features & guides
Turn an Adelaide weather day into one right-click.
Start with 7 days free: the full operating system, real data, Oryn™ inside every module. $199 for your first month, then $555/mo. Set up a real job, move a date and watch the chain, the text, the weather day and the EOT all follow.