Professionals and Qualifications

What a reviewer takes on when signing off a draft

6 min readBy PlanScope Editorial Team

A reviewer who signs a drafted report is taking on a professional position on its content. Scope, data, site inspection and the wording of the declaration decide how far that goes.

Professional review of a planning report is an opinion on someone else's work, given in a form the local planning authority will rely on. That is a narrower thing than authorship and a larger thing than proofreading, and the reviewer who has not decided which they are doing is the one who gets into trouble.

The question to settle before reading a word of the draft: what standard is this report measured against, and do I hold the competence to apply it. If the answer to the second half is no, the review should not happen, regardless of how good the draft looks.

What a review is and what it is not

A review tests four things. Whether the method used is the right method for the question. Whether the data supports what the report says. Whether the reasoning from data to conclusion holds. And whether the document meets the standard the council and any statutory consultee will apply to it.

It is not a rewrite, a second survey or a guarantee of consent. A reviewer who finds the survey design inadequate has found a fault in the work, not a task to absorb. Where the only route to a signature is redoing the analysis, the honest response is to say so and to be engaged as author.

PlanScope's own review flow reflects that structure: a request is sent, accepted, taken into review, and then either signed off, returned with changes requested, or rejected. Changes requested is not a failure state. On technical drafts it is the most useful outcome, because it records what was wrong.

Scope of review against authorship

Write the scope down before starting. A short paragraph naming the documents, their revision numbers, the dates, the standard applied and the matters excluded will do more for a reviewer than any disclaimer.

Where the line sits in practice:

  • checking a metric calculation against the habitat plan and the condition criteria is review
  • classifying the habitats from scratch because the plan is unclear is authorship
  • confirming that noise measurement positions were appropriate is review
  • specifying new measurement positions and returning to site is authorship
  • assessing whether a harm conclusion follows from the significance assessment is review
  • writing the significance assessment because none was attempted is authorship

Some report types remove the choice. Protected species survey work and any mitigation licence require a licensed ecologist under the Wildlife and Countryside Act 1981 and the Conservation of Habitats and Species Regulations 2017. The statutory biodiversity metric expects a competent person under the Environment Act 2021 regime, and a Biodiversity Net Gain Assessment draft is a starting point for that person rather than something review can substitute for. What competent person means in planning legislation works through the statutory usages.

Site visits and whether a reviewer needs one

The test is whether the conclusions depend on observed conditions. A tree report that categorises specimens, records defects and sets root protection areas is a record of what someone saw with a tape and a probe. A reviewer who has not stood under the trees is reviewing a description, and should say so plainly.

Cases where a visit is effectively required before signature: arboricultural surveys, ecological appraisals and species surveys, acoustic assessments relying on measured baselines, contamination reports with a walkover element, structural surveys, and any report describing the condition of a building.

Cases where a desk-based review is defensible: archaeological desk-based assessments, flood risk work built on published modelling and mapping, viability appraisals, policy statements, and transport work built on published count data. Even then, a visit tends to surface the thing the drawings do not show, such as a dropped kerb that is not where the plan says it is.

Data the reviewer must see to sign

Ask for the primary record. A report is a narrative built from evidence, and the evidence is what a reviewer is actually checking:

  1. Survey forms and field notes with dates, times, weather and personnel.
  2. Photographs, ideally with locations marked on a plan.
  3. Instrument records, including calibration before and after for acoustic work.
  4. The model or metric file rather than a screenshot of the output.
  5. The drawing revision the assessment was based on, checked against the drawings being submitted.
  6. The version of the standard or guidance applied, because standards are revised.

Point five catches more errors than the rest. A report assessed against a superseded layout is wrong even when every calculation inside it is right. And whether a survey is still valid is a separate question again, since ecological data ages faster than most applicants expect.

Illustrative example: a reviewer receives a drafted noise assessment for a restaurant extraction system. The draft is well written and cites the right standard. The survey record shows a single measurement taken on a Tuesday afternoon, with no night-time data, while the proposed opening hours run to 23:00. The right outcome is changes requested, with a short schedule: night-time baseline required, plant sound power data to be supplied by the supplier rather than assumed, and the assessment rerun. Illustrative only.

Recording the limits of the review in the report

A reviewer's statement should let a case officer see exactly what was and was not done. Four sentences will usually cover it: what was reviewed, by reference to document titles, revisions and dates. Whether the site was inspected, and when. What the review checked against. What assumptions the opinion depends on.

