top of page
Search

Contract Disputes Case Studies for Underground Works

  • Writer: RXM Advisory
    RXM Advisory
  • Jul 11
  • 7 min read

A tunnel delay can become a balance-sheet event long before it becomes an arbitration. In contract disputes case studies related to geotechnical/underground works, the immediate issue may be water ingress, an uncharted obstruction, settlement, or a changed ground-support design. The eventual dispute, however, commonly turns on a more difficult question: which party assumed the commercial and technical risk, and what contemporaneous evidence proves it?

For boards, investors, owners, contractors, and professional consultants, underground disputes demand more than a technical opinion. They require disciplined analysis of contract allocation, causation, program impact, financial exposure, governance conduct, and the credibility of the record. The following case studies are representative scenarios drawn from recurring dispute patterns. They are not substitutes for the facts, contract language, or governing law of a specific project.

Why underground works produce disproportionate disputes

Ground conditions are inferred rather than manufactured. A project team may have borehole logs, geophysical surveys, baseline reports, historical mapping, and laboratory data, yet the actual excavation face can still reveal materially different conditions. The commercial consequences are amplified where progress depends on sequential works: a delay in excavation may hold up lining, waterproofing, mechanical and electrical installation, commissioning, and revenue commencement.

The contractual framework is therefore decisive. Some contracts transfer most subsurface risk to the contractor. Others establish a geotechnical baseline, permit time and cost relief for defined differing site conditions, or require early notice and a jointly managed investigation. Labels alone are insufficient. A clause titled “unforeseen conditions” may be narrowed by tender assumptions, disclaimers, notice requirements, design responsibility, or an obligation to inspect available information.

Disputes also become expensive because the technical issue and the financial claim often travel separately. A consultant may focus on whether a support system was adequate, while management must assess liquidated damages, extension-of-time entitlement, variation valuation, insurance notifications, impairment risk, debt covenants, and the recoverability of claims. These matters need to be brought together early.

Case study 1: The baseline report that was treated as informational

A contractor priced a deep excavation and underground station package on the basis of a geotechnical baseline report. The report described weathered rock at a specified range and assumed manageable groundwater inflows. During excavation, the contractor encountered fractured zones with sustained inflows, requiring additional grouting, modified support sequencing, dewatering, and a slower excavation cycle.

The owner argued that the baseline report was provided “for information only” and that the contractor had accepted all site risks. The contractor responded that the employer’s tender documents contained detailed baseline parameters, that the bid program relied on those parameters, and that the encountered conditions were materially worse than the stated baseline. The contractor claimed prolongation costs and an extension of time. The owner counterclaimed for delay damages.

The central issue was not whether the ground was difficult. Both sides accepted that it was. The issue was whether the contract established an objective benchmark against which the conditions should be judged. The outcome depended heavily on document hierarchy, tender clarifications, exclusions, and project correspondence before award. An early internal presentation describing the baseline report as the “design basis” conflicted with the owner’s later position that the report carried no contractual weight.

The broader lesson is that risk allocation must be consistent across commercial, technical, and governance documents. Boards approving a major underground package should ask whether the organization’s risk register, bid evaluation, financing assumptions, and contract language describe the same allocation. Contradictions do not merely create legal ambiguity. They can weaken a party’s negotiating position and impair the credibility of senior witnesses.

Financial and governance implications

A claim of this kind should be evaluated as an asset with uncertainty, not treated as a certainty in project forecasts. Management should distinguish between incurred cost, potentially recoverable cost, disputed delay exposure, and contingent funding needs. If the project company is highly leveraged or tied to a development timetable, directors should receive scenario-based reporting rather than a single optimistic claim value.

The board’s role is not to direct technical means and methods. It is to ensure that management has an appropriate claim protocol, independent financial oversight, appropriate delegation limits for settlements, and clear disclosure controls where the dispute could affect lenders, investors, or transaction counterparties.

Case study 2: Settlement damage and the divided design record

On an urban utility tunnel project, surface settlement exceeded trigger levels near a sensitive neighboring structure. The contractor immediately reduced advance rates and installed additional monitoring. The professional engineer and qualified person, or PE/QP, directed temporary stabilization measures while the project team investigated the cause. Possible contributors included ground loss at the face, incomplete grouting, utility leakage, and a change in construction sequence.

The owner alleged defective temporary works and sought recovery for remediation, third-party claims, and delay. The contractor contended that it had followed the issued design and that the owner’s late instruction to maintain access for adjacent works had constrained the planned sequence. The PE/QP faced a separate professional-liability exposure: whether monitoring data had been assessed promptly, whether hold-point decisions were adequately documented, and whether advice to proceed was based on sufficient information.

