Why a healthy fleet-monitoring feed can show zero new alerts
One easy mistake in public-data monitoring is treating an empty alert table as a failed feed. Baseline coverage and change detection answer different questions.
A healthy result can mean:
- the official source was reached,
- the expected baseline was checked,
- the last sync completed, and
- no previously unseen record met the alert rules.
In FleetStart's current West Midlands configuration, a searchable CQC baseline can cover 12,869 locations while showing zero new CQC change alerts since that baseline. Roadworks is different again: thousands of received Street Manager events only become customer alerts when they intersect saved jobs. Zero matches can be the correct result.
The useful health indicators are records monitored, last successful sync, source status and the official-source route. Alert count alone is not a health check.
A source-backed July example and methodology is here:
These are research signals, not proof of buying intent. For public-data products, which status builds the most trust for you: coverage count, last sync or the direct source link?
Replies