Module · Scheduling
Move one date.
Don’t blow up the schedule.
Scheduling is one module of VIABUILD, the Construction Operating System for residential builders. A task-based, goal-driven schedule with real dependencies, milestones and baseline tracking. When a date slips, the chain follows automatically, you can always see how far you’ve drifted, and because it’s one connected system, the milestones already line up with your progress claims.
7 days free · $299 first month · $555/mo after · Month-to-month
01 / What it does
What this feature does
The VIABUILD scheduling module is how you sequence a build and keep it honest when reality hits, the connected core of residential construction scheduling. It’s task-based and goal-driven, with real dependencies between tasks, so the schedule behaves like a plan, not a picture. Set a baseline, and you can always compare where you are against where you said you’d be. As one module of the operating system, the dates here are the same dates the rest of the build runs on.
Most “scheduling” in builder software is a colourful Gantt chart you drag around by hand. When something moves, you fix every downstream bar yourself. Here, dependencies do that work, and a clean undo means you’re never afraid to test a “what if”.
The same module, set out for how a build sequences in different parts of the country, around the local weather window, the trades and the supply lead times. See scheduling for Brisbane, Melbourne, Sydney, Adelaide and Perth.
02 / Why it matters
Why builders need it
Delays cascade
A late slab pour moves everything after it. Without real dependencies, you re-draw the whole chart by hand and miss something.
A picture isn’t a plan
A pretty Gantt that nobody trusts gets ignored. A schedule that reschedules itself stays the source of truth.
Drift is invisible
Without a baseline you can’t tell how far you’ve slipped. Baseline tracking makes the drift obvious early.
Subbies need certainty
Trades plan their week around your dates. A schedule that updates cleanly means fewer wasted call-outs and arguments.
Milestones drive cash
In one connected system, stage milestones line up with progress claims automatically. Keep the schedule current and the claims follow the build, no re-entry.
The trade finds out too late
A date moves and the subbie turns up anyway, because the change never reached them. From any task, one tap texts, WhatsApps or emails the assigned trade, and they reply without logging into anything.
03 / The VIABUILD way
How VIABUILD handles it
Dependencies, baselines and a clean undo.
Build the schedule as tasks with dependencies (finish-to-start and the relationships that actually describe your sequence). Set milestones for the stages that matter. Lock a baseline when the plan is agreed.
Then run the job. When a date moves, dependent tasks shift with it, and you see the new finish immediately against the baseline. Don’t like the result? Undo cleanly and try a different sequence. Marking a stage done is a completion, not yet a sign-off, which is the distinction between approvals and completions that keeps the schedule honest. The schedule stays something everyone can trust.
The schedule also talks to the people doing the work. From any task, send an update, a change or an attachment to the assigned subbie or supplier by SMS, WhatsApp or email. They reply straight back to the task, so the conversation lives next to the work and nobody has to log into a portal. On site, the same dates and tasks show up in ViaSite, the field app, alongside diaries and photo logs. One operating system, one set of dates from the office to the site to the claims.
- Task-based, goal-driven structure
- Real dependencies between tasks
- Milestones for key stages
- Baseline tracking to measure drift
- Reschedule with a clean undo
- Message the trade from any task (SMS/WhatsApp/email)
- Milestones line up with progress claims
04 / The workflow
How it runs, step by step
- 01
Build the sequence
Lay out tasks and the dependencies between them, mapping how the job actually runs.
- 02
Set milestones
Mark the stages that matter, including the ones that trigger progress claims.
- 03
Lock a baseline
Capture the agreed plan so you can measure drift against it later.
- 04
Run the job
Update real dates as the build progresses.
- 05
Absorb the slip
Move a date and dependent tasks follow automatically, with no manual re-draw.
- 06
Tell the trade
One tap messages the affected subbie or supplier from the task, by SMS, WhatsApp or email. They reply without a portal login.
- 07
See the drift
Compare current vs baseline to know exactly how far you’ve moved, and act early.
05 / FAQ
Common questions.
A normal Gantt is a picture you drag around by hand. Move one bar and you fix every downstream bar yourself. VIABUILD is task-based with real dependencies, so moving a date shifts the dependent tasks automatically, and baseline tracking shows how far you’ve drifted from the agreed plan.
A baseline is a snapshot of the agreed schedule. As the job moves, you compare the live dates against that baseline to see exactly how much you’ve slipped, so delays are visible early instead of at handover.
Yes. Dependencies handle the downstream shift for you, and there’s a clean undo, so you can test a different sequence without fear of making a mess you can’t reverse.
Yes, that’s the advantage of an operating system over a standalone scheduler. 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 between the two.
Yes. From any task you can send an update, change or attachment by SMS, WhatsApp or email, and the trade replies straight back to the task. There is no portal for them to log into and no app for them to install.
06 / Keep reading
Related features & guides
Build a schedule that survives the first delay.
Start with 7 days free: the full operating system, real data, Oryn™ inside every module. $299 for your first month, then $555/mo. Set up a real job and move a date to see the chain follow.