A quality assurance routine before a report leaves the office

Planning report quality assurance fails in a practice for a predictable reason: one person reads the document through once, looking for everything at the same time, and finds the typographical errors while missing the policy number that was renumbered two years ago. A routine fixes that by splitting the job. One pass checks facts against primary sources and nothing else. A second pass reads the document as a document. Different passes, written down, ideally different people, and a record of who did which.

Why a routine beats a careful read

Three failure modes account for most of the documents that come back from a council. Stale policy references, where a paragraph number or a plan policy has been superseded. Unverified site facts, where a constraint, an area or a drawing number was carried over and never checked. And borrowed structure, where a document follows a template that does not match this authority's validation list.

None of those is caught by reading for quality. They are caught by checking specific items against specific sources, which is a different cognitive task and belongs in its own pass.

The practices that get this right are usually the ones that got caught once. An invalid application costs a fortnight and a conversation with the client, and the second time around somebody writes a checklist.

Pass one: facts against primary sources

Work from a list, in a fixed order, with the source open. Nothing is confirmed from memory and nothing is confirmed from the draft itself.

1. Site address, site area in hectares or m², and the red line boundary against the location plan.
2. Constraints: flood zone from the Environment Agency Flood Map for Planning, designations and Article 4 directions from the national planning data service, listed buildings from the National Heritage List for England, protected sites and priority habitat from the government's magic mapping service.
3. Planning history, from the authority's own register, with reference numbers and decision dates.
4. Development plan policy numbers against the adopted plan document, not against a previous report.
5. National policy references against the current edition of the National Planning Policy Framework, naming the edition in the text, because the Framework has been renumbered and then restructured and readers may hold an older copy.
6. Application type, fee and the authority's local validation list.
7. Numbers that appear in more than one document: floor areas, unit numbers, parking spaces, drawing numbers and revision letters.

That last item is the one that catches practices out most often. A planning statement citing drawing 102 Rev B when the submitted pack contains Rev C is a validation query, and it is also the sort of inconsistency a hostile objector reads for.

Pass two: the document as a document

Only now read it for quality, and read it against the authority's validation checklist rather than against your own template.

What this pass looks for: whether each section answers the question the council asks, whether the assessment reaches a conclusion rather than describing policy, whether any claim is made without evidence behind it, whether the tone is consistent, and whether anything in it would embarrass the practice if it were read aloud at committee.

Cut the unevidenced sentences. A drafted document tends to produce confident general statements, and the ones to delete are those asserting what a council usually does, what applicants typically find, or how a policy is normally applied. If it cannot be attributed to a document, it goes.

Resolve every flagged gap

A PlanScope draft inserts a "[TO BE CONFIRMED]" marker wherever a site-specific fact is missing rather than inventing one. That is a deliberate safeguard, and the routine has to close each one.

Make the search for that token a formal step, run on the final file rather than the working copy, and log what each gap was resolved with. Where a gap cannot be closed because the information does not exist yet, say so in the document itself and explain how it will be provided, usually through a condition. A report issued with an unresolved marker is worse than one with an honest gap, because it reads as carelessness rather than candour. Our note on version control when report sections are regenerated covers the related problem of a resolved gap reappearing after a section is redrafted.

Who signs, and what they are signing

Be precise about this, because it is where liability sits. The person who signs is confirming that the document is fit to be submitted on the practice's name, that the facts in it have been checked, and that its conclusions are ones they are competent to reach.

Competence is the limit. Chartered professionals are bound by codes of conduct that prohibit acting outside their competence, and the practice's professional indemnity cover will be written around the services it declared. A planning statement, a design and access statement, a heritage statement at the lower tiers of significance and a transport statement for a small scheme are all within the reach of a general practice with planning experience.

Several report types are not, as a matter of law. An Environmental Statement under the Environmental Impact Assessment Regulations 2017 must be prepared by competent experts. Protected species surveys and mitigation licences require a suitably licensed ecologist. The statutory biodiversity metric requires a competent person under the Environment Act 2021 regime. Land contamination work is expected to follow BS 10175 and be carried out by suitably qualified and experienced persons. A Fire Statement at Planning Gateway One needs fire engineering competence under the Building Safety Act 2022 framework and Article 9A of the Development Management Procedure Order 2015. For those, a draft is a starting point for the specialist, and the professional directory is the route to someone who can review and sign it.

Recording the checks

A one-page sheet per document, kept with the file. Date, document name and version, who ran pass one and when, which sources were checked, who ran pass two, the list of resolved gaps, and the name of the signatory.

This takes a few minutes and earns its keep in three situations: when a council queries a fact and you need to show where it came from, when an appeal arrives nine months later and nobody remembers which plan version was current, and when the practice's insurer asks how documents are checked before issue.

Keep the version numbering on the file itself rather than in a folder name. Final, final-2 and final-client are how the wrong file gets submitted.

Building it into the fee

The honest objection to all of this is time, and the answer is to price it rather than absorb it. Quote the drafting and the checking as separate lines so the client can see what the second one buys, and allow a fixed proportion of the drafting time for it that you review after a few jobs rather than guessing once.

Two side effects are worth having. The practice gets a record of which documents needed the most correction, which tells you where the template is weak. And junior staff learn policy by checking it against the source, which is a better training than reading a finished report. Where applications do come back, why planning applications are returned as invalid lists the reasons councils actually give, and most of them are checkable in pass one.

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. See PlanScope pricing if your practice needs unlimited reports, your own branding and a saved project library.