Static bat detectors: deployment and data interpretation

Static bat detector deployment earns its place when the question is how a site is used across the season rather than what leaves a particular roof at dusk. Passive acoustic units record every night they are out, in weather that would cancel a manual survey, and they cover positions no surveyor can stand in. What they cannot do is tell you where a roost is, how many animals there are, or reliably which Myotis species you are listening to.

That trade is the whole of the interpretation problem. A reviewer signing off a bat report needs to see that the author understood it.

Where static units add value over manual surveys

Manual emergence and re-entry surveys answer roost questions. Observers watch a defined elevation at a defined time and record animals leaving. A static detector answers activity questions: which linear features carry commuting bats, when the season starts and ends at this location, and whether the hedgerow proposed for removal is used differently from the one being retained.

Both belong in the same Bat Survey for most development sites of moderate or high suitability. Statics supplement the manual work and do not replace it, and a report that offers detector data instead of emergence surveys on a building with roost features will be sent back.

The other genuine advantage is coverage. Five units across a 12 hectare site for a week produce a spatial picture of activity that nine surveyor nights cannot, and that picture is what the lighting design and the mitigation layout are eventually built on.

Deployment positions, height and duration

Position the microphone away from clutter. Foliage within a metre of the element produces false triggers and masks calls, hard vertical surfaces behind the microphone create echoes that defeat classifiers, and a unit strapped to a tree trunk facing into a hedge records the hedge rather than the bats.

For each deployment record the grid reference, the height above ground, the orientation of the microphone, the habitat within 10 metres, the make and model of unit, the firmware, the trigger settings and the sample rate. Photograph each position. Those fields are what allows a reviewer to compare one location with another, and their absence is the most common reason detector data gets discounted.

Height depends on the question. Commuting activity along a hedge is recorded at roughly the height of the flight line. Activity over open grassland or a proposed building footprint is recorded higher. Where a scheme involves tall buildings, a single ground level unit will understate activity aloft, and saying so in the report is better than being asked.

Survey effort follows habitat suitability. The Bat Conservation Trust good practice guidelines set effort by suitability category, with a minimum number of consecutive nights per survey month and coverage spread across the active season. Take the figures from the current edition, note the edition in the methodology, and state plainly where the survey fell short of it.

What the classifier gets wrong

Automated classification is a screening tool. Treat its output as a hypothesis set rather than as a species list.

The error patterns are well established in the field and should be described in the report rather than assumed:

• Myotis species are not reliably separable to species from echolocation calls alone, and classifier output at Myotis species level needs manual support or should be reported at genus level
• long-eared bats echolocate quietly and are systematically under-recorded, so absence in the data is weak evidence of absence on the ground
• the two common pipistrelle species separate reliably by peak frequency, which is why they are the species people over-trust everywhere else
• social calls and feeding buzzes are frequently misassigned by classifiers tuned for search phase calls

State the software, the version and the confidence threshold used. Different versions of the same package produce different results from the same files, and a report that omits the version cannot be reproduced.

Manual verification of species level records

Set a verification protocol before the analysis starts and report it. At minimum, every record of a rarer species, every record that would change the assessment, and a stated sample of the bulk records should be checked against the sonogram by a named analyst.

Say what proportion was checked and what the checking changed. A sentence recording that manual review reassigned a proportion of automated barbastelle records to Myotis is more persuasive than silence, and reviewers read it as competence rather than as weakness. Where the Protected Species Survey supports a licence application, the licensing body will look at this section specifically.

Weather, battery failures and the honest record

Report effort as nights of usable data, not nights deployed. A unit that ran for seven nights and recorded nothing on two of them because the batteries failed produced five nights of data.

Tabulate the deployment with, for each night, the date, sunset and sunrise, temperature, rainfall, wind and whether the unit functioned. Nights below the temperature threshold in the guidelines are still data, but they are data about a night when few bats flew. Where results are being compared between locations, only nights common to both units belong in the comparison.

Theft and vandalism are ordinary events on development sites. Plan for a proportion of units to disappear and deploy accordingly rather than reporting a gap.

Presenting activity data without overstating it

A bat pass is a recording of a bat, not a bat. Passes cannot be converted into numbers of animals, and any statement about population derived from detector data is unsupportable.

Present activity as passes per night by species or species group, by location, with the deployment effort alongside. Compare locations within the study. Do not compare absolute values with figures from other sites or published studies, because different equipment, settings and software produce different counts from identical activity.

Where the assessment needs a significance judgement, make it explicitly and by reference to the ecological framework used, as set out for significance of effects, rather than letting a high pass count stand in for a conclusion. A scoping level Preliminary Ecological Appraisal should already have identified which features matter, and the detector data either supports that or revises it.

Turning the data into lighting and mitigation

This is where static data pays for itself. A week of recordings along each boundary tells you which features are commuting routes and which are not, and that distinction decides where dark corridors go.

Use the activity map to fix the lighting layout: zero direct illumination on the retained commuting features, luminaire positions and mounting heights set so that spill onto those features stays within the limits in the current lighting and bats guidance, warm spectrum sources, shields and part night operation where activity is concentrated after dusk. Then specify the lux limit as a measured commitment at named points, because a condition worded that way can be checked after construction.

Surveys and any mitigation licence for bats require a suitably licensed ecologist under the Wildlife and Countryside Act 1981 and the Conservation of Habitats and Species Regulations 2017. A drafted report is a starting point for that professional and not a substitute for them.

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. For specialist technical reports, qualified professional input may be required.