Peer review of a specialist report: when it earns its cost
Peer review pays where a report will be attacked, where the method is unusual, or where you inherited the work. Elsewhere it is comfort, which is a decision to make consciously.
A peer review of a specialist report costs between a fifth and a half of the original fee, depending on discipline and depth, and it earns that back in exactly three situations. When the report will be tested by an opponent, when the method is unusual enough that a consultee will query it, and when the report was written by someone whose work you have not seen before.
Everywhere else it is a comfort purchase. Buying comfort is a legitimate use of money, and it should be a conscious decision rather than a habit.
When a second pair of eyes pays for itself
Appeal evidence is the clearest case. Once a report becomes proof of evidence, it will be read by an advocate whose job is to find the weakness, and the cost of a review is trivial against the cost of a dismissed appeal.
Contested applications come next. Where a scheme has organised objection, a resident group with its own consultant, or a member of the planning committee who has taken a position, the technical work will be picked over. A Viability Assessment on a scheme reducing affordable housing is almost certain to be reviewed by someone, and it is better if the first person to find the error works for you.
The third case is inherited work. A report produced for a previous owner, for a lapsed permission, or by a consultant no longer instructed, carries assumptions you cannot see. Reviewing it before you rely on it costs less than discovering the site boundary changed between versions.
There is a fourth case that comes up less often and matters more when it does. Where the report supports a position you want to be true, get it reviewed. Confirmation bias is not a consultant failing so much as a client one, and a scheme that depends on a favourable trip rate, a favourable base value or a favourable habitat baseline is exactly where an independent reader earns their fee.
Then there are the reports councils have reviewed for you whether you like it or not. Several London boroughs require a basement impact assessment to be audited by an independent engineer at the applicant's expense, and viability assessments are routinely sent to an authority's own consultant. Where that is going to happen, an internal review first is straightforward risk management. Read the borough's requirements before you commission the Basement Impact Assessment rather than after.
What a review should cover
Scope it in writing, because an unscoped review produces either a rubber stamp or a rewrite.
- Is the brief the right brief, and does the report answer it?
- Does the method follow the applicable standard or guidance, and is any departure explained and justified?
- Are the input data current, from a named source, and correctly transcribed?
- Are the assumptions stated, and are they reasonable for this site?
- Do the calculations reproduce, on a sample basis at least?
- Are the conclusions supported by the results, without overstatement?
- Is the report internally consistent, and consistent with the other documents in the application?
- Would a case officer with no technical background understand what it concludes?
Point seven catches more problems than any other. Cross-document inconsistency, where the drainage report assumes a permeable surface that the landscape drawings show as tarmac, is the single most common finding on a multi-consultant submission, and it is invisible to each consultant reading only their own work.
Reviewing method against reviewing conclusions
These are different exercises and they need saying apart in the brief.
A method review asks whether the work was done properly. It checks sampling density against the standard, survey timing against the season, the measurement positions, the software version, the version of the guidance applied.
A conclusions review asks whether the professional judgement is defensible. That is a heavier task, requires equivalent seniority to the author, and produces a genuine risk of two experts disagreeing in writing.
Most clients want the first and ask for the second by accident. If you commission a conclusions review, be prepared for the answer, because a written opinion that the original conclusion is unsound is disclosable in some circumstances and awkward in all of them.
Handling disagreement between consultants
Disagreement is a normal outcome and it should be managed rather than suppressed.
Start by separating fact from judgement. Two acousticians who disagree about a measurement position have a factual dispute that can be settled by going back to the standard. Two who disagree about whether a rating level penalty applies to a tonal component have a judgement dispute that may not resolve.
Get them talking directly, with you present, rather than exchanging notes through you. A single call usually narrows the dispute to one point.
Where it does not resolve, record it. A short note stating the point of difference, each position and the basis for each, kept on file, is better than a report that quietly adopts one view without explaining why. If the disagreement is material to the recommendation, the client needs to know, and burying it transfers the risk to you.
What you must not do is instruct the reviewer to soften their finding, or shop for a third opinion until one agrees. Both are visible in disclosure, and both destroy the value of having commissioned a review at all.
Cost and programme
Budget three to six weeks for a review of a substantial technical report, including the author's response and any revision. On an appeal timetable that has to be planned in, because a review delivered after the statement deadline is worth nothing.
Front-load it. Reviewing at draft stage costs less, produces changes the author can accept without loss of face, and avoids the situation where a finalised, issued report has to be reissued.
Where drafting is quick, the review is where the time goes. An AI-assisted draft of a narrative document can be produced in an afternoon and still needs a qualified reader to check every policy citation, every site fact and every conclusion before it goes anywhere. For report types where a licensed or competent person is legally required, the professional is not reviewing the draft so much as adopting it, and that distinction changes what the review has to cover. The professional directory is one route to reviewers who take that role.
Recording the review in the submission
Say that a review happened, who carried it out in general terms, what it covered, and what changed. A short statement at the front of the report is enough.
Do not overclaim. A review is not certification, it does not transfer liability from the author, and describing it as independent verification invites a question about what exactly was verified.
Keep the review report itself. It is not usually submitted, and it is exactly the document you will want if the work is challenged later. Alongside it, keep the scope you issued, so the boundaries of what was checked are on the record.
For a scheme still being scoped, decide which reports warrant review before you commission any of them, so the fee sits in the budget from the start rather than arriving as an overspend. The report index shows which types carry professional requirements and which are most often contested.
This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional 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
When is a peer review worth commissioning?
Three situations justify it reliably. Where the report will become appeal evidence and be tested by an opponent, where an unusual method will draw questions from a statutory consultee, and where the work was produced by someone whose output you have not seen before or inherited from a previous owner. Elsewhere it buys reassurance rather than risk reduction.
What should the review scope include?
Whether the brief was right and answered, whether the method follows the applicable standard, whether input data are current and correctly transcribed, whether assumptions are stated and reasonable, whether sample calculations reproduce, whether conclusions follow from the results, and whether the report is consistent with the other documents in the application.
What is the difference between reviewing method and reviewing conclusions?
A method review checks whether the work was done properly against the standard, including sampling, timing and measurement positions. A conclusions review questions the professional judgement itself, needs a reviewer of equivalent seniority, and carries a real chance of two experts disagreeing in writing. Decide which one you are buying before you commission it.
What should I do if the reviewer disagrees with the author?
Separate factual disputes from judgement disputes, then get both consultants talking directly with you present. Where the difference persists, record it in a short note setting out each position and its basis. Never instruct a reviewer to soften a finding, and never keep commissioning opinions until one agrees, because both are visible later.
Should the review be mentioned in the submission?
A short statement saying a review took place, what it covered and what changed is helpful and honest. Avoid describing it as independent verification or certification, because a review does not transfer liability from the author. Keep the review report and the scope you issued on file even though they are not usually submitted.
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.