Learning purpose

Causation connects an established breach or contractual event with the delay, disruption, physical damage or financial loss for which relief is claimed. The existence of a breach does not prove that every adverse project consequence which followed it was caused by that breach. A sound claim must identify the relevant event, trace what it changed within the works, establish the resulting consequence and connect that consequence to the particular loss advanced.

Successful completion requires the learner to distinguish breach from consequence; explain why chronological sequence alone does not establish causation; identify an effective cause rather than a mere occasion for loss; prepare an event, cause, effect and loss chain; test every link against contemporary project records; distinguish evidence of occurrence from evidence of consequence; recognise when a programme assists but does not complete the analysis; and state a causal conclusion at the level which the available facts can support.

1. Causation as a separate condition of contractual liability

A claimant seeking damages must prove more than the existence of a contractual obligation and its breach. The claimant must establish a sufficient causal connection between the breach and the loss for which compensation is sought. These questions are separate because a contract may be broken without causing the particular consequence alleged. An employer may provide design information late, yet the affected operation may still finish by its planned date because the contractor had float, resequenced the work or lacked the labour needed to start. A contractor may install defective work, yet the employer's later operating loss may have arisen from an unrelated plant failure. The legal analysis cannot move directly from proved non-performance to the amount claimed.

This separation protects the compensatory character of contractual damages; damages respond to loss caused by breach; they do not impose a general financial sanction whenever performance departs from the contract. The claimant must therefore state the causal proposition with enough precision to be tested; "the drawing was late and the project was delayed" contains two facts but no demonstrated connection. A properly framed proposition identifies the drawing, its contractual due date, the activity which required it, the date upon which that activity could otherwise have proceeded, the particular work prevented or altered, the period of resulting effect and the financial consequence attributed to that effect.

Causation must also remain separate from remoteness, mitigation and valuation because each enquiry performs a different legal function; causation asks whether the breach brought about the claimed consequence in the legally relevant sense. Remoteness asks whether responsibility for that kind of consequence falls within the contractual rule governing recoverable loss. Mitigation examines the reasonable response to an established breach and its consequences, while valuation measures the amount which the claimant has proved. A claim may establish one stage and fail at another, so a report which collapses them into a single assertion prevents the reader from identifying the actual defect.

The relevant starting event need not constitute wrongdoing because many construction contracts allocate time or money consequences to valid instructions and specified risk events. A variation may alter the scope without any breach, while an unforeseen condition may activate contractual relief according to the agreed risk allocation. In each instance, the claimant must identify the event, the affected work, the factual consequence and the contractual relief engaged. Describing every event as a breach may direct the analysis towards damages when the agreement instead supplies a valuation mechanism, an extension procedure or another defined contractual response.

The Court of Appeal examined the causal requirement in Galoo Ltd v Bright Grahame Murray [1993] EWCA Civ 3, [1994] 1 WLR 1360. Galoo and Gamine alleged that negligent audits had allowed them to continue trading and incur later trading losses. Glidewell LJ held at pages 1374 to 1375 that the alleged audit failures gave the companies the opportunity to incur those losses but did not cause the trading losses in the legal sense advanced. The historical sequence satisfied a simple counterfactual proposition, yet it did not demonstrate what had produced the particular losses during the later trading activity.

Construction claims commonly display the same incomplete reasoning when an event precedes a later delay or cost. Late design information may exist during a period of inefficient work, but the inefficiency may result from labour levels, plant availability, access congestion or defective planning. A delayed payment may precede reduced procurement, while the evidential record fails to connect the missing payment with any identified order or financing decision. The causal enquiry must determine what the event changed within the performance of the works rather than merely placing the event before the claimed consequence on a chronology.

A realistic counterfactual assists this enquiry by asking what would probably have occurred if the relied-on event had not happened. That comparison cannot assume perfect performance where contemporary records show that labour, plant, materials or preceding work were unavailable. Nor should it treat every baseline date as an inevitable fact when the planned logic remains untested. The proper comparison preserves all project conditions which would still have existed and removes only the event under examination. Lesson 9 examines the formal "but for" question and multiple causes in greater detail, but the present lesson requires this disciplined factual comparison at every stage.

Different consequences arising from the same event require separate causal chains because their mechanisms and evidence may differ. Late information might delay fabrication, alter the installation sequence, require temporary protection and extend supervision. Proof that fabrication moved does not establish the later cost consequences without further evidence. A claims schedule should therefore divide time, method and financial consequences into distinct rows, allowing the decision-maker to accept one causal chain while rejecting or reserving another. This structure prevents a supported event from becoming an assumed explanation for every adverse result recorded during the project.

2. Effective cause, dominant cause and mere occasion

