Say what is being proposed
A useful description identifies the main building work, its position and the intended use where that is relevant. For new housing, the number and type of homes matter. For a change of use, identify both the existing and proposed use and include associated external alterations. [1]
As a hypothetical example, “rear extension and alterations to the roof” is more informative than “improvements to the property”, but it still needs enough detail to distinguish the actual proposal. The correct wording depends on the submitted design; copying a description from a neighbouring approval is not a substitute for checking it.
Keep explanation in the right document
The description is not the place for a lengthy argument about why permission should be granted. Design explanations, policy justification and detailed specifications belong in the relevant supporting material. Avoid personal information and product branding that do not help describe the development. [1]
Treat the description as an index to the proposal. Ask whether somebody unfamiliar with the project would understand the main changes, then use the drawings and supporting statement to explain them properly.
Match the drawings and application route
Check that the description agrees with the floor plans, elevations, proposed use and application form. A description of an extension to one house would not adequately describe a proposal also creating separate homes. The legal application requirements include the information necessary to describe the development, not just a completed title box. [3]
For staged or amendment applications, identify the relevant earlier permission and the matter now being decided. Do not leave the council to infer whether you are seeking a new permission or a change to an existing one. [1]
If the council proposes different wording
National guidance says the council should discuss revised wording with the applicant or agent before changing the description. It should check accuracy before publicity, without allowing that check to delay validation. [2]
Review the proposed change carefully. Confirm that it captures the intended scheme and does not omit a component. Keep the agreed version with the drawing register so later amendments can be checked against it.
Why wording can matter after approval
Section 73 is a route for changing conditions, not for changing the operative description of the permitted development. A later proposal falling outside that description cannot simply be authorised by rewriting a drawing condition under Section 73. [4]
This is a reason to be accurate at the outset, not to make the description deliberately vague. When the design changes, check the correct amendment route against the actual permission and its conditions. [4]