What a case officer notices in a drafted statement

A case officer reads dozens of supporting statements a month, and the ones written by a machine and submitted unedited share a small number of tells. Case officer ai planning statement scepticism is not about the drafting tool. It is about whether anybody applied the document to the site. Officers do not object to a drafted statement that has been edited into something specific. They object to twelve pages of national policy that could have accompanied any application in England.

Four checks take an officer under ten minutes, and all four are avoidable.

Policy recited instead of applied

The pattern is a paragraph summarising what national policy says about design, followed by a sentence asserting that the proposal accords with it. Nothing between the two connects the policy to the drawing.

What applying policy looks like is shorter and harder. The policy requires development to respond to local character, so the statement identifies the character: the prevailing two storey eaves line on this side of the street, the red brick with cast stone cills, the rhythm of bay windows at first floor. Then it says what the proposal does about each, and which drawing shows it.

Officers write the report from that material. A statement that gives them the character description and the response saves them writing it, which is the single most useful thing a supporting statement can do. One that recites the policy leaves them to do the work and to wonder whether the applicant understood the site.

Local plan policies the officer expects and cannot find

Drafted statements are strong on national policy and weak on the adopted development plan, which is the wrong way round. Section 38(6) of the Planning and Compulsory Purchase Act 2004 requires the determination to be made in accordance with the development plan unless material considerations indicate otherwise, so the local policies are the primary framework.

An officer will look for the policy numbers they use every day: the design policy, the amenity policy, the parking standard, the relevant allocation or settlement boundary policy, any neighbourhood plan policy, and the topic policies for whichever constraint applies. A statement citing none of them, or citing a policy from a superseded plan, reads as generic whatever else is in it.

Two specific errors recur. Citing a saved policy from a plan that has been replaced, which happens because superseded documents stay online for years. And citing a policy number that exists but says something else, which is worse, because it looks deliberate.

Assertions with nothing behind them

Every statement contains claims. The question is whether each one is supported by a drawing, a survey, a calculation or a cited source.

The assertions officers test first:

• that the extension will not affect neighbour amenity, without a section through the boundary
• that parking is adequate, without a dimensioned parking layout
• that the site has no flood risk, without a reference to the published flood map
• that there are no protected trees, without a check against the council's records
• that the design matches local character, without a street elevation or a context photograph
• that highway visibility is acceptable, without splays drawn on the plan

None of those needs a specialist report on a small application. They need a drawing or a screenshot and a sentence. An assertion with the evidence attached moves the officer forward. The same assertion alone generates a further information request, and the eight week clock keeps running.

Length that does not match the scale of the proposal

A single storey rear extension does not need a twenty page statement, and an officer receiving one assumes it was generated rather than written.

There is a reverse failure too, where a major application arrives with four pages that address none of the plan's strategic policies. Both waste time, but the long document on a small scheme is more common and more irritating, because the officer has to read it to confirm there is nothing in it.

Proportion, roughly: a householder application needs two to four pages. A minor scheme of up to nine dwellings, six to twelve. A major application, as long as the policies require, structured by policy topic so the officer can find each one. The guidance on writing a document an officer can use is set out in our note on drafting a design and access statement an officer can use.

Inconsistency with the application form

This is the check that costs applications their validation date, and it is entirely mechanical.

Officers cross read the form, the drawings and the statement. The figures that have to agree: site area, existing and proposed floor area, number of bedrooms, number of parking spaces, materials, means of access, whether trees are present, whether the site is in a flood zone, and the ownership certificate.

A drafted statement that says the scheme provides two parking spaces while the form says one, or that describes a two bedroom unit where the drawings show three, fails on its own terms. Worse, it raises a question about which document is right, and the officer cannot determine the application until they know. The cost of that is set out in our note on the cost of failing validation and resubmitting.

Reconcile the numbers last, after the drawings are final, and reconcile them against the form rather than against the previous version of the statement.

How officers verify a claim quickly

Worth knowing, because it explains which claims get tested.

Officers have the constraint layers on screen: flood zones, conservation area boundaries, listed building records, tree preservation orders, article 4 directions, and the planning history for the address. They have street level imagery, which shows the building as it was when the imagery was captured. And they have the previous applications on the site, including anything refused and the reasons.

Three consequences. A claim about a constraint is checked in seconds, so do not describe the site as unconstrained without checking the same layers. A statement that ignores a refused application on the same site looks evasive, because the officer has read the earlier decision. And a description of the existing building that contradicts the imagery gets a question, which is a reason to say when a photograph was taken.

Editing a draft so it reads as site specific

The productive sequence is to let the tool produce the structure and the policy scaffolding, then spend the saved time on the parts only a human on the site can write.

1. Replace every generic character description with what is actually opposite and adjacent, from a site visit or photographs.
2. Insert the local plan policy numbers from the current adopted plan, checked against the council's policies map.
3. Attach evidence to each assertion, or delete the assertion.
4. Cut every paragraph that would read identically on another site.
5. Reconcile every number against the application form and the drawings.
6. Add the site specific history, including previous refusals and what has changed.
7. Read the first page as though you were the case officer with forty applications open.

Step four is the one that shortens the document most, and step seven is the one that catches the rest. PlanScope drafts insert a "[TO BE CONFIRMED]" flag wherever a site specific fact is missing rather than inventing one, and the presence of those flags in a submitted document is itself a tell, so clear them before submission.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. Where a council asks who prepared a document, the position is set out in our note on when a council asks who wrote your report. This is general guidance and not legal advice, so check the position with your local planning authority or a qualified professional before relying on it.

See PlanScope pricing if you want to edit drafts in the platform and keep a project library rather than starting each statement from nothing.