Concurrent Delay and Apportionment in British Columbia

That distinction is not a stylistic preference. It changes what you file, what you ask the court to do, and what your delay expert is retained to produce. In England the concurrency argument is a fight about the extension-of-time mechanism: which event caused what, and whether the contractor is relieved. In British Columbia the reported cases treat concurrency as an incident of assessing damages for breach of contract. The court accepts that both sides contributed, and then divides responsibility, sometimes to the day and sometimes by impression.

The BC apportionment line is real, it runs from 1983 to 2004, and it includes an appellate percentage split. It is also almost invisible to current national commentary, which is the second thing an adviser needs to know: the cases exist, and the judge you appear before will probably not have seen them. The pan-Canadian doctrine sits on the Canada concurrent delay page and is not repeated here. What follows is what BC does differently.

How British Columbia decides concurrent delay

BC courts apportion. Where both the owner and the contractor have contributed to overlapping delay, the reported BC approach is to divide responsibility as part of assessing damages for breach of contract and of causation, not to run a doctrinal test that hands the whole extension to one party. The split may be precise or impressionistic. Nothing in the BC authorities requires an entitlement analysis to be completed before the money is divided.

The practical consequence for an incoming practitioner is that the submission you would file in London, Toronto or Edinburgh is the wrong shape. You are not persuading a BC judge to adopt a rule. You are offering a split, and offering more than one route to arrive at it.

The BC apportionment line the national commentary has forgotten

Five BC decisions carry the apportionment line, and between them they produce four different techniques: precise day-by-day allocation, week-by-week allocation, rough justice, burden-shifting, and (at appellate level) a straight percentage. The most useful of them for a claimant is the appellate one, because it is the only one an opponent cannot dismiss as a first-instance curiosity.

Layer: jurisdictional. Every row rests on the secondary evidence tier, no BC judgment was read in original text for this corpus, and no paragraph pinpoints are given. The two ✔ entries are verified as to citation only. The three rows marked UNVERIFIED rest on a single survey as to holding.

Two traps sit inside that table. First, do not cite Kraft, 2001 BCSC 1306, for concurrency, that is an earlier and different decision in the same litigation, on third and fourth party procedure, contribution and indemnity. It is a procedural ruling, not the delay judgment. Second, Foundation Co is doing more work in the BC cluster than apportionment alone: it is also the authority that an extension of time is permissive rather than mandatory, that a contractor need not seek an extension in order to claim delay damages, and that an owner's delay counterclaim can be barred where the owner strategically withheld its own notice. That last point is developed on the BC notice and time bars page.

Precise or rough justice. BC runs both, and has no rule choosing

BC has two incompatible models on its books and no authority selecting between them. Pacific Coast Construction and Kraft apportion by window, Evergreen Building refuses to and apportions by impression. Which one a trial judge adopts appears to be a matter of judicial preference rather than principle. No BC decision reconciles them, and none states a threshold at which granular analysis becomes required.

Evergreen Building cuts both ways, and anyone commissioning a delay expert in British Columbia should read it before signing the engagement letter. It is BC authority that a trial judge may refuse a granular schedule analysis altogether and apportion impressionistically. A real risk for a claimant who has invested six figures in a windows analysis, and a real opportunity for a respondent attacking one.

The corollary from Kraft is the more encouraging one, and it is the answer to the respondent who says the claim must fail because the delays cannot be matched in time: Kraft apportioned week-by-week despite an inability to match the delays temporally. On the BC line, precision is not a precondition to apportionment. It is a way of arriving at one.

This is also where BC's methodological silence bites. NEGATIVE FINDING There is no BC judgment on delay-analysis methodology at all, not critical path, not as-planned versus as-built, not windows, not retrospective time impact analysis, and no BC judgment comments on the admissibility, weight or preferred methodology of delay-analysis expert evidence. A BC court applies the general expert-evidence framework with no BC methodological authority to apply. The consequences for expert instruction are worked through on the delay analysis methods page and on the BC prolongation and quantum page.

What British Columbia has never decided

These are searched negative findings, not gaps in the research, and for concurrency they are more useful than most of the positive law. State them flat.

Layer: jurisdictional, searched negative findings recorded against the secondary evidence tier. A negative finding here means the corpus searched and did not locate the item. It is not a statement that no such decision could exist.

The North Midland gap deserves to be pleaded as a gap rather than glossed. A concurrency-allocation clause, the drafting that makes contractor-concurrent delay non-excusable by agreement, is now common in international forms and is appearing in Canadian bespoke drafting. If your BC contract contains one, neither party can tell you what a BC court will do with it, because no BC court has ever been asked. Whether a BC court would follow the English answer, treat the clause as engaging the prevention principle, or decline to enforce it, is prediction. Say so in the submission rather than asserting an outcome, and run the prevention argument alongside it.

The tension inside BC's own authority

