Time, Delay and Completion

Introduction and Context

Time is one of the three principal dimensions of construction performance, alongside cost and quality. In construction contracts, time is not merely an administrative target. It allocates risk, determines entitlement to additional payment, affects financing and occupation, and may trigger damages or termination rights. A delay that appears simple on a programme may therefore have complex legal consequences.

This chapter examines how contractual time obligations are created, measured, analysed and enforced. It focuses on commencement, milestones, extensions of time, critical-path delay, concurrency, acceleration, suspension, practical completion, liquidated damages, penalties and time-at-large principles. The central professional skill is to connect legal entitlement with reliable schedule evidence.

Contract law differs among jurisdictions and contract forms. The discussion states general principles commonly encountered in common-law construction contracts; the governing legislation, judicial decisions, amendments and contract wording must always be checked before advice is given.

Learning Objectives

By the end of this chapter, a student should be able to:

1. Explain commencement dates, contractual periods, milestones and completion obligations.
2. Distinguish an event causing delay from delay that affects the contractual completion date.
3. Analyse critical-path delay using programmes, updates, contemporaneous records and accepted methods.
4. Explain extensions of time, concurrency, acceleration and suspension.
5. Distinguish practical completion from final completion, sectional completion and contractual completion.
6. Evaluate liquidated damages, penalties and the time-at-large principle.
7. Prepare a reasoned time analysis supported by schedule evidence.

1. The Contractual Architecture of Time

A construction contract normally contains several interrelated time obligations:

• the date or event for commencement;
• the date by which the contractor must begin work on site;
• the duration or period for completion;
• sectional or phased completion dates;
• milestone dates for design, procurement, testing or access;
• notice requirements for delay and claims;
• extension-of-time provisions;
• obligations to mitigate delay;
• consequences of late completion; and
• provisions governing suspension, termination and acceleration.

The contract should be read as a system rather than as isolated clauses. For example, a clause requiring completion within 300 calendar days may be qualified by a provision allowing an extension for variations, exceptionally adverse weather or employer delay. A milestone may be described as binding, indicative or linked to payment. Its legal significance depends on the wording and the surrounding contract structure.

Commencement and the Time Base

Commencement may be fixed by a calendar date, a notice to proceed, possession of the site, satisfaction of a condition precedent, or a combination of these. The time base must identify:

• the reference date from which time runs;
• whether days are calendar days or working days;
• treatment of holidays and weather;
• the effect of delayed access to parts of the site;
• whether sectional possession creates separate time periods; and
• the date on which completion is assessed.

A notice to proceed does not automatically cure the employer’s failure to provide access if the contract makes access a prerequisite to performance. Conversely, a contractor may not rely on a minor access difficulty to suspend all obligations where the contract permits progress in other work areas.

Milestones

A milestone is a specified event or date within the project. Examples include approval of shop drawings, completion of foundations, delivery of major equipment, energisation, commissioning or handover of a section. Milestones may be:

1. Contractual and enforceable: failure may constitute breach or trigger a specified remedy.
2. Payment milestones: achievement permits an interim payment but may not itself be a completion obligation.
3. Management milestones: used for coordination and monitoring but not necessarily enforceable.
4. Access or interface milestones: required to enable another contractor or the employer to proceed.

The legal effect depends on clear drafting. A milestone should identify the responsible party, required evidence, acceptance criteria, consequences of failure and relationship to the overall completion date.

2. Delay, Disruption and the Completion Date

Delay is a failure to complete an activity or project by the time required. Disruption is interference with the planned method or efficiency of working, even if the final completion date is not extended. Disruption may cause additional cost through reduced productivity, out-of-sequence work, overcrowding or repeated mobilisation.

A delay event is not necessarily a compensable delay. Four questions should be asked:

1. Did an event occur?
2. Was the event the responsibility or risk of the employer, contractor, neutral event or another party?
3. Did it affect an activity on the relevant critical path or otherwise delay a contractual milestone?
4. Was the contractual notice and substantiation procedure followed?

Delay Classification

The same physical event may have different legal outcomes under different contract forms. A change in design may entitle the contractor to time and money under one contract, but only time under another.

3. Programme Logic and the Critical Path

