You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pclass="govuk-body">We’ve created a data design process that is repeatable and modular to produce better and more consistent results. This approach also makes it easier to open up our process for others to contribute and follow.</p>
31
-
<pclass="govuk-body">Our process is split into several stages. We want to make it easy to see where a planning consideration is in our process and what we need to do to make progress.</p>
32
-
<pclass="govuk-body">Each planning consideration we take through the process gives us more information. Measuring what worked, what didn’t work and what needs tweaking helps us make each step more efficient.</p>
30
+
<pclass="govuk-body">We have created a data design process to determine what data is needed to support planning in the UK and should be made available on <ahref="https://planning.data.gov.uk" class="govuk-link">planning.data.gov.uk</a>.</p>
31
+
<pclass="govuk-body">The output of the process is a technical specification that data providers can use to provide high-quality planning data.</p>
32
+
<pclass="govuk-body">Once we have created, tested and verified the technical specification we will hand it over to a data management team, who will work with data providers to get the data onto <ahref="https://planning.data.gov.uk" class="govuk-link">planning.data.gov.uk</a>.</p>
33
+
34
+
<h2class="govuk-heading-l">About the design process</h2>
35
+
36
+
<pclass="govuk-body">This process needs to explore different aspects of the planning system, determine what is underpinned by legislation and what data us needed to support how it is used in planning.</p>
37
+
<pclass="govuk-body">We’ve created a repeatable and modular data design process to produce better and more consistent results. This approach makes the process more transparent and makes it easier for interested parties to contribute.</p>
38
+
<pclass="govuk-body">Our process is split into several stages. We want to make it easy to see where a planning consideration is in our process and what we need to do to make progress. It is worth noting that the process is not always linear. A planning consideration might move back a stage if we need to do more work on it.</p>
39
+
<pclass="govuk-body">Each planning consideration we take through the process gives us more information about our process. Measuring what worked, what didn’t work and what needs tweaking helps us make each step more efficient.</p>
40
+
41
+
<detailsclass="govuk-details">
42
+
<summaryclass="govuk-details__summary">
43
+
<spanclass="govuk-details__summary-text">
44
+
What is a planning consideration?
45
+
</span>
46
+
</summary>
47
+
<divclass="govuk-details__text">
48
+
<p>A planning consideration is something specific to an area that may impact the outcome of a planning decision.</p>
49
+
<p>For example, a national planning policy impacts what can be built across the whole of England, and a conservation area restricts what can be developed in that area.</p>
50
+
</div>
51
+
</details>
52
+
53
+
<h2class="govuk-heading-l">Stages of the design process</h2>
33
54
34
55
<pclass="govuk-body">There are 8 stages in total.</p>
35
56
36
-
<h2class="govuk-heading-l">1. Backlog</h2>
57
+
<h3class="govuk-heading-m">1. Backlog</h3>
37
58
38
59
<pclass="govuk body">This stage helps us to understand the planning data landscape.</p>
39
60
40
61
<h3class="govuk-heading-s">What happens</h3>
41
62
42
-
<pclass="govuk-body">Someone tells us about a subject area (we call these planning considerations) that plays a part in planning decision-making. This can be during the application or plan-making processes. They are expressing an opinion that data for this consideration should be more readily available.</p>
63
+
<pclass="govuk-body">Someone tells us about a subject area (we call these planning considerations) that plays a part in planning decision-making. This can be during an application or plan-making process. They are expressing an opinion that data for this consideration should be more readily available.</p>
43
64
<pclass="govuk-body">We then add it to the backlog and indicate where we think it fits with our programme objectives.</p>
44
65
<pclass="govuk-body">Once it’s on the backlog, this means we’re committed to looking at this consideration.</p>
45
66
46
67
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Backlog')}}" class="govuk-link">See planning considerations in the Backlog stage</a>.</p>
47
68
48
-
<h2class="govuk-heading-l">2. Screen</h2>
69
+
<h3class="govuk-heading-m">2. Screen</h3>
49
70
50
-
<pclass="govuk body">This stage helps us to verify that a consideration plays an important role in the planning system.</p>
71
+
<pclass="govuk body">This stage helps us to verify that a consideration plays an important role in planning decision-making.</p>
51
72
52
73
<h3class="govuk-heading-s">What happens</h3>
53
74
54
75
<pclass="govuk-body">We answer set questions in the screening stage to help us to understand the legal underpinnings of the consideration, where it is used and needed in the planning system and what, if any, data already exists.</p>
55
-
<pclass="govuk-body">At this stage, it is usually possible to tell if we can use an existing national dataset or whether a new standard is needed.</p>
76
+
<pclass="govuk-body">At this stage, it is usually possible to tell if we can use an existing national dataset or whether a new technical specification will be needed.</p>
56
77
57
78
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Screen')}}" class="govuk-link">See planning considerations in the Screen stage</a>.</p>
58
79
59
-
<h2class="govuk-heading-l">3. Research</h2>
80
+
<h3class="govuk-heading-m">3. Research</h3>
60
81
61
82
<pclass="govuk body">This stage is intended to help us to understand the planning need for a consideration.</p>
62
83
63
84
<h3class="govuk-heading-s">What happens</h3>
64
85
65
-
<pclass="govuk-body">We answer set questions in the research stage to help us understand the planning and data need.</p>
66
-
<pclass="govuk-body">We capture how and where the considerations are used, the size and scope of any potential data yield, assumed user needs, use-cases for the data and an expectation of who might be able to provide the required data.</p>
67
-
<pclass="govuk-body">This information is essential for data modelling.</p>
86
+
<pclass="govuk-body">We answer set questions in the research stage to help us understand the planning and data needs.</p>
87
+
<pclass="govuk-body">We capture how and where the considerations are used, the size and scope of any potential data yield, assumed user needs, usecases for the data, and an expectation of who might be able to provide the required data.</p>
88
+
<pclass="govuk-body">During this stage, we will capture any existing open data we find. Analysis of this data will help us to design a feasible and value data model in the co-design stage.</p>
68
89
69
90
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Research')}}" class="govuk-link">See planning considerations in the Research stage</a>.</p>
70
91
71
-
<h2class="govuk-heading-l">4. Co-design</h2>
92
+
<h3class="govuk-heading-m">4. Co-design</h3>
72
93
73
-
<pclass="govuk body">This stage is focused on us designing the smallest data model that will satisfy the highest number of needs.</p>
94
+
<pclass="govuk body">This stage is focused on designing the smallest data model that will satisfy the highest number of needs.</p>
74
95
75
96
<h3class="govuk-heading-s">What happens</h3>
76
97
77
98
<pclass="govuk-body">In the co-design stage we develop a draft data model.</p>
78
-
<pclass="govuk-body">Our approach is to start small and build up. So at this stage we’ll design a data model to capture the fewest data points needed to satisfy the clearest, most important use-cases.</p>
79
-
<pclass="govuk-body">The data model will be co-designed with users: people needing the data, people providing the data and stakeholders.</p>
99
+
<pclass="govuk-body">Our approach is to start small and build up from there. At this initial stage, we will design a data model that captures only the essential data required to meet the most pressing and clear needs. We anticipate that these data models will grow and evolve as new needs emerge. Each dataset will be designed with a minimal set of fields to start.</p>
100
+
<pclass="govuk-body">The data model will be co-designed with our users: people needing the data, people providing the data and stakeholders.</p>
80
101
81
102
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Co-design')}}" class="govuk-link">See planning considerations in the Co-design stage</a>.</p>
82
103
83
-
<h2class="govuk-heading-l">5. Test and iterate</h2>
104
+
<h3class="govuk-heading-m">5. Test and iterate</h3>
84
105
85
106
<pclass="govuk body">This stage helps us to build confidence in the data model, proving it is both feasible and will add value.</p>
86
107
87
108
<h3class="govuk-heading-s">What happens</h3>
88
109
89
-
<pclass="govuk-body">We take the draft data model and create the specification for it and any supporting materials.</p>
90
-
<pclass="govuk-body">We then test these materials along with the data model in a controlled environment. We do this with potential data providers.</p>
91
-
<pclass="govuk-body">This testing allows us to check the data will work in reality, that it's feasible to produce and provides value.</p>
92
-
<pclass="govuk-body">This stage may lead to changes to the data model.</p>
110
+
<pclass="govuk-body">We take the draft data model and create a detailed specification and any supporting materials.</p>
111
+
<pclass="govuk-body">Next, we test the data model and these materials in a controlled environment with potential data providers.</p>
112
+
<pclass="govuk-body">This testing helps us ensure that the data will work in practice, is feasible to produce and provides value.</p>
113
+
<pclass="govuk-body">If no existing data is available for a specific planning consideration, we may decide to create some sample data. This sample data, based on real instances of the planning consideration, allows us to test the data model and create an example data explorer to demonstrate how the data can be used.</p>
114
+
<pclass="govuk-body">We expect to iterate the data model during this stage.</p>
93
115
94
116
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Test and iterate')}}" class="govuk-link">See planning considerations in the Test and iterate stage</a>.</p>
95
117
96
-
<h2class="govuk-heading-l">6. Go / no-go</h2>
118
+
<h3class="govuk-heading-m">6. Go / no-go</h3>
97
119
98
-
<pclass="govuk body">This stage helps us to get sign-off for any potential risks we have identified.</p>
120
+
<pclass="govuk body">This stage allows us to check we have followed the process and completed the expected steps.</p>
99
121
100
122
<h3class="govuk-heading-s">What happens</h3>
101
123
102
124
<pclass="govuk-body">We will summarise what we've learnt during the data design process and check off any associated risks.</p>
125
+
<pclass="govuk-body">This stage gives us the chance to consider the potential costs, and any legal challenges and to prepare supporting guidance we think will help data providers to provide quality data.</p>
103
126
<pclass="govuk-body">This is a governance step for <ahref="https://www.planning.data.gov.uk/" class="govuk-link">planning.data.gov.uk</a></p>
104
127
105
128
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Ready for go/no-go')}}" class="govuk-link">See planning considerations in the Ready for go/no-go stage</a>.</p>
106
129
107
-
<h2class="govuk-heading-l">7. Prepare for platform</h2>
130
+
<h3class="govuk-heading-m">7. Prepare for platform</h3>
108
131
109
-
<pclass="govuk body">This stage is focused on preparing for the productionisation of the dataset(s) for the consideration.</p>
132
+
<pclass="govuk body">This stage is focused on preparing for the productionisation of the dataset(s) for the planning consideration.</p>
110
133
111
134
<h3class="govuk-heading-s">What happens</h3>
112
135
113
-
<pclass="govuk-body">We want to make sure everything is in place to move from experimental to production quality data that you can trust.</p>
114
-
<pclass="govuk-body">We wouldn't expect to make any changes to the data model at this point.</p>
115
-
<pclass="govuk-body">We’ll articulate what to expect from an authoritative dataset - for example, who we expect to publish, what we expect them to publish and how often.</p>
136
+
<pclass="govuk-body">We will ensure we have provided all the required information needed by the data management team for them to be able to start collecting and publishing production-quality data that you can trust.</p>
137
+
<pclass="govuk-body">We wouldn't expect to make many changes to the data model at this point.</p>
138
+
<pclass="govuk-body">We’ll articulate what to expect from an authoritative dataset — for example, who we expect to publish, what we expect them to publish, and how often.</p>
116
139
117
140
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='Prepared for platform')}}" class="govuk-link">See planning considerations in the Prepare for platform stage</a>.</p>
118
141
119
-
<h2class="govuk-heading-l">8. On the platform</h2>
142
+
<h3class="govuk-heading-m">8. On the platform</h3>
120
143
121
-
<pclass="govuk body">At this stage authoritative data will be collected and made available on <ahref="https://www.planning.data.gov.uk/" class="govuk-link">planning.data.gov.uk</a>.</p>
144
+
<pclass="govuk body">At this stage, we will handover to the data management team. They will work with data providers, collect the data they publish and make authoritative datasets available on <ahref="https://www.planning.data.gov.uk/" class="govuk-link">planning.data.gov.uk</a>.</p>
122
145
123
146
<h3class="govuk-heading-s">What happens</h3>
124
147
125
-
<pclass="govuk-body">Work will shift from designing the data to collecting the data.</p>
126
-
<pclass="govuk-body">Some, less authoritative, datawill be on the platform for data consumers to use. Over time we’ll collect more data from the dataset(s), increasing the quality and authority of the available data.</p>
127
-
<pclass="govuk-body">Feedback from providers and consumers will be collected and fed back to the data design team for future iterations of the standard.</p>
148
+
<pclass="govuk-body">The focus will shift from designing the data to collecting the data. The data management team will lead this work.</p>
149
+
<pclass="govuk-body">Some, less authoritative, data, created in earlier stages, will be on the platform for data consumers to use. Over time more data for the dataset(s) will be collected, increasing the quality and authority of the available data.</p>
150
+
<pclass="govuk-body">Feedback from providers and consumers will be collected and fed back to the data design team for future iterations of the data model.</p>
128
151
129
152
<pclass="govuk-body"><ahref="{{ url_for('planning_consideration.considerations', stage='On the platform')}}" class="govuk-link">See planning considerations in the On the platform stage</a>.</p>
0 commit comments