Briefing a consultant so the report answers the council

Briefing a planning consultant well takes about ninety minutes and saves two revision rounds. The brief has one job: to tell the author which validation requirement, which policy and which consultee the report exists to satisfy. Most technical reports that come back wrong come back wrong because the author was told the site address and the report type and nothing else.

For a self-builder or a small developer with three or four specialists to instruct on one scheme, that ninety minutes is also the only chance to make the reports consistent with each other.

Start from the validation list and the policy

Article 11 of the Town and Country Planning (Development Management Procedure) (England) Order 2015 lets a local planning authority require local information alongside the national requirements, provided the local list has been published within the previous two years and the requirement is reasonable in relation to the application. Download that list before you brief anyone.

Then quote it. A brief that says "Flood Risk Assessment in accordance with local list item 14" gives the author the wording they have to satisfy. A brief that says "we need an FRA" invites a generic document.

Do the same with policy. Name the adopted local plan policy numbers that the report has to engage with, and the relevant part of the national Framework. The author may know the policy better than you, but stating which ones you consider engaged sets the scope, and a disagreement about that costs far less before the work starts.

Where you are still working out which documents the scheme needs, our comparison of a chartered town planner and a planning agent covers who is best placed to tell you.

Naming the consultee who will read it

Every technical report has a reader beyond the case officer, and that reader decides whether the objection comes in.

Name the body in the brief and, where you know it, name the guidance that body publishes. A lead local flood authority with a published local standards document will assess your drainage strategy against that document, so the author needs to have read it. This single line in a brief prevents a large share of holding objections.

Ask the author what they need from the consultee too. Several will want a pre-application enquiry or a data request answered before they start, and those take time you should be spending now.

Supplying the site information you already hold

Authors bill for assembling information you are sitting on. Send a single package at the outset.

• A measured topographical survey with levels, in a named coordinate system.
• The red line boundary as a drawing and, if you have it, as a digital file.
• Title plan, and any covenants or rights of way you know about.
• Existing drainage information, including any CCTV survey or sewer records you have obtained.
• Photographs of the site and the surroundings, dated.
• Any previous applications on the site, with decision notices and officer reports.
• Earlier surveys, even old ones, and any pre-application advice you have received.
• The draft scheme drawings, marked with their revision.

Include the failures. A refused application from six years ago and the reason for refusal tells a technical author more about the council's concerns than any amount of policy reading.

Agreeing the assumptions before work starts

Every technical report rests on assumptions, and unstated assumptions are what make two reports on the same scheme contradict each other.

Write down the ones that matter. The development quantum and unit mix. Finished floor levels, or the fact that they are not yet fixed. The construction programme and its likely start date. Whether the existing buildings are being retained. Parking numbers. The assumed point of connection for foul and surface water. Whether a site is to be treated as brownfield or greenfield for run-off purposes.

Then circulate the list to every author on the scheme, and ask each to confirm they are working to it. A drainage strategy built on a 100 mm lower finished floor level than the flood risk assessment assumed is a straightforward way to lose four weeks.

One honest caveat. On small schemes the design is still moving while the surveys are commissioned, so the assumption list needs a version number and a date, and a rule about who reissues it.

Deliverables, format and revision rounds

Be specific about what arrives and when.

1. The deliverable itself, named, with the standard or guidance it follows.
2. Drawings and appendices, and whether a native file is provided alongside the PDF.
3. Number of revision rounds included in the fee, and the hourly rate beyond that.
4. Who responds to consultee comments after submission, and whether that is inside the fee.
5. A licence to use the report in the planning application and in any appeal.
6. Professional indemnity insurance confirmed in writing, at a level proportionate to the risk.

Point four is the one people skip. A holding objection arriving four months after submission, from a consultee asking three questions, needs the original author to answer it. If that work sits outside the appointment you will be negotiating a variation under time pressure.

Our notes on who should prepare a transport assessment and on choosing an arboriculturist and reading credentials go into the competence questions for two of the trickier disciplines.

Attendance at meetings and consultee calls

Decide up front which authors attend which meetings. A pre-application meeting where the highways officer raises an access concern is a meeting the transport author should be in, and a summary from you afterwards is a poor substitute.

Set out in the brief how many meetings are included, whether attendance is remote or in person, and who takes the note. Then circulate the note to everyone on the team, including the authors who were not there, because a concession made in a highways meeting often has drainage consequences.

Reviewing the draft properly

Read the draft against the brief rather than against your hopes for it. Four checks catch most problems.

Does the report answer the validation requirement you quoted, in words a validation officer will recognise. Are the policy references current, with editions stated. Do the assumptions match the list you circulated, including the drawing revision. Are the conclusions supported by something in the report rather than asserted at the end.

Then look for the gaps the author has flagged. A good technical author marks where site data is missing rather than filling it in, and those flags are instructions to you. Chasing them down before submission is what stops a validation query.

Where a first draft has been produced with AI assistance, the review is the same exercise with one addition: verify the site-specific facts and the policy citations independently, because that is exactly where a draft needs a human. PlanScope's own professional directory is the route for arranging review and sign-off by a qualified reviewer, and browsing the 66 report types will tell you which of them are labelled as needing a professional author by law.

This article is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. For specialist technical reports, qualified professional input may be required. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.