The expressions "effective cause" and "dominant cause" distinguish events which produced the claimed loss from circumstances which merely created an opportunity for loss to occur. Neither expression supplies an automatic formula, and both require examination of the facts, the obligation and the relationship between event and consequence. An event may remain causally operative even though later steps occur before the loss, while an event may be necessary to the history without attracting legal responsibility for everything which follows. The classification should therefore record the result of the analysis rather than substitute for an explanation of the causal mechanism.

That distinction between cause and occasion provides a useful early test for construction claims. An event is a possible effective cause where it changes the performance of an identified operation in a manner which produces the claimed consequence. By contrast, an event is merely an occasion where it places the claimant in circumstances in which another act, omission or condition produces the loss. A proper conclusion explains the physical, operational or financial mechanism through which the event acted upon the project before applying either label. Without that explanation, the chosen label adds emphasis but supplies no verifiable reasoning.

The construction decision considered within Galoo illustrates this distinction; in Quinn v Burch Bros (Builders) Ltd [1966] 2 QB 370, the main contractor failed to supply a requested step-ladder to an independent subcontractor; the subcontractor used a folded trestle against a wall, fell and suffered injury. As recorded by Glidewell LJ at page 1371 of Galoo, the Court of Appeal held that failure to provide the ladder was a contractual breach, but the subcontractor's choice of unsuitable equipment caused the accident. The breach supplied the occasion upon which the unsafe choice occurred rather than the legal cause of the injury.

That reasoning does not establish that a claimant's later conduct invariably breaks the causal connection. The result depends upon the nature of the obligation, the risk against which it operates and the character of the response. Reasonable resequencing after late access may transmit or reduce the effect of the original breach, while an independent and unreasonable decision may create a separate consequence. The analyst should identify the information available when the response occurred, the contractual choices open to the claimant, the purpose of the action and the extent to which the resulting cost remained attributable to the initial event.

At pages 1372 to 1375 of Galoo, the Court examined whether inaccurate audit certificates caused the later trading losses of companies which otherwise would have ceased business. Continued existence placed the companies in a position where trading results could occur, but those results depended upon the matters which happened during trading. The pleaded case did not examine the particular operations, decisions or market conditions which produced the losses. Glidewell LJ consequently rejected the argument that permission to continue trading, without a proved relationship to the particular losses, satisfied the causal requirement.

The construction equivalent arises when a claimant relies upon the continued existence of a project condition without proving what produced the cost. A delayed design decision may keep a workface open for longer, but site management could have remained for unaffected operations and labour could have undertaken productive work elsewhere. The claimant must identify which resources were changed, when that change occurred, which productive alternative was available and why the claimed expenditure would otherwise have been avoided. Proof of longer presence on site does not establish that every cost incurred during that presence resulted from the relied-on event.

The expression "dominant cause" requires particular care because the contract may not demand selection of one prevailing event. Some provisions use language which makes dominance relevant, whereas others allocate relief when an event causes delay without requiring the claimant to defeat every other explanation. Multiple causes may also contribute to the same consequence, which is examined in Lesson 9. A search for one dominant cause can distort a record which supports two operative events, so the analyst should first determine the actual mechanisms and then apply the language required by the contract and governing law.

An effective cause need not be closest to the loss in time. A design error made months before fabrication may remain operative when the steel fails to fit, notwithstanding the later stages of manufacture, delivery and erection. Those stages may transmit the effect rather than displace it; conversely, a disproportionate redesign adopted after discovery of a minor discrepancy may create additional cost through a later independent decision. The assessment must trace whether the original event continued to operate and whether the later response was a reasonable consequence within the contractual and factual setting.

Examining the purpose of the obligation assists selection of the legally relevant cause. A duty to issue construction information by a stated date protects performance which depends upon timely information, while a coordination duty addresses clashes and resulting rework; a payment obligation protects receipt of the sum when due, although a claim for wider financing or procurement consequences requires proof of the mechanism by which non-payment caused them. Examining the obligation prevents the claimant from attaching consequences which merely followed the breach but arose outside the risk which the relevant promise addressed.

A reasoned finding should therefore state more than the chosen causal label. It may find that late connection details were an effective cause of delayed fabrication because dimensions were indispensable, preceding checks were complete and the fabricator had reserved capacity. A contrary finding may conclude that lateness merely coincided with delay because the contractor's model remained incomplete and fabrication could not otherwise have begun. Each conclusion identifies readiness, dependency and the operative mechanism, allowing the parties to test the finding against records rather than debating an unexplained assertion of dominance.

Concurrent and competing causes

