The current employment module requires:
existing-employees
proposed-employees
Each uses the employees component, which expects full-time, part-time and total FTE counts.
For outline applications, this may be too strict. Employment numbers may not yet be known in enough detail to provide reliable counts. In those cases, forcing numeric values may create misleading data, for example entering 0 when the real answer is unknown.
Other parts of the specification already allow an unknown answer for outline applications where detail may not yet be settled, for example some floorspace, waste and rights-of-way questions. We should check whether employment needs a similar pattern.
Questions for feedback:
- Do applicants commonly know existing and proposed employee counts at outline application stage?
- Are there proposal types where unknown employment numbers should be allowed?
- How do planning officers currently use employment numbers from outline applications?
If there is evidence this need exists, the next step would be to draft a small proposal for updating the employment module for outline applications.
The current
employmentmodule requires:existing-employeesproposed-employeesEach uses the
employeescomponent, which expects full-time, part-time and total FTE counts.For outline applications, this may be too strict. Employment numbers may not yet be known in enough detail to provide reliable counts. In those cases, forcing numeric values may create misleading data, for example entering
0when the real answer is unknown.Other parts of the specification already allow an
unknownanswer for outline applications where detail may not yet be settled, for example some floorspace, waste and rights-of-way questions. We should check whether employment needs a similar pattern.Questions for feedback:
If there is evidence this need exists, the next step would be to draft a small proposal for updating the employment module for outline applications.