The programme is the budget, in another form

A development programme looks like a list of dates and behaves like a cost schedule.

Every week between the first drawdown and the last settlement carries interest, rates, insurance and whatever the site costs simply to hold.

The critical path is short, and it is not the building

Most programmes lose their time before anybody pours concrete: planning, the authority referrals, the construction certificate and the finance approval.

Those items run in sequence and depend on other people, which makes them the genuine critical path on nearly every project.

Authority timeframes are estimates, not commitments

A statutory period describes the assessment, and the clock stops whenever a council requests further information.

A programme built on the headline number, rather than on what similar applications actually took in that council, reads as optimistic to anybody experienced.

Name who owns each date

A programme where every line belongs to the developer hides the truth. A consultant, a council or a bank owns most of those dates.

Naming the owner turns a slipping date into a phone call to a specific person rather than a general anxiety.

Lead times sit outside the builder's control

Lifts, switchboards, windows and structural steel all carry long lead times, and a supplier's queue does not care about a construction programme.

Ordering those early, and naming the order date on the programme, prevents a finished building waiting on one item.

Weather and site conditions belong in the programme

Wet weather stops earthworks and concrete, and a contract usually allows the builder an extension for it.

A programme with no allowance produces a claim instead, which costs the same time and adds an argument to it.

Every week costs a knowable amount

Interest on the drawn balance, council rates, land tax, insurance and any rent forgone all accrue weekly whatever happens on site.

Our guide to holding costs covers calculating that figure. Once a developer knows it, every programme decision has a price beside it.

Consultants need booking before they are needed

A good traffic engineer, acoustic consultant or certifier carries a queue, and the week a developer needs one is rarely the week they are free.

Booking them against the programme, rather than ringing when the task arrives, removes a delay that is invisible until it happens.

Settlement dates drive everything backwards

Presold apartments settle after an occupation certificate, and the certificate follows practical completion, which follows the defects the certifier finds.

Working the programme backwards from settlement, rather than forwards from the start, shows which dates actually matter.

Update it monthly, honestly

A programme nobody revises describes the project somebody hoped for in a meeting eight months ago.

A monthly update, showing the slippage plainly, gives the financier and the equity partners a picture they can act on early.

Sales and construction run on different clocks

A display suite opening too early sells into a market the project cannot deliver to for two years, and buyers walk away during the wait.

Aligning the sales launch with a credible completion window keeps the deposits, which is what the financier is watching.

A slipped programme needs a decision, not a new date

Moving a date on a spreadsheet changes nothing. The question is whether to spend money recovering the time or accept the cost of losing it.

Both answers are legitimate, and a developer who has priced the week can choose between them rather than hoping.

What to change first

• The critical path covers approvals and finance, not only construction
• Authority timeframes reflect what this council actually takes
• Every programme line names the person or body who owns it
• Long lead items appear with their order dates
• The programme allows for weather rather than assuming none
• The weekly holding cost sits beside the programme
• A monthly update shows slippage plainly to everybody funding it