This scenario illustrates why an underground incident must be managed as both a safety event and a future evidentiary event. The first priority is protection of people, assets, and the public. Yet decisions made in the first 48 hours can shape the dispute years later. Was the baseline survey preserved? Were instrument readings retained in their native format? Did the meeting minutes distinguish observed facts from hypotheses? Were instructions confirmed in writing? Was a root-cause analysis kept separate from privileged legal advice where appropriate?

Professional responsibility cannot be resolved by pointing to a title block or a broad disclaimer. A practicing PE/QP must act within the applicable professional and statutory framework, exercise independent judgment, identify conditions requiring review, and maintain adequate records of decisions and instructions. The exact standard will depend on jurisdiction, scope of appointment, contractual role, and the facts. In markets such as Singapore, where regulated professional roles may be central to underground construction approvals, the distinction between design accountability, site supervision, and contractor execution should be carefully defined from the outset.

For the company and its board, the question is equally practical: has the organization created an environment in which the PE/QP can escalate concerns without commercial pressure obscuring professional judgment? A governance failure may arise not only from poor technical decisions, but also from informal directions, suppressed escalation, or a culture that rewards schedule recovery while minimizing documented risk.

Case study 3: The variation that became a valuation dispute

A design-and-build contractor encountered a mixed-face condition that required a revised excavation support arrangement. The owner accepted that a change was necessary but rejected the contractor’s pricing, arguing that the revised arrangement was more conservative than required. Months later, the project was completed, but final account discussions stalled over the value of the variation, alleged disruption, and the contractor’s claimed loss of productivity.

The dispute became a valuation exercise. Direct costs were relatively visible: additional steel, labor, plant, grouting, and specialist subcontractors. The difficult items were time-related preliminaries, site overheads, head-office overhead, financing charges, and the asserted loss of opportunity from resources retained on the project. The owner also challenged whether the contractor had mitigated its costs and whether productivity losses were caused by the changed ground condition rather than its own planning deficiencies.

A credible valuation requires a transparent bridge from technical event to cost consequence. Expert analysis may examine planned versus actual production, critical-path effects, resource deployment, procurement records, contemporaneous site diaries, and market rates. It should avoid treating every overrun as recoverable merely because a variation occurred. Equally, it should not dismiss disruption simply because it is difficult to quantify.

This is where finance, project controls, and dispute strategy must operate together. A weak cost ledger can undermine an otherwise valid technical claim. Conversely, a technically persuasive narrative without a disciplined quantum model may produce a settlement at a substantial discount. For investors considering an acquisition or refinancing, unresolved claims and counterclaims should be diligence items, with attention to probability-weighted exposure, retention rights, security instruments, and the enforceability of dispute-resolution provisions.

Building the record before the conflict hardens

The strongest disputes are usually built through ordinary project discipline, not reconstructed after completion. Daily records should identify location, equipment, labor, conditions encountered, instructions received, production achieved, and disruptions observed. Photographs and monitoring data should be dated, traceable, and retained with appropriate metadata. Meeting minutes should record decisions, dissenting views where relevant, action owners, and deadlines.

Technical notices should be issued when required by contract, even while the parties cooperate on site. A notice is not necessarily an act of aggression. Properly framed, it preserves rights while describing the event, immediate mitigation, information required, and the anticipated time or cost effect. Delayed or vague notices can create avoidable defenses, especially where the contract makes timely notice a condition of entitlement.

Document control matters just as much at senior level. Board packs should preserve the distinction between confirmed facts, management estimates, legal positions, and settlement authority. Informal messages that speculate about fault or instruct a consultant to “find a way through” can be damaging when extracted from a wider context. Sensitive issues should be escalated through a defined protocol involving project leadership, commercial management, finance, legal advisers, insurers where necessary, and independent technical experts.

A disciplined approach to resolution

Not every underground dispute should proceed to arbitration or litigation. Early neutral review, structured without-prejudice negotiations, dispute adjudication mechanisms, and targeted expert determination can protect value where the parties still need to complete the works or preserve a commercial relationship. The appropriate forum depends on the contract, urgency, technical complexity, confidentiality needs, enforceability, and the gap between the parties’ valuation positions.

Before selecting a path, decision-makers should test their case against the actual record rather than the project narrative. What does the contract require? What did the ground data reasonably communicate? When did the event become known? What mitigation occurred? Can the delay and cost be separated from unrelated inefficiencies? Which witnesses can explain the decisions with precision and credibility?

Underground risk cannot be eliminated by contract drafting, monitoring, or insurance alone. It can, however, be made governable. The organizations best positioned in a dispute are those that treat technical evidence, commercial entitlement, professional accountability, and board oversight as one connected discipline from the first indication that the ground is not behaving as expected.

 
 
 

Comments


bottom of page