What a reviewer's sign-off declaration commits them to

A professional sign off declaration on a report is a statement about three things: who you are, what you looked at, and what you are not saying. Reviewers get into difficulty when the second and third are left vague. A declaration that reads "I have reviewed this report and consider it fit for submission" tells nobody which version you saw, which standard you applied, or whether you ever stood on the site.

The fix is dull and effective. Name the document version, name the standard, name the limitations, and sign only within the competence you can evidence.

What a declaration usually states

A workable declaration carries, as a minimum:

• Your name, professional qualifications and the body you are a member of, with grade where it matters
• A statement that the work falls within your competence, and on what basis
• The exact document reviewed, with its version number or date and file reference
• The scope of the review, described by what was examined
• The standard, guidance or methodology the review was conducted against
• The information you relied on and who supplied it
• The limitations and assumptions
• Whether a site visit formed part of the review, and when
• Your conclusion, worded to match that scope
• The date of signature

The conclusion is where precision pays. "The methodology and reporting conform to the relevant guidance, on the information supplied" is defensible. "This report is correct" is not.

PlanScope's review flow moves a request through named statuses, from sent and accepted to in review, changes requested, and signed off or rejected. The declaration attaches at the sign-off stage, and the reviewer treats the draft as AI-assisted work to be checked rather than a finished submission. Reviewers who want to see how the product frames that role can look at the professional directory.

Scope of review and what it excludes

Write the exclusions before the conclusion. They are the part that protects both you and the client, because an unqualified sign-off invites the reader to assume you verified everything.

Common exclusions worth stating plainly: no independent survey or measurement was undertaken, site data, drawings and levels were taken as supplied, no structural, contamination or legal opinion is offered, the review does not extend to appendices produced by others, and the review addresses planning adequacy rather than compliance with the Building Regulations.

Where the draft contains flags for missing information, say what happened to them. PlanScope drafts insert a to-be-confirmed marker wherever site-specific facts are absent, and a reviewer who signs a document still carrying one should record either that it has been filled or that the sign-off is conditional on filling it.

Reviewing against a standard rather than generally

A review with no named standard is an opinion. A review against a named standard is evidence.

So cite the thing you measured the document against: BS 5837:2012 for arboricultural work, BS 4142:2014+A1:2019 for industrial and commercial sound, BS 10175:2011 for contaminated land investigation, the CIEEM guidelines for ecological impact assessment, GLVIA3 for landscape and visual work, the RICS whole life carbon methodology, CIfA standards for archaeology. Then say which clauses or sections the review covered and which it did not.

This matters more for the report types where a licensed or competent professional is legally required. An Environmental Statement must be prepared by competent experts under the Town and Country Planning (Environmental Impact Assessment) Regulations 2017. Protected species survey work and any mitigation licence need a suitably licensed ecologist under the Wildlife and Countryside Act 1981 and the Conservation of Habitats and Species Regulations 2017. Biodiversity net gain expects the statutory metric to be completed by a competent person under the Environment Act 2021 regime. Reviewing an AI-assisted draft does not convert it into work prepared by a competent expert, and a declaration should not imply that it does. Where you are in fact the competent person, say so and say what you did beyond reading.

Site visits and whether the review requires one

Sometimes yes, sometimes no, and the declaration has to say which.

A review of policy coverage and structure in a planning statement needs no visit. A review of a noise assessment where the receptor positions determine the outcome usually does, because the only way to test whether the monitoring location was representative is to see the site. Arboricultural, ecological and heritage reviews sit in the same category: the document's conclusions depend on observations that cannot be checked from a desk.

Where you have not visited, write "no site visit was undertaken and the site description has been accepted as supplied" rather than leaving the reader to infer. Where you have, date it and state the conditions, since a bat assessment reviewed after a visit in November is a different exercise from one reviewed in June.

Recording the limitations in the document

Put the limitations in the report itself rather than in a covering email alone. Reports travel. A document that reaches a planning committee with the reviewer's name on it and the caveats stripped out is the scenario to design against.

Three practical habits. Keep the declaration on its own page with the version reference in the header so it cannot be separated silently. Insist that the version you signed is the version submitted, and ask for a copy of the submitted pack. And where changes were requested and only partly made, record that, because "changes requested" followed by a later sign-off should show what moved. Accountability for the measures inside a document works the same way, which we look at in construction management plan author accountability.

Insurance implications of signing

Check the policy wording before the first review, not after a claim. Two questions matter: does your professional indemnity cover the review or certification of documents prepared by others, and does it cover work where artificial intelligence tools formed part of the drafting process? Policies differ, and some carry exclusions for certification activities.

Tell your insurer what the work involves in plain terms. A declaration that limits scope, names a standard and records limitations is also the document that makes the risk assessable, which tends to help the conversation.

Fee and scope should match the exposure. A review priced as an hour's reading, signed as though it were authorship, is the worst combination available. Technical competence questions for individual disciplines run the same way, as in our note on drainage strategy engineer competence.

Declining a review that cannot be done properly

Saying no is part of the job. The clear cases: the subject falls outside your competence, the information needed to form a view does not exist, the survey season has been missed and no amount of desk work replaces the data, or the client wants a sign-off that asserts more than the evidence supports.

Decline in writing, give the reason, and say what would make the review possible. That record is useful to everyone later, including the client, who often returns with the missing survey rather than finding a less careful reviewer.

Where a report has passed between consultants, check the handover carefully before taking it on. The pitfalls are set out in changing consultant mid planning application.

Browse all 66 PlanScope report types to see how each one is labelled for professional requirement before accepting a review.

This is general guidance, not legal advice; 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. For specialist technical reports, qualified professional input may be required.