Skip to main content

    April 2026: New National Minimum Wage rates now in effect. Check your pay →

    SiteKiln — Your rights on site. In plain English.
    SiteKiln

    SiteKiln gives you plain-English information, not legal advice. If you need advice specific to your situation, talk to a qualified professional.

    Time at Large: What It Means and Why It's a Mess

    7 min read·Reviewed April 2026
    By SiteKiln Editorial TeamFirst published 25 Mar 2026Updated 21 Apr 2026
    Contracts & Disputes
    UK-wide

    How this site is funded →

    ‍‌​‌​​‌‌‌​​​​​‌‌​‌​​​​​​​​‌‌‌‌‌‌‌‍Most contracts pin you to a completion date and give the employer a clean LDs button if you're late. "Time at large" is when that button stops working because the contract machinery for dealing with delay has broken down or never existed in the first place.

    Under the prevention principle, no one can insist you meet a deadline if they themselves have prevented you from doing it and the contract hasn't given you a way to adjust the date.


    1. What "time at large" actually means

    In a normal construction contract:

    • there's a completion date
    • if delay events happen, you use the extension of time (EOT) rules to move that date
    • if you still overrun your adjusted date for reasons that are your fault, LDs can bite.

    "Time at large" is when:

    • there is no effective completion date anymore (because none was set, or the date has become invalid); and
    • your obligation becomes to complete within a reasonable time, not by a fixed date.

    In that situation:

    • LDs usually fall away -- there's no valid contractual date to measure them against; and
    • the employer, if they want money for delay, has to claim general damages and prove their actual loss and reasonableness.

    Sounds great for contractors, but it's rare and hard to win -- courts don't call time at large lightly.


    2. The prevention principle -- the engine behind time at large

    The prevention principle is simple in theory: a party can't rely on your failure to do something on time if their own actions prevented you.

    In construction delay, courts have distilled it down to points like:

    • Employer's acts that delay the works (even if "legitimate" under the contract, like variations or late info) can be "acts of prevention".

    • If the contract has a workable EOT mechanism that covers those prevention events, then granting extensions is enough -- time is not set at large just because the employer caused delay.

    • If there is no EOT mechanism, or it doesn't cover employer prevention, or the contract machinery has truly broken down, then it's unfair to hold you to the original date -- that's where time can become at large.

    • Courts have also said a contractor can't sit on its hands -- if you had a right to claim EOT and didn't bother, you usually can't then cry "prevention" and demand time at large.


    3. How contracts usually avoid time going at large

    Modern JCT/NEC and decent bespoke contracts are written precisely to stop time going at large.

    They do that by:

    • Having clear completion dates and EOT clauses that cover employer-driven and neutral events (variations, late info, access, exceptionally adverse weather, etc.).

    • Letting the CA/PM change the completion date when those events happen -- so the LDs mechanism still has a valid date to bite against.

    • Giving procedures for resolving delay disputes (EOT decisions, adjudication) without blowing up the whole programme logic.

    Time tends to become "at large" only when those mechanisms are missing, so badly drafted or so badly mis-used that they stop working altogether.


    4. Common routes to "time at large" (and why they're rare)

    Things that can push a project towards time at large include:

    • No completion date at all in the contract -- you then default to "reasonable time" as a term implied by law.

    • No EOT mechanism for employer/neutral delay -- contract has a fixed date and LDs but no way to move the date when the employer holds you up.

    • EOT machinery breaks down -- for example, the employer/CA fundamentally fails or refuses to operate the EOT process in good faith so delay caused by them is never properly recognised.

    • EOT clause too narrow -- it doesn't cover the sort of acts of prevention that actually happen, and there's no other way to adjust time.

    But the case law trend is clear:

    • If the contract has any plausible extension mechanism for employer delay, courts lean hard towards using that and keeping LDs alive, rather than declaring time at large.

    • If you fail to use the EOT rights you had (late notices, no evidence), you don't get time at large for free. You generally stay stuck with the contractual dates and LDs.

    So "time is at large" is not a magic defence. It's a niche outcome when the contract has really been allowed to fall apart.


    5. How to use this knowledge without kidding yourself

    For contractors and subs:

    • Assume your standard JCT/NEC contract does not easily go "time at large" -- your main protection is still EOT notices and records, not this doctrine.

    • When you're delayed by the employer, hit the EOT procedure hard and on time; don't just moan about prevention and hope a judge will later declare time at large.

    • If you're stuck on a really poor, one-page contract with a fixed finish date, no EOT clause and the client constantly holding you up, that's when a lawyer may start talking about time at large and prevention as a real argument.

    For employers:

    • Make sure your contracts have proper EOT clauses that cover employer acts and neutral events -- that's what keeps LDs enforceable.

    • Operate the EOT machinery fairly and consistently; bad-faith refusal to grant time is how you hand the contractor ammunition.


    "Time at large" myth-buster

    Myth: Any employer-caused delay makes time at large. Reality: If the contract has a workable EOT clause that covers that delay, you use that. Time generally stays not at large and LDs can still bite.

    Myth: If the employer is slow with decisions, LDs automatically fall away. Reality: You still have to serve proper delay/EOT notices and follow the contract. Courts expect you to use the machinery before shouting "prevention".

    Myth: Saying "time is at large" in a letter gets you off the hook. Reality: It's a complex legal conclusion, used rarely. Just writing the phrase doesn't change your obligations one bit.

    Myth: Modern JCT/NEC jobs often end up with time at large. Reality: Those forms are specifically drafted with EOT regimes to avoid time at large. It tends to arise, if at all, on badly drafted or very bare-bones contracts.

    Myth: If time is at large, you're home free. Reality: You still must finish within a reasonable time and the employer can still claim general damages for your unreasonable delay -- they just can't use the LDs shortcut.


    Disclaimer: SiteKiln gives you plain-English information, not legal advice. Talk to a solicitor before making big decisions on live disputes.


    What to do next

    • Do not rely on "time at large" as your main defence -- your first line of protection is always properly notified, evidenced extension of time claims.
    • If you are delayed by the employer, hit the EOT procedure hard and on time with proper notices and records.
    • Check whether your contract has a workable EOT clause that covers employer-caused and neutral delay events -- if it does, time at large is very unlikely to apply.
    • If you are on a very bare-bones contract with a fixed finish date and no EOT clause, and the client is constantly holding you up, get legal advice on whether a prevention or time-at-large argument has real legs.
    • Even if time is at large, you still have to finish within a reasonable time -- so keep working and keep records.

    Sources


    Know someone who needs this?

    How this site is funded →

    Was this guide useful?

    Didn't find what you were looking for?

    Spotted something wrong or out of date? Email us at hello@kilnguides.co.uk.

    In crisis? Samaritans 116 123 ·

    How this site is funded →

    What to do next

    Found this useful?

    Get updates when we add new guides. Once or twice a month. No spam. Unsubscribe anytime.

    We don't ask for your name, age or gender. Just your email and trade. Region is optional but helps us write better guides for your area.

    Important disclaimer

    SiteKiln provides general guidance only. Nothing on this site — including our guides, tools, templates and document hub — is legal, tax, financial or professional advice.

    Every situation is different. Laws, regulations and industry standards change. You should always check with a qualified professional before making decisions based on what you read here.

    We do our best to keep information accurate and up to date, but we cannot guarantee it is complete, correct or current. SiteKiln accepts no liability for actions taken based on the content of this site.