Skip to content

How scores update

Scores refresh monthly

BaseScore is recalculated and published once a month, usually in the first week. Between refreshes the score for a location does not move.

What you see in the platform is always the current score. The platform does not hold historical BaseScores, so you cannot look back at what a location scored earlier in the year.

What makes a score move

New data. Each refresh brings in the latest reported incidents. Where an area has seen a sustained rise in a particular kind of activity, that shows up in the score — and usually more visibly in the sub-scores for the categories involved.

Most month-to-month movement is small. A meaningful change generally reflects a real change in conditions rather than anything about the data.

What does not move a score

Changing the date range. This is the most common misunderstanding. BaseScore is fixed at the monthly refresh — adjusting the date filter changes the events and trends you are looking at, but it does not recalculate the score.

Changing the radius or filters — with one exception. Turning event categories on or off does change the score, because the score is aggregated across the categories you have selected. That is a change to what you asked for, not a change to the underlying data.

Tracking scores over time

If you need to follow how a location's score moves across months or quarters, the practical approach today is the API — pull BaseScore for your locations on a monthly or quarterly cadence and keep the series on your side. That is what most organizations tracking scores currently do.

Native change tracking is on the roadmap. See Integrations, and talk to your Customer Success Manager about setting it up.

If a score looks wrong

Ask us. If a score does not match what you know about a location, or has moved in a way you cannot explain, that is worth raising rather than working around:

  • support@baseoperations.com, or the Report an issue button in the platform
  • Your Customer Success Manager, for anything that needs interpretation or affects a deliverable

Include the location and what you expected to see. Ground-truth conflicts are genuinely useful to us — a score a team quietly distrusts is a score that stops getting used.