Bat emergence survey results: what reviewers check

The results section of a bat emergence survey report has one job: to show that the survey effort was adequate, that the conditions were suitable, and that the conclusions follow from what was recorded. A reviewer asked to sign off the report reads it in that order, and a section that leads with the conclusion and buries the effort table in an appendix gets sent back.

Bats and their roosts are protected under the Conservation of Habitats and Species Regulations 2017 and the Wildlife and Countryside Act 1981. Surveys informing a mitigation licence must be carried out by a suitably licensed ecologist, and a drafted report is a starting point for that person rather than a substitute for them.

What the results section has to prove

Three propositions, in this order. That the building or tree was assessed and assigned a suitability, that the survey effort matched that suitability, and that what was observed supports the roost status and species conclusions drawn.

Everything else is supporting material. The preliminary roost assessment sets the level of effort, so the results section should restate the suitability category, not make the reader flip back to find it. Where the assessment came out as negligible and no emergence surveys were done, say so explicitly and give the reasoning, because a silent absence of survey looks identical to a missing survey.

Where the preliminary ecological appraisal and the bat work were done by different people at different times, reconcile them. A report describing a building as having moderate suitability when the appraisal called it high is the kind of inconsistency that stops a sign-off.

Survey effort against the guidelines

The Bat Conservation Trust good practice guidelines set the benchmark, and the current edition is the one to cite. In broad terms, effort scales with the suitability of the feature: a single dusk or dawn visit for a structure of low suitability, two for moderate and three for high, spread across the survey season rather than clustered in a single fortnight.

Present it as a table, not as prose. A usable effort table gives, for each visit: the date, the survey type, the sunset or sunrise time, the start and end times, the number of surveyors and their positions, the equipment used including detector models and any thermal or infrared cameras, and the licence number of the lead surveyor.

Two omissions recur. Surveyor positions matter because a building with four elevations and two surveyors has blind spots, and the report should say how they were covered or acknowledge that they were not. And where static detectors were deployed, the deployment dates, positions and the analysis method belong in the same table, since a week of static data is evidence and a passing reference to it is not.

Weather, temperature and abort criteria

Emergence surveys carried out in the wrong conditions produce negative results that mean nothing. Record the temperature at the start and end of each survey, the wind, the cloud cover and any rain, and state the criteria used to decide whether to proceed or abort.

Conditions around or below 10 degrees at sunset, persistent rain and strong wind all suppress activity. A negative result in those conditions is not evidence of absence, and a report that presents it as such is making a claim the data does not support. Where a survey went ahead in marginal conditions, say why, and say what weight the result can carry.

Abort criteria should be stated in advance and applied consistently. A team that continued through a downpour on the third visit because the programme was tight should record that, and the reviewer will decide what to do with it.

Roost characterisation and species conclusions

Counting bats out of a gap is the easy part. Saying what kind of roost it is takes more.

The report should distinguish between a day roost, a night or feeding roost, a transitional or occasional roost, a maternity roost and a hibernation site, and should justify the classification from the evidence: the number of animals, the timing of emergence relative to sunset, the behaviour observed, the presence of droppings or staining at the access point, and the time of year.

Species identification needs the same discipline. Where identification rests on call analysis, say which calls, analysed how, and where the recordings are held. Where two species cannot be separated reliably on call, say so and give the genus rather than guessing. Annotated elevations showing each emergence point, cross-referenced to the visit on which it was recorded, are worth more than a page of description.

Where the report should say the evidence is insufficient

An honest report says when it cannot answer the question. The circumstances are predictable:

• Surveys carried out outside the optimal season, or with fewer visits than the suitability warrants.
• Access denied to part of a roof void or to a neighbouring elevation.
• A feature identified late in the survey programme with no time for the required effort.
• Conditions that fell outside the criteria on more than one visit.

In each case the right conclusion is that further survey is needed before the impact can be assessed, and the practical consequence is a delay to the following season. That is an uncomfortable sentence to write for a client, and writing it anyway is the difference between a report that survives review and one that does not.

Linking results to the licence application

Where a roost will be affected, a European protected species mitigation licence from Natural England is needed before the works, and the survey results are its evidential base. The licence application has to satisfy the three tests: that there is an imperative reason of overriding public interest or another qualifying purpose, that there is no satisfactory alternative, and that the favourable conservation status of the species will be maintained.

The results section feeds the first of those indirectly and the third directly. Roost type, species and numbers determine the scale of compensation, the timing of works, and whether the scheme can proceed under a low impact class licence held by a registered consultant or needs a full individual licence.

Write the results so that the method statement can be drafted from them without further site visits. A protected species survey whose results cannot support a licence application is a survey that will have to be repeated.

Red flags a reviewer will not sign off

Six patterns end a review quickly. A conclusion of absence based on one visit to a high suitability building. An effort table with no temperatures. A roost described as a maternity roost with no count, no date range and no supporting behaviour. Survey dates outside the season with no acknowledgement. Static detector data referred to but not presented. And a report that describes bats as present but proposes mitigation without characterising the roost.

The bat pages and report structure on the bat survey report type set out what a complete document contains. For specialist technical reports, qualified professional input may be required, and for bats it is a legal requirement rather than a recommendation.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

Browse the report types on PlanScope to draft the structure, then have a licensed ecologist complete and review it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.