Eagle Ops
← Eagle AI
BIGGABIGGA (2026) Royal Mid Surrey - After the Flood. BIGGA News, 1 February 2026. (Course Manager Graham Down on Royal Mid-Surrey's recovery from a 20-metre Thames riverbank breach in October 2024 affecting six holes across Taylor and Barton courses.)

Flood Recovery — Royal Mid-Surrey Case

What it is

A case-study entry documenting Royal Mid-Surrey's ongoing recovery from a major Thames-corridor flood event — and, more usefully for Eagle AI, the decision-sequence framing Graham Down (Course Manager) uses to plan multi-hole flood recovery: assess baseline first, then sequence interventions. The entry is honest that this is not a completed worked example — at the time of source publication (1 February 2026) the recovery is still in baseline-assessment phase, with full recovery projected "won't see full recovery until spring."

The case-study value is the shape of the decision constraint (twice-daily tidal water ingress, six-hole footprint, multi-month timeline) and the assess-before-deciding doctrine (Down's explicit "we need to understand where that settles before making decisions"), not a step-by-step recipe. This is intentional in the source — Down is documenting the situation in the assessment-not-yet- intervention phase, and the curator has matched scope to source rather than inflate.

The flood event

Per the source [bigga:2026-mid-surrey-flood]:

  • Cause: 20-metre breach in the Thames riverbank, October 2024
  • Affected area: six holes compromised — mostly Taylor Course, parts of Barton Course
  • Water-ingress pattern: "Water came in twice a day regardless of tide height" — i.e. the breach turned the affected six holes into effectively tidal-zone turf, not single-event flood damage
  • Rainfall / depth metrics: not documented in source

The twice-daily-water-ingress detail is the operationally-critical constraint. Single-event flood damage (one storm → one inundation → recovery cycle) is one shape. The Royal Mid-Surrey shape is continuous saturation until the breach is sealed, which:

  1. Makes baseline assessment impossible until the water source is addressed (you can't measure compaction or soil profile under tide)
  2. Extends the recovery timeline indefinitely until the upstream cause is fixed
  3. Changes the recovery doctrine from "act fast on a known damage footprint" to "wait, assess, and act once the situation is stable"

The decision-sequence framing

Down articulates the planned-but-not-executed sequence [bigga:2026-mid-surrey-flood]: "We're considering scraping, aeration, decompaction, overseeding – whatever is appropriate once we know the baseline."

Operational read for Eagle AI's flood-event recovery surface:

  • The named sequence — scrape → aerate → decompact → overseed — is the canonical UK flood-recovery vocabulary. Even though Down has not yet executed any of these, the four-step ladder is the framework the recovery plan is structured around.
  • The decision gate between steps is "baseline understanding," not "calendar." Down: "We need to understand where that settles before making decisions." This is the asymmetric-information frame — premature intervention on uncertain baseline wastes effort or makes damage worse; waiting for baseline clarity costs time but preserves decision quality.
  • "Whatever is appropriate" is load-bearing — the four-step ladder is available actions, not required sequence. Some flood footprints need scrape only, some need full ladder, some need drainage redesign (see Howat / Woodham consultancy below) instead of any of the four.

The advisory network

Royal Mid-Surrey is operating with three named advisors during the recovery planning phase [bigga:2026-mid-surrey-flood]:

  • Paul Woodham — water-management consultant (same Woodham as the STRI source on rolling treatments cited in green-speed-stimpmeter, distinct advisory engagement)
  • Gordon Howat — drainage-redesign / drainage-project designer
  • The R&A — advisory-partner role

Operational read: a flood-recovery project of this footprint (six holes, multi-month, tidal-constrained) is not a course-manager-solo decision in UK practice. The advisory-network shape (water consultant

  • drainage designer + R&A governance) is the expected operational structure for major events. Eagle AI surfaces should treat multi-advisor coordination as an information signal — when the recovery is being planned with this advisory network, the timeline and complexity are above-routine.

Timeline framing

Down on recovery timeline [bigga:2026-mid-surrey-flood]: "Realistically, we won't see full recovery until spring."

Published February 2026; spring 2026 is the expected baseline-recovery window. This is the multi-month-recovery horizon for a tidal- constrained, six-hole-footprint event. Single-event flood recovery on a smaller footprint may complete in days-to-weeks; this case is months. Eagle AI surfaces tracking flood-recovery timelines should treat horizon as a function of (a) cause-removal completion, (b) affected-hole count, (c) ingress pattern (single-event vs continuous).

Predecessor context

Gavin Kinsella MG served as Royal Mid-Surrey Course Manager for ~20 years prior to Graham Down arriving in summer 2025. Down arrived to post-breach planning rather than pre-breach baseline operations — which is itself an operational note: course-manager transitions during recovery events compound the assess-baseline difficulty.

What this entry doesn't yet cover

Per source-scope discipline, this entry deliberately does not publish:

  • Specific timing between sequence steps (source has none)
  • Tool/equipment brand recommendations (source has none)
  • Quantitative damage assessment (source has no mm-depth, area-square- metres, or compaction-reading data)
  • Recovery completion record (the recovery is ongoing as of source publication)

Future Curator pass should re-pull when Royal Mid-Surrey publishes a follow-up piece documenting completed sequence + actual timeline + final baseline restoration. Until then, this entry is the decision-frame anchor — what to think about, not how long it takes.

<!-- WRITER NOTE: Slug `flood-recovery-decision-sequence` chosen per architect pre-triage proposal. Title uses case-anchor framing (`— Royal Mid-Surrey Case`) per the championship-greens-prep-belfry precedent. If/when a multi-club flood-recovery source surfaces with generalised sequence guidance, this entry can be retitled to drop the case anchor and the new generalised entry would supersede this one. --> <!-- WRITER NOTE: Scout-note framed this as "a real worked example of post-event recovery; useful narration material." WebFetch revealed the source is actually mid-recovery assessment-phase content with *planned* (not executed) sequence and no completed timeline. Entry has been scoped to what the source actually says rather than the scout-note framing. Same scope-discipline pattern as championship-greens-prep-belfry (where the scout-note implied brand-specified instrument readings that the source did not contain). -->

Related

  • course-closure-tier-policies-uk — sibling event-response entry on the closure side of the flood-event cycle (close → assess → recover)
  • climate-adaptation-uk-course-management — multi-club doctrine on storm-event whiplash variability and cluster-deviation patterns; Kirwan's "45mm in a couple of hours → all bunkers washed out" is the storm-side single-event-flood analogue
  • moisture-deviation-thresholds-uk-2025 — the drought-pole counterpart on the moisture axis; this entry's twice-daily-saturation is the opposite-pole deviation
  • green-speed-stimpmeter — Paul Woodham's STRI rolling-treatments research is cited there; his involvement at Royal Mid-Surrey is in a separate water-management advisory capacity