Concurrent causation arises only after the evidence establishes that two or more events were each effective causes of the same period of delay or the same loss. Simultaneous events are not necessarily concurrent causes because one event may have produced no delay to completion, while events occurring on different dates may produce overlapping delaying effects. In Walter Lilly & Company Ltd v Mackay [2012] EWHC 1773 (TCC), Akenhead J explained at paragraphs 366 to 370 that the enquiry concerns a period caused by two effective causes, one being a contractual Relevant Event and the other not. That judgment approved a working description based upon effective causes of approximately equal causative potency, but the description cannot displace proof of actual effect. An analyst must identify the critical work, the period during which each event operated, and whether removing either event would have left the same work delayed for the same period.

The English extension-of-time approach considered in Walter Lilly followed the common ground recorded in Henry Boot Construction (UK) Ltd v Malmaison Hotel (Manchester) Ltd (1999) 70 Con LR 32. Under an extension provision of the kind examined, a contractor receives the full extension for delay caused by a Relevant Event even where another effective cause operates concurrently and rests with the contractor. Akenhead J adopted that approach at paragraph 370, subject to the wording of the contract under examination. This rule concerns entitlement to time under the particular extension mechanism; it does not establish automatic recovery of prolongation cost, disruption loss or damages. Those monetary claims require their own causal proof, contractual entitlement and valuation, and a contractor-risk cause may prevent attribution of the whole financial consequence to the employer-risk event.

The distinction between time and money should govern the claims schedule whenever concurrent events appear. A Relevant Event may protect the contractor against liquidated damages by supporting an extension, while the contractor may still fail to prove that the employer-risk event caused the expenditure claimed for the same period. At paragraph 486 of Walter Lilly, Akenhead J stated that global presentation does not remove the claimant's burden to prove that the relied-on events caused or materially contributed to the loss. If a contractor-risk event made a material contribution, the court must examine whether the evidence permits the loss attributable to that event to be separated. The practical response is to divide time entitlement, prolongation cost and disruption cost into separate causal chains rather than importing the time result into every financial head.

Scottish authority has permitted a different response where competing causes cannot be separated through a dominant cause. In John Doyle Construction Ltd v Laing Management (Scotland) Ltd [2004] ScotCS 141, the Inner House considered a global loss-and-expense claim and explained at paragraphs 4 and 10 to 16 that the claimant still had to prove causal responsibility. The court accepted that, in a proper case, evidence might permit attribution to a dominant cause or apportionment between concurrent causes. That decision arose under Scots law and concerned whether the pleaded claim should proceed to proof; it does not establish an English rule allowing a decision-maker to divide contractual loss whenever exact causal proof proves difficult.

The Scottish Inner House applied an apportionment approach to delay in City Inn Ltd v Shepherd Construction Ltd [2010] CSIH 68. Lord Osborne stated at paragraph 42 that, where a Relevant Event and a contractor-responsibility event were both operative and neither was dominant, the decision-maker could apportion delay on a fair and reasonable basis. That treatment belongs to Scottish law and has not been followed as a general rule of English law. Walter Lilly expressly contrasted the English and Scottish approaches at paragraphs 366 to 370 and adopted a full extension under the clause before the English court. English practitioners should therefore use City Inn to understand the jurisdictional difference, not as authority for an English power to apportion delay without contractual language conferring that power.

The contract may alter the result that would otherwise follow under a standard extension provision. In North Midland Building Ltd v Cyden Homes Ltd [2018] EWCA Civ 1744, the parties amended clause 2.25.1.3(b) so that delay caused by a Relevant Event would not be taken into account where it was concurrent with delay for which the contractor was responsible. Coulson LJ held at paragraphs 36 and 47 that the parties were entitled to make that express allocation, and the Court of Appeal enforced it. The decision does not prescribe a general rule that contractor delay defeats an extension whenever concurrency exists. Its force lies in freedom of contract: the court gave effect to clear wording which deliberately placed that concurrent-delay risk upon the contractor.

The authorities require a disciplined order of analysis before any legal consequence can safely be stated. An analyst first proves each effective cause and the period of its operation, then identifies the governing law and construes the actual extension, compensation and damages provisions. Labelling two contemporaneous difficulties as concurrent does not prove that either caused critical delay. Applying City Inn to an English contract would ignore the jurisdictional division, while applying North Midland without equivalent wording would convert a decision about an express bargain into a default rule. The conclusion must preserve the contractual language, the jurisdiction and the separate evidential treatment of time and money.

3. Building the event, cause, effect and loss chain

A practical construction claims method divides each allegation into four linked stages: the contractual event, the immediate causal mechanism, the project effect and the claimed loss. The event identifies what happened and its contractual status; the mechanism explains what operation, decision or resource was changed; the effect records the resulting delay, disruption, rework or physical consequence, while the loss identifies the time or money relief attributed to that effect. This structure does not replace the legal test, but it exposes missing connections before a claim or assessment is finalised.

