Checking whether the report author visited the site

Whether the report author visited the site is a question worth asking before you argue about anything inside the report, because it decides how much of the document is observation and how much is inference. On a contested application it is also the fastest way to test the quality of an opponent's evidence. A report built from a site inspection carries the fingerprints of that inspection throughout. One built from aerial imagery and a records search reads smooth and slightly generic.

None of this is about catching consultants out. Desk-based work is proper work when the question suits it. The problem is a document that presents inference as observation, because the decision maker then relies on something that was never checked.

Why a site visit changes a report's reliability

Most technical planning judgements rest on observed conditions. A tree's category under BS 5837:2012 depends on its form, condition and defects, which means someone with a probe and a tape. A habitat classification depends on the species present, which means walking the parcel in the growing season. A noise assessment depends on what the baseline actually sounds like, including the intermittent sources that never appear on a map.

What inspection adds that no dataset provides: the thing that changed recently. Hedges grubbed out last autumn, a new access formed, a gully blocked, an outbuilding demolished, a neighbour's extension built. Published data lags reality by months or years, and the site is where the lag shows.

Internal evidence that a visit happened

Read the methodology and limitations sections first. A report based on inspection will normally contain:

• the date and time of the visit, and its duration where that matters
• weather, temperature and, for ecological work, the conditions relevant to the species surveyed
• the surveyor's name or role and their qualification
• what was accessible and what was not, stated plainly
• observations that could not be derived from published sources
• photographs with locations shown on a plan

A report based on desk study will usually say so in a single sentence, often buried: that the assessment is based on a review of available information. Take that sentence at face value.

The tell in the other direction is a limitations section that is generic. Where it lists constraints that would apply to any site anywhere, rather than to this one, the author may not have encountered any constraints because they were never there.

Photographs, dates and metadata

Photographs are the most useful evidence and the easiest to check. Look for: consistency of season and weather across the set, shadows consistent with the stated date and time, vegetation state consistent with the month, and viewpoints that correspond to a location plan.

Where the point is material, ask for the original image files rather than the report versions. Capture dates in the file metadata settle the question, and a set of images taken across two seasons tells you there were two visits. Be proportionate about it. This level of scrutiny is for a contested major application or an appeal, not for a neighbour's porch.

Surveys where a visit is mandatory

The report types where inspection is effectively a requirement, and where its absence undermines the conclusions:

Protected species work goes further: surveys and any mitigation licence require a suitably licensed ecologist, and the licence application itself depends on survey effort at the right time of year. A Preliminary Ecological Appraisal that recommends further survey has usually done its job. One that rules out protected species without a visit has not.

Acoustic work has its own tell. A Noise Impact Assessment should state instrument type, calibration before and after measurement, measurement positions with heights, and the duration of each period. Those details only exist if someone stood there.

Where a desk based assessment is legitimate

Say plainly which ones are fine as desk exercises. Archaeological desk-based assessment is a defined product built from historic environment records, maps and aerial photography, and the standard for it expects exactly that, with field evaluation as a separate later stage. Flood risk work relying on published modelling and mapping is a desk exercise until levels are needed. Viability appraisals, policy statements, transport work built on published count data and heritage significance assessments of a building whose interior is inaccessible all sit in the same category.

The honest form of words is a limitations paragraph saying what was not seen and what difference that could make. Where a contamination assessment says the walkover was not undertaken because access was refused, that is a limitation the reader can weigh. Where it silently omits the walkover, it is not.

Illustrative example: a tree report supporting an application to fell two trees for an access. The report gives categories and root protection areas, but no survey date, no photographs and no defect observations, and the schedule lists stem diameters in exact round numbers. The objection worth making is not that the categories are wrong. It is that the evidence base for them is not disclosed, and a re-survey is needed before the harm can be assessed. Illustrative only.

Questioning an opponent's report at appeal

At appeal the point has to be made properly. Set it out in the statement of case rather than saving it, identify the specific conclusions that depend on observation, and say what you say the correct position is, with your own evidence where you have it.

What tends to work: asking for the survey record as part of the evidence, drawing attention to internal inconsistencies between the report and the drawings, and putting your own dated photographs in. What tends not to work: asserting that the author cannot have visited, without evidence. An inspector will not make a finding of that kind on inference.

Remember that the drawing revision matters as much as the visit. An assessment prepared against a superseded layout may be diligent and irrelevant, and the check takes thirty seconds.

Asking the question before you rely on it

If you are the one commissioning, put it in the brief: a site visit is required, the report must state the date and conditions, photographs are to be supplied with a location plan, and the raw survey record is to be retained and made available. That removes the argument later.

If you are reviewing rather than commissioning, the same material is what a reviewer needs before signing anything, and reviewers who sign off drafts work to that standard. Whether a survey is still valid is the companion question, because a visit two years ago may no longer describe the site. And an Arboricultural Impact Assessment prepared to BS 5837:2012 is the clearest example of a document that cannot be written from a desk.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it. For specialist technical reports, qualified professional input may be required.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.