1 of 39

Planning Application Data specifications

Drop In - 29th Jan

2 of 39

Introductions

Matt Scarth

3 of 39

Welcome

Welcome - Matt Scarth

Recap and updates - Mike Rose

Work by community - All (Mike Rose)

MHCLG overview - Discussion Points - Colm Britton

Close/AOB - Matt Scarth

4 of 39

5 of 39

Hybrid meeting format

please raise your hand to ask a question or add to the chat.

6 of 39

Recap and updates

Mike Rose

7 of 39

Reminder

  • Aim: To develop a set of open, reusable data specifications to underpin planning applications. These will make sure the current templates are underpinned by data.

  • Scope: The specifications will define the structure and format of data that is required when submitting a planning application based on the national legislation in place.

8 of 39

Reminder

Intended outcomes:

  • improve interoperability, accessibility and understanding
  • enable integration with existing datasets (for example land use, infrastructure)
  • foster collaboration among government bodies, developers, planners, software providers​ and everyone else
  • improve data flow, quality, consistency and transparency in the planning process

9 of 39

We are aiming for the floor, not the ceiling

10 of 39

We don’t want to break anything

11 of 39

We want the approach to be scalable

12 of 39

Since the last drop in session

We have:

  • had our second advisory group meeting
  • planned out the meetings until the end of March
  • been responding to questions on github
  • been working with MHCLG policy team
  • begun engaging with existing groups (industry working group)
  • set up https://design.planning.data.gov.uk/advisory-group
  • been monitoring the spreadsheets
  • started developing the initial specifications

13 of 39

Your questions answered

Will the new data standards force planning authorities to capture data that does not add value?​

More information about the definition of MUST, SHOULD, and MAY can be found here

What is the value that the customers and the vendors will get from implementing this new data specification? ​

Consistency, interoperability, national picture of planning activity, easier reporting etc

Are the standards likely to change over time? How often? ​

It will evolve over time based on feedback and the community's needs​

How long would legacy data standards need to be supported for?​

The timeline for wider adoptions of the data standards across all LPA in England isn’t determined yet.​

What are some of the use cases for data in planning under the new data standards?​

Some examples are tracking housing delivery, identify stalled sites, support building safety initiatives and see how our cities and rural areas are changing

14 of 39

Building the community

We want to be engaging with as many people as possible -

  • Can you invite your contacts towards our drop ins and discussions?
  • Who could / should we be making sure are aware / involved?
  • Would you be willing to write a guest blog for us on this work?
  • Would you blog on your website?
  • What else could we / should we do?

15 of 39

Work done by the community

Mike Rose

16 of 39

Thank you to those that have completed the spreadsheet.

Share your thoughts…

17 of 39

MHCLG - update

Colm Britton

18 of 39

Process - recap and where we are at

19 of 39

Application forms

Process - goal

Information model

Specifications

20 of 39

Application forms

Information model

Specifications

Application types

Existing forms

Components

Fields

Background information

Paper forms -> underlying data

Process - what

21 of 39

Application forms

Information model

Specifications

Application types

Forms

Components

Fields

Background information

Paper forms -> underlying data

Dataset of application types

Components per app type

Fields per component

Requirement levels

Use cases / rationale

Issues

Process - what

22 of 39

Application forms

Information model

Specifications

Application types

Forms

Components

Fields

Background information

Paper forms -> underlying data

Dataset of application types

Components per app type

Fields per component

Requirement levels

Use cases / rationale

Issues

Specification per module

Documentation

Feedback loops

Process - what

23 of 39

Application forms

Information model

Specifications

Application types

Forms

Components

Fields

Background information

Paper forms -> underlying data

Dataset of application types

Components per app type

Fields per component

Requirement levels

Use cases / rationale

Issues

Specification per module

Documentation

Feedback loops

Process - now

24 of 39

Process - how

25 of 39

Assumptions and questions (aka issues)

26 of 39

Should "notification of proposed works to trees in a conservation area" be its own application type?

Application types

27 of 39

Materials

The additional materials information required for listed building consent applications would be useful for the other application types as well

Assumption

28 of 39

Is it necessary for agents and applicants to provide an address?

What is the address used for?

Agent name and address

Applicant name and address

29 of 39

The minimum viable specification for site location is just the UPRN and/or site boundary (shapefile), rather than requiring a full address

Site address details

Assumption

30 of 39

What are the Ecclesiastical Grades?

Are they still used?

How do they differ from normal listed building grades?

Listed building grading

31 of 39

Is it important to explicitly capture from the applicant whether they have NOT obtained pre-application advice?

Who uses this data and how?

Pre application advice

32 of 39

Is there a reason why the `location of advertisement(s)` section provides a free text box for when the work started and doesn't just ask for the date?

Location of advertisement(s)

33 of 39

Combine applicant name and address and applicant contact details

Combine agent name and address and agent contact details

Agent name and address

Applicant name and address

Agent contact details

Applicant contact details

34 of 39

Add "Hedgerow Removal Notice" to list of application types

Application types

35 of 39

Next Steps

Mike Rose

36 of 39

Resolve issues

37 of 39

Build the community

  • invite your contacts towards our drop ins and discussions?
  • Who could / should we be making sure are aware / involved?
  • write a guest blog for us on this work?
  • blog on your website?

  • Anything else?

38 of 39

Timeline:

March

‘Refining Specifications’

26th March: Advisory Group

28th March: Drop In

Hand over specifications

MHCLG begin testing and planning for mandating.

January

‘Developing an information model’

22nd January: Advisory Group

29th January: Drop In

February

Drafting Specifications’

26th February: Advisory Group

5th March: Drop In

April

39 of 39

Thank you