What a professional certifies when signing off a draft report
A signature says the work is within your competence and the conclusions follow from the evidence. Defining the scope of review is what makes that statement safe to make.
Signing a report means taking professional responsibility for its content within a stated scope, and the scope is the part most reviewers define too loosely. A signature on a bat survey says the surveyor holds the licence, did the work to the standard, and stands behind the conclusion. A signature on a document someone else drafted says the same things, which is why the reviewer has to know exactly what they are adopting.
The question is not whether a draft can be signed off. It is what the signature covers and what it silently excludes.
What signing a report actually means
When you put your name and post-nominals on a planning report, you are stating that the work falls within your competence, that the method used is appropriate, that the conclusions follow from the evidence, and that you have not misrepresented anything. Every professional institute's code of conduct says a version of this.
You are also, in practice, the person a local planning authority will rely on. Officers read the author's credentials before they read the results, because competence is what makes the results usable.
None of that changes because the first draft came from a template, a junior colleague or an AI-assisted tool. The obligations attach to the signature rather than to the keyboard.
What does change is where your attention needs to go. Reviewing a draft you did not write means checking things you would otherwise know by having done them, starting with whether the site described is the site you visited.
Scope of review and how to define it
Write the scope down before you start, and reproduce it in the report.
- What you checked. The brief, the method, the input data, the calculations, the policy citations, the conclusions.
- What you did not check. Third-party survey data, structural information supplied by the client, drawings not issued to you, anything outside your discipline.
- Whether you attended the site, when, and in what conditions.
- Which version of the draft you reviewed, by date and revision.
- Which standard or guidance edition you applied.
That list is short and it does most of the protective work. A reviewer who has stated that they did not verify client-supplied ground data is in a very different position from one who said nothing.
Be careful with the word independent. If you are being paid by the applicant to review a draft prepared for the applicant, you are the author's reviewer rather than an independent expert, and describing yourself otherwise invites a question you will not enjoy answering.
Where liability sits for the underlying data
Most planning reports rest on information the author did not generate. Topographical surveys, historic maps, client-supplied floor areas, a previous consultant's borehole logs, published datasets.
Standard practice is a reliance statement saying that information provided by others has been used in good faith and has not been independently verified, and naming the sources. Include it, and then be specific about what falls inside it rather than using it as a blanket.
There is a limit to how far that carries. A caveat does not protect a reviewer who accepts data that is obviously wrong, or who fails to notice that the flood zone quoted is out of date, or that the site boundary differs between the drawing and the application form. Reasonableness is the test, and a competent professional is expected to spot the obvious.
Where the underlying data cannot be verified and the conclusion depends on it, say so in the conclusion itself rather than in a limitations appendix at the back.
Declaring assumptions and limitations
A limitations section is not a disclaimer. It is a description of the boundary of the work, and it should be written so that a reader can tell what would change the answer.
Good limitations are specific. Access to the roof void was not possible on the survey date. Weather conditions during the emergence survey were outside the recommended range. Floor areas were taken from the architect's drawings dated March and not measured on site. The assessment assumes the neighbouring first-floor window serves a bedroom.
Bad limitations are generic disclaimers that say nothing about this site and this survey.
Where a draft arrives with placeholders marking missing site facts, treat those as instructions rather than as tidying. A flag saying a fact is unconfirmed exists to stop an assumption becoming a finding, and the reviewer's job is to fill it with verified information or convert it into a stated limitation. Deleting it and letting the sentence read as fact is the single worst thing a reviewer can do.
Refusing to sign, and why that happens
Reviewers decline for a small number of recurring reasons, and all of them are legitimate.
The conclusions are not supported by the data presented. The scope of work needed to reach the conclusion has not been done, such as a seasonal survey that was never carried out. The work sits outside the reviewer's competence, which happens more often than people admit in disciplines that overlap. The client will not allow the limitations to be stated. Or the timescale offered does not allow a proper review.
That last one deserves saying plainly. A reviewer given four hours to sign off a substantial technical report has been asked to lend a signature rather than to review anything, and the correct answer is no.
For report types where a licensed or competent professional is legally required, refusal is not a commercial decision at all. An Environmental Impact Assessment must be prepared by competent experts under the 2017 Regulations. A Protected Species Survey and any mitigation licence require a suitably licensed ecologist. A Biodiversity Net Gain Assessment under the Environment Act 2021 regime expects the statutory metric to be completed by a competent person. If you are not that person, you cannot become one by signing.
Practical steps before adding a signature
- Read the brief and confirm the report answers it.
- Read the whole draft, including the appendices, before forming a view.
- Visit the site, or record clearly that you did not and why.
- Verify a sample of calculations independently, not by rechecking the author's arithmetic in their own spreadsheet.
- Check every policy and standard citation against the current edition, since framework and guidance numbering changes.
- Check the report against the drawings and the application forms for consistency of site area, floor area and description.
- Convert every placeholder into verified fact or a stated limitation.
- Write your scope of review into the report.
- Confirm your professional indemnity cover extends to this type of work.
- Keep the draft you reviewed, your comments and the final version.
Point ten matters most a long time later. Where a sign-off route records the stages of a review request, use it, and keep your own copy as well. Reviewers listed through a professional directory are taking on the same responsibility as any other author, and the record is what evidences it.
This is general guidance, not legal advice, and it does not describe your obligations under any particular institute's code. Check the position with your professional body, your insurer or a qualified adviser before relying on it.
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 does signing a planning report commit me to?
That the work falls within your competence, the method is appropriate, the conclusions follow from the evidence, and nothing has been misrepresented. Professional codes of conduct set out versions of the same obligations. They attach to the signature rather than to who typed the first draft, so a reviewed document carries the same responsibility as one you wrote.
How should I define the scope of my review?
State what you checked, what you did not check, whether you attended the site and when, the version and date of the draft reviewed, and the edition of the standard applied. Reproduce that statement in the report. A reviewer who has recorded that client-supplied ground data was not verified stands in a very different position from one who said nothing.
Does a reliance statement protect me from bad input data?
Only up to a point. Saying that information from others has been used in good faith and not independently verified is standard and appropriate. It does not protect a professional who accepts data that is obviously wrong, quotes an out-of-date flood zone, or misses a site boundary that differs between the drawing and the application form.
What should I do with placeholders in a draft?
Treat them as instructions. A marker showing that a site fact is unconfirmed exists to stop an assumption becoming a finding. Either fill it with verified information or convert it into a stated limitation. Deleting the marker and letting the sentence read as established fact is the most damaging thing a reviewer can do.
When should a reviewer refuse to sign?
When the conclusions are not supported by the data, when work needed to reach them was never done, when the subject sits outside your competence, when the client will not allow limitations to be stated, or when the time offered does not allow a proper review. For report types requiring a licensed or competent person, refusal is not a commercial choice.
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.