FITZROVAI

Capabilities

What we build, shown by the UK Business Crime Map

Every capability on this page is in use on a live public product. Each one links to the place on the map where you can check it for yourself.

1Open data at national scale

Bringing a large public dataset together, cleaning it and checking it against official statistics before anyone relies on it.

On the map

  • Three years of police.uk street-level crime, September 2023 to September 2026, from 43 police forces across England, Wales and Northern Ireland.
  • 322 areas: Business Improvement Districts, plus town centres with no BID as controls.
  • Police.uk checked against ONS police recorded crime tables for completeness.
Check it: the data download →

2Fair comparison

A method that compares like with like, says how sure it is, and flags where the numbers are too small to read.

On the map

  • Each BID is compared with the area around it over the same months, so local trends don't masquerade as BID effects.
  • A verdict only where the gap is ten points or more, with robustness tests and small-number flags on every result.
  • Plain-English readings with the caveat attached: recorded crime is not the same as crime committed.
Check it: the methodology →

3Boundaries and geography

Getting the edges right, and being open about where they are not yet right.

On the map

  • 94 official boundaries, from the Greater London Authority's BID file, council digital files and traced council maps.
  • 189 provisional outlines, drawn paler and dashed, so each BID can see its area and correct it.
  • Police points shown as pins when zoomed in, with every shop shown only as "a commercial premises".
Check it: zoom in on the map →

4Forecasts checked in public

Expected ranges that close the gap before official data is published, fixed in advance and scored afterwards.

On the map

  • Police.uk publishes about seven weeks after each month ends. Looking ahead gives an expected range up to February 2027 for each area with enough data.
  • Ranges are dated and fixed before the police data for that month is opened.
  • First live check, September 2026: 247 of 295 areas (84%) fell inside their range, against a design target of about eight in ten. The misses are published too.
Check it: the looking-ahead record →

5AI assistants with guardrails

An assistant built into a public product that answers from your data, not from guesswork, and knows what it must not do.

On the map: Member B (Beta)

  • Answers only through the map's own tools and published sources, with each figure kept to its own period.
  • States its caveats, points to 999 or 101 where that matters, and declines questions about personal safety or individual shops.
  • Privacy by design: places are resolved in the browser, full postcodes are cut to the district, and no accounts or IP addresses are stored.
  • Tested against a fixed set of questions, including attempts to misuse it, before launch. Rate limits and an off switch are built in.
Check it: ask Member B →

6Sourcing and information rights

Going to primary sources, and using Freedom of Information where the data isn't published.

On the map

  • A BID counts as a BID only with a primary source: a council record, a ballot result, the BID's own plan or the British BIDs index.
  • Council Freedom of Information requests for levy lists and boundary maps.
  • Greater Manchester Police doesn't publish to police.uk, so three Greater Manchester BIDs were added from a Freedom of Information reply.
Check it: data sources →

7Public tools that work everywhere

Products that work on a phone in the street as well as on a desk.

On the map

  • A fast map with search by BID, town or postcode, a full-screen mode, light and dark themes, and filters for London, robust results and larger areas.
  • Charts, tables and an area drawer for each result, readable on a phone.
  • No cookies and no personal data collected.
Check it: open the map →

8Engagement that brings data in

Turning a public product into a two-way relationship with the people who hold the local picture.

On the map

  • A contribute form for corrections and local context. Nothing is published without review, and Member B can draft a contribution for checking.
  • Individual briefings for each area, and a note showing business crime partnerships how the map helps evidence the BCRP National Standards.
  • A counts-only monthly return so partnerships can show what never becomes a police record.
Check it: the contribute form →

9Governance and transparency

Clear licences, published methods and a record of every change.

On the map

  • Published under Creative Commons Attribution 4.0, built on police.uk data under the Open Government Licence.
  • A dated corrections log and a data dictionary for every column.
  • Neutral by design: no politics, no league tables, nothing about individuals.
Check it: corrections log →

What it could do for you

The same approach, applied to your place or your data

BIDs and town centres

An honest picture of your area against its surroundings, briefings for your board and levy payers, and your own data alongside police figures.

Business crime partnerships

Evidence for the BCRP National Standards from counts you already collect, set against police data and an expected range.

Councils and police

A shared, neutral picture to bring to ward panels and partnership meetings, with the method in the open.

Security and place teams

Officer logs turned into area-level counts in police categories, with no personal data, showing what never reaches a police record.

Any organisation with data

An AI assistant tuned to your own published data, with the same caveats, guardrails and privacy rules as Member B.

Talk to us

To explore any of this for your place or your data, email Dan Sandford at dan@oxcam.online.