CONFLICT, and it has never been resolved. One comparative paper reads Perini Pacific Ltd v Greater Vancouver Sewerage & Drainage District BC's own leading appellate delay authority, as denying delay damages to both parties, with no apportionment, where both contributed. Meanwhile BC's first-instance line, and Foundation Co at appellate level, apportion freely. The BC Court of Appeal has never addressed the tension.

The same comparative paper records that the Quebec Court of Appeal in Ansa Construction, 1987 CanLII 799 (QCCA), expressly rejected the no-apportionment approach. Both the Perini Pacific reading and the Ansa characterisation are UNVERIFIED and rest on that single paper. Neither is adopted here. Quebec is a civil-law jurisdiction and its position does not transfer to BC. It is recorded only because it is the source of the recorded tension.

The safest formulation for a BC submission, and the one that survives a well-prepared opponent, is this: British Columbia apportions concurrent delay, usually as a matter of damages assessment rather than entitlement, but the province's leading appellate authority, Perini Pacific, has been read as denying recovery to both parties without apportionment, and that tension has never been addressed by the BC Court of Appeal.

Where prevention makes the concurrency argument unnecessary

Run prevention first. N.B.C. Mechanical Inc v A H Lundberg Equipment Ltd, 1999 BCCA 775, carries a refinement worth pleading: once the owner's conduct has prevented performance within the deadline, contractor delay on other aspects of the project becomes irrelevant. The refinement is UNVERIFIED, but if it is right it is BC's implicit answer to concurrency in the prevention context.

That answer is more contractor-friendly than the English one. Where prevention is established, BC does not appear to require the contractor to disentangle its own concurrent delay before defeating the liquidated damages clause, which is the opposite of what a North Midland-style allocation is designed to achieve. If prevention is available on the facts, it may dispose of the concurrency exercise before it starts, and it should be pleaded ahead of apportionment rather than as a fallback. The mechanism, and BC's unusually strong time-at-large material, are on the BC prevention page.

The Negligence Act, and why the pleading matters

NEGATIVE FINDING No BC decision was located applying the Negligence Act, RSBC 1996, c 333, to apportion responsibility for construction delay. Apportionment of delay in BC construction cases is a contractual and damages exercise, not a statutory one. In Pacific Coast Construction, Evergreen Building, East Kootenay, Kraft and Foundation Co, the courts split responsibility as a matter of assessing damages for breach of contract and of causation, without invoking the statute.

The statute becomes relevant only where the delay claim is pleaded in tort or in concurrent liability, and BC construction delay claims very often are. Foundation Co itself ran against the consulting engineer in negligent misrepresentation as well as against the owner in contract. The pleading consequence follows: a defendant who wants statutory apportionment needs the claim characterised as tortious or concurrent, and a plaintiff who wants to avoid it pleads contract only.

Record that consequence as inference from the structure of the cases, not as a holding. No BC judgment decides it in the delay context, and the underlying question, whether a BC court will apportion for contributory fault in a pure breach-of-contract delay claim, absent the statute, remains open. The corpus logs it as an unresolved item rather than answering it.

One further trap, and it is a live one in BC pleadings: the Negligence Act is c 333. The Law and Equity Act the source of the relief-from-forfeiture power at s 24, is c 253. The two chapter numbers are frequently transposed. Separately, NEGATIVE FINDING no BC decision applies s 24 to a construction notice provision or time bar, that argument is open and untested.

How to run a concurrency case in British Columbia

Brief both lines. The BC apportionment cases give you the outcome a BC court has actually reached, Schindler Elevator Corporation v Walsh Construction Company of Canada, 2021 ONSC 283, gives you the analytical framework a BC judge is most likely to be shown, because the national commentary runs on Ontario authority. Schindler is Ontario and persuasive only, but the inference the corpus draws is that a BC court asked to decide concurrency today would probably reach for it rather than for Kraft or Evergreen Building.

One last point on the contract. CCDC 2 – 2020 the form most BC private work is built on, says nothing about concurrency at GC 6.5. The general conditions allocate delay by cause: owner or consultant delay contrary to the Contract Documents at GC 6.5.1 and stop work orders at GC 6.5.2 are compensable, and neutral events at GC 6.5.3 attract time only, with the GC 6.5.3.4 carve-back returning a cause beyond the contractor's control to the compensable side where the delay in fact results from owner or consultant action. What happens when two causes overlap is not addressed, and supplementary conditions rarely address it either. That silence is why the question is a pure common-law and evidential one in BC, and why the shape of the apportionment you offer matters more than the label you put on it. The rest of the BC delay picture the clocks, the notice position and the forum, sits on the British Columbia extension-of-time hub.

Sobre este material El contenido de la biblioteca es información general sobre la práctica de las reclamaciones de construcción, no asesoramiento jurídico. El derecho a reclamar, los plazos y el procedimiento se rigen por su propio contrato y por el derecho del lugar donde se ejecuta la obra. Revisado el 10 de agosto de 2026 · Informar de una corrección