Avoid the two failure modes. A bare signature tells the authority nothing about scope, so an officer may read it as full authorship. A page of exclusions reads as an attempt to sign without taking a position, which invites a request for a different reviewer.

Where a draft was produced with AI assistance, say that in the document rather than concealing it, and say what the reviewer did about it. The draft will carry markers where site facts were missing, and those markers are the reviewer's checklist rather than an embarrassment to be tidied away.

Insurance and liability considerations

Three practical matters, none of which is legal advice. Check that professional indemnity cover extends to review or certification of work prepared by others, because some policies treat it differently from ordinary consultancy. Check who the report is addressed to and who is entitled to rely on it, since reliance by a purchaser or a lender is a different exposure from reliance by the applicant. And keep the file, including the version reviewed, the schedule of changes and the final version signed, because a dispute two years later turns on what was in front of you.

Fees should reflect the work rather than the length of the document. A short structural review with a site visit can take longer than a long policy statement.

A review checklist for technical drafts

Run the same sequence every time:

  1. Confirm the report type, the standard that applies and your competence to apply it.
  2. Check the site address, application description and drawing revisions against the submission.
  3. Read the limitations section first, then the conclusions, then the method.
  4. Trace two or three conclusions back to primary data at random.
  5. Check the policy and standards citations, including editions and dates.
  6. Look for missing site facts left as flags, and resolve each one.
  7. Decide: sign off, changes requested, or reject, and record the reasons.

Reviewers who work through PlanScope's sign-off route can be found via the professional directory, and the report families that most often need review are set out across all 66 report types. 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.

Frequently asked questions

Is reviewing a report the same as writing it?

No, and the distinction should be recorded. A reviewer checks method, data, reasoning and conclusions against the applicable standard. An author is responsible for the survey design, the fieldwork and the findings. Where a reviewer has to redo the analysis to be satisfied, they have become an author and should be engaged and paid as one.

Does a reviewer have to visit the site?

It depends on what is being reviewed. Where the report's conclusions rest on observed conditions, a visit is usually the only way to be satisfied the description is accurate. Where the work is a desk study using published datasets, a visit adds little. Say in the report which of the two applies.

What data should a reviewer insist on seeing?

The raw material, not the summary: survey forms with dates and conditions, photographs, calibration records for instruments, the metric or model file, the drawings the assessment was based on, and the version of the standard applied. A conclusion that cannot be traced to primary data cannot responsibly be signed.

Can a reviewer limit their liability in the report?

A reviewer can and should state the scope, the documents reviewed, the date and the assumptions relied on. That defines what the opinion covers rather than excluding responsibility for it. Whether any further limitation is effective depends on the contract and on professional indemnity cover, which is worth checking before the first review.

What happens where the draft is wrong rather than incomplete?

Return it with reasons rather than correcting it silently. A review that quietly rewrites conclusions leaves no record of the original error, and the applicant may not understand what changed or why the programme has moved. A short schedule of required changes protects everyone, including the applicant.

Sources and further reading

professional reviewsign offcompetenceliabilityreport quality

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.

More in Professionals and Qualifications

View all →
Professionals and Qualifications7 min read

Who prepares a utilities assessment

A utilities assessment is written by an engineer but built from capacity responses only the network operators can give. Running those enquiries late is what wrecks programmes.

Read article →
Professionals and Qualifications6 min read

Who prepares a waste management strategy

A waste strategy is a calculation and a drawing, not a narrative. The architect usually owns it, the transport consultant checks the access, and the council's waste team decides whether it works.

Read article →
Professionals and Qualifications6 min read

Ecologist competence for a preliminary ecological appraisal

A preliminary ecological appraisal is a scoping exercise. Its value lies in the limitations it states honestly and the survey seasons it puts into your programme.

Read article →
Professionals and Qualifications6 min read

Odour assessor competence and the assessment benchmarks

Odour assessment has no statutory register, so you are judging method rather than credentials. Emission rate provenance and receptor characterisation are where most reports fail.

Read article →
Professionals and Qualifications6 min read

Who prepares a viability assessment and to what standard

A viability assessment is prepared under a mandatory professional standard that requires objectivity, declared conflicts and transparent inputs. It is not an advocacy document.

Read article →
Professionals and Qualifications7 min read

Energy assessor competence for an energy statement

An accredited energy assessor produces the modelling for an energy statement. Reading the local policy and staging the hierarchy is a separate skill, and the gap between the two is where statements fail.

Read article →