1 of 43

Reducing Invalid Planning Applications A service pattern for digital planning submissions

Show & Tell 12

20 November 2020

2 of 43

Partners collaborating:

working with

Open Systems Lab

Ho Lam User Researcher

Project website: www.ripa.digital

Blog: medium.com/@digitalplanning

Twitter: @DigitalPlanTech

Facebook: Facebook.com/Digitalplantech

LinkedIn: linkedin.com/company/reducing-invalid-planning-applications

digitalplanning@lambeth.gov.uk / OSL (Open Systems Lab)

3 of 43

The Problem

4 of 43

RIPA

  • Average of 50% of all Householder applications are invalid on receipt
  • Confusing system to navigate
  • Costly - in terms of time and money for applicants and planning services
  • Build a tool that brings the planning service into the 21st Century

5 of 43

Southwark - BoPs - www.bops.digital

RIPA

6 of 43

Show and Tell No. 12

  1. Project team sprint catch up

    • Content Design (CM)
    • Planning Officer / Validator Survey (JS)
    • LDC Workshop with Enforcement (EH)
    • Other sprint work (CN/JS)

  • User Researcher updates

  • OSL updates

  • Q&As

RIPA

7 of 43

1.a Content Design

8 of 43

RIPA

Reviewing the Prototype

  • Divide the user journey into stages

  • Looking at language, accessibility and general flow

  • Focus on how users interact with the service

    • Hemingway
    • Gov.uk Pay
    • Digital, Data and Technology Capability Framework

  • E.g. ‘Were the works completed more than 4 years ago?’

9 of 43

RIPA

Adding to the Back Log

  • Adding any comments to the spreadsheet

    • Priority
    • Effort level
    • Status

  • Edits checked against feedback from User Research

  • ‘About the Applicant/Agent’
    • -> ‘About You’

10 of 43

1.b Planning Officer / Validator Survey

11 of 43

RIPA

  • This sprint we have been working on a survey with Southwark.�
  • The survey is designed to capture the officer’s experiences and satisfaction with the system they are using to validate, assess and decide an application using the existing back office systems.�
  • Validations officers, planning officers and managers will complete this survey on a variety of different application types.�
  • Once the Private Beta is running, we will re-run the survey. This will allow us to compare the experiences and satisfaction level of officers using the RIPA and BOPS systems.�
  • We will be finalising the survey at a workshop later today and hope to roll out the survey in the next sprint.

12 of 43

1.c Workshop with enforcement officers

13 of 43

What to submit with a LDC application

RIPA

Drawings:

  • Location plan
  • Floor plans
  • Elevations
  • Roof plans*
  • Site sections*
  • Other relevant drawings

Information:

  • Applicant information
  • Details of proposal
  • Interest in land
  • Ownership details
  • Completion date
  • Statement of evidence

Evidence:

  • Photographs (incl. aerial)
  • Agreements / contracts
  • Invoices / Bills
  • Registration details
  • Certificates
  • Statutory declaration

14 of 43

RIPA

Summary:

  • Starting point for necessary information / evidence / drawings to be submitted with a LDC application
  • Minimal variance in documents, but opportunity for irrelevant drawings / documents to be excluded
  • Benefits for enforcement as well as development management, better quality submissions / information
  • ‘Find out if you need planning permission service’ serves multiple functions (proposal description, evidence of compliance with PD, is or is not development)
  • Wider workshop with validators / officers to follow

Immunity:

  • Specific to ‘existing’ use / development
  • Development becomes ‘lawful’ after a certain amount of time has lapsed
  • 4 years (operational development), 10 years (everything else)
  • Guidance, not guiding

15 of 43

1.d Other Sprint things

16 of 43

RIPA

  • Gov.UK Pay
  • IT Change Freeze
  • GIS Layers
  • Article 4 Mapping

Other

  • Customer Survey circulating / active
  • Planner/Validator survey circulating / active
  • Time recording in place / ongoing
  • Brand identity guide from partners

17 of 43

RIPA

Steps ahead and monitoring the private beta

18 of 43

2. Show & tell: User research

19 of 43

RIPA

What we’ve up to this sprint

Conducted 4 usability testings Journeys tested:

- LDC 4 years immunity submission journey. Prototype V.011 (Figma clickable prototype). End to end journey-’Landing’ page to ‘Application submitted’.

User group we spoke to:

4 participants, all agents applicants. 1 agent applicant applied for LDC for her own property

20 of 43

RIPA

LDC 4 year immunity submission journey V.01 overall:

All participants were able to complete the journey by themselves with no major difficulties. Participants thinks the new service is pretty clear and neat.

“...it all seemed simple which is appropriate for an LDC e.g. very limited information required (although the evidence could be difficult to work out) - quite a streamlined process, neat, clear…”-P17

