Module · Scheduling · Brisbane & South East QLD

A wet week hits.
Right-click, and it’s handled.

In South East Queensland the program lives and dies by the weather window. A wet November can move a slab pour, and everything behind it. In VIABUILD 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 wet 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 Brisbane 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 the South East Queensland year splits into a dry, reliable stretch and a wet storm season from roughly November to March. When the rain lands you do not want to redraw a chart bar by bar. You want to right-click the affected task, reschedule, and have the whole chain move, the vendor told, the wet day logged and the Extension of Time drafted, in one move.

02 / Why it matters

Why builders need it

The wet moves the slab

A saturated site pushes the pour, and everything behind it. Right-click, reschedule, and the dependent chain moves with it. No dragging bars one at a time.

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 wet day is captured

The delay is recorded automatically as 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 wet day and the moved dates, ready for you to send to the client for signature. You act at speed.

Humidity stretches cure times

Waterproofing, render and paint all cure slower in a humid SEQ summer. Build realistic durations into the tasks so the program reflects the weather, not a wish.

Milestones drive cash

Stage milestones line up with progress claims automatically. Keep the schedule current through a wet week 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 wet week lands, 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 wet day.

From that wet 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 a weather-affected program honest. On site the same dates show up in ViaSite, and because Queensland builders carry QBCC home warranty 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 day recorded automatically as a wet day
  • Oryn prepares the Extension of Time for client signature
  • Baseline tracking to measure wet-season 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

  1. 01

    Build the sequence

    Lay out tasks and dependencies the way a SEQ build runs, aiming to get roof cover on before storm season.

  2. 02

    Lock a baseline

    Capture the agreed plan so you can measure wet-season drift against it later.

  3. 03

    Right-click to reschedule

    When the wet lands, reschedule the task and the whole dependent chain moves with it.

  4. 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.

  5. 05

    The wet day is logged

    The delay is recorded automatically as a wet day, building the record behind any Extension of Time.

  6. 06

    Oryn prepares the EOT

    The Extension of Time is drafted from the wet day and the moved dates, ready to send to the client for signature.

  7. 07

    See the drift

    Compare current vs baseline to know exactly how far the weather has 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 wet 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 for them to log into, no app to install and no in-app notification they will never open.

Yes. When a delay is logged as 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 the program has moved around a wet week.

06 / Keep reading

Related features & guides

Turn a Brisbane wet week 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 slab date and watch the chain, the text, the wet day and the EOT all follow.