A programme is evidence of intended sequence and duration. It is not automatically a contractual promise, nor is it conclusive proof of actual causation. Its reliability depends on logic, update quality, actual dates, resource assumptions and consistency with site records.

The critical path is the sequence of activities that determines the earliest possible completion of the project, subject to the programme’s logic and constraints. Delay to a critical activity can delay completion; delay to a non-critical activity may consume available float without changing completion.

For a simple activity network, the earliest finish is:

where:

• EF_i is the earliest finish of activity i;
• ES_i is its earliest start; and
• D_i is its duration, all measured in consistent time units.

For an activity with successors, the earliest start is governed by predecessor logic. Under a simple finish-to-start relationship with no lag:

where i represents all activities that must finish before successor j can start. The latest finish and latest start are calculated by backward pass, and total float can be represented as:

where LS_i and LF_i are latest start and latest finish. Zero or near-zero float indicates a critical or potentially critical activity under the model.

These equations assume a deterministic network, correctly defined logic, and durations that are being used for planning analysis. Real projects contain resource limits, calendars, uncertainty, multiple critical paths and changing logic. Therefore, float values should not be treated as legal conclusions without examining the actual programme and contract.

Worked Schedule Example

Consider the following simplified activities:

The route A–B–C–E–F has duration 5 + 15 + 20 + 10 + 5 = 55 days. The route A–B–D–E–F has duration 5 + 15 + 12 + 10 + 5 = 47 days. On this simplified logic, A–B–C–E–F is critical and the second route has 8 days of float before E is affected. A four-day delay to D would not delay completion if the stated logic and durations remain valid. A four-day delay to C would delay completion by four days, unless recovered by acceleration or changed sequencing.

This is not a conclusion that D is legally irrelevant. Delay to D may affect cost, create disruption, consume float, or become critical after a programme update.

Schedule Evidence

A robust delay analysis commonly examines:

• the accepted baseline programme;
• contract and approved revisions;
• periodic updates with actual start and finish dates;
• logic ties, constraints and calendars;
• progress photographs, daily reports and site diaries;
• design registers and requests for information;
• correspondence and notices;
• delivery records and inspection reports;
• change orders and instructions;
• resource records and productivity information; and
• testing, commissioning and snagging records.

The analyst should preserve the contemporaneous position rather than retrospectively moving activities to make the result fit a claim. Common analytical approaches include as-planned versus as-built, impacted as-planned, time impact analysis, collapsed as-built and windows analysis. The appropriate method depends on the contract, data quality, period under review and purpose of the analysis.

4. Extensions of Time

An extension of time (EOT) changes the contractual completion date because a qualifying event has delayed completion. It is not a reward and does not necessarily compensate the contractor. Its primary function is often to prevent the employer from imposing damages for delay that the contractor was contractually entitled to suffer.

Typical EOT events include:

• late possession or restricted access;
• employer variations;
• late information or approvals;
• suspension instructed by the employer;
• delay by nominated or designated parties;
• exceptionally adverse weather, where defined;
• changes in law; and
• force majeure or other expressly identified events.

A claimant generally must demonstrate causation: the event affected activities that controlled the relevant completion date. A mere increase in work quantity does not establish an EOT unless the additional work affects the completion path.

Notice and Particulars

Many contracts require prompt notice, followed by regular updates and detailed particulars. Notice clauses may be conditions precedent, meaning that failure to comply can bar or limit entitlement. Other clauses treat notice as an administrative obligation subject to substantial compliance or proof of prejudice.

A good delay notice identifies:

• the event and contractual clause;
• date of occurrence and expected duration;
• affected work and programme activities;
• likely effect on milestones and completion;
• mitigation measures; and
• continuing information to be provided.

An administrator or contract manager should assess EOT claims fairly and promptly. Failure to make a decision can create uncertainty, affect damages and encourage disputes.

5. Concurrency

Concurrent delay occurs when two or more independent delay events overlap during a period relevant to completion, and at least one is an employer-risk event while another is a contractor-risk event. The concept is difficult because “concurrency” may refer to different situations:

• events beginning at the same time;
• events overlapping for part of their duration;
• two causes independently capable of delaying completion; or
• one event causing delay while another merely affects a non-critical activity.

