Explaining an AI-assisted draft to a client or a committee

Explaining AI drafted planning documents is a conduct question before it is a technical one. The professional who signs a planning statement is responsible for its content, its policy analysis and its accuracy, and that responsibility does not change with the tool used to produce the first draft. Say that plainly, early, and the conversation is usually over in a sentence.

What creates difficulty is vagueness. A consultant who avoids the subject until an objector raises it at committee has handed the objector the framing.

What clients assume and what is actually true

Clients arrive with one of two assumptions, and both are wrong in useful ways.

The first is that a tool has replaced the planner, so the fee should drop accordingly and the work is somehow automatic. The second is that everything was typed from scratch by a chartered planner reading the local plan line by line, which has not been true of template-driven practice for twenty years.

The accurate description sits between them. Drafting produces a structured first version grounded in national policy and local plan text, with policy citations and with flags where site-specific facts are missing. A planner then verifies, corrects, adds the site judgement and takes responsibility. That is a different distribution of effort, not an absence of it.

Be specific about where the time goes now. It moves from assembling structure and boilerplate to checking facts, testing the policy fit and writing the parts that depend on having stood on the site.

Describing the drafting process honestly

A short, repeatable form of words is worth writing down once.

Something like: the first draft was produced with AI assistance using structured planning data, then reviewed, corrected and completed by a named planner who takes professional responsibility for it. Drafts of this kind cite policy and flag missing information rather than inventing it, and every fact in the submitted version has been checked.

Three things that description avoids. It does not claim the tool has any authority of its own. It does not suggest the output was submitted unedited. And it does not overstate the checking by implying a level of verification you have not actually done.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. That wording exists because it is accurate, and borrowing its shape for your own description is sensible.

Where professional review sits in the workflow

Review is not a proofread. It is the stage at which a qualified person confirms that the document says what it should and that its factual basis holds.

1. Check every site-specific fact against a source: address, area, red line, existing use, constraint designations, distances.
2. Remove every placeholder. A draft that inserts a flag where a fact is missing is doing its job, and a submitted document containing one is a validation problem and an embarrassment.
3. Verify every policy citation against the adopted plan and the current national framework, including the edition, because national policy has been renumbered and restructured more than once.
4. Read the site judgement sections as a planner rather than an editor. Character, context, design response and access are the parts a draft cannot supply.
5. Confirm the document answers the council's validation list and the case officer's likely questions.
6. Record who reviewed it and when.

For report types where a licensed or competent professional is legally required, ecological survey work, biodiversity metric work, contamination assessment, fire statements, review means sign-off by that professional rather than by a planner. A draft is the structure they fill, never a substitute for them. The professional directory is the route to that sign-off where you do not have the discipline in house.

Answering the question about accuracy

The honest answer is that accuracy is a property of the process, not of the tool, and that the process has a named person at the end of it.

If asked whether the document could contain an error, say yes, in the same way any professional document can, and describe the controls that catch errors: source checking, policy verification against the current edition, a review log, and the fact that every figure in the document can be traced to something. Then invite the questioner to point at anything they doubt. Almost nobody does, because the question is usually about trust rather than about a specific line.

Where a document has flagged missing information rather than filling it in, say so and treat it as a feature. An application that admits it cannot yet confirm a finished floor level is more credible than one that quietly asserts a number.

What to say if an objector raises it

Objectors sometimes argue that a document produced with software should carry less weight. Answer on substance and keep it short.

The weight a document carries depends on whether its facts are right and its analysis sound, not on the software used to produce it. Nobody argues that a report is less reliable for having been typed rather than handwritten. If the objector has identified an actual error, deal with the error. If they have not, say so once and move on.

Where the point is raised in writing to the council, a brief note to the case officer is usually better than silence. Set out who prepared and checked the document, confirm that its facts have been verified, and leave it there. Committees respond well to a straightforward answer and badly to defensiveness. The same is true when a council asks who wrote your report.

Recording the review in your file

The file is what protects you, and it needs three things: a version history, a review record and a source list.

Keep the draft as issued and the submitted version as separate files so the changes made at review are visible. Record the reviewer's name, the date and what was checked, using a standing checklist rather than free text. Keep the sources behind every fact, particularly constraint data, measurements and policy references, in a single folder with the date each was retrieved.

Two years later, at appeal, that folder is the difference between a confident answer and a guess. Building an internal review checklist for submissions once and using it every time is less work than reconstructing your reasoning.

Terms of engagement wording worth considering

Client care documents are the right place to settle this, before a project starts rather than during a difficult meeting.

Consider stating four things. That drafting tools may be used to produce first drafts. That the named consultant reviews and takes professional responsibility for all submitted documents. Which report types require a separately appointed licensed or competent professional. And that no consultant can guarantee the outcome of a planning application.

One more point belongs there. Client material uploaded to any third party service raises confidentiality questions, and the only safe position is to check the current policies of any service you use before uploading confidential material, and to tell the client what you do. Where a client's information is commercially sensitive, agree the position in writing first.

This is general guidance on professional practice rather than legal advice, and members of professional institutes should read their own code of conduct alongside it. Pricing for drafting is published at PlanScope pricing if you need to set out costs to a client.