Weekly register changes

We diff the register rather than re-reading it

The interesting question is never who is on the register. It is what appeared on it since the last time you looked.

Diffing, not scraping

We keep a dated snapshot of every registered location in England and compare each new pull against the last. What comes out is a change set: appeared, disappeared, altered. That is a far smaller and far more useful object than the register itself, which is tens of thousands of rows that barely move week to week.

Things that go wrong when you do this carelessly

A failed fetch reading as empty: An empty result must never be recorded as a successful run, or the watermark advances past a window nobody read.
Concurrency mistaken for a hang: The CQC API throttles on concurrency and signals it with a bare 403. One worker is measured, not cautious.
Deregistrations going unseen: A delta that only fetches unseen locations never notices the ones that quietly left.
Counting the same service twice: Both registrations stay live through a handover, so a naive diff reports one home as two.

Contacting us, and not hearing from us

We work only from published UK public records and lawfully accessible business information. If we have emailed you from this domain and you would rather we did not again, reply with "remove" or write to the address below. Suppression is permanent and applies across every campaign, brand and sending domain we operate, not only the one that contacted you.