A practical analysis should ask whether each event would independently delay the contractual completion date and whether the overlap is legally material. Merely overlapping dates in a programme do not prove concurrent critical delay.

The consequences depend on the contract and applicable law. Possible approaches include:

• time but no money for the overlapping period;
• apportionment between causes;
• the dominant-cause approach;
• the “first-in-time” approach; or
• a contractual rule expressly defining the result.

Because courts and tribunals do not apply one universal rule, a contract should state how concurrent delay is treated. Parties should also distinguish true concurrency from sequential delay, float consumption and contractor delay that follows an employer event.

6. Acceleration

Acceleration is the adoption of measures intended to achieve completion earlier than the contractor’s existing entitlement or to overcome delay. It may be:

1. Express acceleration: the employer instructs additional resources, overtime, resequencing or other measures under an express clause.
2. Voluntary acceleration: the contractor chooses to increase resources for its own reasons.
3. Constructive acceleration: the contractor claims that the employer refused or failed to grant an EOT and implicitly required completion by the original date.

Acceleration costs may include overtime premiums, additional shifts, extra plant, parallel working, expediting, temporary works and productivity loss. The contractor should not assume that working harder creates an entitlement. It should obtain a written instruction or reservation of rights, identify the target date, agree valuation principles and maintain evidence of additional cost.

Acceleration may also create safety, quality and labour-law risks. Excessive overtime, overcrowded work areas and premature commissioning can undermine the very completion being pursued.

7. Suspension

Suspension is a direction or event requiring work to stop or substantially reduce. It may be authorised by the contract, arise from employer default, result from a safety or legal requirement, or be caused by a neutral event.

The consequences may include:

• extension of time;
• prolongation and demobilisation costs;
• protection and storage of materials;
• remobilisation costs;
• design or price adjustment; and
• a right to terminate after a stated period.

The contractor must comply with a valid suspension instruction while preserving records and mitigating loss. It should secure the site, protect incomplete work, identify off-site materials and document labour and plant consequences. An instruction to “slow down” may be legally different from a suspension and should be clarified in writing.

8. Practical Completion and Completion Standards

Practical completion, substantial completion or completion on a similar formulation generally means that the works are complete enough for their intended use, despite minor defects or outstanding items that do not prevent beneficial occupation. The precise test depends on the contract and jurisdiction.

Practical completion is usually assessed by considering:

• whether the works can be used for their intended purpose;
• whether outstanding work is minor and capable of completion without substantial interference;
• whether statutory approvals, testing and commissioning are complete;
• whether life-safety systems operate;
• whether essential documents and certificates have been delivered; and
• whether remaining defects are listed and controlled.

A building may be physically usable but not practically complete if fire certification, permanent power, access, sanitation or essential commissioning is absent. Conversely, minor cosmetic defects should not normally prevent practical completion if the contract adopts a substantial-completion standard.

Practical completion often triggers possession, release of retention in part, commencement of the defects-liability period and transfer of certain risks. It may also stop liquidated damages. The certificate should therefore record the date, conditions, outstanding items and contractual consequences.

Final completion generally follows correction of defects and submission of close-out documents. Sectional completion applies where distinct parts have separate completion dates and consequences. Taking over by the employer is not always identical to practical completion; the contract should be checked carefully.

9. Liquidated Damages and Penalties

Liquidated damages are a pre-agreed sum payable for a specified breach, commonly late completion. Their purpose is to estimate or allocate loss and avoid proving actual loss in every case. A clause may specify a daily amount, weekly amount or formula, subject to any statutory controls.

A liquidated-damages clause should identify:

• the triggering breach;
• the relevant completion date;
• the rate and calculation period;
• the relationship to sectional completion;
• the effect of EOTs and partial possession; and
• the procedure for deduction or recovery.

A penalty is generally a contractual sum that is out of proportion to the legitimate interest protected or is imposed in a punitive manner. The distinction is jurisdiction-specific and depends on substance rather than label. A commercially negotiated sum is not automatically enforceable merely because it is called liquidated damages.

The employer must still establish that the contractual trigger occurred. If the employer caused critical delay and failed to grant an available EOT, imposing damages may be invalid or expose the employer to a claim. Damages should be calculated only for the period after the properly adjusted completion date and before valid completion.

