Writing a survey brief that gets you useful work back

Write the survey brief backwards. Start with the sentence the council's validation officer will read, work back to the conclusion the report has to reach, then work back again to the work needed to reach it. A survey brief planning teams produce this way is usually a page and a half, and it removes most of the reasons technical reports get rejected at validation or come back short at condition discharge.

The alternative is an email saying "can you price a bat survey for this site", which is how a scheme ends up with a preliminary roost assessment in November and no emergence survey window until the following May.

Start from the decision the survey has to support

Name the decision at the top of the brief. Not the report type, the decision.

"The council's validation checklist requires an ecological appraisal for any application affecting a building with bat roost potential. The appraisal has to conclude whether further survey is required, and if so which surveys and when." That tells a consultant what success looks like.

Compare "we need an ecology report", which leaves the consultant to guess whether you want a screening opinion, a full appraisal, a survey programme or a licence application, and to price defensively for all four.

Then state the secondary decisions. Will this report also serve a Building Regulations submission, a discharge of condition, a funder's due diligence, or a land transaction. Consultants scope and insure differently when they know, and a report written for one purpose rarely stretches to another.

Define the site before anyone prices it

Half the price variation between proposals comes from uncertainty about the site rather than about the work.

Supply a drawing with the red line application boundary and any blue land, at a stated scale with a north arrow and a bar scale. Supply the site area in hectares and the existing and proposed floor areas by use. Say who owns the access and whether the consultant can get on site without an appointment.

Then say what is already known. Previous reports, including ones with unwelcome findings. Pre-application advice in full. Planning history with application references. Any constraint the authority has already identified.

Withholding an earlier report never works. The consultant prices for work already done, and the council's file may hold a copy anyway.

Name the standard rather than the outcome

This is the line that separates a usable brief from a wish list.

Write "arboricultural survey and impact assessment prepared in accordance with BS 5837:2012, with a tree constraints plan and a tree protection plan". Do not write "tree report confirming the trees can be retained". The second is asking for a conclusion, and a consultant who agrees to supply it has told you something about the value of their opinion.

Name the standard precisely, with the year and the amendment where one exists. BS 4142:2014+A1:2019 rather than BS 4142. BS 10175 rather than "a contamination report". CIEEM's ecological impact assessment guidelines rather than "an ecology assessment". Where competence is defined by a scheme or an institute, say which, as the notes on geotechnical competence and Eurocode 7 and overheating assessment competence set out for two very different disciplines.

If laboratory analysis is involved, say whether accredited testing is required, because laboratory choice matters to whether the results will be accepted.

Deliverables, formats and drawings

List the physical things you expect to receive.

The report, in PDF and in an editable format if you need to extract text. The figures, with the scale at which they must remain legible, normally A3. Any drawings required as CAD or as georeferenced files. Raw survey data where a later reviewer may need it, which is common for noise and traffic work. A non-technical summary if the application will attract public interest.

Say how many rounds of comment are included. Two is normal: a draft for client comment and a final. A brief that is silent on this produces either one unreviewable draft or an open-ended series of revisions.

And say explicitly whether the report is to be addressed to you or to a project company, because changing the addressee after issue is not always straightforward.

Who talks to the consultees

Consultee liaison is the item most often left undefined and most often the source of a variation claim.

Decide, in writing, who contacts the lead local flood authority, the county ecologist, the highway authority, the conservation officer or the water undertaker. Decide who attends any scoping meeting. Decide who pays for pre-application advice where the discipline needs it.

Then set an assumption. "The fee includes up to three written exchanges with the county ecologist and one scoping call." That gives you a baseline to price against and gives the consultant a defensible point at which additional work begins.

Programme, seasons and the date that matters

Give the target submission date and the date the report has to be with you, which should be at least three weeks earlier to allow for review and correction.

Then ask the consultant to tell you, in the proposal, the earliest date each element can be completed and what happens if a seasonal window is missed. Ecology is the obvious case, with survey windows measured in months rather than weeks. Traffic counts avoid school holidays and December. Parking surveys under the Lambeth methodology need midweek and weekend overnight counts outside holiday periods. Ground investigation takes longer and costs more in a wet winter.

Build the programme backwards from the tightest constraint. And check whether work already done is still usable, because the question of whether a survey is still valid is answered differently by different disciplines and different authorities.

Agreeing how the scope changes

Every technical survey finds something unexpected. The brief should say what happens next.

1. The consultant notifies the client in writing before carrying out work outside the agreed scope.
2. The notification states what was found, what additional work is proposed, why it is needed and what it will cost.
3. The client confirms in writing before the additional work starts.
4. Agreed rates for additional work are set out in the appointment, by grade and by day.
5. Where the additional work is urgent, a stated sum can be authorised verbally and confirmed within a working day.

Five sentences in the brief, and they remove most fee disputes. They also protect the consultant, who would generally rather ask than absorb.

One honest uncertainty. Local validation checklists differ enough between neighbouring authorities that a brief written from the national requirements alone will sometimes miss a local one. Read the council's own checklist before writing the brief, and if the requirement is ambiguous, ask the validation team rather than the case officer, because they are the people who will reject it.

For specialist technical reports, qualified professional input may be required, and for some report types a licensed or competent professional is legally required rather than advisable. Browse the PlanScope report types to see which documents a scheme is likely to need, and use the professional directory when a draft needs review and sign-off.

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.