Key takeaways
- A programme is a sequence of dependencies, not a list of dates, and on a home job the longest chain of dependencies sets the completion date.
- Float must sit on the activities that absorb delay, not spread evenly across the programme, or it protects nothing.
- Procurement lead times and approval hold points drive the critical path on small residential work as much as site trades do.
- Weather, client selections and inspection bookings are the three recurring delay sources on home jobs and each needs its own buffer.
- A programme that is not updated weekly becomes a document for the file rather than a tool for running the job.
A construction programme for a home job is not a list of dates. It is a sequence of dependencies with float held in the places where delay actually occurs. Builders who understand that distinction finish jobs on time more often, because they can reason about what to do when a trade is late or a client changes a selection, rather than just watching the dates slide.
Most small residential programmes fail for the same reason. The builder sequences the trades correctly, then compresses every activity to fit the client’s expectation, leaving nothing in the programme to absorb the delays that always arrive. The programme looks tight on paper and falls apart on site.
This article sets out a sequencing and float method for home jobs — renovations, extensions, knockdown rebuilds and small new dwellings. It does not compare software, and it does not deal with time management generally. It deals with the order of work and where the buffer sits.
Sequencing a home job by dependency
- 1Set the completion constraintWork back from the date the client needs to be in, or the date the contract fixes, and write it down before anything else.
- 2List the physical dependenciesFor each trade, note what must be finished and inspected before it can start on site.
- 3Find the longest chainTrace the path through those dependencies that takes the most time end to end; that chain is your critical path.
- 4Attach procurement lead timesPut window, door, truss and cabinetry lead times against the date each item must be ordered to hit its install slot.
- 5Place float on the critical chainAdd buffer to the activities that, if they slip, move the completion date, rather than spreading it thinly everywhere.
- 6Publish and update weeklyIssue one page to the client and subbies, then re-mark it every week against what actually happened.
Why the critical path on a home job is usually not what you think
On a large commercial project, a programmer will model hundreds of activities and let software work out the critical path. On a home job you usually have a dozen or so real activities and one obvious chain, and the chain is often not the one the builder assumes.
Take a straightforward extension. The builder might think the critical path runs through the slab, frame, roof, lock-up, fit-out and handover. In practice, the longest chain often runs through a council or certifier approval, a client selection, or a long-lead order. If the windows are not ordered before the frame goes up, the frame sits open for weeks while the builder waits on supply, and the whole job shifts.
The practical method is to trace the dependencies rather than the dates. For each activity, ask what must be physically complete and signed off before it can start. Follow those dependencies from the first site activity to handover. The path with the most elapsed time is your critical path, and every activity on it is one you cannot let slip without moving the completion date.
The corollary is that activities off the critical path have float. You can let them slip by a certain amount without affecting completion. Knowing which is which is what allows you to make decisions about where to put labour when a subbie is late.
Sequencing by dependency, not by trade order
The trade order on a home job is familiar: site cut, piers or slab, frame, roof, rough-in, lock-up, linings, fit-out, practical completion. That order is necessary but not sufficient. What matters for the programme is the dependency between each step and the one before it, and the hold points where an inspection or approval gates the next trade.
For example, the frame cannot be lined until the rough-in trades have finished and been inspected. The rough-in cannot be finished until the frame is erected and the roof is on. The frame cannot start until the slab has cured and the certifier has inspected. Each of those dependencies has a time cost, and several of them have a booking cost because you are waiting on an inspector, not just a trade.
When you build the programme, list the dependencies as explicit statements: “Plaster cannot start until electrical rough-in is complete and inspected.” Then work out how many days each dependency realistically takes, including the time to book and attend an inspection. That is the real sequence.
The sequencing method is what makes the programme defensible when a client asks why the job is taking so long. You can point to the chain and show where the time actually goes. That is also the basis for a realistic conversation about variations, which is covered in the article on dealing with neighbours and site access.
Where float belongs and where it does not
Float is the amount of time an activity can slip without affecting the completion date. Builders often treat float as something to be squeezed out, on the logic that if there is spare time in the programme the client will ask for it back. That is the wrong way to think about it. Float is the mechanism that lets the job survive normal disruption.
The mistake is to spread float evenly across every activity. If you add a day to every trade, you have not protected anything; you have just made the programme longer and given each trade a day they will probably use. Float needs to sit where delay actually lands.
On a home job, delay lands in three recurring places: weather, client selections, and inspection or approval bookings. Each has a different pattern and needs a different buffer.
- Weather. Earthworks, slab pour, frame and roof are exposed to rain. Buffer needs to sit across those activities as a block, not spread across the whole programme, because rain does not delay the tiling.
- Client selections. Selections for tiles, tapware, cabinetry and finishes need to be locked before the relevant trade is booked. Buffer here is time between the selection deadline and the order date.
- Inspections and approvals. Certifier and council inspections are booked, not instant. Buffer here is the gap between the trade finishing and the inspection being available.
Put the float there, and mark it clearly on the programme as buffer rather than as part of an activity. When a delay happens, you draw on the buffer and you know exactly how much you have left.
Where float belongs on a small residential programme
| Float placed well | Float placed badly |
|---|---|
| Buffer held at the end of the frame stage | Buffer spread in equal days across every trade |
| Extra days built into the wet weather season for the slab and frame | Assumption that no rain days will occur at all |
| Time allowed between practical completion and handover for defects | Handover booked the day after the last trade leaves |
| Early order dates for long-lead items so a late delivery does not stop the frame | Ordering windows after the frame is up and hoping supply is quick |
| A clear owner for each hold point | Every hold point assumed to be someone else’s job |
Procurement lead times and why they drive the programme
On small residential work, procurement is often the real critical path. Trusses, windows, doors, cabinetry, appliances and some cladding systems have lead times that are longer than the site activities they support. If the order is placed late, the trade cannot start, and no amount of labour on site fixes it.
The programme method is to work backwards from the install date for each long-lead item. If windows are to be installed after the frame is up, the order must be placed well before the frame starts. That order date becomes a milestone on the programme with the same status as a site activity.
This matters commercially because late procurement is one of the most common causes of a job running over. It is also one of the easiest to prevent, because it is entirely within the builder’s control. A programme that lists order dates alongside site dates gives you an early warning: you can see the order milestone coming and chase it before it becomes a site delay.
For builders running several jobs, procurement milestones across all of them need to be visible in one place. That is a legitimate reason to use software, and the criteria for choosing it are set out in the article on getting your team to use the software you paid for. The programme logic comes first; the tool holds it.
Building the programme: a worked example
Consider an unnamed builder in western Sydney running a single-storey rear extension on an occupied home. The client wants to be in by a fixed date because of a family event. The builder starts with that date and works backwards.
The physical dependencies are: demolition cannot start until the asbestos clearance and the certifier’s demolition approval are in place; the slab cannot be poured until the excavation is inspected; the frame cannot start until the slab has cured and been inspected; the roof cannot be sheeted until the frame is up; rough-in cannot start until the roof is on; linings cannot start until rough-in is inspected; fit-out cannot start until linings are finished; practical completion cannot occur until fit-out is complete and the final inspection is booked.
The builder traces the longest chain and finds that the critical path runs through the certifier approvals and the window order, not through the trades. The demolition approval has a booking delay. The window order needs to be placed before the frame starts, not after. The inspection bookings each add time between the trade finishing and the next trade starting.
Now the builder places float. Two days of weather buffer sit across the slab and frame. A week of selection buffer sits between the client’s selection deadline and the cabinetry order date. Inspection buffer sits after each hold point. The programme is drawn with the critical path highlighted and the buffer shown separately, so the client can see where the risk is.
Three weeks in, the window supplier advises a delay. Because the order milestone was on the programme, the builder sees it immediately and can decide whether to resequence, substitute a product, or draw on buffer. The decision is made on evidence, not on panic. That is the value of the method: it gives you options before the problem reaches the completion date.
The mistake that costs the most. Booking trades back-to-back with no float and no procurement milestones turns a single late delivery into a cascading delay that moves the completion date, and by then the client has already given notice to their landlord. The cost of that cascade lands on the builder, not the supplier.
Hold points, inspections and approvals as programme activities
Inspections are not administrative overhead. They are activities with duration, and on a home job they are often the point where the programme breaks. A certifier may need notice, a council may need to book an inspection, and the trade cannot proceed until the inspection passes.
Treat each hold point as an activity in the programme with its own duration. Then attach the dependency: the next trade cannot start until the inspection is passed. That makes the inspection visible and gives you a reason to book it early rather than on the morning you need it.
The same logic applies to approvals that are not site inspections: BASIX commitments, council conditions, and any consent requirements that gate a stage. If an approval is a condition of proceeding, it belongs on the programme with a date, not in a folder.
High risk construction work adds another layer. Where a safe work method statement is required, the sequencing needs to reflect the controls in it, and the programme should show where those activities sit so that supervision is available when they occur. The information sheet on safe work method statements for high risk construction work from Safe Work Australia sets out when one is required and what it must contain.
Updating the programme weekly and using it commercially
A programme that is not updated is a document for the file. The value comes from marking it weekly against what actually happened, then recalculating the buffer. Fifteen minutes a week is enough on a home job.
The weekly update does three things. It shows whether you are ahead or behind on the critical path. It shows how much float you have used. And it gives you the evidence base for any conversation about time, whether with the client, a subbie or a supplier.
That evidence matters commercially. If a client delays a selection and the job runs over, the programme shows the dependency and the date the selection was needed. If a subbie is late and it affects the critical path, the programme shows the knock-on. Without a current programme, those conversations become arguments about memory.
It also matters for record keeping. A dated programme, updated weekly, is a contemporaneous record of what was planned and what changed. That is useful if a dispute arises, and it is useful for your own estimating on the next job, because you can see where your assumptions were wrong.
Common programme failures on home jobs and how to avoid them
The failures recur across small residential work. Naming them makes them easier to spot before they cost you.
- No procurement milestones. The programme lists trades but not order dates, so long-lead items are ordered too late.
- No inspection duration. Hold points are assumed to be instant, so the gap between trades is not planned.
- Float spread evenly. Buffer is added to every activity rather than concentrated where delay lands, so it protects nothing.
- Client selections not on the programme. Selection deadlines are not shown, so the client does not know when decisions are needed.
- No weekly update. The programme is issued once and never revised, so it stops reflecting reality within a fortnight.
- One programme for the client and another for the site. Two versions create confusion; use one version with the level of detail appropriate to each audience.
Avoiding these failures is mostly about discipline. The sequencing method is straightforward; the hard part is holding the float rather than spending it the first time a trade is late.
Where the programme sits alongside your other obligations
A programme is one of several documents that govern a home job, and it needs to be consistent with the others. The contract sets the completion date and any liquidated damages. The safety documentation sets the controls for high risk work. The approvals set the conditions that gate stages. If the programme contradicts any of those, it is the programme that is wrong.
For builders in NSW, keeping the programme method current is part of running a compliant business, and it sits alongside the CPD obligations that apply to licensed builders. The guide to how NSW builder CPD works explains the framework, and the course catalogue lists the available programs. Builders who want to see how the business topics fit together can start from the PointCPD home page.
One further consideration for builders running multiple jobs: the programme is also the input to your own cash flow. Progress claims are tied to stages, and stages are tied to the programme. If the programme slips, the claim slips, and the business carries the cost. That is the commercial reason to protect float, not just the contractual one.
Finally, the programme interacts with how you run subbies. A clear sequence with realistic durations is the basis for a fair conversation about access and completion, and it reduces the disputes that come from trades arriving to find the previous trade not finished. The related article on managing subcontractors on site in NSW covers that side of the job.
Questions builders ask
How detailed should a construction programme be for a home job?
Detailed enough to show the dependencies and the hold points, but not so detailed that it becomes a burden to update. On a home job, a single page with the critical path highlighted, procurement milestones, inspection durations and buffer marked separately is usually sufficient. If you cannot update it in fifteen minutes a week, it is too detailed.
What is float and why does it matter on a small residential job?
Float is the amount of time an activity can slip without moving the completion date. It matters because delay is normal on a home job, whether from weather, client selections or inspection bookings. If the programme has no float, the first delay moves the completion date, and the builder carries the consequences. Float is the mechanism that lets the job absorb disruption.
Should I include procurement lead times in the programme?
Yes. On small residential work, long-lead items such as trusses, windows, cabinetry and appliances often drive the critical path more than site activities do. The order date for each item should sit on the programme as a milestone, so you can see it coming and chase it before it becomes a site delay.
How do I handle inspections and approvals in the programme?
Treat each inspection or approval as an activity with its own duration, and attach the dependency that the next trade cannot start until it is passed. That makes the hold point visible and gives you a reason to book it early. If an approval is a condition of proceeding, it belongs on the programme with a date.
How often should the programme be updated?
Weekly is the practical standard on a home job. The update should record what actually happened, recalculate the buffer, and show whether the critical path has moved. A programme that is issued once and never revised stops reflecting reality within a fortnight and becomes a document for the file rather than a tool for running the job.
What is the most common reason home job programmes fail?
Spreading float evenly across every activity instead of concentrating it where delay actually lands. Adding a day to every trade does not protect the completion date; it just gives each trade a day they will probably use. Float needs to sit across the weather-exposed stages, between selection deadlines and order dates, and after inspection hold points.
Sources
- Safe work method statement for high risk construction work · Safe Work Australia
- Flood risk management manual · NSW Government
- Small business cyber security · Australian Signals Directorate
- Privacy for small business · Office of the Australian Information Commissioner
Published 15 July 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
