Writing a consultant brief you can hold someone to
Asked to assess noise, a careful acoustician prices a full survey and an aggressive one prices a desk review. Both are honest answers to the same words, and neither is comparable.
A technical consultant brief for planning work earns its keep in two places: when the report arrives and when the fee proposals are compared. A brief that says "undertake a noise assessment" produces a document that may or may not answer the question the council asked, and three fee proposals that cannot be compared with each other because each consultant has guessed at a different scope.
The fix is not a longer brief. It is a brief that names the decision, the standard, the deliverable and the dependencies, which fits comfortably on two pages.
Why vague briefs produce vague reports
Consultants price what they read. Asked to "assess noise", a careful acoustician will scope conservatively and price for a full survey. A commercially aggressive one will price for a desk review and caveat the result. Both proposals are honest responses to the same words, and they are not comparable.
Compare that with a brief that says: assess plant noise from the proposed kitchen extract and refrigeration at the nearest noise sensitive receptor in accordance with BS 4142:2014+A1:2019, including a background sound survey over a representative weekday night, and advise on the plant specification and mitigation required to achieve a rating level not exceeding the measured background.
Now every proposal covers the same work. The prices differ on rate and efficiency rather than on scope, which is what a comparison should test.
Stating the decision the work must inform
Write one sentence saying what the output is for. It changes the work more than any other line in the brief.
A report written to support a planning application is a document for an officer, structured around the policy test, with a clear conclusion. A report written to tell the client whether to buy the site is a risk assessment, and it should say what could go wrong rather than argue a case. A report written for an appeal needs to survive cross examination and has to disclose its assumptions explicitly.
Consultants asked to produce a planning report and then handed it to a funder, or to an inspector, routinely have to rewrite it. That rewrite is a variation, it is chargeable, and it was avoidable.
Deliverables, formats and revision rounds
This is the section most briefs omit and most disputes concern.
| Specify | Why it matters |
|---|---|
| File formats, including an editable version | A PDF only deliverable cannot be updated when a drawing changes |
| Number of revision rounds included | Otherwise every comment becomes a variation |
| Appendices and raw data | Survey sheets, model files and metric calculations belong to the project |
| Drawings and figures, with scale and revision | A figure that cannot be submitted is not a deliverable |
| Licence to use the report | For the application, for appeal, and by a purchaser or funder |
| Who the report is addressed to | Reliance by a third party needs saying up front |
Two revision rounds is the usual fair allowance: one for client and design team comments, one for the authority's consultation response. Anything beyond that is new work and should be priced as such, which protects the consultant as much as the client.
The raw data point is worth insisting on. A biodiversity metric file, an acoustic model or a daylight model that stays with the consultant makes a change of consultant expensive and a reassessment slow.
Site access, information and dependencies
A consultant's programme depends on things the client controls, and the brief should list them with dates.
- the drawing set the assessment is based on, named by number and revision
- the topographical survey, and whether levels are to ordnance datum
- site access arrangements, including keys, induction and any need for an escort
- third party permissions for access to neighbouring land, and who obtains them
- existing reports being relied on, and whether reliance has been confirmed
- the point at which the design is frozen for assessment purposes
That last item prevents the commonest and most expensive failure: an assessment carried out on revision C while the architect works on revision F. Freeze the drawings, record the revision in the brief, and treat any change afterwards as a variation on both sides.
An assumptions register is the other useful device. Ask the consultant to list every assumption on a single page at the front of the report. It takes them ten minutes and it tells a reviewer exactly where the soft ground is.
Programme and the consequence of slippage
Survey seasons are the hardest constraint in planning work and the one clients underestimate. Bat emergence surveys run from May to September. Great crested newt environmental DNA sampling has a window from mid April to the end of June. Reptile surveys need April to October with the best results in spring and early autumn. Botanical survey needs the growing season.
Miss a window and the programme slips by up to a year, not by a few weeks. So the brief should state the survey window being targeted, the date by which the appointment must be in place to hit it, and what happens if the client's information is late.
A Preliminary Ecological Appraisal can be carried out at any time of year and will tell you which seasonal surveys are needed, which is why it should be the first ecology appointment rather than an afterthought. Where protected species are involved, the licensing timetable sits on top of the survey timetable, and how a protected species mitigation licence works explains why that matters for the programme.
Liquidated damages in a consultant appointment are rarely worth the argument. Staged payment tied to deliverables achieves more, because it aligns the consultant's cash flow with the programme without needing anyone to prove loss.
Sign off, review and who carries liability
Three things to settle before signing.
The professional indemnity level and the period for which it will be maintained. For a report that supports a planning permission, cover needs to outlast the application by years, and a consultant who lets cover lapse leaves the client with nothing to claim against.
Whether a third party can rely on the report, and how. A funder, a purchaser or a contractor usually needs either a reliance letter or a collateral warranty, and both are easier to agree at appointment than two years later.
Who signs the report. For disciplines where competence is regulated or licensed, the brief should require the named individual with that competence to be the author rather than a reviewer of someone else's work. The same discipline applies to highway design, where technical approval competence is a formal requirement rather than a preference.
Where the report needs independent sign off before submission, the professional directory is the route to a reviewer with the right standing.
Comparing fee proposals on the same basis
Build a simple comparison table before the proposals arrive, with a row for each element of the brief, and fill it in as they come. The rows that expose the differences:
- Is the survey included, and how many visits.
- Is the site visit included, or priced separately.
- How many revision rounds.
- Is the consultation response included.
- Is attendance at a meeting or committee included.
- Is appeal support included, and at what rate.
- What is excluded, in the consultant's own words.
Row seven is the one that decides it. A proposal with a short exclusions list and a higher fee is frequently cheaper than a low fee with half a page of exclusions, and the only way to see that is to read both.
And ask every bidder the same clarification questions in writing, with the answers circulated to all of them. It takes an afternoon and it removes most of the ambiguity that produces disputes later.
This is general guidance, not legal advice. For specialist technical reports, qualified professional input may be required. Check the position with your local planning authority or a qualified professional before relying on it.
Browse the 66 report types on PlanScope to see the scope each one usually covers before you write the brief. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
What makes a technical brief enforceable?
Naming the standard the work is to be carried out under, the decision the output informs, the deliverable format, the number of revision rounds included and the information the client will supply with dates. Those five items turn a request into a scope that can be measured against what arrives.
How many revision rounds should a brief include?
Two is the usual fair allowance: one for client and design team comments and one for the authority's consultation response. Anything beyond that is new work and should be priced separately, which protects the consultant as much as the client when the scheme changes.
Should I ask for the raw data and model files?
Yes. A biodiversity metric file, an acoustic model, a daylight model or survey sheets held only by the consultant make a change of consultant expensive and a reassessment slow. Specify that appendices, raw data and editable files form part of the deliverable at the outset.
Why does freezing the drawing revision matter?
Because the commonest and most expensive failure is an assessment carried out on one revision while the architect works on a later one. Name the drawing numbers and revisions the assessment is based on in the brief, and treat any change afterwards as a variation on both sides.
How do I compare fee proposals properly?
Build a comparison table with a row for each element: survey visits, site visit, revision rounds, consultation response, meeting attendance, appeal support and exclusions. The exclusions row usually decides it, because a higher fee with few exclusions often costs less than a low fee with many.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.