Exact identification governs the event stage because an imprecise starting point contaminates every later conclusion. The analyst records the instruction, late information, access restriction, defective work, payment failure or allocated risk event together with dates and the governing provision. A valid instruction should not be misdescribed as breach merely because it carries a financial consequence. The date of occurrence should also remain distinct from the date of first effect. Information issued twenty days late may cause only five days of delay where the receiving activity did not require it until the final part of that period.

The causal mechanism describes how the event acted upon planned or actual performance. Late structural details may prevent fabrication because connection dimensions cannot be finalised, while restricted access may prevent a crane from reaching its lifting position. Defective waterproofing may require completed finishes to be removed, and non-payment may prevent an identified order where the financial evidence proves that connection. General expressions such as "impacted progress" or "caused disruption" fail to identify any mechanism which a programme, witness, technical record or cost ledger can properly test.

Project effect must be classified at the correct level because an activity consequence does not automatically become a completion consequence. An operation may start late yet recover through float, additional resources or lawful resequencing. Disruption may reduce productivity without extending duration, and rework may consume resources while remaining outside the critical sequence. The assessment should identify whether the effect concerns activity start, duration, sequence, resource efficiency, a contractual milestone or overall completion. That classification determines the appropriate evidence and prevents the duration of the event from being adopted as the duration of project delay.

The loss must correspond to the effect which has actually been proved. If an event delays one package for ten days without extending overall site duration, ten days of total project preliminaries do not follow automatically. The appropriate claim may concern identifiable idle resources, local supervision or resequencing cost, subject to proof. Where overall completion is extended, time-related cost may arise, but the claimant must still identify resources and expenditure associated with the extended period. A percentage applied to event value cannot replace causal evidence connecting each claimed cost with the established consequence.

Every transition within the chain requires records suited to the proposition being advanced. Contract documents and communications may prove occurrence, while design registers, information schedules and technical evidence may prove why work could not proceed. Programmes, daily reports, photographs, labour returns and plant records may establish project effect. Cost ledgers, invoices, payroll and resource allocation records may establish loss; witness evidence can explain how those materials fit together, but recollection should not supply specific facts which reliable contemporary records contradict or leave unrecorded.

A programme remains evidence rather than a self-proving causal conclusion; the baseline may record intended logic and timing, while updates show when activities moved. Neither document establishes automatically why movement occurred because links may be inaccurate, overly broad or reconstructed after the dispute. Programme relationships should be tested against method statements, drawings, procurement requirements and actual working practice. If steel erection is linked to connection details, the technical record should establish which details were necessary, which zones depended upon them and whether the relevant work was otherwise ready.

The granularity of the records must match the granularity of the claim. Daily labour inefficiency cannot safely be proved through monthly progress reports which record no crew-level deployment. A three-week steelwork allegation should examine workfaces, planned crews, actual labour, plant, preceding work and information status for the days in question. Evidence from a different area or later period cannot be transferred without proving comparable conditions. The causal schedule should cite the exact document, date and relevant entry supporting each factual transition.

Alternative explanations require testing rather than omission; where design information and labour shortages occur during the same period, the claimant should identify which activities each matter affected and on which dates. The respondent cannot defeat a supported causal chain merely by naming another possible event, because the alternative also requires an evidential connection to the consequence. A schedule which sets both explanations beside the actual records provides a stronger basis for decision than a narrative which removes inconvenient project conditions from the analysis.

Gaps should remain visible where the evidence cannot establish a transition; records may prove that late information prevented work in Zones A and B while supplying no basis for Zones C and D. Cost data may combine productive and unproductive hours, and a revised programme may show movement without reliable logic. Those limitations require further disclosure, narrower valuation or an unresolved finding; recording "not established" at the unsupported link is more reliable than completing the chain through assumptions which cannot withstand examination.

4. Evaluating causal evidence and stating a defensible conclusion

Causal analysis requires evaluative judgment applied to evidence rather than a diagram which produces an answer without legal or factual assessment. Construction projects contain interdependent activities, incomplete records and changing intentions; the decision-maker must determine what probably happened and why, while respecting the contractual allocation of risk. A detailed model may assist this task, but complexity cannot repair unsupported inputs. The strength of the result depends upon the accuracy of the propositions used, the transparency of the assumptions and the analyst's treatment of contrary material.

Contemporary records ordinarily carry weight because they were created before the dispute fixed the parties' positions, although their value depends upon purpose, authorship, timing and consistency. A daily report prepared to count labour may establish attendance but say little about design readiness; a programme update prepared for progress monitoring may record status dates without verified causal logic, while meeting minutes may preserve an allegation rather than agreement. The analyst should state what each document proves and should not convert every contemporary entry into an accepted fact merely because it was recorded at the time.

