The Modern Housebuilder

All seven outputs

The roof slips two weeks. What else moves, and who needs telling?

Anybody can draw bars on a chart. The hard part of a building programme is knowing what goes on it, in what order, and what happens to everything downstream when one thing does not turn up. That is the part you have never done before and your builder has done a hundred times, and it is the part that decides whether you are still paying for scaffold in November.

The programme on a real build: phases down the left from land and finance through design, surveys, planning and building control, with durations, start and finish dates, and linked bars across a two-year calendar.

The build you can look round, from land purchase to practical completion.

It opens two years before the first brick. Land, finance and insurance. Appointing a design team. Pre-application, planning, discharging conditions. Surveys you have to commission before anybody can design anything. Most self-build overruns are decided in that period, by somebody who did not know the ecology survey has a season.

It is composed from five answers about your house

Not chosen from a library of templates. You answer five questions, and the programme is built from them — the tasks, the order and the links between them all follow from what kind of house this is.

  1. What it is built of

    Traditional masonry

  2. What the outside is

    Block and render

  3. How many storeys

    Two storeys

  4. How you are buying the work

    Self-managed packages

  5. Retaining or feature walls on the plot

    None

The five questions that decide the shape of the programme, each answered from a short list: build system, external face material, storeys, how the work is being procured, and whether there are retaining or feature walls.

Answer these five and the programme composes. Leave one and it will not.

Until all five are answered nothing is produced, because a programme drawn off a missing answer would be a picture of somebody else’s house. Every combination of those five works out — there are two hundred and forty of them and each one has been put through the composer and scheduled.

Our durations are labelled as ours until you stand behind them

The programme as a table: each task with its start, finish and working days, and beneath the ones the reader has not confirmed a small line reading our duration, not yet yours.

Our duration, not yet yours — until you replace it with the one your groundworker gave you.

Every duration we supply carries that line. They are indicative figures that come with the template, and they stay marked as ours until you put in the number somebody actually quoted you. Nothing pretends a figure is yours when it is not, which is the difference between a programme you can defend and a chart you inherited.

It tells you where you stand without having an opinion about it. On this build: started on site 15 September 2025, and on your durations and your sequence the work finishes 3 July 2026 — twenty working days before the date you said you wanted. It is arithmetic, not a verdict.

The end of the programme: scaffold strike, service connections, external works, snagging and commissioning including the air test, then handover — building control certificate, warranty final inspection, EPC lodged, completion pack assembled, practical completion.

The last eight weeks, which is the part nobody remembers to programme.

Commissioning, the air test, snags walked and re-walked, running the house before handover, the EPC lodged, the completion pack assembled. Every one of those is a real week of your life and none of them is on the chart somebody sketches on the back of a drawing.

Issue it and that version is fixed for good

A programme nobody can point at afterwards is a picture of a programme.

The issue panel: who the programme is going to, what has changed since the last issue, and beneath it the record of what has already been issued — Rev A, the date, who it went to, and that all one hundred and forty-four durations were stood behind, making it the baseline.

Rev A, the day it went out, and who it went to.

Issuing takes a dated copy of every row and the dates it currently shows, and records who you sent it to. Nothing on your live programme changes, and the copy can never be edited afterwards — which is exactly what makes it worth having when a trade tells you in April that they were never given a date.

The programme summary: planned dates from Rev A against what actually happened — land purchase, design team appointed, planning permission granted, start on site, practical completion, and the pre-construction duration planned at 219 working days against 109 actual.

What you issued against what happened, side by side.

Once one issue has every duration stood behind it, it becomes the baseline, and from then on the summary reads planned against actual on the dates that matter. Not a percentage of how well you are doing — a pair of dates, and you draw your own conclusion.

What you get out

A dated issue

Every row and every date as they stood the day you sent it, with who you sent it to, locked.

Something to print

The bars, the tasks and the dates on paper, for the wall of the site cabin or an inbox.

A file for planners

An XML a contractor’s planner can open in Microsoft Project, Primavera P6 or Asta Powerproject.

The planning file carries the sequence and the durations across into a planner’s own software, so a contractor can work with it rather than retyping it. It is a copy and not your issued record — what you issued stays where it is, untouched by whatever anybody does to their copy of it.

video slot: one duration changing, and the finish moving with itfilmed once the build stops moving

Start seven daysSee this one on a real build