For a simple daily-rate clause:

where LD is liquidated damages, r is the contractual rate per day, and N is the number of chargeable days. The formula assumes the clause uses a constant daily rate and that the chargeable period has been correctly established. If an EOT changes the completion date, N must be recalculated.

Worked Example: Adjusted Completion and Damages

Suppose the original completion date is 30 September. The contractor proves an employer-risk delay of 18 days, and the contract grants an EOT. The adjusted completion date becomes 18 October, assuming the contract counts the dates in this manner. Practical completion occurs on 25 October. If liquidated damages are £4,000 per day, the chargeable period is seven days, not twenty-five days from 30 September:

LD = £4,000 × 7 = £28,000

This calculation assumes there is no further EOT, no sectional-completion adjustment and no contractual issue concerning inclusive or exclusive counting of dates.

10. Time at Large

Time at large is a principle arising in some common-law systems. In broad terms, where the contract requires the employer to grant an EOT for an employer-caused delay but the mechanism cannot operate because the employer failed to administer it properly, the original completion date may cease to be enforceable. The contractor then must complete within a reasonable time rather than by the original date, and liquidated damages tied to that date may become unavailable.

The principle is not an automatic remedy for every administrative failure. The contract may contain wording that preserves the completion date, grants an alternative EOT mechanism or permits the employer to assess time retrospectively. The contractor must also prove employer-caused delay and cannot deliberately rely on its own default.

A sound analysis asks:

1. Does the contract contain an operative EOT mechanism?
2. Is the employer-risk event within its scope?
3. Did the event actually delay completion?
4. Was the administrator required to assess an EOT?
5. Was the mechanism rendered inoperative or merely imperfectly administered?
6. Does the contract or governing law provide an alternative remedy?

The commercial lesson is clear: employers should administer EOT provisions promptly and consistently, while contractors should give notices, maintain updated programmes and reserve rights rather than simply asserting that time is at large.

11. Applied Case: Riverside Medical Centre

The following is an illustrative fictional case designed for educational purposes.

Background

A contractor agreed to construct a medical centre with a contractual completion date of 30 June. The contract required completion within 420 calendar days of possession of the site. The employer was responsible for issuing coordinated design information. Liquidated damages were set at £12,000 per day. The contractor submitted a baseline programme showing that the operating-theatre mechanical systems, testing and certification formed part of the critical path.

Problem

The employer issued revised mechanical design information 35 days late. During the same period, the contractor experienced a 20-day delay in procuring specialist switchgear because it placed the order later than its procurement schedule required. The contractor claimed a 35-day EOT and £420,000 in prolongation costs. The employer argued that the contractor’s procurement delay was concurrent and that no EOT was due.

Analysis

The delay analyst first verified the baseline logic and examined monthly updates, design transmittals, procurement records, inspection reports and site diaries. The revised design could not be installed until issued, and the affected mechanical systems were on the critical path for testing. The employer event therefore had a potential 35-day critical effect.

The switchgear delay began 10 days after the design information delay and affected an activity that also fed into testing. The evidence showed that, even without the employer delay, the contractor’s late order would have delayed testing by 20 days. However, the two effects overlapped for 20 days. The contract contained an express clause stating that concurrent employer and contractor delay entitled the contractor to time but not delay costs for the concurrent period.

The analyst concluded that:

• the employer event caused 35 days of critical delay;
• 20 days were concurrent with contractor delay;
• 15 days were employer-only critical delay; and
• the contractor was entitled to a 35-day EOT, but cost recovery was limited to the 15 non-concurrent days under the contract.

If the proven daily prolongation cost was £8,000, the potentially recoverable delay cost would be:

15 × £8,000 = £120,000

The liquidated-damages date moved from 30 June to 4 August, subject to the contract’s date-counting rules. The contractor achieved practical completion on 10 August, creating six chargeable days. Liquidated damages would therefore be:

6 × £12,000 = £72,000

Outcome

The employer granted the EOT, paid the substantiated £120,000 delay cost and applied £72,000 liquidated damages for the remaining six days. The parties avoided a larger dispute because the baseline and updates were logically consistent and the records separated employer delay from contractor procurement failure.

Learning Points

