What to do when one delayed trade blows out your schedule
One delayed trade can ripple through framing, rough-in, lock-up, and progress claims faster than most teams expect. In Australia, weather windows, subcontractor availability, and council timing can all squeeze the program at once.
What this means: if you only react day-by-day, you usually lose both time and margin. The better move is to run a simple recovery sequence with clear ownership.
First, diagnose the delay properly (not just “they’re late”)
A delay looks simple from a distance, but the fix depends on the root cause.
Scenario 1 (metro infill): Your electrician is three days late because they were pulled onto an insurance job. The next trades are booked tightly, and the plasterer has no flexibility for two weeks.
Scenario 2 (regional build): Heavy rain in northern NSW delays slab-related tasks, but the schedule was built assuming dry access roads and uninterrupted deliveries.
What this means: the delay type tells you whether to resequence, replace, or hold.
Quick delay classification framework
Use this 4-part check within 30 minutes of learning about the delay:
- Constraint type — trade capacity, weather, materials, access, or documentation.
- Critical path impact — does this task block the next revenue-linked milestone?
- Recovery options — resequence, split scope, swap supplier, add labour, or shift milestone timing.
- Commercial consequence — likely cost increase, claim delay, and client communication impact.
If your PM, estimator, and accounts can all see the same task status and dependencies, decisions are cleaner. This is where a task-driven workflow and Gantt view are useful: everyone works off one sequence instead of conflicting spreadsheets.
The 24-hour recovery playbook
When a trade slips, the first day is where jobs are saved or lost.
Step 1: Freeze assumptions and confirm facts
Call the delayed trade and confirm:
- earliest realistic start date
- crew size available
- what would help them start sooner (documents, access, staged areas)
What this means: you need a committed date, not “we’ll try tomorrow”.
Step 2: Re-run dependencies in your schedule
Review the next 10 business days and identify:
- tasks that can be pulled forward
- tasks that must move
- tasks needing client or certifier approvals
What this means: most programs can recover 20–40% of lost time through resequencing before spending extra money.
Step 3: Send one coordinated update
Issue one update to site team, affected trades, and office:
- what moved
- new dates
- who is confirming each date
- next review time (usually same day end)
What this means: one source of truth avoids duplicate calls and accidental no-shows.
Recovery options compared (time vs cost vs risk)
Different fixes suit different delay types. Pick based on both time pressure and margin pressure.
| Recovery option | Best when | Time impact | Cost impact | Risk level | What to do next |
|---|---|---|---|---|---|
| Resequence downstream tasks | Non-critical tasks can be advanced | Low to medium recovery (1-4 days) | Low | Low | Rebuild next 2 weeks in Gantt and lock owners |
| Split scope across two crews | One trade can’t complete full scope in time | Medium recovery (2-6 days) | Medium | Medium | Define handover boundaries in writing |
| Replace delayed trade | Current trade is unreliable or unresponsive | Medium to high recovery | Medium to high | High | Check quality history and insurance before award |
| Add overtime / extended hours | Access rules and supervision allow it | Fast recovery (1-3 days) | Medium to high | Medium | Confirm supervision and safety controls |
| Move milestone / claim timing | Physical recovery impossible this cycle | No schedule recovery | Low direct cost, cashflow hit | Medium | Align accounts timing and client notice early |
What this means: the cheapest option is not always cheapest once claim timing and team disruption are included.
Cost and timeline breakdown builders can use straight away
A short delay can become expensive through stacked consequences.
Typical 5-day delay impact model (illustrative)
- Direct site overhead extension: $400-$1,200/day depending on project structure
- Rebooking/standing costs for affected trades: $1,000-$4,000 total
- Supervision/admin rework: 6-15 hours of PM/admin time
- Progress claim shift: often 1-3 weeks later depending on stage rules and evidence readiness
Practical timeline view:
- Day 0: delay confirmed, constraints classified
- Day 1: resequence + communication sent
- Day 2-3: supplier/trade confirmations locked
- Day 4-5: milestone readiness rechecked
- Day 5+: accounts aligned for claim timing (invoicing still handled in Xero)
What this means: treat delay recovery as both a site issue and a cashflow issue.
What some software tools don’t tell you
Many tools show dates moving around. Fewer tools force the right handoffs between PM, estimator, and accounts.
The gap usually appears in three places:
- No single owner for resequencing decisions
Result: five people “helping”, no one accountable. - No evidence pack discipline for progress stages
Result: site thinks stage is done, accounts can’t claim confidently. - No supplier response rhythm
Result: trades respond in fragments, and the schedule gets rebuilt multiple times.
What this means: software helps, but rhythm and ownership rules are what protect margin.
Practical checklist: use this every time a trade slips
- Confirm delay root cause (capacity, weather, material, access, docs)
- Confirm hard restart date (not estimate)
- Check critical path impact in current Gantt
- Decide recovery path (resequence, split, replace, overtime, or milestone shift)
- Notify all affected trades with one coordinated update
- Recheck client-facing milestone expectations
- Align PM + accounts on progress claim timing and evidence
- Review margin risk before approving extra cost recovery
- Set next review checkpoint within 24 hours
What this means: consistency beats heroics. The same checklist each time prevents expensive misses.
How iGyro helps teams handle this without chaos
iGyro is strongest when teams use it as one workflow hub:
- task-driven workflow keeps responsibilities visible
- Gantt scheduling shows dependency impact quickly
- supplier coordination reduces back-and-forth
- job costing visibility helps compare recovery cost vs margin impact
For progress payments, iGyro can flag stage readiness and status, while invoicing is still raised in Xero by the bookkeeper.
What this means: better recovery decisions happen when scheduling, task ownership, and costing visibility stay connected.
FAQ
How quickly should we react after a trade delay is confirmed?
Within the same day. If you wait 24-48 hours, resequencing options usually shrink and rebooking costs rise.
Should we always replace the delayed trade?
No. Replacement can recover time, but it can also increase defects and admin friction. Use replacement when reliability risk is clearly higher than transition risk.
How do we protect progress claims during schedule disruptions?
Keep stage evidence and task completion records tidy, then align site and accounts early. iGyro can help track stage readiness; invoice creation still happens in Xero.
Is this mainly a problem for larger builders?
No. Smaller builders often feel it more because one delayed trade can affect a higher share of active jobs and cashflow.
Related iGyro Reading
- Construction Scheduling Software with Gantt for Home Builders
- Builders Job Management Software for Australian Residential Teams (Practical 2026 Guide)
- Progress Claim Workflow Software for Australian Builders
- How to stop missed progress claims when site and accounts are disconnected
- Construction scheduling for small builders: practical weekly cadence
Next step CTA
If delays are hitting your cashflow rhythm, book a video call to map your current handoff points.
If you want to test a cleaner workflow with your team first, sign up for a free account and run one live job through it.
