Reviewing a specialist report you did not commission

Reviewing someone else's technical report is a different job from writing one. You are not checking the acoustics or the hydrology; you are checking whether the document supports the decision it is offered for, whether it assesses the scheme that is actually being submitted, and whether its conclusions follow from its own evidence. A planner can do all three without holding the technical qualification.

Work through it in a fixed order. Reports fail early far more often than they fail deep, and finding the wrong scheme reference on page two saves an afternoon.

First checks on scope and date

Read the instruction the report was written to. A competent report states its scope and its limitations near the front, and those two paragraphs tell you what it does not cover. If no scope is stated, that is the first finding.

Check the dates. Three matter: when the site work was done, when the report was written, and what has changed since. A ground investigation from 2019 on a site that has been used for storage since then is a desk study with old holes in it. Survey data also has its own currency rules: ecological survey information more than about two to three years old is routinely questioned, traffic counts drift, and flood mapping is updated.

Then check that the report you have is the version referred to elsewhere in the application. Appendices go missing, and a report cited in the planning statement as revision C arrives as revision A more often than anyone admits.

Author competence and declared limitations

Find out who wrote it and what they are qualified to write. Several report types require a licensed or competent person as a matter of law rather than preference: ecological survey and mitigation licensing work, biodiversity metric calculations, contaminated land investigation, and fire engineering documents. Others carry a strong professional expectation, such as acoustics, arboriculture, transport and heritage.

Look for the author's name, their institute membership, and whether the document has been checked and approved by someone more senior. A report with no named author and no quality assurance block is harder to rely on and easier to attack. Where you are unsure whether the author's competence matches the standard, our note on who can prepare an overheating assessment shows how to frame that question for one report type, and the professional directory sets out the review route where sign-off is needed.

Declared limitations are useful rather than embarrassing. A report that says it could not access the rear garden is telling you where the risk sits. A report with no limitations at all on a constrained site is usually hiding them.

Whether the scheme assessed is the scheme submitted

This is the check that catches the most problems and takes the least time. Open the report's site plan and the application drawing side by side.

• Is the red line the same, including any land taken for visibility or drainage
• Is the unit count and mix the same, and the floorspace
• Are the levels the same, particularly finished floor levels in a flood risk report
• Is the access in the same position
• Does the parking provision match the transport work
• Are the drawing numbers and revisions cited the ones being submitted

A mismatch does not always invalidate the report, but it has to be explained, and the explanation belongs in a covering note rather than in a hope that nobody notices. Consultees notice.

Methodology against the cited standard

You do not need to run the method to check that it was followed. Take the standard the report names and look for its main procedural steps in the document.

Where the report cites a standard and then departs from it, the departure should be explained. An unexplained departure is a finding worth raising, because a consultee will raise it anyway.

Data sources and their age

Check where each input came from. Public datasets carry a date and a version, and a report that reproduces a flood map without saying when it was accessed is inviting a question. Trip rates taken from a national database should name the site selection criteria. Groundwater levels should come from monitoring rather than from a single dip.

Watch for assumptions that have quietly become inputs. A statement early in the report that a figure was assumed, followed later by that figure appearing in a calculation without its caveat, is the most common way a technical document overstates its certainty. Sampling and analysis introduce the same risk, which is why laboratory accreditation matters for soil and water work, as set out in our note on accredited laboratories.

Conclusions that outrun the evidence

Read the conclusion first and last. On the second reading, ask whether each sentence in it is supported by something earlier in the document.

The patterns to watch for are familiar. A conclusion of no adverse effect where the assessment identified effects and proposed mitigation, without saying that the conclusion depends on that mitigation. A recommendation for further survey buried in an appendix but absent from the summary. A statement that the proposal accords with policy, when the policy is not cited anywhere in the report. And an executive summary written for the client rather than for the council, which the case officer will read as advocacy.

Mitigation needs to be capable of being secured. If a report relies on a measure that cannot be written as a condition or an obligation, it has not solved the problem.

Raising issues without losing the relationship

Send findings as questions with references, not as a list of faults. "Section 4.2 assumes a 30 mph approach speed, but the submitted drawing shows the access on a 60 mph section. Can you confirm which applies?" gets a quick answer. "The transport report is wrong" gets a defensive email and a delay.

Separate the findings into three groups: matters that must change before submission, matters to note in a covering letter, and matters that are a difference of professional view. Agree who is responsible for each, and set a date. Where the appointment is being transferred to a contractor partway through, clarify who answers consultee comments afterwards, which is covered in our note on novating a consultant appointment.

And be willing to accept an answer you did not expect. A reviewer who treats every query as a defect burns the relationship with the one consultant who will be available in three weeks when the council asks something harder.

PlanScope drafts the narrative documents that sit around specialist reports and flags where facts are missing, which makes gaps easier to spot at review. 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.

This is general guidance, not legal advice. Validation requirements and local expectations vary, so check with the local planning authority before relying on any review conclusion.