<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Flood risk sequential test vs. retail sequential test</title>
  <link rel="self" href="https://khub.net/c/message_boards/find_thread?p_l_id=53683759&amp;threadId=644510860" />
  <subtitle>Flood risk sequential test vs. retail sequential test</subtitle>
  <id>https://khub.net/c/message_boards/find_thread?p_l_id=53683759&amp;threadId=644510860</id>
  <updated>2026-03-16T14:20:33Z</updated>
  <dc:date>2026-03-16T14:20:33Z</dc:date>
  <entry>
    <title>Flood risk sequential test vs. retail sequential test</title>
    <link rel="alternate" href="https://khub.net/c/message_boards/find_message?p_l_id=53683759&amp;messageId=644510859" />
    <author>
      <name>Richard Wood</name>
    </author>
    <id>https://khub.net/c/message_boards/find_message?p_l_id=53683759&amp;messageId=644510859</id>
    <updated>2022-04-27T08:27:25Z</updated>
    <published>2022-04-27T08:17:52Z</published>
    <summary type="html">&lt;p&gt;We have an edge-of-centre retail proposal which is largely in flood
  zone 2.  The applicant has submitted a flood risk sequential test to
  demonstrate that the scheme could not be reasonably accommodated on
  any site with a lower flood risk.&lt;/p&gt;
&lt;p&gt;A rival developer, promoting a different, out-of-centre retail scheme
  has submitted their assessment of developer 1's flood risk sequential
  test. They conclude (not surprisingly) that there is an alternative,
  lower flood risk site that could accommodate the scheme.  But the
  lower risk, sequentially preferable in flood risk terms site
  is sequentially less preferable in retail terms.&lt;/p&gt;
&lt;p&gt;How do we balance between the two seemingly conflicting sequential
  approaches?  Does anyone have any examples of where this circle has
  been squared previously?&lt;/p&gt;</summary>
    <dc:creator>Richard Wood</dc:creator>
    <dc:date>2022-04-27T08:17:52Z</dc:date>
  </entry>
</feed>
