Writing a brief that gets a usable specialist report

Most disappointing specialist reports were ordered badly. The consultant answered the question they were asked, the question was wrong, and the document arrives three weeks before submission without the one calculation the case officer will want. A brief of half a page fixes more problems than a long review at the end.

The test of a good brief is simple. Could a competent consultant who has never spoken to you price the work accurately and produce something the validation officer will accept? If not, the gaps will be filled by assumption.

Why weak briefs produce weak reports

A consultant prices risk. A vague scope gets a defensive fee, a narrow method and a report written to protect the author rather than to support your application. That is rational behaviour on their part, and it shows up as caveats, missing site work and a conclusion that recommends further assessment.

The other failure is scope drift in the opposite direction. An acoustician asked for "a noise report" may produce a full assessment against BS 4142 when the council wanted a short statement about plant selection, and you pay for the difference. Both outcomes come from the same cause.

Stating the decision the report must support

Start the brief with the decision. Not the document, the decision. "This report supports a full application for 14 dwellings on a former builders yard, to be determined by the district council, where the officer has raised contamination as a validation requirement." That sentence tells the consultant which regime applies, who the audience is, and what a successful outcome looks like.

Then say what the report has to overcome. If there is an objection from the lead local flood authority, quote it. If a previous application was refused, attach the decision notice and the officer's report. Consultants write better documents when they can see the sentence they are answering.

Defining the site and the scheme precisely

Send the same information you would send to a contractor: the red line boundary as a drawing rather than a description, the topographical survey, the current and proposed layouts with levels, the schedule of accommodation, the intended use classes, and any constraints already identified. Where the scheme is still moving, say so and state which elements are fixed.

Attach the validation checklist. Many local requirements are specific about format, and a report that meets the national expectation but not the local one still holds up validation. If you do not know which documents the council expects, the report index groups them by category and the professional directory sets out the review route for drafts that need sign-off.

A brief that hides bad news produces a report that discovers it late. If you know the ground is made up, that the neighbours objected last time, or that the client will not pay for trial pits, put it in writing at the start and let the consultant price around it.

Specifying standards and output format

Name the standard and the version. BS 5837:2012 for trees, BS 10175 for contaminated land investigation, BS 4142:2014+A1:2019 for industrial and commercial sound, CIBSE TM59 for residential overheating, GLVIA3 for landscape and visual work, the statutory biodiversity metric for net gain. Where the council's guidance names a different method, that one governs.

Specify the deliverables as precisely as the method:

• A written report as PDF, with figures at a stated scale and an appendix of raw data
• The model or calculation file where the council or a reviewer will want to interrogate it
• Drawings in a format your design team can overlay, not images pasted into a document
• A short summary suitable for quoting in the planning statement
• Confirmation of professional indemnity cover and the author's membership of the relevant institute

The last point matters more than it looks. Councils increasingly ask who wrote a technical report, and a document signed by someone without the relevant competence invites a request for a second opinion. Our note on who can prepare an overheating assessment shows how that plays out for one report type, and accredited laboratories for soil and water analysis covers the same question for sampling.

Deciding how much assessment is proportionate

Ask the council what it expects before you fix the scope. A pre-application response, or even an email to the case officer quoting the validation list, often settles whether a statement or a full assessment is needed. The difference between a transport statement and a transport assessment on a small scheme can be several thousand pounds, and the officer has no reason to refuse to say which they want.

Where the answer is still uncertain, scope the smaller piece of work with a defined extension. That way the consultant can add the extra modelling on the agreed rate rather than repricing the whole job halfway through.

Programme, seasons and dependencies

Survey seasons are the hardest constraint in the whole programme and the one most often discovered late. Bat emergence surveys run broadly from May to September. Great crested newt environmental DNA sampling has a window from mid-April to the end of June. Reptile surveys need suitable temperatures in spring and early autumn. Breeding bird surveys sit in the March to August season. Traffic counts should avoid August and the weeks around Christmas, and parking surveys follow the same logic.

Put the dates in the brief, with the drop-dead date for the submission, and ask the consultant to confirm in writing that the programme is achievable. Then list the dependencies: which report needs the topographical survey first, which needs the drainage strategy, which needs the ground investigation. The specification of that topographical survey is itself worth getting right, as set out in our note on specifying a topographical survey.

Review points and draft stages

Build in a draft. One draft at 80 per cent, reviewed within a stated number of working days, catches the wrong baseline, the wrong scheme drawing and the missing policy reference while there is still time to change them. A single delivery at the end leaves you with an invoice and a document you cannot use.

State what the review is for. You are checking that the scope was met, the scheme described is the scheme being submitted, and the conclusions are expressed in terms the planning system uses. You are not editing the technical judgement, and a client who rewrites a consultant's conclusion has bought nothing.

Fee structure and what it buys

Ask for the fee broken down by stage: desk study, site work, assessment, reporting, and a separate line for meetings, planning committee attendance and responses to consultee comments. The last line is the one that saves arguments, because responding to a highway authority holding objection in month three is work that nobody scoped in month one.

Agree the number of revisions included, the rate beyond that, and who owns the data. Where the appointment may later move to a contractor, say so at the start, as covered in our note on novating a consultant appointment.

One honest caveat. A tight brief will not rescue an unsuitable scheme, and a consultant who tells you that early is worth keeping. The reports that fail at committee are usually the ones where the applicant asked for support rather than for an assessment.

PlanScope drafts the narrative documents around the specialist work, including the planning statement and the design and access statement, and flags where technical facts are missing so the brief can capture them. 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.

This is general guidance, not legal advice. Check validation requirements with your local planning authority before finalising any brief.