Version control between consultants on one application

The fastest way to weaken a major application is to submit reports that disagree with each other about the size of the scheme. A transport assessment quoting 148 units, an affordable housing statement quoting 150, and a design and access statement showing 147 on the plans will all be read together by a case officer, an objector and, if it goes that far, an inspector. Version control across a multi-consultant submission is dull work that decides how the application is received in its first week.

The fix is procedural. One controlled schedule of numbers, one register of drawing revisions, one person who says what has been issued.

Why inconsistency is the easiest thing for an objector to find

Objectors and consultees read across documents in a way that project teams rarely do. A resident with a spreadsheet will find a floorspace discrepancy in an afternoon, and a parish council with a retired surveyor on it will find three.

The damage runs past the error itself to what it implies about everything nobody has checked. Once an officer has found two conflicting unit numbers, every figure in the submission is treated as provisional, and the request for clarification arrives with a list rather than a question.

Statutory consultees behave the same way. A highway authority that finds the trip generation was calculated on a superseded parking layout will withdraw its comments and ask for a revised assessment, which resets the clock on the determination period whatever the extension of time says.

One controlled area and site schedule

Every number that appears in more than one document belongs in a single schedule owned by one person, usually the architect or the project manager. Nothing gets quoted from a drawing, an email or a previous version of a report.

The schedule needs, at minimum:

1. Site area, in hectares and square metres, with the red line drawing number and revision it was measured from.
2. Unit numbers by tenure, by bedroom count and by storey.
3. Gross internal and gross external floorspace by use, and the existing floorspace to be lost.
4. Parking and cycle spaces by type, and the number of accessible bays.
5. Building heights in metres above ground and above ordnance datum, and storey counts.
6. Existing and proposed hard surfaced area, for the drainage calculations.

Distribute it as a dated PDF with a revision letter, never as a live spreadsheet. A live file gets edited by whoever opens it last, and then nobody knows which version the noise consultant used. Name the revision in every report that relies on it, in the methodology section, so a reader can see which set of numbers produced which conclusion.

Site area deserves particular attention because so much hangs off it. Major development thresholds, biodiversity net gain baselines, drainage discharge rates and the fee calculation all key off the same figure, and a red line redrawn late in the process quietly invalidates all of them.

Aligning drawing revisions across reports

Each technical report should name, in its own document control page, every drawing it relied on with the drawing number and revision. Not "the architect's plans". The number and the revision.

That single discipline makes a late change traceable. When the ground floor plan moves from revision C to revision E, you can see in twenty minutes which reports need revisiting and which do not. Without it, the only honest answer is that everything needs rechecking, and on a major application nobody has time for that.

The reports most sensitive to drawing revisions are the ones built on geometry: daylight and sunlight, overshadowing, wind, visual assessment and anything modelled in three dimensions. A change to a parapet height or a setback that reads as trivial on a plan can change a daylight result. Visual work is sensitive in the same way, since photomontage methodology in a landscape and visual assessment depends on the massing model matching the submitted elevations exactly.

Issue sheets and who holds the master

One person holds the master register, and that person is not the busiest designer on the team. Give the job to whoever is coordinating the submission, and give them authority to refuse a report that arrives without a document control page.

The register lists every document and drawing intended for submission, its number, its current revision, its author, whether it is complete, and which schedule revision it used. Circulate it weekly during the run-up and daily in the final fortnight. The point of the weekly circulation is to make gaps visible while there is still time to close them.

Set a file naming convention at the start and enforce it. A submission arriving at the portal as forty files named by whoever exported them is a validation risk in itself, because the council's own checklist is matched against document titles.

Handling a late design change

Late changes are normal on a major scheme. The problem is not the change. It is the change that reaches four consultants and not the fifth.

Run it as a short formal loop. The change is described in writing with the affected drawing numbers, issued to everyone on the register including the ones you think are unaffected, and each consultant replies with one of three answers: no effect, effect assessed and reported, or effect requires further work with a time estimate. Keep the replies. When an officer asks later whether the acoustic report accounted for the revised plant location, the answer is a dated email rather than a guess.

Where the change lands after some reports are already final, resist the temptation to submit the old version and correct it later. A submitted report that assessed a superseded scheme is a defect on the file that an objector can point at for the whole determination period.

The pre-submission reconciliation check

Two days before submission, one person who did not write any of the reports reads the numbers across the whole pack. No technical review, only reconciliation.

The check that catches most errors is mechanical:

• Search every document for the unit number and confirm it matches the schedule.
• Search for the site area and the floorspace figures and confirm the same.
• Confirm every report names the schedule revision it used.
• Confirm every report's drawing list matches the drawings actually being submitted.
• Confirm the application form matches the schedule, including the fee calculation and the ownership certificate.
• Confirm the description of development is word for word identical on the form, the covering letter and every report cover.

The description of development is the one people skip, and it causes more trouble than any of the others. A description that differs between the form and the planning statement gives the officer a reason to query validation on day one.

Reports that carry condition ratings or graded judgements need the same treatment, because a grading that moved between drafts is easy to miss. The same care that goes into condition grading and defect schedules in a structural survey belongs in the reconciliation pass.

When an inconsistency surfaces after submission

Tell the case officer before they find it. A short letter identifying the error, explaining which figure is correct, confirming that the conclusions are unaffected and attaching a corrected page reads as competence. The same error found by an objector reads as carelessness.

Where the correction changes a conclusion rather than a typographical detail, expect re-consultation and agree an extension of time in writing. Where it changes the scheme itself, the choice is between a revised submission and, after a decision, a non-material amendment under section 96A of the Town and Country Planning Act 1990 or a variation under section 73. Neither is a substitute for getting the pack right the first time, and both cost weeks.

Keep the register after submission, too. Discharge of conditions applications two years later are much easier when you can still say which revision of which drawing the permission approved, and evidence-heavy chapters such as the supply chapter of an Employment Land Assessment often get reopened at that stage.

Drafting the narrative documents from one controlled set of figures is easier when the reports share a structure. You can generate drafts across the whole pack in PlanScope from the full report index and send each one for professional review. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.