Council spending check, run in your browser

This page runs the Council Spending Scanner's checks on your own device for the council above and lists every row the checks flag. Each flagged row shows the council's own transaction number and the council's file it comes from, so you can look it up in the council's published file yourself. The scanner's other councils are shown as prepared results only.

See this council's prepared results in the Council Spending Scanner

Run the check

on your device


    

What has and has not been tested

the limits, stated plainly

Tested on a Windows 11 desktop computer, in Microsoft Edge 154 and in Google Chrome 155 (the Chrome for Testing build, not the everyday release). We recorded at least 79 complete runs of the whole check in these two browsers, from our own computer and from a public web host. Every run started from a newly created browser profile, with nothing saved from an earlier visit; 36 of them loaded the page straight after the browser launched, with the page's automatic retries switched off, and the slowest of all of them took 35 seconds (Bracknell Forest, over the internet, in Edge). Every one of these runs finished, and in every one the export files the program produced were the same as the original desktop program's, as compared by a separate test program (this page does not compare anything for you). The time each run took is in the line above the button.

We also looked up every flagged row's transaction number in the council's file named for it, with a separate program: all 49,300 rows of Wokingham and all 56,723 rows of Bracknell Forest were found in the TransNo column of that file, the column the council uses for its transaction number.

We also ran it in Mozilla Firefox 155 on the same Windows computer (the build that comes with the Playwright test tool, run without a window): at least 3 runs of each council, all finished, with the same export files as the desktop program. The other tests (cancelling, a failed download, fresh-profile starts) were not repeated in Firefox.

Not tested: phones and tablets, Safari (on a Mac or an iPhone), any other version of Firefox, and anything other than Windows. Before it downloads anything the page checks that your browser can set aside the memory the check needs (the most we measured was a few hundred MiB, on the computer we tested; the page asks for a little more than that to be safe) and shows the prepared results when it cannot. That check has not been run on a phone or in Safari, so there a run may be refused, may be slow, or may fail in a way we have not seen.

What this page does not do. It lists the rows our checks flag in the copies of the council's files we saved. It does not check the council's current files and it does not check our results for you: to check a row, look up its transaction number in the council's file.

What this page fetches, and from where

privacy

Opening this page fetches the page itself and three small files (the list of councils, the timing figures and the wording of the rules) from this site. Nothing else is fetched until you press the button.

Report a problem, or ask for a file to be removed

corrections

If a figure on this page looks wrong, or you are a council and would like a file taken off this page, open an issue on the public issue tracker of this site, naming the council, the file and the row number, and please do not paste personal data into it. You can also use the contact on the home page (under "Build with our stack"). A rule that looks wrong can be reported as described in Report a wrong rule. Reports are read; no response time is promised.