How to read your ward’s crime data without getting it wrong

Crime data is the dataset councillors most often quote and most often misread. A resident asks “is crime going up on our street?” and the honest answer is usually “I do not know, and here is why the headline figure is unreliable.” But almost nobody says that. Instead we repeat the number that happens to fit the narrative we already had.

This is a guide to reading police.uk data at ward level without falling into the traps that make councillors look either naive or alarmist. I have watched both mistakes happen. Neither is fatal, but both are avoidable.

What police.uk actually measures

Police.uk publishes monthly snapshots of reported crime at street level. “Reported” is the word doing the heavy lifting. It covers crimes that were logged with a police force and assigned a record. It does not cover crimes that were never reported. For categories like anti-social behaviour and vehicle crime, under-reporting is significant and varies by area.

The categories are standardised across forces: anti-social behaviour, bicycle theft, burglary, criminal damage and arson, drugs, other crime, other theft, possession of weapons, public order, robbery, shoplifting, theft from the person, vehicle crime, violence and sexual offences. Each record is geolocated to the nearest “snap point” (usually a road junction), not to the precise address, to protect victims.

This matters because the snap-point system means a cluster of records at the same junction does not necessarily mean the same property. It might be three incidents on three different streets that all route to the same junction on the map.

The two-month lag and what it hides

Police.uk lags real life by roughly two months. March data appears in late May. If a resident asks you about something that happened last weekend, the data will not help you for another eight weeks. For doorstep conversations that is usually fine. For anything time-sensitive: a spike residents are noticing right now, for example: you need to supplement the data with whatever the local safer neighbourhood team is willing to share.

The lag also hides genuine surges until it is too late to act politically. If vehicle crime tripled in your ward in February, you will not see it until April. A councillor who is only watching police.uk is always responding to the last quarter’s problem.

Categories that mislead the most

Two categories are particularly easy to misread.

Anti-social behaviour

ASB covers an enormous range of behaviour: noise complaints, gatherings, verbal abuse in the street, drug paraphernalia, intimidation. A ward with ten ASB records a month could be noisy on Friday nights or could have a genuine fear-of-crime problem. The number alone does not tell you which. You have to pair it with what residents actually describe.

Violence and sexual offences

This category lumps together two very different things. Violence includes everything from shouting matches to assault; sexual offences are a separate category of crime with different victim-support needs. In police.uk they are combined. Residents reading raw numbers sometimes conclude a ward is unsafe because of a spike in “violence” when most of that figure is actually low-level public-order incidents.

When you cite the number, specify what you mean. “Five reports of violence and sexual offences last month, most of which appear to be public-order incidents around the high road on Friday nights” is more honest and more informative than “five violent crimes last month.”

Concentration versus rate

A common mistake is to compare raw counts between wards. Ward A had 40 crime records, Ward B had 20, therefore Ward A is more dangerous. This ignores population, footfall, and the location of any major transport hub.

A ward that contains a mainline station will always have higher raw counts because people passing through commit and experience crime there. That does not make it more dangerous for residents. The right comparison is either per-resident rate (counts divided by ward population) or change over time within the same ward (this month versus the same month last year).

If you are going to quote crime figures in a leaflet, use change over time in your own ward, not comparisons between wards. “Burglary in our ward has fallen by 30% since last year” is a defensible statement. “Our ward is safer than the one next door” almost never is.

Stop and search: the hardest dataset

Stop and search records are published on police.uk separately from crime reports. Each record lists the location (at snap-point resolution), the legislation used, the officer-recorded ethnicity, gender and age of the person stopped, the reason for the stop, and the outcome.

This is the dataset where poor analysis causes the most political damage. Councillors who say “stop and search is going up in our ward” without context are usually missing three things:

• Whether the legislation used is Section 1 (reasonable suspicion) or Section 60 (blanket authorisation for a specific area and time). These are very different operationally.
• Whether the outcome field shows a find rate that matches the stop rate. High volume with low finds usually means an operational problem worth raising; high volume with high finds usually means intelligence-led stops.
• Whether there was a specific operation in the area that month. A named operation can inflate the numbers without indicating anything about day-to-day community experience.

If you are planning to speak publicly about stop and search numbers in your ward, talk to the borough’s safer neighbourhood lead first. The raw data will not give you the context you need to avoid saying something that is technically true but misleading.

Using the data without alarming residents

The strongest thing crime data can do for a councillor is let you answer questions without reaching for generalities. “We have had X reports of vehicle crime on this road over the last six months, and the pattern looks like it is concentrated on Friday and Saturday nights” is a useful thing to say on the doorstep. “Crime is a problem in our area” is not.

Specificity reassures. Generality scares. This is especially true with older residents, who are more likely to overestimate their actual risk and more likely to stop leaving the house if the conversation drifts into vague warnings. If you have the data, use it to narrow the picture, not to widen it.

When to loop in the policing team

There are three situations where you should stop reading the data and just call your local safer neighbourhood inspector:

• A sudden cluster that residents are noticing now (the two-month lag means the data will not help).
• A specific location that has had repeated violent or drug-related incidents (the snap-point system makes the data noisy at the single-location level).
• A pattern that looks like it might be organised: repeat vehicle crime on the same streets, for example, or burglaries following a predictable route.

Police.uk is excellent for trend-reading at ward level. It is not a live operational feed. Treat it as the overview and the policing team as the detail.