Witness evidence may explain working methods, decisions and documents which otherwise remain difficult to interpret. Its weight increases when the witness identifies personal involvement, distinguishes memory from reconstruction and engages with contrary records. A statement which repeats the claim schedule without explaining the underlying operation contributes little to causal proof. Interviews should follow the chronology and ask what work was intended, what prevented it, what response followed and which contemporary material confirms that account. Any conflict between recollection and records should be addressed directly rather than removed from the final statement.

Expert evidence assists where technical, delay or quantum knowledge is required, but the expert must work from proved or expressly assumed facts. A delay expert cannot determine whether an instruction was contractually late until the relevant obligation and due date have been established; a quantum expert cannot convert a gross cost ledger into loss caused by one event without a supported allocation. The report should state its contractual assumptions, factual assumptions, method, data limits and sensitivity to disputed inputs, allowing the decision-maker to revise the result when an assumption is rejected.

Chronology identifies the question but does not answer the causal enquiry; the sequence "event, later delay, later cost" requires tests of readiness, dependency and change. Readiness asks whether the affected work could otherwise have proceeded; dependency asks whether that work actually required the delayed input, access or decision. Change asks what performance occurred differently because of the event; failure at any stage may narrow or defeat the asserted connection, while proof at every stage supplies a reasoned path from the contractual occurrence to the project consequence.

Each contractual head of relief should receive its own causal assessment because one finding may not control every remedy. An event may support an extension of time under particular wording without establishing general damages. A variation may attract valuation despite the absence of breach, while a compensable event may permit defined Cost subject to contractual conditions. The analyst should use causal language matching the entitlement route and avoid treating a conclusion reached for time as automatic proof of disruption, financial loss or every contractual condition attached to payment.

Activity delay must remain distinct from completion delay throughout the report; an activity may recover through float or resequencing, while a short event affecting critical work may move completion by more than its own duration if it creates further necessary operations. The conclusion should identify the affected milestone, the relevant logic and the period of proved consequence. Comparing event duration with the eventual completion date without analysing the intervening sequence measures temporal association rather than causation and produces an unsafe basis for financial assessment.

The working file should distinguish established facts, reasonable inferences and unresolved matters. An issue date appearing in a reliable register may constitute an established fact, while an inference that a crew stood down may arise from consistent daily reports, plant returns and correspondence. A conflict between the programme and site diary may remain unresolved pending witness or technical evidence. These internal classifications prevent an inference from being repeated later as an established fact and allow the final opinion to identify the precise evidential basis for each conclusion.

Adverse-case testing requires the analyst to assume that a disputed witness recollection, programme link or cost allocation will be rejected and then determine what remains of the chain. The exercise may reveal that occurrence is established but effect is not, or that activity delay is proved while completion and cost remain open; the claim can then be narrowed, supported through further disclosure or presented with an express alternative. This method prevents one weak assumption from carrying an otherwise substantial claim and exposes the evidence which should receive priority.

A defensible conclusion states both its answer and its boundary; it may find that late connection details were an effective cause of delayed fabrication in two zones during an identified period, while labour and crane constraints prevent attribution elsewhere. The same conclusion may reserve overall completion effect because available float and later sequence require examination. This measured form assists commercial and legal decision-making because it identifies what can presently be advanced, which matters remain open and what evidence is required before the conclusion can safely be enlarged.

5. Case focus: Galoo Ltd v Bright Grahame Murray

Galoo Ltd v Bright Grahame Murray [1993] EWCA Civ 3, [1994] 1 WLR 1360 arose from claims against auditors by Galoo Ltd, Gamine Ltd and Hillsdown Holdings plc. Galoo and Gamine alleged that negligent audits failed to reveal their true financial position and allowed them to continue trading. Their pleaded causal sequence asserted that competent audits would have disclosed insolvency, disclosure would have produced liquidation, and liquidation would have prevented the later trading losses. Accordingly, the Court of Appeal had to decide whether the pleaded counterfactual established the legal connection between the alleged audit failures and the particular losses. What mattered was whether those failures effectively caused the trading results, rather than whether the audits formed part of the historical sequence.

Glidewell LJ began with the distinction between a necessary condition and a legally effective cause. At pages 1369 to 1375, he examined whether the alleged breach had produced the loss or had merely enabled later events to occur. The fact that proper audits might have stopped the companies trading answered a simple historical counterfactual, but it did not identify what caused losses during the continued trading period. Those losses could have arisen from trading decisions, market conditions or operational events which the pleaded case had not connected to the auditors. Accordingly, the judgment refuses the assumption that every consequence which disappears from a hypothetical history must have been caused, in the legally relevant sense, by the event removed from that history.

