Writing a consultant brief that avoids scope creep

A consultant brief planning report that comes in on time and on fee usually started as two pages written before anyone was asked to quote. Scope creep is not caused by consultants being difficult. It is caused by briefs that describe a subject rather than a deliverable, leaving the boundary between what was bought and what was assumed to be settled later, when one party is already out of pocket.

Write the brief once, send the same one to everybody, and the fee proposals become comparable. That alone is worth the hour.

What a brief has to define

Six things, and a brief missing any of them will produce a variation.

The site, by address, red line plan and area. The proposal, described as it will be described on the application form, with the unit count or floorspace figure that drives the work. The purpose, which is the specific decision or application the report supports. The audience, which is normally a named local planning authority and sometimes a specific consultee. The policy or standard the report must be prepared against. And the deliverable itself, in a stated format at a stated stage of the design.

Purpose is the one people leave vague. A noise survey for a planning application, a noise survey to discharge a condition and a noise survey for an appeal are three different jobs with different levels of rigour, and a consultant who was told the first cannot be criticised for not delivering the third.

Deliverables, format and review rounds

State what lands on your desk. A signed PDF report. The number of copies. Any drawings, at what scale and in what format. Any model files, calculation sheets or data exports. A non-technical summary if the council will publish it.

Then state the review process, because this is where fees quietly double. Two rounds of comment is normal: one on a draft, one on the report as revised. Say so in the brief. A consultant who priced two rounds and receives five sets of comments from the client, the architect and the client's solicitor will charge for the difference, and will be right to.

Set out who is entitled to comment. A single consolidated set of comments from one named person, by an agreed date, is the arrangement that actually works.

Assumptions and exclusions stated up front

This is the section that does the most to prevent an argument later, and the section most briefs omit.

Ask the consultant to state, in their proposal, what they are assuming and what they are excluding. Then read it properly. The usual candidates:

• Site access arrangements and who arranges them
• Whether third-party data purchases, search fees or licence costs are included
• The number of site visits and whether a return visit is chargeable
• Whether attendance at meetings, pre-application discussions or committee is included
• Whether responding to consultee comments after submission is included
• Whether reissuing the report after a design change is included
• Whether appeal support, including a proof of evidence, is included

The last two are where most disputes sit. A design change that moves a building 4 m is trivial for the architect and means a new calculation run for the daylight consultant.

Our companion note on writing a brief for a specialist planning report goes into the technical scope for individual report types, which sits alongside the commercial framing here.

Programme and dependency on other consultants

Most specialist reports depend on somebody else's output. The drainage strategy needs the topographic survey. The biodiversity metric needs the habitat survey. The energy statement needs the final areas and fabric build-ups. The transport work needs a layout that is not going to change.

Write the dependency into the brief as a date and an input, not as a hope. "Report issued four weeks from receipt of the approved layout and topographic survey" is enforceable. "Report issued by the end of March" is not, because the consultant will be waiting for something that arrives on 28 March.

Seasonal constraints are a dependency too. Ecological survey windows, noise surveys avoiding school holidays, traffic counts in neutral months, daylight modelling benchmarks. A brief that sets a submission date without checking the survey calendar is setting a date that will move.

State who holds the programme. On most projects that is the architect, which means the architect needs to know every consultant's lead time and dependency, in writing, before the programme is issued.

How to compare fee proposals fairly

Put them in a table and normalise them. Same scope, same rounds, same exclusions.

The lowest number is rarely the lowest cost. A proposal that excludes consultee responses will cost more than one that includes them, on any application where a consultee comments, which is most of them.

Ask each consultant to confirm in writing that their fee covers the brief as written, with any exclusions listed. That one sentence converts an ambiguous quote into a comparable one.

Managing variations

Agree the mechanism before you need it. A variation should be a short written instruction identifying what changed, the agreed additional fee and the effect on the programme, confirmed by both sides before the work is done.

Verbal instructions on site and requests by message are how small variations become invoices nobody recognises. Neither side benefits.

Where the change originates with the client, pay for it. Where it originates with a consultee or a council request that could not reasonably have been foreseen, it is still usually a variation, and a brief that pretends otherwise just moves the argument to the end of the job. The exception is rework caused by an error in the consultant's own output, which is not a variation and should be said so plainly in the appointment.

Keep a running variation log. On a scheme with six consultants it is the only way to know what the evidence base has actually cost.

Sign off and handover of data

Define what you receive at the end and what you may do with it.

The report as issued, with version number and date. The underlying data: survey files, calculation models, GIS layers, photographs with location references, measurement logs. A licence to use the material for the application, for discharge of conditions and for any appeal on the same scheme, which is worth naming explicitly because a licence limited to the original application is unhelpful two years later.

Ask for the raw data even when you have no immediate use for it. The consultant who did the original ecology survey may not be available when the biodiversity gain plan is being prepared, and reconstructing a habitat baseline without the original files means surveying again.

Competence checks belong in the brief too, alongside the commercial terms. Our note on independence and conflicts of interest in planning evidence sets out where that matters most, and where a report needs signing off by someone with the relevant competence, the professional directory is one route to a reviewer.

A PlanScope draft can give you the structure and the policy framing before you go out to fee, which makes the brief more specific and the proposals easier to compare. Browse the report types by category to scope what the application actually needs. 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 the position with your local planning authority or a qualified professional before relying on it.