Guide · Scheduling
Build a schedule that survives
the first delay.
Every residential build hits a delay. The schedules that hold up aren’t the prettiest. They’re the ones with real dependencies and a baseline. This guide covers how to build one and keep it honest.
01 / The basics
In plain English
A construction schedule is the plan for the order and timing of the work: when the slab goes down, when the frame goes up, when the trades come through. On a residential build the sequence matters enormously because so many tasks depend on the one before: you can’t fit out before lock-up, you can’t lock up before the frame.
The mistake most builders make is treating the schedule as a one-time picture, a colourful chart drawn at the start and never trusted again. A schedule earns its keep only if it stays current as reality changes, which means it has to be easy to resequence and honest about how far you’ve drifted.
What makes a schedule actually useful
- Dependencies: the real relationships between tasks, so a delay cascades correctly.
- Milestones: the key stages, including the ones that trigger progress claims.
- A baseline: the agreed plan, so you can measure drift against it.
- Easy resequencing: because no build runs to the first version.
02 / The reality
Where builders get stuck
A picture, not a plan
A Gantt chart drawn once and never updated gets ignored within a fortnight. Nobody plans around a schedule they don’t trust.
Manual re-draws
Without dependencies, every delay means dragging dozens of bars by hand, so it doesn’t get done properly.
No baseline
If you can’t compare against the original plan, you can’t tell how far you’ve slipped until it’s a crisis.
Trades left guessing
Subbies plan their week around your dates. A schedule that doesn’t update means wasted call-outs and friction.
Claims out of sync
When schedule milestones don’t connect to claim stages, claiming becomes a separate, error-prone exercise.
Fear of changing it
If editing the schedule is painful and risky, you avoid it, and it drifts from reality entirely.
03 / The fix
A workflow that holds up
- 01
Sequence the trades
Lay out tasks in the real order of work, from site prep to handover.
- 02
Add dependencies
Connect tasks so a slip in one moves the ones that depend on it automatically.
- 03
Mark milestones
Flag the key stages, including the ones that trigger progress claims.
- 04
Lock a baseline
Capture the agreed plan so you can measure drift later.
- 05
Update as you build
Move real dates as work progresses and let dependencies do the resequencing.
- 06
Watch the drift
Compare live dates against the baseline to catch slippage early and act.
04 / The tooling
How software helps
Scheduling software earns its place by making the schedule maintainable. Real dependencies mean a delay propagates correctly without you re-drawing the chart. A baseline lets you see drift at a glance. And a clean undo means you can test a different sequence without fear, which is what keeps the schedule current instead of abandoned.
When the schedule connects to the rest of the job (claims, cost, the site app) it stops being a standalone diagram and becomes the way you actually run the build.
05 / In practice
Where VIABUILD fits
VIABUILD scheduling reschedules without the mess.
VIABUILD scheduling is task-based and goal-driven, with real dependencies, milestones and baseline tracking. Move a date and the dependent tasks follow; compare against the baseline to see exactly how far you’ve drifted; and undo cleanly when a “what if” doesn’t work out.
Because milestones line up with progress claims, and the schedule sits alongside cost tracking and ViaSite, it’s connected to how the job actually runs, not a chart in a drawer.
- Task-based, goal-driven schedule
- Real dependencies between tasks
- Milestones for key stages
- Baseline tracking for drift
- Reschedule with a clean undo
- Milestones line up with claims
06 / FAQ
Common questions.
One that stays current. That means real dependencies between tasks so delays cascade correctly, milestones for the key stages, a baseline to measure drift against, and easy resequencing, because no residential build runs to its first version.
A plain Gantt is a picture you drag by hand. When a date moves you have to fix every downstream bar yourself, so it falls out of date and gets ignored. A schedule with real dependencies updates the chain for you and stays trustworthy.
A baseline is a snapshot of the agreed schedule. As the job moves, you compare live dates against the baseline to see exactly how far you’ve slipped, so delays surface early rather than at handover.
VIABUILD uses a task-based schedule with real dependencies, milestones and baseline tracking, plus a clean undo for resequencing. Moving a date shifts dependent tasks automatically, and milestones line up with progress claims so the schedule connects to how you run the job.
07 / Keep reading
Related guides & features
See it on your own jobs.
Start with 7 days free: the full platform, your real data. $199 for your first month, then $435/mo. Month-to-month, no lock-in.