Held, Not Spare: A Client's Ledger for Time Contingency in Commercial Refurbishment
Photo: Barbara Carr , CC BY-SA 2.0, via Wikimedia Commons
A completion date on a UK commercial refurbishment is rarely just a date. It may anchor a rent commencement, a lease event, a fit-out sequence or the return of an operational floor. Yet time contingency often sits in the programme as an unlabelled buffer, available to the first activity that runs late. The difficulty is not that delay occurs. It is that the reserve is spent before anyone can say who authorised its use, what risk it was held against, or how much remains.
Two kinds of time that look alike
Programmes commonly show float on activities that are not critical. That float is a scheduling property: it describes how much an activity can move before it affects a linked path. It is not the same as a client-held reserve. Contractor slack sits within the contractor's plan and is shaped by its sequencing, resource assumptions and procurement choices. Client time contingency is a governance instrument. It is set aside to absorb identified risks, decision latency or unforeseen site conditions without automatically moving the completion date.
When the two are blurred, early progress is sometimes treated as a bank of spare time. Late decisions are then absorbed quietly into the programme, and the first clear signal is a revised completion forecast. By then the reserve may already be gone. The practical remedy is to separate the concepts in the programme documents and in the reporting routine.
Give the reserve a name and an owner
A client-side team should establish a time contingency register that sits alongside the programme, not inside activity durations. The register should state the amount of time held, the risks it is intended to cover, the person or group authorised to release it, and the threshold above which escalation is required. A risk-based allocation is more defensible than a single percentage applied to the whole programme. Landlord approvals, utility connections, asbestos containment, procurement of long-lead items and access to occupied areas may each justify a defined allowance.
Each drawdown should be recorded with the cause, the activities affected, the forecast impact, the mitigation proposed and the remaining balance. That record need not be elaborate, but it should be contemporaneous. A reserve without a ledger is simply an assumption waiting to be consumed.
Consumption is not the same as entitlement
One reason time contingency is poorly managed is that clients and contractors often talk past each other. A programme moving into reserve is an operational fact. It does not, by itself, establish an extension of time, a compensation event or a change to the contract sum. Those questions are resolved under the contract, not by the colour of a bar chart.
Keeping the two conversations separate reduces friction. The programme record shows what time has been used and why. The contractual record shows whether notice has been given and whether entitlement follows. Where early warning procedures exist, they should be used as a routine management tool rather than as the opening move in a dispute. A short warning that identifies the issue, the likely drawdown and the decision needed is more useful than a letter written after the date has moved.
Track leading indicators, not only the critical path
Critical path movement is a lagging signal. By the time it appears, the reserve may already be under pressure. Client teams should watch the rate at which contingency is being consumed and the indicators that tend to precede consumption: approval turnaround, technical query closure, sample sign-off, procurement lead times, site access constraints and progress against planned percentages.
Thresholds help. At, say, twenty-five per cent consumption, the project board should review the causes and the remaining risk allocation. At fifty per cent, a recovery plan and a revised decision calendar should be expected. A monthly contingency statement, even a single page, gives the client a clearer view than a programme update alone.
Make early warning a habit
The aim is not to make every variance a formal event. It is to ensure that the programme does not absorb the reserve silently. A standing agenda item at progress meetings can ask a simple question: on current trends, which risks are likely to require a drawdown in the next reporting period? That question invites mitigation before the date is affected.
A decision log should sit beside the contingency register. Many drawdowns trace back to a pending instruction, an unresolved design query or a late approval. Recording the decision required, the owner and the date needed turns time contingency from a passive buffer into an active management tool. It also gives the client a fair basis for challenging optimistic sequencing without treating the contractor as an adversary.
Protect the date without weaponising the programme
Time contingency is most effective when it is visible, owned and spent deliberately. It should not become a hidden pool that disguises late decisions, nor a contractual weapon that turns every programme movement into a claim. For UK commercial refurbishment clients, the discipline is straightforward: hold the reserve separately, allocate it against named risks, record each use, review consumption early and keep operational reporting distinct from contractual entitlement. A completion date is better protected by a managed reserve than by an unspoken hope that the programme will recover on its own.
