Accuracy checks

Each layer of the archive is scored against a sample checked by hand against the source pages: motions and votes, split votes and the ordinance pipeline, the payables lists and Treasurer's reports, project facts and the debt figures. The scores below are computed on the live data.

Hand-checked samples and the current errors
AreaWhat is checkedCheckedErrorsError rate
VotesMember votes on 114 hand-checked motions
wrong, missed or invented votes
48500.0%
VotesMotion results (carried or failed)11400.0%
VotesDissents (no votes and abstentions)
missed or invented
3000.0%
DecisionsSplit-vote rows (tally, who voted no, result)3600.0%
DecisionsOrdinance pipeline rows (reading dates, status, days)4100.0%
SpendingPayables line fields (25 of 28 sample lines found)
lines recalled: 89% (scans with missing rows)
4500.0%
ProjectsPay application fields9000.0%
ProjectsChange order fields1400.0%
FundsTreasurer's report values (5 reports)6000.0%
FundsSummary of Receipts values1000.0%
ProjectsStatus, contractor, contract amount, dates and parties of sampled projects5200.0%
DebtIssue facts and balances (15 issues)5000.0%
DebtCity-wide totals and debt-limit figures800.0%

What the samples do and do not show

The samples are small (tens of motions, a few hundred votes, a handful of reports per layer), chosen at random across eras where possible, and some were drawn from documents never used while writing the rules. A clean score means the rules work on documents like those; it does not prove every page in the archive was read correctly. Old, faint or handwritten scans are the most likely to be misread. Known gaps and the data checks that flag doubtful rows are on the coverage page.

If you find an error, please .

Data last updated October 15, 2026. Built from the archive's documents; see how the data is built.