Version control when report sections are regenerated

Regenerate the flood risk section of a report and the drainage conclusions two sections later may now contradict it. That is the practical problem with version control planning report sections, and it gets worse the more selectively you edit. A document assembled from independently produced parts is internally consistent only if somebody checks it, and the check has to happen after the last edit rather than after the first.

PlanScope lets paid users edit in the platform, regenerate individual sections, and save and version reports. The versioning tells you what changed. It does not tell you what the change broke.

Why regenerating one section breaks the rest

Planning reports are more interconnected than they look. Four kinds of dependency cause almost all the trouble.

Cross references. A section that says "as set out in section 4.2" when section 4 has been rewritten and the numbering has moved.

Carried figures. A floor area, a unit count, a flood zone, a distance to a designated site: quoted once where it is derived and then repeated in the summary, in the policy assessment and in the conclusions. Change it in one place and the document now contains two answers.

Conclusions that depend on findings. A conclusion that no protected species survey is required, written before the ecology section was regenerated to record a preliminary roost assessment recommending emergence surveys.

Tone and position. A section rewritten in a more concessive register than the rest, which reads as though the applicant has changed position halfway through.

The last one is the hardest to spot and the most damaging on a contested application, because an objector will quote the concessive passage back at committee.

Cross references and internal consistency

A checking pass that takes twenty minutes on a 40 page report:

1. Search the document for every section number reference and confirm each points where it should.
2. Search for every figure that appears more than once, starting with areas, unit numbers, heights and distances, and confirm they agree.
3. Read the executive summary last, against the current body, and rewrite it rather than patching it.
4. Read the conclusions of each section against its own findings.
5. Check the document title, the site address and the application description against the application form.
6. Check every drawing number quoted in the text against the current drawing schedule.

Point six is the one that causes trouble after submission rather than before. Reports quote drawing numbers, drawings get revised, and a report referring to revision A when revision C was submitted invites the officer to ask which scheme is being assessed.

Where the factual content is what changed, the wider checking approach is set out in our note on factual errors to look for in a drafted planning document.

Keeping a revision history on the document

Put it on page two, not in a project management system nobody outside the office can see.

The last row is the one most often missing and the one an officer relies on most. A report that states which drawing revision it describes can be checked in a minute. One that does not has to be read against three possible drawing sets.

Never reissue a document under the same revision. If a typographical correction goes out after a document has left the office, it is a new revision, even if the change is a comma.

Matching document revisions to drawing revisions

The relationship is one to many, and it needs a single owner.

On any project with more than a handful of documents, keep one schedule listing every drawing and every report, with the current revision of each and the date. Issue the schedule with every submission. Officers use it, consultees use it, and it settles arguments about what was submitted six months later.

A design and access statement is the document most exposed to this, because it describes the scheme in words and pictures and every drawing change touches it. The approach to writing one that survives revision is covered in our note on drafting a design and access statement an officer can use.

Where a report has been regenerated in sections, record on the front which sections changed. A reviewer who knows that only sections 3 and 7 moved will read those two carefully. A reviewer given a whole new document will skim all of it.

What the council holds on the file

This is the point that makes document control a planning issue rather than an office housekeeping issue.

The authority determines the application on the documents before it. If permission is granted, the approved plans condition lists the drawings and often the reports by title and revision, and those listed versions are the permission. A report you consider superseded, still sitting on the file and still listed, is the version that binds.

So three rules:

Submit a complete document set rather than replacement pages. Councils do not reliably insert loose pages into an online file, and a reader who downloads the original document will not see your amendment.

When you supersede something, say so in writing: the document title, the old revision, the new revision, and a request that the earlier version be marked superseded on the public file.

Before the decision is issued, check the draft conditions against your own schedule. If the plans condition lists a revision you have replaced, raise it then. Correcting it afterwards means a section 96A application.

Reissuing during determination

Reissuing mid-determination is normal and it has consequences.

The statutory publicity has run against what was submitted. A revised document that changes the substance of the proposal may require re-consultation, which resets part of the timetable and gives objectors a fresh opportunity.

The practical approach:

• Batch changes rather than issuing a revised document every fortnight. Officers find a stream of revisions harder to handle than one consolidated reissue.
• Tell the officer before you send, and agree whether it will be treated as an amendment to the application or as further information.
• Include a short covering note listing what changed and why, keyed to the consultee comment or officer request that prompted it.
• Never send a revised report without the revision letter changed and the revision table updated.

A naming convention that survives the project

Simple, and applied by everyone from the first day:

Project code, document type, document number, revision, date. For example a planning statement might be issued as "2431-PS-001-RevC-20260926". Sort order then matches issue order, the revision is visible without opening anything, and nothing called "final" or "final v2" ever appears.

Three rules that matter more than the format itself. No spaces or punctuation beyond hyphens, because some council portals mangle them. The revision in the file name and inside the document, matching. And one person who owns the schedule.

An honest note on where this goes wrong even with good systems. Regenerating a section is quick, which means it gets done late, often the evening before submission, by someone who then has no time to run the consistency check. Build the check into the programme as a task with a name against it, a day before the submission date rather than an hour.

If you want the per-report or unlimited option for teams producing several documents per scheme, see PlanScope pricing, and you can enter your postcode to see which reports a site is likely to need.

This is general guidance, not legal advice. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.