What professional sign off of a drafted report involves

Professional sign off of a planning report is a named individual putting their name, their competence and their professional indemnity cover behind a document. It is not a proofread. A reviewer who signs a Preliminary Ecological Appraisal is stating that the methodology is appropriate, that the conclusions follow from the evidence and that the report meets the standards of their institute, and they can be asked to justify all three later.

Understanding what that signature covers, and what it deliberately does not, is what makes the process work rather than turning it into a rubber stamp nobody trusts.

What a reviewer is actually certifying

Three things, in most disciplines.

That the method used is appropriate to the question, the site and the receptor. That the data relied on is adequate in scope, age and quality to support the conclusions drawn. And that the conclusions are ones a competent practitioner in that field could reasonably reach on that evidence.

What the signature does not certify is the accuracy of facts the reviewer cannot verify. Site levels taken from a survey they did not commission. Floor areas from drawings they did not check. The client's statement about the existing use. Reviewers handle this by listing their sources and stating what they took at face value, which is standard practice and not a weakness.

Nor does it certify the planning outcome. No professional signs a report saying the application will be approved, and any document implying that should be treated with suspicion.

Scope of review and what it excludes

Agree the scope in writing before the work starts, because an unbounded review is one nobody can price and nobody can complete.

A well-drawn scope names the report and its version, the standards against which it is being reviewed, whether a site visit is included, whether the reviewer is verifying input data or accepting it as supplied, whether the reviewer will sign as author or as reviewer, and what happens if the report needs substantive change rather than correction.

The distinction between signing as author and signing as reviewer is the one that matters most and is most often fudged. An author takes responsibility for the whole document including the survey work behind it. A reviewer takes responsibility for the review. For report types where legislation names the author, only the first is any use, and the reviewer will normally need to have carried out or directly supervised the survey work.

Where the report is one requiring a licensed or competent person, no review can substitute for that competence. The law names the author on environmental statements, protected species surveys, biodiversity metric work, land contamination investigation and fire statements, and the review route does not change that.

Evidence the reviewer needs from you

Send everything at once. Reviews stall on missing inputs more than on disagreements.

• The draft report in an editable format, with a version number.
• The site plan and the proposed layout at a readable scale.
• The survey data behind the draft, with dates and the name of who collected it.
• The application description and the red line boundary.
• The local planning authority's validation checklist for that application type.
• Any pre-application correspondence or consultee comments already received.
• A statement of what is still unknown, which is more useful than it sounds.

That last point deserves emphasis. A draft that marks unknown facts clearly, rather than filling them with plausible text, gives the reviewer somewhere to direct their attention. PlanScope drafts insert a "[TO BE CONFIRMED]" flag wherever a site-specific fact is missing, which is a deliberate safeguard rather than an omission, and a reviewer should expect to see those flags resolved rather than deleted.

Checking the draft yourself first shortens the review and lowers its cost. The checks worth running are set out in building an internal review checklist for submissions.

Changes requested and how to respond

A review that comes back with changes is a review working properly. The request usually falls into one of three kinds.

Corrections, where a fact, reference or figure is wrong. Turn these around immediately and resubmit.

Evidence gaps, where the reviewer cannot sign because something was not surveyed, not measured or not dated. This is the expensive one, and the answer is usually to do the work rather than to argue. A reviewer who signs across an evidence gap is taking a risk they should not take, and a reviewer who does that routinely is not worth having.

Method disagreements, where the reviewer would have approached it differently. Discuss these rather than conceding automatically. Where two defensible approaches exist, the reviewer's preference usually wins because they are the one signing, but the reasoning should be recorded.

In the PlanScope review flow the request moves through defined statuses, including sent, accepted, in review, changes requested, signed off, rejected and expired. A request sitting at changes requested is waiting on you, and an expired request has to be reissued.

Professional indemnity and reliance

This is the part clients ask about last and should ask about first.

A signed report is relied on by the applicant and, in practice, by the local planning authority. Where the report turns out to be wrong and loss follows, the claim runs against the professional who signed it, within the terms of their indemnity cover. That is why reviewers are careful about scope, why they state their assumptions, and why they decline work outside their competence.

Two practical points. Ask what cover is in place and whether the review falls within it, particularly where the reviewer is signing work they did not produce. And understand that a report addressed to you is not automatically capable of being relied on by a funder or a purchaser, which is a separate reliance question usually handled by a letter.

Do not ask a reviewer to sign a document they did not have time to read. It is the request that damages the relationship fastest.

Recording the review in the submission

Put the review on the face of the document.

The report should carry the author, the reviewer, their professional qualifications and institute membership, the date of review, the version reviewed, and a short statement of scope and limitations. Where the reviewer signed as author rather than as reviewer, say so. Where the review excluded input verification, say that too.

Councils increasingly ask who prepared a document, and a report that answers the question on its front page avoids the exchange entirely, as when a council asks who wrote your report sets out. The form of words reviewers use in the declaration itself is covered in signing off a draft and the reviewer's declaration.

Keep the reviewed version in the project file alongside the draft it replaced. If a condition discharge or an appeal follows two years later, the version history is what lets anyone reconstruct what was known when.

Timescales and planning for them

Build the review into the programme rather than treating it as the last step before submission.

Allow time for the reviewer to accept the request, read the material, raise questions, receive answers and issue the signed version. Where a site visit is included, that has to be scheduled. Where seasonal survey data is missing, the review cannot complete until the season arrives, and that is measured in months rather than days.

Two habits help. Send the draft for review before the drawings are final, so that method issues surface while the design can still absorb them. And ask the reviewer at the outset what would stop them signing, which is the same question worth asking any consultee.

Review requests go through PlanScope's professional directory and sign-off portal, and report types are labelled as professional required or professional recommended so the position is clear before drafting starts. Pricing is one free report, £50 per report, or £150 per month for the Professional tier.

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.