Back to Insights

Time at large and the prevention principle: when the employer's delay frees the completion date

Aven-AI InsightsContracts & Claims8 min read
Steel building frame under construction beside a tower crane.

Citable answer: Time at large means there is no longer a fixed completion date the contractor must hit. It arises where the employer causes delay but the contract has no mechanism to extend time for it. Under the prevention principle the employer then cannot enforce the original date or deduct liquidated damages, and the contractor must finish within a reasonable time.

Short answer: "Time at large" means there is no longer a fixed completion date the contractor must hit. It happens when the employer causes delay but the contract has no mechanism to extend time for it. Under the prevention principle, the employer then cannot enforce the original date or deduct liquidated damages, and the contractor's duty falls back to finishing within a reasonable time.

That is a large consequence to hang on a drafting gap, and it is why the point matters to anyone running a delayed job. It is also widely misunderstood: many teams believe an employer delay automatically sets time at large. In a modern, well-drafted contract, it usually does not. The difference is worth understanding precisely, because it decides whether liquidated damages survive.

What does "time at large" mean?

Time at large means the obligation to complete by a specified date has fallen away, and is replaced by an implied obligation to complete within a reasonable time. There is no date to measure delay against, so there is nothing to which liquidated damages (also called delay damages) can attach. The employer is not left without a remedy entirely, but it loses the fixed, pre-agreed sum per day and must instead prove its actual general damages for late completion, to the extent it can.

For the employer that is a poor position, because liquidated damages exist precisely so it does not have to prove loss. For the contractor, time at large removes the daily deduction and buys breathing room, but it is not a windfall: "a reasonable time" is a genuine standard, and finishing unreasonably late still exposes the contractor to a damages claim.

The prevention principle, plainly

The prevention principle is a long-established doctrine of English law: a party cannot enforce a contractual obligation against the other party where it has itself prevented that party from performing it. In construction, that means an employer cannot hold the contractor to the completion date if the employer, by act or omission, prevented the contractor from meeting it — for example by late access, late information, or extra work instructed without a matching adjustment to time.

The classic statement comes from Peak Construction (Liverpool) Ltd v McKinney Foundations Ltd (1970) 1 BLR 111. There the contract's machinery for extending the completion date did not cover delay caused by the employer. Because there was no way to move the date to account for the employer's own delay, the court held the employer could not insist on the original date, and time was set at large. Salmon LJ's judgment is the root most later cases trace back to.

The crucial detail in Peak is why time went at large: not merely because the employer caused delay, but because the contract had no mechanism to extend time for that delay. That distinction is the whole game.

How modern contracts close the gap

The lesson the industry took from Peak was simple: write an extension-of-time clause wide enough to cover employer-caused delay, and time stays fixed. Standard forms did exactly that. FIDIC, NEC4, JCT and most bespoke contracts now include express "employer's risk" or "relevant" events — variations, late access, late drawings, and similar — that entitle the contractor to move the completion date rather than lose it altogether.

The courts confirmed the effect. In Multiplex Constructions (UK) Ltd v Honeywell Control Systems Ltd (No 2) [2007] EWHC 447 (TCC), Jackson J held that where the contract contains an extension-of-time clause capable of accommodating the employer's delay, and a mechanism for calculating it, the delay is dealt with by granting more time under the contract — it does not put time at large. The Peak principle applies only where the machinery genuinely fails to reach the delay.

Two related points follow. First, how the extension is measured: in Balfour Beatty Building Ltd v Chestermount Properties Ltd (1993) 62 BLR 1, the court adopted the "net" method, extending the completion date by the number of days fairly attributable to the relevant event rather than re-setting the clock from the date of the event. The contractor is relieved of the employer's delay, but not of delay it caused itself. Second, an extension of time relieves the contractor from liquidated damages for that period; it does not, by itself, carry any money. Prolongation cost is a separate entitlement that must be established on its own terms.

Can a contract exclude the prevention principle?

Largely, yes. The prevention principle is not an overriding rule of law that trumps the parties' bargain. In North Midland Building Ltd v Cyden Homes Ltd [2018] EWCA Civ 1744, the Court of Appeal upheld a clause providing that where contractor-caused delay ran concurrently with employer-caused delay, the concurrent period would not count towards an extension of time. The court held the prevention principle can only operate through implied terms, and cannot be implied where it contradicts an express term that allocates the risk. Freedom of contract prevailed.

The practical reading: the prevention principle is a gap-filler, not a trump card. It protects the contractor only where the contract is silent or defective. Where the drafting squarely allocates a risk — including concurrent delay — the express words govern. This is one more reason heavily amended contracts deserve close reading: an amendment can quietly shift where time at large is even possible.

The trap: a mechanism only protects you if you use it

Here is the point most exposed to real-world loss. A wide extension-of-time clause keeps time fixed — but only if the contractor operates it. Almost every modern clause makes the contractor's entitlement conditional on notice within a set period. Under FIDIC, that is the 28-day notice (Sub-Clause 20.1 in the 1999 forms; Clause 20.2 in the 2017 forms); under NEC4, the eight-week limit on compensation events in clause 61.3. Miss the notice, and the entitlement can be time-barred even though the delay was genuinely the employer's.

That creates an uncomfortable asymmetry. If the mechanism exists but the contractor fails to serve notice in time, courts have generally been reluctant to rescue the contractor by declaring time at large — the machinery was there to be used. The Australian decision in Gaymark Investments Pty Ltd v Walter Construction Group once suggested a missed notice could set time at large, but later English authority, including Multiplex, treated that reasoning with caution. The safer assumption on a well-drafted contract is the opposite: a missed time-bar loses the extension and leaves the original completion date — and the liquidated damages — intact.

So the two failure modes point in opposite directions, and both are avoidable. A defective clause that cannot reach an employer delay can hand the contractor time at large. A perfectly good clause, unused because a notice was missed, does the reverse and preserves the employer's damages. Getting either wrong turns on paperwork and dates, not on the merits of who caused the delay.

What this means on your project

For a project director or commercial manager, the working checklist is short. Know whether your contract's extension-of-time clause actually covers every category of employer delay, or whether an amendment has narrowed it. Assume the prevention principle will not save a missed notice — serve every time-related notice inside the contractual window, on the merits and in the correct form. Track concurrent-delay wording specifically, because an express allocation there will override the general doctrine. And keep the contemporaneous records that let you prove both the cause and the number of days, since even a valid extension is measured, not assumed.

None of this is exotic. It is the same discipline that protects any extension-of-time entitlement: read the clause, watch the clock, serve on time, keep the records. Time at large is best understood not as a prize to aim for but as evidence of a contract that failed to do its job — and on most projects, the more likely risk is the mirror image, a good clause quietly lapsed through a missed notice.

This is where a contract-aware reasoning layer earns its place. Aven-AI reads the contract — including bespoke amendments to the extension-of-time and concurrent-delay provisions — maps every notice window and time-bar, and warns the responsible person before a deadline lapses. It flags and drafts, with every point cited to the clause; the human decides and serves. It does not send anything on your behalf. The aim is simple: make sure the mechanism that keeps time fixed, or protects your entitlement, is actually operated in time — so the argument is about the merits, never about a date you missed.

This article is general information, not legal advice. It cites its sources so you can verify each point; take advice on your specific contract and facts.

Sources & further reading

Related reading: Extension of time under FIDIC, plainly · Clause 20.1 and the 28-day time bar · Concurrent delay: who owns the time?

Ready to put this into practice?

See how Aven-AI flags notice, time-bar, programme and QHSE risks before the window closes.

Request early access