What a professional sign-off commits the signatory to
A reviewer who signs a planning report is taken to stand behind its conclusions. The declaration is where scope, reliance and limitations get fixed, or left dangerously vague.
Putting your name and your post-nominals on a planning report tells the reader that a competent person stands behind its conclusions. That is the point of the exercise, and it is also the risk. Whether you wrote the document or reviewed someone else's draft, the local planning authority, the applicant and any third party who relies on the report will treat the signature as your professional judgement on the content.
Which means the useful question is not whether to sign but what exactly you are signing, and the answer belongs in a written declaration rather than in an email.
Review is not authorship, and the document should say so
There is a real difference between preparing a report and checking one. An author designs the method, carries out or commissions the fieldwork, interprets the data and reaches the conclusion. A reviewer examines a completed document against the method it claims to follow, the data behind it and the standards that apply.
Both can be legitimate professional services. Problems start when the distinction is invisible in the output, so that a report drafted by someone else and reviewed by a chartered professional reads as if that professional produced it.
State the position on the face of the document. Who prepared the draft, what the reviewer examined, what the reviewer did not examine, and what the reviewer concludes. A reader who understands the division of labour can weigh the report properly. A reader who does not is being misled, and that is a conduct issue as much as a liability one.
What a declaration should contain
A useful declaration is short and specific. Six elements cover most cases.
- The identity of the reviewer, the professional body, the grade of membership and any relevant licence or registration number.
- A statement of competence limited to the matters actually reviewed.
- The exact documents and revisions examined, listed by number and date.
- The standards, guidance or methodology against which the review was carried out.
- The data relied upon and its source, with a statement that it has not been independently verified where that is the case.
- Any limitations, assumptions or matters excluded from the review.
Date it, and say what it does not cover. A declaration that reads "I have reviewed this report and confirm it is accurate" is unbounded and, on a document containing survey data the reviewer never saw, indefensible.
Where an AI-assisted draft has been reviewed, describe that plainly rather than obscuring it. A draft generated from structured planning data and reviewed by a qualified professional is a legitimate way to produce a document, and honesty about the process protects everyone in the chain.
Liability for data supplied by others
Most of the exposure sits here. A reviewer typically receives site information, drawings, survey results and background data from the applicant or from a third party, and cannot re-survey the site.
The professional answer is to record reliance rather than to imply verification. Name the source, give the date, and state that the review proceeded on the basis that the information is accurate and complete. Where the data looks internally inconsistent, say so and either resolve it or exclude it from the scope.
Two situations need more care than that. The first is where the underlying work required a licence or a specific competence, such as a protected species survey carried out under a licence issued for that purpose, or an Environmental Statement prepared by competent experts under the Environmental Impact Assessment Regulations 2017. A reviewer cannot cure the absence of that competence by signing. The second is where the report will be relied on by a party you have no contract with, which is the normal position for a document submitted to a council. Assumption of responsibility can arise without a contract, and your professional indemnity cover should be checked against that scenario rather than assumed to cover it.
Your institute's code of conduct sits over all of this. The RTPI, RICS and CIEEM codes all require members to act within their competence and to be candid about the basis of their advice, and a signature outside your field is a conduct breach before it is anything else.
Limits worth recording every time
Some limitations recur so often that they belong in a standard schedule you adapt rather than write from scratch.
- The review covers the named revision only, and later revisions are outside it.
- No site visit was made, or the site visit was on a stated date and in stated conditions.
- Survey data was collected on stated dates and has a limited useful life.
- Areas not accessed during any inspection.
- Matters outside the reviewer's discipline, such as structural, legal or highway design questions.
- Any policy position that may change before the application is determined.
The revision limit is the one that saves the most trouble. Design teams issue new drawings, and a signature attached to revision C is routinely reproduced in a submission containing revision F. Naming the revision in the declaration makes that visible.
Saying no, and how to say it
Declining to sign is a normal professional act and it should be recorded as calmly as an approval. Give the reason in writing, keep it factual, and separate what is missing from what is wrong.
Three reasons cover most refusals. The report falls outside your competence. The evidence does not support the conclusion and the author will not amend. The information needed to form a view is not available, most often because the survey window has passed or the fieldwork was never done.
Do not sign with heavy caveats as a compromise. A signature qualified into meaninglessness still appears on the front of a document submitted to a council, and the qualification will not be read by the person who matters. Either the report is fit to carry your name or it is not.
Where the fix is achievable, say what would change your answer. That is more useful to the client than a refusal on its own and it usually gets the work done properly.
Keeping the record
Keep the version you reviewed, the declaration you issued, your review notes and the correspondence, and keep them for as long as your indemnity arrangements require. The claim, if one ever comes, will arrive years after the decision and will turn on which revision you saw.
Where reviews are handled through a structured route such as PlanScope's professional directory, the request statuses run from sent and accepted through in review, changes requested, signed off, rejected and expired, which produces a dated record of what was asked and what was answered. That trail is worth as much as the declaration itself.
For report types where a licensed or competent professional is legally required, including Environmental Impact Assessment, protected species work, biodiversity net gain, land contamination and fire statements, the draft is a starting point for that professional rather than something a review can substitute for. The report types and their professional flags are listed on the planning documents index, and a Planning Statement is one of the few where an unqualified author is entirely normal.
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
Am I liable for a report I reviewed but did not write?
You can be. A signature indicates that a competent person stands behind the conclusions, and responsibility can arise towards parties you have no contract with, including a council relying on the document. The protection is a precise declaration setting out what you examined, what you relied on and what you excluded, backed by indemnity cover that fits the work.
What should a reviewer's declaration say?
Identify the reviewer and their professional body, state competence limited to the matters reviewed, list the documents and revisions examined by number and date, name the standards applied, record the data relied upon and its source, and set out limitations and exclusions. Date it. An open ended confirmation of accuracy offers no protection.
Can a professional review replace a survey that was never done?
No. Where the underlying work requires a licence or a specific competence, such as a protected species survey or an Environmental Statement prepared by competent experts, a review cannot supply what is missing. The correct response is to say the evidence is absent and to identify the survey or fieldwork needed.
Should I sign a report with extensive caveats instead of refusing?
Generally no. A heavily qualified signature still appears on a document submitted to a local planning authority, and the qualifications are rarely read by the decision maker. If the report is not fit to carry your name, decline in writing, give the factual reason, and say what would change your answer.
How long should I keep review records?
Keep the reviewed version, the declaration, your notes and the correspondence for at least as long as your professional indemnity arrangements require. Claims typically surface years after the decision and turn on which revision was examined, so a dated record of documents, revisions and correspondence is the most useful thing you can hold.
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.