Regenerating a section without breaking the document

Regenerate report section planning workflows go wrong in a predictable place. The new section is better than the old one, reads well on its own, and quietly contradicts three other parts of the document. The site area in the drainage section no longer matches the site area in the opening paragraph. A cross reference points at a section that has moved. The scheme description says four dwellings and the schedule says five.

None of that is caught by reading the regenerated section. It is only caught by reading the document.

When regenerating beats editing by hand

The decision is about the size of the change rather than the length of the text.

Regenerate when the input has changed: the scheme description, the site area, the unit mix, a constraint that was missed, the policy edition being cited, or the conclusion the section has to reach. A section built on a wrong premise cannot be edited into correctness, and trying produces text that argues with itself.

Edit by hand when the content is right and the expression is not. A figure to correct, a sentence order to fix, a paragraph to cut, a local plan policy number to update, a name to change. Hand editing keeps everything else in the document stable, which is worth a great deal.

The middle case is a section that is right in substance but needs a different emphasis for a particular officer. That is usually a hand edit too, because regeneration will change wording you had already settled.

On a paid PlanScope tier you can regenerate individual sections and edit in the platform, and reports can be saved and versioned, so both routes are available on the same document. The pricing page sets out which tier includes which.

Keeping the scheme description consistent

The scheme description is the spine. It appears on the application form, on the drawings, in the opening of every supporting document and usually in the conclusion of each one.

Fix one wording and use it everywhere, exactly. Not a paraphrase in the planning statement and a different paraphrase in the design and access statement, because the officer will read both and the difference will look like a substantive discrepancy even when it is not.

A short discipline that works: keep the agreed description in a single line at the top of your working file, copy it into each document, and when it changes, search every document for the old wording rather than relying on memory. A Planning Statement and a Design and Access Statement that open with identical descriptions of development signal a coordinated submission before anyone reads the argument.

Where the description changes after drafting, the places to check are the opening paragraph, the site and proposal section, the conclusion, any table of accommodation, and the compliance section that lists what is being applied for.

Cross references that break silently

This is the failure that causes the most embarrassment, because it is invisible until someone follows the reference.

The patterns to watch:

• References by section number, where regeneration or reordering has changed the numbering.
• References to a table or figure by number, where a table has been added or removed.
• References to an appendix that was removed when the section citing it was rewritten.
• References to a drawing number, where a revision has been superseded.
• References to another document in the submission by its title, where that document has been renamed.

The practical fix is to reference by name rather than by number wherever you can. "As set out in the drainage strategy" survives reordering. "As set out in Section 6.3" does not.

Where numbered references are unavoidable, do a single pass at the end searching for the word section followed by a digit, and check each one. It takes ten minutes on a long document.

Numbers repeated in several places

Every planning document has a handful of numbers that appear in more than one section, and a regenerated section will restate them from whatever it was given.

The usual suspects:

Build a short list of these for each project, with the agreed value, and check the list after every regeneration. It is unglamorous and it catches more errors than any other single step.

Where the draft contains a to be confirmed marker in place of a number, that is a deliberate safeguard rather than an oversight. The marker is there because the site fact was not available. Resolve it with the actual figure, and never with a plausible estimate, because an invented number in a submitted document is a professional problem that an unresolved marker is not.

Re-checking policy citations after a change

Policy references date faster than anything else in the document, and a regenerated section may reproduce citations from an earlier framework.

Two checks, every time.

National policy. The National Planning Policy Framework has been reissued more than once in recent years, and the current edition is organised by policy codes rather than the paragraph numbers older documents cite. Verify the citation against the published Framework at the time of writing and state the edition you are citing. Never carry a paragraph number across from an older document or from generated output without checking it.

Local policy. Check each cited policy against the adopted development plan, including whether the plan has been replaced, whether the policy number changed on adoption of a new plan, and whether a supplementary planning document you rely on has been withdrawn. An argument built on a superseded policy is worse than no argument, because it tells the officer the document was not checked.

Supporting guidance dates too. A British Standard reference should carry its year, and a guidance document reference should carry its edition.

Recording what changed and why

Version control on planning documents is usually treated as a filing question. It is really a liability question, because six months later someone will ask why a figure changed.

What to record for each saved version:

1. The date and the reason for the change, in one line.
2. Which sections were regenerated and which were hand edited.
3. The drawing revision the text describes.
4. Any input that changed, such as a revised site area or a new survey result.
5. Who reviewed the version.

Keep the superseded version rather than overwriting it. Where the change followed advice from a specialist or the case officer, note that too, because the reason for a change is the part nobody remembers.

Where part of the document needs a specialist author rather than a reviewer, the professional directory is the route to someone who can take that section and sign it off, and the review request records who signed what.

A final read through that catches the rest

Do this in one sitting, on the whole document, after the last regeneration.

• Read the document against the drawings, with both open. Every dimension, every count, every orientation.
• Search for each number on your repeated numbers list.
• Search for the scheme description wording and confirm it is identical everywhere.
• Search for to be confirmed markers and square brackets, and resolve every one.
• Follow every cross reference.
• Check the policy citations and their editions.
• Read the conclusion of each section against the conclusion of the document, looking for contradictions.
• Read the opening paragraph last, because after everything else has changed it is often the part that no longer fits.

Then have someone who did not draft it read it for sense. Not for accuracy, for sense. A reader who has never seen the site will notice the paragraph that assumes knowledge nobody has been given.

The honest position on iterative drafting is that it makes the writing faster and the checking more important. A document assembled in one pass by one person carries that person's consistency automatically. A document regenerated section by section does not, and the checking is what replaces it. Budget the time for it rather than hoping the last version was fine. If you want to see how the sections are structured before you start, the full list of report types shows what each document covers.

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. For specialist technical reports, qualified professional input may be required.