What a professional reviewer takes responsibility for

A reviewer who signs a report someone else drafted takes on responsibility for the professional judgements in it, and for nothing else. That distinction is the whole of the professional review planning report responsibility question, and getting it clear in writing protects the reviewer, the client and the authority relying on the document.

Review is not a rubber stamp and it is not authorship. A reviewer who signs a document without the site knowledge, the survey data or the competence to form the judgements in it has given the client a signature and no assurance.

Reviewing against authoring

An author takes responsibility for the whole document: the method, the data, the analysis, the conclusions and the fitness of the whole for its purpose. The author's name on the cover means they stand behind every statement.

A reviewer takes responsibility for the judgements they have actually formed, within a scope they have defined. In practice that usually means confirming that the method is appropriate, that the analysis follows from the data, that the conclusions are supportable, and that the document meets the relevant standard. It does not mean warranting data they have not collected.

There is a middle position, which is where most sign-off work sits: the reviewer adopts the document as their own after satisfying themselves on the matters that make it defensible, which may include a site visit and re-running calculations. If that is the arrangement, the reviewer is closer to an author and should price and insure the work accordingly.

Decide which of the three you are doing before the engagement starts, and record it. Ambiguity on this point is what turns a modest fee into a claim.

What review can and cannot cure

Review can fix structure, policy citation, internal inconsistency, omissions against a standard, overstated conclusions and the use of unsupported assertions. Those are the commonest problems in a draft and they are exactly what a careful read finds.

Review cannot create data that was never collected. If the bat survey was not done in the right season, no amount of reading resolves it. If the noise monitoring ran for 15 minutes when the standard expects a representative period, the result is unusable whatever the reviewer writes. If the ground investigation did not sample at the depth the development will disturb, the contamination conclusions rest on nothing.

That is the test a reviewer should apply early: is the gap a drafting gap or an evidence gap? Drafting gaps are what review is for. Evidence gaps mean more fieldwork, and the right response is to say so and quote for it, not to add caveats until the document reads as acceptable.

Site visits and unverifiable assertions

A draft report contains three categories of statement, and a reviewer should separate them as they read.

The first is verifiable from the document and its appendices: a calculation, a policy citation, a plan measurement. The second is verifiable only on site: boundary treatments, the condition of a neighbouring wall, whether the hedge marked on the plan is actually there, the relationship between the proposal and the window it is said not to affect. The third is unverifiable by anyone at review stage, because it depends on survey data that either exists or does not.

The second category is the argument for a site visit, and it is why remote review of a document about a place you have not seen has limits. For some report types a visit is effectively mandatory in practice, because the standard assumes the author has been there.

Where a draft carries a "to be confirmed" flag against a missing fact, treat it as what it is: an instruction to obtain the fact. An AI-assisted drafting process that inserts those flags instead of inventing site data is behaving correctly, and the reviewer's job is to close them, not to delete them. The article on signing off an AI-drafted report as the named author goes into that workflow in more detail.

Recording the scope of review in the report

Put the scope in the document as well as in the appointment letter, because the authority reading it needs to know what the signature covers.

A usable review statement says:

• what was reviewed, by document title, revision and date
• the reviewer's name, qualification and institute membership
• what the review covered: method, data interpretation, compliance with the named standard, conclusions
• what the review expressly excluded: field data accuracy, survey coverage, third party information, matters outside the reviewer's competence
• whether a site visit was undertaken and when
• what changes were required and whether they were made
• the basis of reliance: who may rely on the document and for what purpose

The exclusions are the part most often left out and the part that matters most. A reviewer who has not verified the survey data should say so plainly rather than allowing a reader to assume otherwise.

Insurance and reliance

Professional indemnity cover responds to the work described in the policy, and reviewing another party's draft may sit awkwardly with a policy written around original design or assessment work. Three questions are worth asking the broker before the first review instruction, not after: does the cover extend to review and certification of third party documents, does it respond where the underlying data was collected by someone else, and is there an exclusion for documents produced with automated drafting tools.

Reliance is separate from insurance. A report addressed to a client can usually be relied on by that client. Where the local planning authority, a funder or a purchaser also needs to rely on it, that requires a reliance letter or an express statement in the document, and each additional party extends the reviewer's exposure. The related piece on professional indemnity insurance for a planning consultant covers the cover itself, and the question of where liability sits with sub-consultants deals with the chain below the reviewer.

Where competence cannot be delegated

Some report types carry a legal requirement for a licensed or competent person, and no review arrangement substitutes for it.

For these, an AI-assisted draft is a starting point for the licensed or competent professional and never a substitute for them. A reviewer without that specific competence should decline rather than qualify, and a draft Environmental Impact Assessment or Fire Statement reaching a reviewer who lacks the relevant competence is a referral, not a job.

Report types labelled professional recommended, including preliminary ecological appraisal, arboricultural impact assessment, air quality, noise, transport and viability work, are different: councils usually expect a suitably qualified author and professional review is strongly advised, but the competence rule is a matter of expectation rather than statute.

Declining properly

Declining a review is a professional act and should be done like one. Say why, in a sentence that identifies the gap rather than the client. Identify what would need to change for the review to be possible, usually specific fieldwork or a specific competence. Suggest the discipline or institute register where the right reviewer can be found. Do it in writing, promptly, and before invoicing anything beyond an initial assessment fee.

A declined review that explains the evidence gap is more useful to a client than a signed one that does not. The professional directory is one route to a reviewer with the right competence, and an institute register is the way to verify that competence independently.

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.