Page 1371 supplies a construction example through the discussion of Quinn v Burch Bros (Builders) Ltd [1966] 2 QB 370. Burch Bros had breached its contractual duty by failing to provide a requested step-ladder. An independent subcontractor instead used a folded trestle against a wall and suffered injury when he fell. In that setting, the Court of Appeal treated the breach as the occasion for the accident, while the use of unsuitable equipment was the effective cause of injury. That reasoning does not create an automatic rule that later conduct displaces an earlier breach. It requires examination of the precise obligation, the risk addressed by that obligation and the mechanism by which the eventual harm occurred.

At pages 1374 to 1375, Glidewell LJ concluded that the alleged audit failures gave Galoo and Gamine the opportunity to incur later trading losses but did not cause those losses in the legal sense pleaded. Accordingly, the Court dismissed the companies' appeals concerning that pleaded trading-loss claim. Hillsdown's position involved separate allegations about reliance and acquisition expenditure, and parts of its case were permitted to continue. The judgment must therefore be used for its actual causal reasoning rather than as a proposition that audit negligence can never cause trading or investment loss. Different pleadings and evidence could establish a direct mechanism which the Galoo and Gamine allegations lacked.

The construction application is exacting because late information, restricted access or defective work often appears before a period of delay and increased cost. Claims patterned upon the failed Galoo reasoning state that the project would have proceeded differently if the event had not occurred, yet omit the operations which produced the actual consequence. A complete causal case identifies which work was otherwise ready, why that work required the missing information or access, how resources changed, how long the effect persisted and which cost followed. Labour shortage, plant failure or available float may show that the breach supplied only an occasion during which a different cause determined progress.

The reasoning also requires separate causal chains for distinct losses and contractual consequences. Proof that late information delayed fabrication does not prove an extension of completion, and proof of completion delay does not establish every item of site cost or labour inefficiency. Each transition requires its own evidence and an account of competing explanations. Galoo supplies no mathematical causation formula and does not remove contractual questions about time, compensation or risk allocation. Its instruction is narrower: the claimant must prove that the relied-on event was an effective cause of the particular consequence, rather than a historical condition which merely allowed that consequence to occur.

6. Construction claims method

For each alleged event, prepare a separate causal schedule which records the contractual provision, event date, affected operation, realistic counterfactual, immediate mechanism, measured effect, competing explanation, contractual relief, claimed loss, supporting records, unresolved assumptions and provisional conclusion. Distinct consequences require separate rows even where they originate from the same event. This arrangement prevents proof of one consequence from being treated as proof of every other cost or time effect attached to the claim.

7. Construction workshop: late connection details, labour and plant constraints

Project record

L8-R01 records that the fictional contract requires Alder Quay Developments Ltd to issue approved structural steel connection details in accordance with an information schedule. The schedule gives 4 February 2026 as the required issue date for Zones A to D; the contract provides a potential time and money route for late employer information, subject to proof of effect and compliance with its notice provisions.

L8-R02 records that approved connection details were transmitted to Northbridge Steel Ltd on 25 February 2026, twenty-one days after the scheduled date. The transmission record establishes occurrence and lateness, but does not establish which fabrication or erection operations were otherwise ready during that period.

L8-R03 records that the accepted baseline planned steel installation between 10 February and 7 March 2026, using twenty operatives and two cranes. Separate activities appear for Zones A to D, although the supplied logic report does not establish that every zone depended upon final connection details on 4 February.

L8-R04 records an average of twelve steel operatives between 10 and 23 February, while the 80-tonne crane was unavailable between 12 and 18 February following a hydraulic fault. A second crane remained available, and the supplied records do not establish which zones or lifts could have proceeded with the available resources.

L8-R05 records a design hold against Zones A and B in the progress update issued on 19 February, while labour constraint is recorded against Zones C and D. Steel installation began on 3 March and finished on 28 March; the facade activity began on 31 March, and the supplied programme records seven days of float between planned steel completion and the facade milestone.

L8-R06 records Northbridge's claim for twenty-six days of time-related site cost valued at £312,000 and steel labour inefficiency valued at £180,000. The report applies the whole period from 10 February to 7 March to late details without division by zone, identification of idle hours or separation of the crane fault and labour shortage.

Learner assignment

Prepare an event, cause, effect and loss schedule for the late connection details, separating Zones A and B from Zones C and D. Identify established facts, reasonable inferences and unresolved matters; draft a provisional conclusion addressing activity delay, completion delay, time-related cost and labour inefficiency without assuming that twenty-one days of lateness caused an equal period of project delay.

Prepare the respondent's strongest evidence-based alternative explanation while accepting the established late issue. Identify the daily fabrication records, zone-level erection records, crane allocation, labour deployment, detailed programme logic, facade records and cost-ledger material required before a final opinion could safely be expressed.