1. A delay event must be connected to the completion path.
2. Concurrent delay requires more than coincident dates.
3. Contract wording controls the financial consequence of concurrency.
4. EOT and compensation are separate questions.
5. Reliable records can convert a complex dispute into a transparent calculation.

12. Professional Practice, Governance and Technology

Time administration is a governance function. The contract administrator should maintain a decision register, record assumptions, identify unresolved notices and issue reasoned determinations. Equality of treatment is important: an employer should not apply strict notice requirements to the contractor while ignoring its own obligations to provide information or assess time.

Digital planning tools, common data environments, digital twins and building information modelling can improve visibility of interfaces and progress. Artificial intelligence may assist with extracting dates from correspondence, identifying inconsistent updates or forecasting schedule risk. It should not replace professional judgment. AI-generated findings require validation against the contract, actual site conditions, data provenance and human records. Sensitive project information must also be governed under confidentiality, cybersecurity and data-protection requirements.

Best practice includes:

• agree the programme structure and coding system at the outset;
• define calendars, relationships, constraints and milestones;
• update progress regularly using actual evidence;
• preserve original baselines and audit changes;
• issue notices promptly and identify contractual grounds;
• analyse delay in relevant time windows;
• separate time entitlement from compensation;
• document mitigation and acceleration decisions;
• certify practical completion against objective criteria; and
• obtain specialist legal advice where time-at-large, penalties or termination may arise.

Challenges and Limitations

Delay analysis is not mechanically objective. Different experts may reach different conclusions because of incomplete records, retrospective logic changes, unreliable progress data, multiple critical paths or uncertainty about causation. Float ownership may be unclear. A baseline may be accepted for management purposes without being accepted as proof of contractual method. Resource-driven delay may not be represented accurately by a purely logic-based network.

The analyst should state assumptions, test alternative scenarios and distinguish facts from opinion. A defensible report explains why a method was selected, identifies limitations, shows the effect of competing causes and avoids claiming greater precision than the evidence permits.

Chapter Summary

Construction time obligations arise from commencement provisions, completion periods, milestones, access requirements and procedures for notices and extensions. Delay must be distinguished from disruption, and a delay event becomes legally significant only when it affects a relevant contractual date or milestone under the governing contract.

Critical-path analysis connects schedule evidence to causation. Baselines, updates, actual dates, logic, records and correspondence must be examined together. Extensions of time protect the contractor from damages for qualifying delay but do not automatically provide compensation. Concurrency requires analysis of overlapping independent causes and is governed by contract and applicable law.

Acceleration and suspension create distinct obligations and financial risks. Practical completion is a functional contractual threshold, while final completion concerns defects and close-out. Liquidated damages are calculated only after the properly adjusted completion date; penalties may be unenforceable depending on their substance and jurisdiction. Where an employer-caused delay cannot be addressed through the contractual EOT mechanism, time-at-large may arise in some legal systems. Sound time administration therefore combines contractual interpretation, programme analysis, contemporaneous evidence and fair governance.

Key Terms

Acceleration: Measures intended to achieve completion earlier or overcome delay.

Baseline programme: The accepted planned schedule against which progress may be assessed.

Completion date: The date by which contractual completion is required, subject to valid adjustment.

Concurrent delay: Overlapping delay causes, commonly involving employer and contractor risk.

Critical path: The sequence of activities controlling the earliest completion under a schedule model.

Delay: Failure to achieve an activity, milestone or completion requirement by the required time.

Disruption: Interference with planned working methods or productivity.

Extension of time: Contractual adjustment of a completion or milestone date.

Float: Time available before delay to an activity affects a relevant successor or completion date.

Liquidated damages: A pre-agreed sum payable for specified breach, commonly late completion.

Milestone: A significant contractual, payment, interface or management event.

Practical completion: A stage at which works are sufficiently complete for intended use, subject to the contract and applicable law.

Programme update: A revised schedule incorporating actual progress and current forecasts.

Sectional completion: Completion of a defined part of the works under a separate date or regime.

Suspension: A required stoppage or substantial reduction of work.

Time at large: A possible consequence where an employer-caused delay cannot be dealt with through the contractual time mechanism.

Time impact analysis: A method of assessing the effect of a delay event by inserting it into a relevant programme update.