‘It's a very simple form, I think anyone could go through it and find it simple to use...in an application such as this I think you need a very detailed guidance form to say to somebody “in this form of application, these are the things that are the basis to which the application must be determined.” A good guidance form is almost as important as the form itself.’ -P16

21 of 43

RIPA

LDC- 4 years immunity submission journey V.11 Key findings:

Landing page:

All participants find the information on the landing page quite clear and knows how to navigate to start an application.�

Some commented they would like to know what exact documents would be needed from the outset.

22 of 43

RIPA

Dashboard:

It is really clear to participants that where they can click to start a new application here.

2 participants would like to see postcode & the reference number to be shown on the project cards.

23 of 43

RIPA

About the project�What did the work involve:

Some of the options needs to be explained in more details.

A couple of participants wonder what ‘Demolish’ & ‘Modify’ would mean.

Participant also commented that some applicants may get confused between ‘Build new’ & ‘ Extension’.

24 of 43

RIPA

About the project�‘The work were completed on’:

It can difficult to find out the exact date of completion sometimes.

The word ‘completed’ may need clearer definition. For architects, completion means when a building is safe to move in but for other, it could mean when the decorations is completed.

'if I were a homeowner, I may get confused by the wording of when the works were 'completed''.

25 of 43

RIPA

About the property:

Participants likes that they are able to see the information the system have on the property. 1 participant wonder if we could incorporate the information we pull out onto the map also

Eg. showing conservation area on map�

Participants also ask if the ‘Property area’ means the size of the land area or if it means the size of property?

26 of 43

RIPA

Drawing/ evidence:

Participants understands that this is evidence to support their application. While all of them think the list of options currently showing is comprehensive, they questioned how they may prove the photo is taken at a certain date and if date on digital photos could be faked.

�2 participants suggested statutory statement as a form of evidence.

27 of 43

RIPA

In what way do these documents prove date of completion/use?:

Agents participants we tested with this round think the question is clear and understood what it is for but some agents commented this may confuse some homeowner applicants.

A participant suggested that we could have the question immediately after each of the chosen option to make it specific to the each option itself.

28 of 43

Declaration:

Participants found this page straight forward.

Some would like to have more explanation of why is it important and how may this affect their application if they are related/partnered with someone in the council.

29 of 43

Payment methods:

Credit card/ debit card are the most common payment methods.

A participant commented ‘we can't do many credit card payments because of the credit limit..." hence the "Nominate to pay" on Planning portal is very helpful for them and hope we will have something similar to allow their client to pay for the application themselves.

Another participant's company still uses cheque as the finance department still uses it. But he further commented that it won’t be an issue if cheque is not an option, he will choose other payment method instead.

30 of 43

RIPA

Application submitted:

All participant understood their application is now been submitted. Thinks this page is clear.

What happen next:

A participant really likes the and he instinctively thought this section is a live tracker of the application.

Participant questions bits of the content and wording. e.g. more clarification on what a 'disputed' scheme means

One participant commented that we should add a paragraph to let applicant know what are their options if they don’t hear back from the council.

31 of 43

Other findings:

https://docs.google.com/spreadsheets/d/103VG7eG1FADJkNPfvHfCJV894Rn3ucmROcLcF0PFiVE/edit#gid=0��

32 of 43

Upcoming sprint �

  • Confirming 3 user testing sessions on the 24/Nov & 25/Nov for the LDC (prospective) journey.�
    • Catch up with OSL on prototype development and feedback research findings. �
    • Continue to improve on content & copy of the service with the team �









33 of 43

3.Show & Tell / OSL

34 of 43

Explore the service mockup here

35 of 43

36 of 43

Project Types / User Journeys

37 of 43

Project Types / User Journeys – What we might expect traffic to look like

38 of 43

- Question

- Checklist (normal / expandable)

– Text (short / long / email address)

– Number (with units)

– Date

– Address

– File upload

– Find property

– Property information

– Draw map boundary

– Result

– Review

– Task list

– Content

– Notice

– Pay

– Page

– Page with sections

– Decision

– Notify

– Calculate

– Checkpoint

– List

➡️

➡️

➡️

➡️

➡️

➡️

🕔

🕔

🕔

❄️

❄️

❄️

Component progress

39 of 43

Q&As

40 of 43

Thank you.

Project website: www.ripa.digital

Project Log Link: https://www.ripa.digital/Project-log

Blog: medium.com/@digitalplanning

Twitter: @DigitalPlanTech

LinkedIn: linkedin.com/company/reducing-invalid-planning-applications

digitalplanning@lambeth.gov.uk / OSL (Open Systems Lab)

41 of 43

3. Collaboration session

42 of 43

RIPA

WORKSHOP SESSION

  • Council Checklist of minimum reqs and timescale for Private Beta Dec

  • Discussion: How will the end to end testing work / look? (Jan-March)

43 of 43

5. Any other business