A flood-risk report on a hillside parcel usually ends with one number: how many plots are affected. When that number comes back as zero, the conversation about flood exposure closes. The deal moves forward on the strength of that single line.
That number tends to get trusted the way a structural certificate is trusted — as a pass/fail test the site had to earn. It isn't always that. In a hydraulic model built the fast way, zero affected plots can be a property of the math, not a finding about the ground.
The datum decides the answer, not the site
A flood-routing model needs a reference elevation — a datum — to measure water depth against at every point along the slope. The fast way to build one is to take the water level at the outlet, treat it as flat, and apply it across the whole reach.
That shortcut has a hidden consequence. Plots higher up the slope sit well above the outlet's pool level by definition. A model using a single flat datum can never show water reaching them, no matter how much rain falls or how drainage actually behaves upstream. The report will say zero affected plots every time it is run, on every version of the site — because the test cannot fail, not because the site has passed it.
On a hillside masterplan, the plots that sit highest are usually the ones priced highest — best view, most separation, first to sell. Those are exactly the plots a flat-datum model is structurally unable to flag. The shortcut doesn't fail randomly across the site. It fails in the one place a developer is least likely to go back and check, because those are the units the report already called safe.

The result can run backwards, too
A second version of the same shortcut produces an even stranger output. Skip the spillway — the crest that lets water actually leave an embanked area once it's full — and a routing model can show elevation ranked backwards from what gravity would do: lower plots draining fine, higher ones flooding, or the reverse.
Read at face value, that output sends redesign effort to the wrong side of the property. A developer working from it might raise plinth levels on plots that were never at risk, while the plots the model quietly couldn't see stay untested. The fix isn't a bigger safety margin. It's modelling the reach properly — real cross-sections carrying flow, plus a pool level only where water actually ponds — so the result reflects the slope instead of the shortcut that produced it.
What this changes before you sign
None of this shows up by reading the report. A page that says "zero affected plots" looks identical whether it came from a full routing model or a flat-datum shortcut. The only way to tell the difference is to ask how the datum was set, and whether the model was ever tested against a case it should have failed.
That question belongs in due diligence, not after possession. A flood clearance built on a model that structurally cannot find a problem isn't a cleared risk — it's an unverified claim wearing the shape of one, sitting inside a pro forma that priced the land as if the question had actually been answered.
Three questions separate the two: what elevation was used as the datum, and is it flat across the whole reach or does it follow real cross-sections; was a spillway or crest modelled at the embankment, or does water simply vanish once it reaches the pool; and has the model ever been run against a case where it should have shown flooding, to confirm it's capable of failing at all. A consultant who can answer all three in one sentence has done the work. One who can't has handed over a number, not a result.
Where the judgment stays
The routing model's job is narrow: turn "is this plot safe" into a testable question instead of an assumed one. It doesn't decide what residual risk is acceptable, how much freeboard a plinth level should carry, or whether a given spillway design is conservative enough for the site — those calls sit with an engineer who has walked the ground and a developer weighing cost against exposure.
What the model owes that conversation is honesty about its own limits: which reaches it actually tested, which datum it used, and where it simply couldn't reach. A report that's silent on those questions hasn't earned the number on its cover.
Every hillside parcel deserves a flood-risk model built to actually fail a test, not one that passes by construction. If you're evaluating sloped land and want the routing checked properly before it goes into your numbers, that's exactly what the 7-day review is for. Start a review.