Candour with the council about an AI-assisted draft

Disclosing AI drafting to the council is not something the planning system requires, and no application form asks how a supporting statement was produced. What the system does require is that the information in the application is accurate. Section 70C and the revocation powers in the Town and Country Planning Act 1990, the certificates on the application form, and the general law on misrepresentation all point the same way: the authority has to be able to rely on what you tell it, and a permission granted on misleading information is vulnerable.

So the honest answer to a client asking whether they must declare that a draft came out of a drafting tool is no. The useful answer is that the question is the wrong one. What matters is whether the agent has checked every factual assertion in the document and can show where each came from.

What the authority needs to be able to rely on

A planning officer writing a delegated report works from the submitted documents. They verify some things independently, such as the flood zone and the listed building entry. Most of the rest they take at face value: the site area, the existing floorspace, the number of bedrooms, the parking count, the date a use started, the condition of a building.

Those facts drive policy tests. Existing floorspace decides whether a Class MA prior approval threshold is met. Site area decides whether a biodiversity net gain exemption applies. The date a use started decides immunity. Get one of them wrong and the officer's conclusion is wrong, through no fault of theirs.

That is why the accuracy duty is about facts rather than authorship. A Planning Statement assembled from policy text and site information is a submission, not a witness statement, and nobody expects it to be written from scratch by hand. They do expect the floor areas in it to match the drawings.

Accuracy duties on the applicant and agent

Three duties operate at once, and they sit on different people.

The applicant signs the certificates on the application form, including the ownership certificate and, where relevant, the agricultural holdings notice. Knowingly or recklessly issuing a false or misleading certificate is an offence under section 65 of the 1990 Act. That duty is personal to the applicant even where an agent fills the form in.

The agent owes a professional duty to the client and, if chartered, to their institute. The RTPI Code of Professional Conduct requires members not to mislead, which covers both positive misstatement and a selective presentation that creates a false impression. An agent who submits a statement containing a floor area they have not checked is exposed on that duty whether the number came from a drafting tool, a junior colleague or an old spreadsheet.

The third duty is practical rather than legal. Councils keep informal records of agents whose submissions need checking, and an officer who has found two wrong numbers in your last three applications reads the fourth differently.

Consequences of inaccurate information

The remedies available to a council escalate, and the serious ones are rarely used but remain available.

Revocation is rare because compensation is payable. The more common outcome is far more mundane and more expensive: the application is held up, the consultation is rerun, the determination slips past the eight or thirteen week date, and the client pays for the delay.

A separate risk sits with lawful development certificates. A certificate under section 191 or 192 obtained on the strength of statements later shown to be false can be revoked under section 193(7), and the evidential basis for immunity claims is scrutinised precisely because so much rests on it.

Whether the drafting method must be disclosed

There is no duty to disclose the software used to prepare a document, in the same way there is no duty to disclose which CAD package drew the plans or that a template was used for the heritage section. The council's interest is the content.

Two situations change that. If an officer asks directly how a document was produced, answer straightforwardly: a drafting tool produced the structure and the policy references, and the author checked and amended it. Evasion on that question causes more damage than the answer ever would.

The second is expert evidence. Where a document is presented as the professional opinion of a named competent person, such as an ecologist's report or a fire statement, the author's declaration matters and the author must be the person who actually formed the opinion. An AI-assisted draft can be the starting point for that professional, and it cannot be the opinion. For report types where a licensed or competent professional is legally required, including Biodiversity Net Gain under the Environment Act 2021, protected species work under the Conservation of Habitats and Species Regulations 2017, and fire statements under the Building Safety Act 2022 framework, the draft is a starting point for that professional rather than a substitute for them. The professional directory exists for that review and sign-off step.

How to describe a document's basis

The cleanest approach is a short methodology note at the front of any document that relies on data you have not generated yourself. Three or four sentences covering where the constraints information came from, which policy edition you relied on, what was taken from the client and what remains unverified.

That note does three things. It tells the officer which facts they can check and which they should treat as the applicant's own evidence. It creates a record that protects you if a client-supplied fact turns out to be wrong. And it makes any remaining gap explicit instead of hidden.

PlanScope drafts insert a "[TO BE CONFIRMED]" flag wherever a site-specific fact is missing rather than filling the gap with a plausible figure. Leaving those flags visible in an internal draft and resolving every one before submission is the discipline that makes the method defensible. A document that reaches a council with a flag still in it tells the officer nothing good, and the fix is a checking pass, not a tidier placeholder. The same logic applies to the other recurring failure mode, which is a draft that reads well and rests on an unchecked number, as discussed in what drafts get right about structure and wrong about evidence.

Illustrative example. An agent submits a change of use application stating an existing floorspace of 148 m². The figure came from a client email and was carried into the statement unchecked. The measured survey later shows 162 m², which moves the scheme into a different parking standard. Caught before validation, it is an amended drawing and a corrected paragraph. Caught after grant, it is a section 73 application and an awkward conversation.

Correcting an error after submission

Correct it immediately, in writing, to the case officer, with the corrected document and a one line explanation of what changed and why.

Do not bury the correction in a revised document uploaded quietly to the portal. Officers notice, and an uncommunicated change to a submitted document is treated as worse than the original error. If the correction is material to the consultation, the officer may have to rerun publicity, and they will decide that faster if you tell them the implication rather than leaving them to find it.

Where the error is found after grant, the route depends on what changed. A trivial inconsistency in a supporting statement may need nothing. A wrong floor area or a wrong plan reference usually needs a section 96A non-material amendment or a section 73 variation, and it is better to raise it than to wait for a building control inspector or a neighbour to raise it for you.

Keep the version history. Where sections of a draft have been regenerated during preparation, knowing which version was submitted is the difference between a one line correction and an afternoon of reconstruction, which is the practical argument for the habits set out in version control when report sections are regenerated.

Keeping the officer relationship intact

Case officers are not adversaries and they have no interest in catching you out. What they resent is being made to do the checking that the agent should have done, because it costs them time they do not have.

Three habits build the credit you draw on later. Flag the weak point in your own case before the officer finds it, since a known weakness with an explanation reads better than one discovered in week six. Answer questions with the document reference and the page, not with an assertion. And when you are wrong, say so in one sentence without a paragraph of justification.

That credit is worth money on the next application, which is the practical reason to take accuracy seriously rather than the regulatory one. See PlanScope pricing for how the drafting and review tiers work if you are deciding where the checking time comes from.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.