Records to keep when an AI-assisted document is submitted

If you sign off a document that was drafted with AI assistance, the question that matters is not how it was produced. It is whether, two years later, you can show where each figure came from. Ai assisted planning document records exist for that moment: an inspector asking which edition of the Framework a citation came from, a client asking who checked the flood zone, a professional body asking what you reviewed before you put your name to it.

The record takes minutes to keep at the time and is close to impossible to reconstruct afterwards.

Why the record matters later

Four situations bring it up. An appeal, where your document becomes evidence and the source of every number can be tested. A complaint to a professional institute, where the question is what you did before signing. A claim, where your insurer asks for the file. And a validation or enforcement query, where the council asks whether what you submitted described the site accurately.

In each case the issue is traceability rather than authorship. Nobody is going to ask whether a paragraph was drafted by a person or a tool. They are going to ask what the paragraph was based on.

The weak point in an AI-assisted document is specific and predictable: assertions that read as authoritative but have no recorded source. A fluent sentence about background sound levels or flood zone classification carries the same confidence whether it was measured or guessed, and only the record tells the difference.

What to keep at drafting stage

Capture the inputs as you go rather than at the end.

• The site identification used: address, postcode, and the boundary as drawn or confirmed, with the date.
• The outputs of any automated constraint check, saved as a dated file rather than relied on from memory, because the underlying datasets are updated.
• The list of documents uploaded or supplied, with their own dates and authors.
• The answers given to any guided questionnaire, because those answers drive what the draft says about the project.
• Each draft version, with a timestamp, kept rather than overwritten.
• Every flag the draft inserted where a fact was missing, and a note of how each was resolved.

PlanScope drafts insert a "[TO BE CONFIRMED]" marker wherever site-specific information is absent. Treat those markers as a checklist and record the resolution of each one, because an unresolved marker that reaches a submitted document is the most visible possible failure of review.

Where sections are regenerated during drafting, the version record is what stops a corrected passage being quietly replaced by an older one, which is the practical problem behind version control when report sections are regenerated.

Sources and the evidence behind each figure

Keep a source register as a table alongside the document. One row per figure or assertion that could be challenged, with five columns: the statement, the source, the edition or version, the date you checked it, and who checked it.

Two rules make the register useful. Record the edition as well as the document, because policy is reissued and maps are updated. And record a measurement's date, because a flood map checked three years ago is not evidence of today's classification.

Where a figure cannot be sourced, the honest options are to measure it, to cite the uncertainty, or to remove it. Carrying an unsourced number into a submitted document transfers the risk to whoever signs.

Who reviewed what, and when

A review record needs more than a name and a date. It needs the scope: which sections were reviewed, against what, and what was outside the reviewer's remit.

An acoustician reviewing a draft is not reviewing the heritage section. A planner reviewing policy coverage is not verifying the ecology survey windows. Where a document has multiple contributors, the scope statement protects each of them and tells the reader who stands behind which part.

PlanScope's professional review flow records a status sequence of sent, accepted, in review, changes requested, signed off, rejected and expired, which gives a dated trail of the request and its outcome. Keep your own copy of that trail with the project file, together with the version of the document that was reviewed, because the reviewed version is the one the reviewer is answerable for. The professional directory is the route to requesting that review.

A worked appeal example

This is illustrative. A commercial scheme is refused on noise grounds and goes to appeal by inquiry. The appellant's noise chapter states a background sound level and a rating level, both drafted into a document that also covers policy and amenity.

In cross-examination the author is asked when the background was measured, with what instrument, and whether the calibration certificate is in the appendix. The answer is that the figures came from an earlier report for a neighbouring site. The chapter loses most of its weight, and the rest of the document is read more sceptically because one section turned out to be unsupported.

Nothing about that outcome depends on how the chapter was drafted. It depends on whether the record existed.

Retention and where to store it

Keep the record for as long as the document could matter, which is longer than most people assume: the life of the permission, the period in which conditions are discharged, and the limitation period for a claim. Your insurer's requirements may be longer still, so check the policy rather than guessing.

Store it with the project file in your own systems as well as inside any platform. Export the drafts, the source register and the review trail, and keep them where a successor could find them.

One caution on confidentiality. PlanScope's site does not publish terms or a privacy policy, so the only safe position is that users should check the site's current policies before uploading confidential material, and should think carefully before uploading third party documents they do not own.

A minimum record set

If you keep nothing else, keep these seven items for every AI-assisted document you submit.

1. The final submitted version, exactly as submitted, with the date.
2. The source register, with editions and dates checked.
3. The dated output of any automated constraint check relied on.
4. The resolution of every missing-fact flag the draft inserted.
5. The reviewer's name, qualification, scope and date, with the version reviewed.
6. The instructions you received from the client, and any limitation on scope you agreed.
7. A short note of what you verified personally, as distinct from what you accepted from others.

The seventh is the one people skip and the one that answers the hardest question. Explaining that distinction clearly is also what makes an AI-assisted draft defensible to a client or a committee, which is covered in explaining an AI-assisted draft to a client or a committee.

Where the deadline is tight, the record is the first thing to be dropped and the last thing you want missing, and the discipline for working at pace is set out in drafting to an appeal deadline without cutting corners.

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