Writing a scope of works that gets the report you need

Most disputes about a technical report are disputes about scope, and almost all of them were avoidable at the point the brief was written. A scope of works that names the deliverable, the standard, the number of revision rounds and the exclusions turns a fee proposal into something you can compare and something the consultant can price honestly. A one-line email asking for a quote for an ecology report produces three proposals that cannot be compared at all.

Write the brief before you ask for fees. It takes an hour and it saves the argument.

What a brief has to state before a fee is quoted

A consultant pricing a job needs to know what they are being asked to prove, for whom, and by when. Give them:

• The site: address, a red line plan, area in hectares, and current use.
• The proposal: description of development, quantum, storeys, and the drawing set available with revision numbers.
• The planning status: pre-application, live application with a reference, appeal, or discharge of a specified condition, with the condition wording quoted in full.
• The authority, and any local validation requirement or consultee comment the report has to answer.
• The audience: the case officer, a statutory consultee, an inspector, or a lender.
• The programme, with the date the report is needed and what happens after it.
• Any existing information: surveys, previous reports, monitoring data, topographic survey.

The condition wording point does more work than the rest combined. A report written to answer a condition should quote the condition and address each element of it, and a consultant who has not seen the wording will write something generic.

Where the report has to satisfy a specific standard, name it. An acoustic assessment prepared to BS 4142 for plant noise is a different job from one prepared to ProPG for residential amenity, and the fee difference is real.

Deliverables, formats and revision rounds

Be specific about what arrives and how many times.

State the format: a PDF report with figures at a stated scale, plus an editable version if you need to append it to a planning statement. State whether drawings are required as separate files. State whether raw survey data is included, because on noise, traffic and ecology work the data has value and consultants differ on whether they hand it over.

Then define the revision rounds. A workable default is one round of client comments on a draft, and one round of amendments in response to consultee comments during the application. Anything beyond that is charged. Both sides benefit from that being written down, because open-ended revision is what turns a profitable job into a resented one.

Say whether the fee includes responding to a consultee objection, attending a meeting with the officer, or giving evidence at a hearing or inquiry. Those are the three items most often omitted from a proposal and most often needed.

Assumptions and exclusions that cause disputes

The exclusions section is the most useful page in any fee proposal. Ask for it explicitly, and read it before comparing prices.

The recurring ones:

1. Site access, including whether the consultant needs keys, an escort, or permission from a neighbouring landowner.
2. Third-party data costs, such as historic environment record searches, trip rate database subscriptions and mapping licences.
3. Topographic and measured building surveys, which are usually assumed to be provided by others.
4. Ground investigation, which is almost always priced separately from the reporting.
5. Licence applications to the statutory nature conservation body, which are a separate instruction from the survey.
6. Reliance by third parties, including lenders and purchasers, and any letter of reliance fee.
7. Attendance at appeal, and any fee for producing proofs of evidence.
8. Value added tax and disbursements.

Where an assumption turns out to be wrong, the proposal should say what happens. A named hourly rate for additional work, agreed in advance, is better than a renegotiation halfway through.

Programme and survey window dependencies

Seasonal constraints are the single largest programme risk on any evidence base, and they belong in the brief rather than in a footnote of the fee proposal.

The ones that bite most often: bat emergence surveys between May and September, great crested newt environmental DNA sampling between 15 April and 30 June, reptile surveys April to October with the best results in spring and early autumn, breeding bird surveys March to August, botanical surveys April to September, wintering bird surveys October to March, traffic counts in neutral months avoiding August and December, and parking surveys taken overnight midweek and at a weekend outside school holidays.

Ask each consultant to state, in the proposal, the earliest date the fieldwork can start and the earliest date the report can be issued given those constraints. That converts a vague programme into a date you can put in a client report.

A Preliminary Ecological Appraisal can usually be done at any time of year and scopes the seasonal work, so instruct it early even where the rest of the ecology programme is months away. Finding out in March that the site needs newt sampling is manageable. Finding out in July is not.

Comparing proposals that are not comparable

Three proposals will arrive with different scopes, different exclusions and different assumptions, and the lowest will usually be the narrowest.

Normalise them. Build a table with one row per scope item and one column per consultant, and mark each cell included, excluded or unclear. The rows worth having: desk study, fieldwork with the number of visits, modelling or calculation, reporting, figures, client revision rounds, response to consultee comments, meetings, appeal attendance, data handover, and third-party costs.

Then price the gaps. A proposal that excludes two site visits included by the others is not lower by the fee difference. It is lower by the fee difference minus the cost of those visits.

Two other things to weigh. Ask who will actually do the work and what their qualifications are, since the person who wrote the proposal is often not the person who visits the site. And ask for professional indemnity insurance cover, because on a scheme of any value the cover level matters more than a modest difference in fee.

Where a report has to be signed off by someone with a particular competence, check that before appointment rather than after. The professional directory is one route to a reviewer, and the report pages set out where a licensed or competent professional is legally required rather than merely advisable.

Signing off the scope with the client

The last step is the one consultants skip. Send the agreed scope back to the client in writing, as a short schedule rather than as a long letter, listing the deliverables, the assumptions, the exclusions, the programme and the fee.

Include a change control line: any variation to the scope will be confirmed in writing with a fee before the work is done. That one sentence prevents most fee disputes, and it protects the client from an unexpected invoice as much as it protects the consultant from unpaid work.

Where you are managing several consultants on the same scheme, issue a single information schedule showing which consultant needs what from whom and by when. Ecology needs the layout. Transport needs the parking numbers. The energy assessor needs the elevations. Drainage needs the levels. Half the delay on a typical evidence base is people waiting for information that nobody was asked to provide.

Getting a first draft in front of the team early helps too. An AI-assisted draft structured to UK planning policy gives the specialist a starting point to correct rather than a blank page, provided everyone understands that it is a draft and that the specialist owns the conclusions.

See how PlanScope is priced if you are costing the drafting stage across a portfolio of applications, and browse the report types when building a scope for a new instruction.

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.