Known Absences, Unknown Delays: A UK Shutdown Calendar for Commercial Programmes

Most programmes are built on the assumption that every week contains five working days of equal capacity. That assumption rarely survives contact with a supplier's annual shutdown, a client's approval queue in late December, or a school holiday that removes half a commissioning team. The resulting delay is seldom mysterious; it is simply unrecorded.

The commercial task is not to eliminate predictable unavailability. It is to name it, place it in the programme and test the programme against it before commitments are fixed. A shutdown calendar is therefore less an administrative nicety than a commercial control.

The difference between a quiet week and a closed week

A quiet week still permits decisions. A closed week does not. When a supplier's factory shuts for maintenance, when a client's approver takes extended leave, or when a site cannot offer term-time access, work does not merely slow. It stops at a defined point and restarts on someone else's timetable.

The distinction matters because many UK programmes already carry float for ordinary variability. That float is often calculated on the basis of normal working patterns: illness, weather, minor design queries and the usual friction of construction and supply. Predictable closures are different. They are known in advance, often announced months ahead and repeated annually. If they are not in the programme, they are being absorbed by float that was intended for something else.

By the time the absence occurs, the commercial conversation has usually moved from planning to causation. A supplier will point to its published shutdown. A client will point to its leave policy. A delivery team will point to the school calendar. None of these explanations is unreasonable. The weakness is that they were available earlier and not used.

Four layers of unavailability

A useful shutdown calendar has four layers. The first is supplier and subcontractor closure. This includes factory shutdowns, annual maintenance, stocktake periods, haulier restrictions and the reduced capacity that often surrounds them. A closure date is not the only relevant date; the days before and after may be affected by backlog, cleaning, restart checks or partial staffing.

The second is client and approver availability. In the UK, late August and the period between Christmas and New Year are common leave windows. An approver's absence is not a closure of the client organisation, but it can be a closure of the decision path. Where a programme depends on a specific signature, a specific panel or a specific technical authority, that dependency belongs in the calendar.

The third is labour and access. School holidays affect site teams, commissioning engineers and specialist subcontractors. Term-time access restrictions affect schools, colleges and some public buildings. Sporting calendars, local events and road restrictions can also create predictable access constraints. These are not random events; they are known patterns that can be mapped.

The fourth is planned maintenance and utility windows. Power shutdowns, water isolation, road closures and landlord works may be scheduled by others. A programme that assumes continuous site services without confirming those windows is relying on an assumption rather than a plan.

Put the calendar on the table at tender

The strongest time to test predictable unavailability is before the programme becomes a contractual baseline. At tender, commercial teams should ask for the supplier's published shutdown dates, not simply its lead times. They should ask which approvals depend on named individuals or panels and when those groups are least available. They should ask how school-holiday capacity affects site supervision and commissioning. They should ask whether any planned maintenance or access restriction falls within the works period.

The next step is to place those dates against the programme and examine the resulting float. A programme that shows two weeks of float in December may be showing float that is already spoken for. If the shutdown is not represented, the float is misleading. If the shutdown is represented, the team can decide whether to accelerate, resequence, hold stock or accept a later completion date.

This is a commercial discussion, not a scheduling formality. A tender programme that ignores known closures is not necessarily dishonest; it may simply be optimistic. But optimism is a poor basis for a delivery obligation. The earlier the calendar is tested, the more options remain available.

Record the basis, not just the dates

Once the calendar is agreed, it should be recorded in the programme basis and, where appropriate, in the contract documents. The record should state which dates were assumed, which activities are affected and what the parties agreed about mitigation. It should also identify the date by which the calendar will be refreshed.

A shutdown calendar is a live document. Supplier dates can move. Client leave arrangements can change. A new school term or a revised maintenance window can alter the picture. The calendar should be reviewed at programme updates, not filed at tender and forgotten. Where a date changes, the commercial team should assess the effect on float before the effect becomes a delay.

This approach also improves delay records. If a closure was known and programmed, a later dispute about its effect is easier to resolve. If it was known and omitted, the programme carries an unexplained gap. Contemporaneous records are strongest when they show what was anticipated, not only what was encountered.

A line in the programme, not a note in a diary

The fortnight nobody programmed is rarely a surprise. It is usually a known absence that was left outside the plan because it did not fit the assumed working week. UK commercial teams can reduce that risk by building a shutdown calendar early, testing float against it at tender and keeping the assumptions visible as the programme develops.

The discipline is straightforward: identify the predictable absence, place it in the programme and price or programme the consequence. A calendar will not remove the festive break or the factory shutdown. It will, however, prevent the programme from pretending they are ordinary working weeks.