Data Refresh Log

A scheduled job checks the source publications on a tiered schedule, matched to how often each subject actually moves. Rates and fuel prices are republished weekly. Assessor rolls and census tables move once a year, and checking those every week would be pointless load on a public service.

Nothing lands unless it passes. Each run rebuilds every derived figure and then runs the full test suite against the fresh data. If a figure regressed, a source changed shape, or a town went missing, the run fails and the previous data stays up. Data is committed only because the checks went green.

"Changed" means the figures moved. Every pull is stamped with the date it ran, so counting that as a change would mark everything as updated every week. We compare the content itself, which is why a run can honestly report that we checked and the publishing bodies had put out nothing new.

Checked is not the same as current. This page tells you when we last asked the publishing bodies for new figures. It cannot tell you how old their figures are, and those are different things: a census table published in 2023 and a tax rate set for fiscal 2026 are both "checked today" and neither is from today. The period a figure actually covers is stated beside that figure, on the page it appears on, because that is where it means something.

We publish what we hold and who published it. We do not publish the machine addresses, query parameters or per-source schedules behind each pull: naming the publishing body is the attribution these public sources ask for, and the assembly is our own work.

Public records contain errors, and we copy them faithfully. If a figure here disagrees with the town's own records, the town is right and we want to know. The contact is on the about page.

A recent refresh date means the figures were checked recently. It is not a warranty that they are accurate, current or complete. See the terms of use.