Methodology

The reasons a scheme is refused are already written down. By the authority. Before it is ever submitted.

Every UK refusal is accompanied by a public officer's report stating the reasoning. Rasmere reads them, structures them and answers the only question that matters at offer stage. What is this authority refusing, for this scheme typology, right now.

Under a minute
Address to sourced read
100% sourced
Every flag links to a published decision
UK wide
Every Local Planning Authority indexed
The five steps

How a postcode becomes a verdict.

  1. 01

    Decisions indexed at authority level

    Rasmere ingests every published decision from every UK Local Planning Authority. For each refusal we extract the application class, the officer's named reasons and the policy clauses cited.

    Every figure ties back to a council document. Nothing is inferred without source.

  2. 02

    Officer language structured into patterns

    Across thousands of refusals the recurring themes resolve. Daylight shortfalls, conservation friction, plot ratio, missing reports. These form the authority level pattern library.

    Officer phrasing repeats by authority. We catalogue it.

  3. 03

    A site address resolves to its authority

    We resolve the address to the binding LPA and retrieve the patterns active in that authority for the relevant typology. No configuration. No integrations.

    Postcode in. Authority aware read out.

  4. 04

    The model reasons over the matched record

    The model reasons across matched patterns, scheme context and policy citations. The output is a probability band, named exposures and concrete design adjustments. Facts and interpretation stay visibly separate.

    Transparent reasoning. Sourced citations on every flag.

  5. 05

    Brief proceeds with the record in hand

    The report makes the binding constraints visible before a drawing is commissioned. The brief is written around known refusal triggers rather than into them.

    Weeks of pre application discovery, compressed into one read.

The pipeline

Signals in.
A verdict out.

Three passes. Each compresses noise until what remains is a decision actionable before an architect is briefed.

  1. Phase 01Collect

    Decision signals from the authority

    Recent approvals, refusals, recurring officer objections, appeal outcomes and site context. Consolidated into one scheme level record.

    IN · Address · TypologyOUT · Raw record
  2. Phase 02Structure

    Patterns the officer keeps citing

    Noise resolved into what tends to be approved, what tends to fail and which adjustments are most likely to change the outcome on this site.

    IN · Raw recordOUT · Pattern map
  3. Phase 03Decide

    A verdict and the next move

    A probability band, named exposures and the scheme adjustments most likely to flip a borderline read. Every claim cites its record.

    IN · Pattern mapOUT · Sourced verdict
End to endUnder a minute, sourced
Run a site

The authority's record, returned for your address.

Enter a postcode. Receive a pre submission read sourced from real officer decisions in that LPA.