Skip to main content
Designing planning and housing data

BETA This is a new service - your feedback will help us to improve it.

Planning consideration

Local area requirements

Requirements (sometimes known as validation checklists) that set out supporting information which applicants need to include with a planning application

Design stage
Test and iterate
Tags

View a glossary of tags

Github
Join the discussion
Synonyms
  • Local validation checklist
Legislation
No legislation added
Expected number of records
350
Frequency of updates
Annually
Useful links
Technical specification
No specification added

Background information

Each planning consideration we work on passes through the stages of our design process, where we research and answer specific questions to help us collect more information.

Backlog

  • Who asked for 'Local area requirements' data?

  • What is the driver for the request?

  • Which 2024 focus area does the request support?

    • Modern planning software
    • Faster local plans
    • Other

Screen

  • What is the 'Local area requirements' consideration?

  • Is there legislation that defines 'Local area requirements'?

    Yes

    • What is the legislation that defines 'Local area requirements'?

      Local Area Requirements are referenced in the NPPF, Paragraph 44

    • What is the specific part of the legislation that describes how a 'Local area requirements' gets designated?

    • What is the specific part of the legislation that requires the publication of 'Local area requirements'?

  • Who, in law, is responsible for the planning consideration or makes decisions about 'Local area requirements'?

  • Which organisations do we think should publish the data?

    • Local authorities

  • Is the Local area requirements a trigger?

  • Is the Local area requirements something to consult during plan making?

  • Is there any Local area requirements data already available?

  • Do we think the data should come from a single source?

  • Will a data standard be required?

Research

  • Do we understand the lifecycle of a Local area requirements?

    Yes

    • Document a stage of the high-level lifecycle of a Local area requirements

      • Item 1

        name
        Updating
        actors
        LPAs
        impact
        output
        An updated local area requirement document
        description
        The local area requirements for each LPA should be reviewed every 2 years. Any associated data should be updated as and when required.

  • Do we understand how the data is created/produced?

  • Where will or should the data be used?

  • Who are the statutory consultees for Local area requirements?

  • Other than the statutory consultees who are the primary users of Local area requirements? How do we expect them to use Local area requirements?

  • What are the planning needs for this data?

    These documents help users to know what they need to do for a given application

  • Who are the types of users who might benefit from having access to Local area requirements data?

    The data design team need to know where the latest local area requirements documents are in order to support our analysis of planning considerations

    Service providers like PlanX need to find local area requirements so that they can codify any rules that might be included in them

  • What are some potential uses of Local area requirements data?

  • What's the value of adding Local area requirements data to the platform?

  • From what we have learnt so far are there any risks to making Local area requirements data available?

    So far the data design team have compiled this data. This might lead to the data being out of date.

0 updates

Last updated: 2024-09-03 14:41:35