Tutor observations

L8-R01 and L8-R02 establish the contractual event and its twenty-one-day duration, but neither record proves readiness, dependency or resulting delay. L8-R05 supplies a provisional connection between the design hold and Zones A and B, while the same document attributes constraints in Zones C and D to labour. Any claim applying late design information across all four zones therefore requires stronger contrary evidence.

The reduced labour and crane fault in L8-R04 prevent an assumption that baseline performance would otherwise have occurred exactly as planned. Those matters require examination by date, zone and lifting operation, although the current record does not prove that either caused every day of delay. The seven days of float recorded in L8-R05 also prevent direct conversion of activity movement into an equal extension of overall completion.

Neither claimed amount is presently connected to the full causal chain; the £312,000 requires proof of an extended period caused by late details and allocation of affected resources. The £180,000 requires zone-level labour analysis, idle or inefficient hours and separation of other constraints. A defensible provisional conclusion identifies late details as a supported possible effective cause in Zones A and B during part of the period, while reserving wider delay and cost pending further evidence.

8. Common errors

1. treating the duration of the event as the duration of its project effect;
2. relying upon chronological sequence without proving the operative mechanism;
3. using one causal statement for several different heads of loss;
4. assuming that programme dates explain why actual performance moved;
5. omitting readiness, float, resequencing and available resources;
6. removing supported alternative explanations from the assessment;
7. applying project-wide cost to an event affecting limited workfaces;
8. describing an event as dominant without explaining the selection;
9. confusing causation with remoteness, mitigation or valuation; and
10. stating a conclusion more widely than the records permit.

9. Practitioner checklist

Before advancing or assessing a causal allegation, confirm that the event, affected operation, realistic counterfactual, immediate mechanism, measured effect and claimed loss are separately identified. Check readiness, dependency, float, programme logic, resource availability, alternative explanations and cost allocation against contemporary records. Record assumptions and conflicts, then state the conclusion no wider than the evidence permits.

10. Further reading

• Galoo Ltd v Bright Grahame Murray [1993] EWCA Civ 3, [1994] 1 WLR 1360, especially pages 1369 to 1375.
• Quinn v Burch Bros (Builders) Ltd [1966] 2 QB 370, as examined by the Court of Appeal in Galoo at page 1371.
• Walter Lilly & Company Ltd v Mackay [2012] EWHC 1773 (TCC), especially paragraphs 366 to 370 and 486.
• John Doyle Construction Ltd v Laing Management (Scotland) Ltd [2004] ScotCS 141, especially paragraphs 4 and 10 to 16.
• City Inn Ltd v Shepherd Construction Ltd [2010] CSIH 68, especially paragraphs 36, 42 and 49.
• North Midland Building Ltd v Cyden Homes Ltd [2018] EWCA Civ 1744, especially paragraphs 36 and 47.

11. Suggested answers

Answer 1

Causation requires a legally sufficient connection between an established event and the particular consequence claimed. Under the effective-cause analysis in Galoo, chronological sequence and a simple counterfactual do not complete that enquiry. L8-R01 and L8-R02 establish the scheduled and actual issue dates, but they do not establish delayed work or financial loss. The missing evidence comprises fabrication readiness, zone dependencies, actual resource deployment and the date upon which each operation first required approved connection details. Accordingly, any conclusion must remain limited until those missing evidential links are proved.

Answer 2

The contractual event is the issue of approved connection details on 25 February 2026 against the scheduled date of 4 February 2026. L8-R01 identifies the contractual information schedule and L8-R02 records the actual transmission, thereby proving twenty-one days of lateness. Galoo requires a further effective-cause enquiry before any consequence is attributed to that event. The learner must obtain the fabrication release records, technical dependency schedule and daily workface records to establish which operations were otherwise ready and when the late information first prevented them.

Answer 3

Zones A and B require separate analysis because L8-R05 records a design hold against those zones in the 19 February update. That entry supports a possible effective causal mechanism under Galoo, but it does not prove the duration of the hold or every resulting cost. L8-R03 does not establish that both zones required final details throughout the entire late period. Zone-level fabrication status, drawing dependencies, reserved workshop capacity and daily erection records are therefore required before the design hold can be converted into an activity-delay or financial conclusion.

Answer 4

Late design cannot automatically be treated as the cause in Zones C and D because L8-R05 attributes their recorded constraint to labour. The effective-cause test in Galoo requires proof of what actually changed performance, rather than selection of the event which appeared first. L8-R03 supplies planned labour and sequencing, while L8-R04 records reduced operatives and a crane fault. The missing evidence includes daily crew deployment, lift plans, zone readiness and any technical need for the delayed details in those zones before design responsibility can displace the recorded labour explanation.

Answer 5

