Why a planning draft should never predict a decision

No planning document can predict approval, and any report that implies otherwise is telling you something false about how the system works. A planning application is decided by a person exercising judgement, on a statutory test that weighs the development plan against other material considerations, with the weight given to each of those considerations left to them. That is a judgement, not an arithmetic. A well evidenced document makes the argument easier to accept and removes reasons to refuse. It cannot convert either of those into a result.

The statutory test puts judgement at the centre

Section 38(6) of the Planning and Compulsory Purchase Act 2004 requires applications to be determined in accordance with the development plan unless material considerations indicate otherwise. Section 70 of the Town and Country Planning Act 1990 requires the decision maker to have regard to the development plan, to other material considerations and to local finance considerations so far as material.

Read those together and the shape of the exercise is clear. Someone identifies the relevant policies, decides whether the proposal accords with the plan read as a whole, identifies other material considerations, decides how much weight each deserves, and reaches a conclusion.

Only the first and third of those steps are largely objective. Whether a consideration is capable of being material is a question of law. How much it weighs is a matter of judgement, and it is well established that weight is for the decision maker rather than for the applicant, the objector or the consultant.

Who actually decides, and on what

Most applications are determined by officers under a scheme of delegation. Larger or more contentious cases go to a planning committee, where elected members decide and may depart from the officer recommendation provided they give planning reasons.

Both routes involve inputs that do not exist when a supporting document is written. The consultation responses have not arrived. The highway officer has not commented on the visibility splay. The neighbours have not written in. The case officer has not stood in the garden and looked up at the proposed roof. A committee has not heard a resident speak for three minutes.

Policy can also move during a determination. A local plan reaches a new stage, the authority's housing land supply position is updated, an appeal decision on a comparable issue is published. None of that is knowable in advance.

Where the weight problem bites

Two applications with identical documents can be decided differently, lawfully, because the weight attached to the same considerations differs.

A rear extension that causes a modest loss of afternoon light to a neighbour is the clearest example. The daylight evidence may be identical on two sites. In one authority the design guide treats the 45 degree line as a firm expectation and the officer refuses. In another the same breach is weighed against the applicant's housing need and the limited harm, and permission is granted. Neither decision is wrong.

Anyone who has watched a committee reverse an officer recommendation on a scheme that accorded with every policy in the plan understands the point. And anyone who has seen the reverse, members granting a departure because the benefits felt real to them, understands it from the other side.

That is not a defect in the system. Local decision making with discretion is the design. The consequence for document writing is that prediction is out of scope.

What a good document can actually do

Four things, all of which improve your position without guaranteeing anything.

It locates the proposal accurately within the development plan, quoting the operative wording of each relevant policy, so the officer does not have to build the policy case for you. A planning statement that does this well saves the officer hours and reads as reliable.

It answers the objections the case will actually attract, including the awkward ones. A document that deals with the overlooking point head on, with measurements, is more persuasive than one that omits it and hopes.

It supplies the evidence the policy test requires, in the form the authority expects. The right survey, done in the right season, to the right standard, by someone competent to do it.

It removes drafting reasons to refuse. Missing floor areas, no bin store shown, an ambiguous red line, a report that contradicts the drawings. Officers refuse or delay on these constantly, and they are entirely within your control.

What honest wording looks like

Write conclusions as arguments with evidence attached rather than as forecasts.

Say that the proposal accords with a named policy, and why, by reference to a document in the pack. Say where you consider harm arises and why it is outweighed. Use language that identifies whose view is being expressed, so a reader can separate your submission from the facts you rely on. Where a matter is uncertain, say so and say what would resolve it.

Avoid the constructions that overreach. A document that says permission will be granted, that a scheme fully complies with all legislation, or that the council will accept a particular mitigation, has made a promise no author can keep. PlanScope's own position is deliberately narrow on this: reports are AI-assisted drafts, they should be reviewed before submission, and we do not guarantee planning approval.

Where a draft is missing a site specific fact, it inserts a flag rather than a plausible number. That is a safeguard rather than an omission, and it exists because an invented figure in a planning document is worse than a gap. Fill the flag, or have your reviewer fill it. Do not delete it.

Managing expectations with a client, a lender or a partner

An illustrative example. A self-builder buys a plot with the benefit of outline permission and instructs a design for reserved matters. The consultant's covering note says approval is expected within eight weeks. The highway authority then asks for a visibility splay that requires removing a hedge the neighbour believes is theirs, the application is delayed twice, and the client's bridging facility has a fixed end date.

Nothing in that sequence was avoidable by better drafting. All of it was manageable by better expectation setting: naming the highway risk at the outset, allowing for an extension of time, and explaining that determination periods are frequently extended by agreement.

Three habits help. Give the realistic programme rather than the statutory minimum. Name the two or three risks most likely to cause refusal or delay, in writing, at the start. And be clear about what is within your control and what is not.

Fixing a document that overclaims

If you inherit or draft something that predicts an outcome, the repair is mechanical.

1. Strike any sentence asserting approval, compliance with all requirements, or what the council will accept.
2. Replace each with the policy, the evidence and the reason you consider the test met.
3. Attribute judgements so the reader can see they are submissions rather than facts.
4. Add the risks you identified, briefly, in the covering letter rather than burying them.
5. Have the document read by someone who will argue with it, which is what the professional directory is for.

An overclaiming document does specific damage. An officer who finds one unsupportable assertion reads the rest sceptically, and the points you needed them to accept are the ones that suffer.

Reports should be reviewed before submission, and for some report types a licensed or competent professional is legally required rather than merely advisable. That is a limit on what any drafting tool can do, including this one.

This is general guidance rather than legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

You can see PlanScope pricing for the drafting, and enter your postcode to see which reports your site is likely to need.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.