Audit trails and version control for AI assisted documents

Version control on planning documents stops mattering right up until the moment it matters completely, which is usually the day an inspector asks why the flood risk assessment submitted in March says one finished floor level and the one in the appeal bundle says another. Nobody remembers. The file is called FRA_final_v3_FINAL.docx and it was last touched by someone who has left. The scheme is defensible and the evidence base looks careless, which in front of an inspector amounts to the same thing.

AI assisted drafting makes that risk sharper, because drafting is faster and revisions multiply. It also makes it easier to solve, because a drafted document starts life in a system that records what it did.

Why version history matters on appeal

An appeal is decided on the documents. The inspector reads what was submitted, what the officer report said about it, and what the appellant now says. Inconsistency between those three is the most common self-inflicted wound in written representations.

Three questions come up often enough to prepare for. Which version of a technical report was before the officer when the recommendation was written. Whether a figure changed between submission and determination, and if so whether the council was told. And who is responsible for the content, which matters where a report was prepared by someone other than the named author on the cover.

The third question has professional weight for anyone in RTPI membership, because the Code of Professional Conduct expects members to act with competence, honesty and integrity, and not to mislead. Answering it well takes a record, not a recollection.

What to record at each revision

Six fields carry almost all the value, and they fit on one line in a revision table on the inside cover.

Revision number. Date. Author or authors of the changes. Reason for the revision, in a short phrase rather than "updates". The sections affected. And the approver, meaning the person who checked it before it left the office.

Two additions are worth making on an AI assisted document. Record which parts of the draft were machine generated and which were written or rewritten by a person, at section granularity rather than paragraph. And record the date of the source data the draft relied on, because a flood zone or a listing entry checked in January and submitted in June may have moved.

That second point is the one most firms skip. A drafted document quoting a constraint is only as current as the day the constraint was checked.

Separating drafting from evidence

Keep two folders and never let them merge. One holds evidence: the survey data, the constraint printouts with the date visible, the correspondence with consultees, the topographical survey, the manufacturer data sheets. The other holds documents: the drafts, the revisions and the issued versions.

Evidence files are never edited. If a survey is updated, the new file sits alongside the old one with its own date, and the old one stays. Documents are edited constantly and carry revision numbers.

The test is simple. If an inspector asked for the source of any number in any submitted document, could you produce a dated file containing that number without opening a word processor? Where the answer is no, the number is an assertion. PlanScope drafts insert a [TO BE CONFIRMED] flag wherever a site specific fact is missing rather than inventing one, and the discipline that flag encourages is exactly this: a number in the document should point to a file in the evidence folder. The wider habit of checking a draft for factual errors to look for in a drafted planning document works the same way.

Naming conventions for submissions

A convention only works if it survives someone in a hurry. Keep it short, put the variable parts in a fixed order, and never use the word final.

So a file reads 2431_FRA_Rev1_ISSUE_20260317. Dates in year, month, day order sort correctly in any file listing, which is the whole reason for the format. Drop the client name, the site address and any personal name from the filename, because all three change and none of them help.

One rule beyond the convention. The file uploaded to the portal and the file in your own folder must be byte identical, which means exporting once and uploading that export rather than exporting twice.

Keeping the source data with the document

An issued document should travel with a small evidence pack, even if nobody asks for it. Constraint checks with the date and the source visible. The survey or data file the figures came from. The consultee correspondence relied on. And a note of any assumption the document makes that could later be questioned.

Where a document was produced in a platform, use the platform's own versioning rather than downloading and renaming. PlanScope's paid tiers save and version reports and allow individual sections to be regenerated, so the history of a document stays attached to it instead of scattering across a shared drive. Regenerating one section leaves the rest intact, which is a cleaner audit trail than rewriting a whole report to fix a paragraph. The Professional tier adds a saved project library for firms carrying many live jobs at once.

One caution on confidentiality. Before uploading anything sensitive, check the current policies published on the site, and apply your own client confidentiality rules to third party platforms the same way you would to any other supplier.

Answering a question about authorship

Councils and inspectors do ask. Answer plainly, in one sentence, and have the record behind it.

The honest and defensible position is that the document was drafted with AI assistance and reviewed, corrected and approved by a named professional who takes responsibility for its content. That is a statement you can make only if it is true, which means the review has to have happened and to have left a trace. A revision table showing a named approver on the issued version is that trace. The question of when a council asks who wrote your report is worth preparing for before it lands.

For report types where a licensed or competent professional is legally required, such as a biodiversity net gain assessment under the Environment Act 2021 regime, a protected species survey under the habitats regime, or a fire statement under the Building Safety Act 2022 framework, the answer has to name that professional. A draft is a starting point for them, and never a substitute. The professional directory is the route to a reviewer who will sign off a draft.

Retention after determination

Keep the full record for as long as the development could still be challenged or enforced against, which is longer than most firms assume. Enforcement time limits, judicial review of the grant, a section 73 variation five years later and a discharge of conditions application after a change of ownership all reach back into the file.

A practical retention rule: keep the issued versions, the revision tables and the evidence pack indefinitely, and keep intermediate drafts for the life of the project plus the period your professional indemnity insurer requires. Ask the insurer rather than guessing, because the answer differs between policies and it is the answer that will matter if a claim arrives.

Before the next submission, write the revision table into your document template rather than promising to add it later. Building an internal review checklist for submissions is the other half of the same job.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. For specialist technical reports, qualified professional input may be required.