L8-R04 establishes an average workforce of twelve operatives and an 80-tonne crane fault between 12 and 18 February, while confirming that another crane remained available. Those facts create competing causal explanations, but contemporaneous occurrence alone does not prove concurrent delay. Walter Lilly at paragraphs 366 to 370 requires two effective causes of the same delay before concurrency affects an extension assessment. Daily lift allocations, crane capacities, planned workfaces and actual crew deployment are required to determine whether labour, plant and late design operated upon the same critical work during the same period.

Answer 6

Twenty-one days of information lateness cannot be converted directly into an equal period of activity or completion delay. L8-R01 and L8-R02 measure the event, while L8-R05 records actual steel dates and seven days of float before the facade milestone. Galoo requires proof that the event effectively caused the asserted consequence, and Walter Lilly requires proof of actual delay caused by any Relevant Event. A tested logic model, zone completion records and facade dependency evidence are needed to identify the period of activity effect and whether any part reached contractual completion.

Answer 7

L8-R03 supplies the accepted planned sequence, twenty operatives and two cranes, but the supplied logic does not prove that every zone depended upon final details on 4 February. A programme is evidence of intended performance, not a self-proving causal mechanism. Technical and factual confirmation of dependency and readiness is required by the effective-cause analysis in Galoo. The learner should obtain connection-design release requirements, fabrication status, preceding-work completion, method statements and actual zone records. Without those materials, the baseline cannot establish which planned activity would probably have proceeded absent the late issue.

Answer 8

Overall completion delay remains unresolved because L8-R05 records seven days of float between planned steel completion and the facade milestone, while the supplied logic does not explain the later facade start. Galoo prevents the analyst from inferring completion effect from temporal sequence alone. If employer-risk and contractor-risk events both caused the same critical period, Walter Lilly supplies the English extension approach, subject to the actual contractual wording. Updated critical-path logic, float ownership provisions, facade readiness records and evidence of mitigation are required before any extension or concurrent-delay conclusion can be stated.

Answer 9

The £312,000 claim requires proof that late details extended site duration and caused the identified time-related resources. L8-R06 applies twenty-six days of site cost without connecting each resource to a proved extension, while L8-R05 records float and other constraints. Galoo requires an effective causal link to the particular loss, and paragraph 486 of Walter Lilly preserves that burden for a globally presented claim. The claimant must provide resource schedules, cost-ledger entries, actual site-presence dates and an allocation separating employer-risk effects from labour, crane and unaffected-work expenditure.

Answer 10

An aggregate figure of £180,000 in L8-R06 does not prove the labour inefficiency claim. Galoo requires identification of the mechanism which produced the particular loss, while paragraph 486 of Walter Lilly requires proof that the relied-on events caused or materially contributed to a global loss. L8-R04 and L8-R05 record labour and crane constraints which may have contributed independently. The claimant must provide crew-level timesheets, planned and earned hours, zone allocation, idle-time records, contemporaneous explanations and a method separating late-design effects from workforce and plant shortfalls.

Answer 11

A respondent should accept the established late issue proved by L8-R01 and L8-R02, while requiring proof of every wider causal link. That position follows Galoo because admitting breach or a contractual event does not admit the particular delay and loss. L8-R04 and L8-R05 support competing labour, crane and float explanations, but they do not prove those explanations caused every day either. The respondent should request zone-level readiness records, tested programme logic, lift allocation, labour deployment and cost-ledger evidence before advancing a positive alternative causal case.

Answer 12

A defensible provisional conclusion is that late connection details were a possible effective cause of delay in Zones A and B, based upon L8-R02 and the design hold recorded in L8-R05. Wider causation remains unresolved because L8-R04 records reduced labour and crane unavailability, L8-R05 attributes constraints in Zones C and D to labour, and float remains available before the facade milestone. On the Galoo analysis, the conclusion cannot extend beyond those presently available records. Daily fabrication, erection, programme and cost evidence is required before duration, concurrency, completion effect or either monetary claim can be determined.

12. Knowledge check

Complete the accompanying ten-question Knowledge Check after reviewing the workshop answers; the assessment tests breach and consequence, effective cause, cause and occasion, the four-stage chain, programme evidence and the boundaries of the supplied project record.

Closing point

A persuasive construction claim proves what the event changed, where and when the change operated, and which identified consequence followed from that change. The causal conclusion should never extend beyond the evidence supporting each link.

Scope of the lesson

This lesson states principles of English contract law and distinguishes the Scottish treatment of apportionment where that comparison assists professional understanding. It provides an educational method for analysing fictional project records and does not determine any live entitlement. Advice upon an existing dispute requires the executed contract, governing law, amendments, notices, complete programme record, technical evidence, resource records, witness evidence and valuation material.