Checking who actually wrote a consultant's report
The quality assurance page tells you whether anyone senior read the report. Here is how to check authorship, spot recycled templates and raise a concern properly.
Turn to the back of any consultant's report and look at the quality assurance page. It should name three people: the author, the checker and the approver, with dates and a revision history. Where it names one person, or a company with no individuals, or the same name in all three boxes, you are looking at a report with no internal check, and that is the single most useful thing you can learn about it in thirty seconds. Checking who wrote the planning report author is a routine act of diligence, not an accusation, and doing it before submission is far better than discovering the answer at appeal.
The question that matters is not whether a graduate drafted it. It is whether anyone senior read it.
Author, checker and approver roles in a report
The three roles do different work and a competent practice keeps them separate.
The author writes it, usually having attended site and done the survey or the modelling. The checker reads it against the brief and the method, verifies the calculations, and tests whether the conclusions follow from the evidence. The approver takes professional responsibility for it leaving the office, which means they are prepared to stand behind the conclusion in front of a planning committee or an inspector.
What goes wrong is role collapse. On a small fee, the author and approver become the same person because there is no time to involve anyone else. That is defensible on a two-page technical note and indefensible on an assessment that supports a major application.
Where a report type carries a formal competence requirement, such as a licensed ecologist for a protected species licence or fire-engineering competence for a fire statement, the named individual with that competence must be the approver and not merely a reviewer in the chain. The professional directory exists for exactly that sign-off role.
Why the signature page matters
It is the only part of the report that makes a person accountable.
Read it for four things. Whether individuals are named rather than only the practice. Whether their qualifications are stated, and whether those qualifications match the work: an ecologist with chartered membership of the relevant institute, an acoustician with institute membership, a transport planner with a chartered transport qualification. Whether the dates are in a plausible order, because an approval date before the site visit date turns up more often than you would expect. And whether the revision history shows the report was revised after check comments, which is evidence the check happened.
A page that says "prepared by" with a company name and no individual tells you the practice does not want to name anyone. That may be policy rather than concealment, but it is worth asking.
Also read the limitations section. A report whose limitations disclaim everything the conclusion asserts is answering a different question from the one on the cover.
Experience of the person who attended site
Site attendance is the part that cannot be delegated upwards, and it is where experience shows.
The survey that matters was done by whoever stood in the field, climbed into the roof, read the sound level meter, or dipped the borehole. A senior approver cannot retrospectively see what was not recorded. So the relevant question is what that person's experience is, how long they spent on site, what the conditions were, and what they could not access.
Access limitations are the telling detail. An ecology report that records "roof void not accessed" and then concludes negligible bat potential has a gap. A structural report that did not lift a floor and concludes the joists are sound is inferring. Good reports state these limitations plainly and recommend what would resolve them. Poor reports leave them out.
Ask for the site record sheets or field notes. They exist, they are rarely requested, and they show how long the visit was and what was actually observed.
Template reuse and its warning signs
Templates are legitimate and necessary. The question is whether the template was adapted or merely populated.
The signs that it was not:
- policy references that do not match the authority or the plan period, for instance a superseded local plan policy number
- a methodology section describing survey work the report does not then present results for
- site descriptions with details that do not match the photographs
- an NPPF paragraph number quoted where the current edition uses policy codes, which indicates text carried over from an older report
- mitigation recommendations that are generic to the report type rather than specific to this site
- a conclusion that could apply to any site of that kind
The NPPF point is worth dwelling on. The Framework was renumbered in December 2024 and re-issued on 17 August 2026 with policy-coded chapters, so a report citing paragraph numbers in an edition that no longer uses them has been copied rather than written. That is quick to spot and it tells you what else to check.
Questions that test authorship quickly
Four questions, asked by telephone, settle it in ten minutes.
Who attended site, on what date, and for how long. What was the single most difficult judgement in the assessment and how was it resolved. Which parts of the conclusion are most sensitive to the input assumptions. And what would they want to do if there were more time and fee.
Somebody who did the work answers all four immediately and with specifics. Somebody who did not will answer the first and hesitate on the others, because those answers are not in the document. None of the questions is hostile, and all four are things a client is entitled to ask.
Illustrative example: a noise assessment supporting a mixed-use scheme. Asked which part of the conclusion is most sensitive, the author says the choice of representative background period, explains that the plant runs at night so the night-time value governs, and names the day in the survey week they used and why. That answer tells you the report is sound. A vague answer about following the standard tells you to read it again.
Raising a concern without a dispute
Most authorship problems are capacity problems, not misconduct, and they are fixed by asking rather than accusing.
Put it in writing as a request for clarification: please confirm who attended site and on what date, please confirm the qualifications of the author and approver, and please confirm whether the report has been subject to internal technical check. Ask for the field notes. Give a date for the response.
Where the answer is unsatisfactory, the proportionate step is an independent technical review of the specific sections you doubt, not a wholesale re-commission. A reviewer who checks the method, the inputs and the arithmetic in the critical section will cost a fraction of a new assessment and will either resolve the doubt or evidence it. Where the relationship has broken down, the handover issues are covered in changing consultant during a live planning application.
Do not raise it for the first time in a committee report or a statement of case. That converts a correctable gap into a credibility problem.
What to specify in the appointment
Write the authorship requirements into the brief, because afterwards you are negotiating.
State that the report must name the author, checker and approver with qualifications and dates. State that the named approver must hold the competence the report type requires, and name the standard or institute. State that the individual attending site must be named in the proposal and that any substitution requires notice. Require the field notes and raw data as deliverables alongside the report itself. Require the quality assurance process to be described in the proposal. And require the report to cite the current edition of national policy by its own referencing convention.
Those six lines change the document you receive. The equivalent checks for specific report types sit in who can sign a construction management plan and drainage engineer competence for a drainage strategy, and the appeal-performance question is covered in checking a consultant's appeal track record.
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.
Frequently asked questions
What are the author, checker and approver roles?
The author writes the report, usually having attended site and done the survey or modelling. The checker verifies the method, the calculations and whether the conclusions follow from the evidence. The approver takes professional responsibility for the report leaving the office. A competent practice keeps the three separate, and the quality assurance page should name all three with dates.
Is it a problem if a junior staff member wrote the report?
Not in itself. Junior staff authoring under supervision is normal and often produces better fieldwork, because they spend longer on site. The problem is an absent check: no named checker, no named approver with relevant competence, or the same name in every box. That means nobody senior tested the conclusion before it was submitted.
How can I tell a report is a recycled template?
Look for policy references that do not match the authority or plan period, a methodology section describing work whose results never appear, site descriptions inconsistent with the photographs, generic mitigation recommendations, and NPPF paragraph numbers quoted where the current edition uses policy codes. Any one of those tells you what else to check.
What should I ask the author directly?
Who attended site, on what date and for how long; what the most difficult judgement in the assessment was and how it was resolved; which parts of the conclusion are most sensitive to the input assumptions; and what they would do with more time and fee. Someone who did the work answers all four with specifics.
Should I ask for the field notes?
Yes. Site record sheets and raw data exist, are rarely requested and show how long the visit lasted, what was observed and what could not be accessed. Access limitations such as an unentered roof void or an unlifted floor are the detail that distinguishes a cautious report from one that infers more than it saw.
How do I raise a concern without a dispute?
In writing, as a request for clarification: confirm who attended site and when, confirm the qualifications of author and approver, confirm whether an internal technical check took place, and provide the field notes, with a date for the response. If the answer is unsatisfactory, commission an independent review of the doubted section rather than a new report.
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.