Variation: A change to the contracted work that may affect time, cost or both.

Review Questions

Short Answer Questions

1. What is the difference between delay and disruption?
2. Why is an accepted baseline programme important in delay analysis?
3. Define practical completion.
4. What is the usual purpose of liquidated damages?
5. What does “time at large” mean in broad terms?

Long Answer Questions

1. Explain how a contractor should substantiate an extension-of-time claim from notice through final assessment.
2. Discuss the role and limitations of critical-path analysis in construction disputes.
3. Compare express, voluntary and constructive acceleration.
4. Explain the legal and practical differences between practical completion, final completion and sectional completion.
5. Discuss why liquidated damages may fail where the employer causes critical delay.

Analytical / Application Questions

1. A contractor’s non-critical activity has 12 days of float and is delayed by 15 days. Explain what further evidence is needed before deciding whether the contractual completion date is delayed.
2. An employer delay overlaps a contractor procurement delay for 18 days, but the contract is silent on concurrency. Identify the issues that should be analysed before determining time and cost entitlement.
3. The employer refuses to assess an EOT for a 30-day design delay and later claims liquidated damages against the original completion date. Prepare a reasoned analysis of the contractor’s possible time-at-large argument and the evidence required.

Multiple Choice Questions with Answers

Question 1

Which statement best describes the critical path?

A. The sequence of activities with the highest labour cost

B. The sequence that controls the earliest possible project completion

C. All activities shown in the accepted baseline programme

D. The activities performed only by subcontractors

Correct Answer: B. The sequence that controls the earliest possible project completion

Question 2

In the simplified schedule A–B–C–E–F, the durations are 5, 15, 20, 10 and 5 days. What is the route duration?

A. 45 days

B. 50 days

C. 55 days

D. 60 days

Correct Answer: C. 55 days

Question 3

What is the primary function of an extension of time?

A. To reward early procurement

B. To change the contractual completion date for a qualifying delay

C. To eliminate all contractor costs

D. To convert every delay into disruption

Correct Answer: B. To change the contractual completion date for a qualifying delay

Question 4

Which item is most directly relevant to proving actual delay causation?

A. The contractor’s logo

B. A contemporaneous programme update with actual progress data

C. The original tender advertisement only

D. A general industry productivity table without project records

Correct Answer: B. A contemporaneous programme update with actual progress data

Question 5

A four-day delay affects an activity with eight days of available float and no other changes occur. What is the most likely schedule effect?

A. Completion automatically moves by four days

B. Completion automatically moves by eight days

C. The float is reduced, but completion need not move

D. The contract is automatically terminated

Correct Answer: C. The float is reduced, but completion need not move

Question 6

Which statement about concurrency is most accurate?

A. Any two events occurring in the same month are concurrent critical delays

B. Concurrency requires analysis of overlapping causes and their effect on completion

C. Concurrency always gives the contractor full time and cost recovery

D. Concurrency can exist only when both events are employer risks

Correct Answer: B. Concurrency requires analysis of overlapping causes and their effect on completion

Question 7

If the liquidated-damages rate is £4,000 per day and seven days are chargeable, what is the amount?

A. £11,000

B. £28,000

C. £40,000

D. £56,000

Correct Answer: B. £28,000

Question 8

Which situation most closely describes acceleration?

A. Reducing the contract price after completion

B. Adding resources or changing methods to achieve an earlier completion

C. Recording a defect after handover

D. Issuing a final account without schedule evidence

Correct Answer: B. Adding resources or changing methods to achieve an earlier completion

Question 9

Which is generally associated with practical completion?

A. The works must have no minor defects whatsoever

B. The works are sufficiently complete for intended use, subject to the contract

C. All future maintenance obligations end immediately

D. All design responsibility automatically transfers to the contractor

Correct Answer: B. The works are sufficiently complete for intended use, subject to the contract

Question 10

Time at large may arise, in some common-law systems, when:

A. The contractor finishes early

B. An employer-caused delay cannot be dealt with through the contractual extension mechanism

C. A subcontractor submits a payment application

D. The project has more than one critical path

Correct Answer: B. An employer-caused delay cannot be dealt with through the contractual extension mechanism