Prepared by: Benford Bench Analysis Project
Data Sources:
Report Date: 2026-05-27
Elections Covered: November 3, 2020 · November 5, 2024
Status: Preliminary — pending precinct-level and device-level log verification; pending by-Ward Benford re-analysis of 2024 logs
This report integrates two independent lines of quantitative analysis applied to Chicago Board of Elections (CBOE) Election Day machine logs for the 2020 and 2024 General Elections:
The two analytical frameworks surface different and in some respects contrasting anomaly profiles for each election year:
Important methodological caveat: The two Benford analyses were not conducted under equivalent conditions. The 2020 logs were processed divided by Ward (each Ward's event stream analyzed independently), while the 2024 logs were processed with all Wards pooled into a single mixed stream. This difference has a direct and potentially significant impact on the number of qualifying data points that survive the 100-second inter-event filter, which in turn affects the statistical power of the chi-square test. The 2024 deviation figure of ~4 % should therefore not be read as a direct apples-to-apples comparison with the 2020 figure of ~10 % until a by-Ward re-analysis of the 2024 data is completed. Further by-Ward testing of the 2024 logs is pending.
Taken together, neither election's machine logs cleanly reconcile with its certified totals. The nature and likely source of anomalies, however, differs between the two cycles. 2020 shows the stronger statistical signature of log-level data manipulation; 2024 shows the greater operational breakdown or record-keeping failure at the scan-event level. The Benford comparison between the two years must be treated as provisional pending methodological alignment.
Traditional applications of Benford's Law to election data examine the leading digits of vote tallies per precinct. This analysis takes a methodologically stronger approach by examining inter-event time intervals (Δt) between consecutive log entries produced by ballot-scanning machines.
Why timestamps instead of vote counts?
Human-driven processes — voters feeding ballots, poll workers handling queues, machine throughput — generate naturally irregular time gaps that organically follow Benford-type distributions. Vote tallies, by contrast, are often artificially constrained by precinct size and are more susceptible to non-Benford behavior for legitimate structural reasons. Timestamp intervals are harder to fake consistently and are less likely to be directly tampered with by someone manipulating outcomes.
Methodology applied:
⚠️ Ward-level vs. pooled-stream methodological difference:
The 2020 analysis was performed on log streams divided by Ward — each Ward's scanner events were processed as an independent time series before aggregation. The 2024 analysis was performed on a single pooled stream with all Wards mixed together. This is not a trivial distinction:
Expected Benford first-digit distribution:
| Leading Digit | Expected Frequency |
|---|---|
| 1 | 30.1 % |
| 2 | 17.6 % |
| 3 | 12.5 % |
| 4 | 9.7 % |
| 5 | 7.9 % |
| 6 | 6.7 % |
| 7 | 5.8 % |
| 8 | 5.1 % |
| 9 | 4.6 % |
Deviation from this distribution in machine-log timestamps suggests that the natural randomness of voter arrival and machine processing was disrupted — either by mechanical issues, artificial batching, or deliberate log manipulation.
Every ballot scanner logs each feed attempt as a discrete event — whether the scan succeeds or fails. These event counts form an internal checksum that should, after accounting for re-feeds, spoiled ballots, and test records, reconcile approximately with the certified count. Material unexplained divergence between total logged scan events and the certified count constitutes a checksum failure.
| Metric | Count |
|---|---|
| Successful Ballot Scans | 629,231 |
| Failed Ballot Scans | 40,254 |
| Total Machine Scans | 669,485 |
| Official Board Report (Certified) | 288,593 |
| Metric | Count |
|---|---|
| Successful Ballot Scans | 862,726 |
| Failed Ballot Scans | 239,743 |
| Total Machine Scans | 1,102,469 |
| Official Board Report (Certified) | 458,144 |
Device clock note (per source): A subset of scanning devices carried incorrect internal date/clock settings during logging. Records falling outside Election Day bounds were identified and flagged; their inclusion or exclusion materially affects total scan counts.
| Election | Log Stream Method | Benford Deviation (Δt intervals) | Chi-Square Result | Comparability |
|---|---|---|---|---|
| 2020 | Per-Ward (divided) | ~10 % | Significant departure | Baseline — larger qualifying pool |
| 2024 | All Wards pooled | ~4 % | Moderate departure | ⚠️ Not directly comparable — smaller qualifying pool expected; by-Ward re-analysis pending |
The 2020 Benford analysis was conducted on log streams segmented by Ward, meaning each Ward's event sequence was processed independently before results were aggregated. This approach preserves the natural intra-Ward voter-arrival rhythm as the signal of interest: consecutive events belong to the same physical polling location, and their Δt values reflect real gaps between individual voters feeding ballots.
A ~10 % deviation from expected Benford first-digit frequencies in these intra-Ward inter-event intervals indicates that the natural irregularity of voter throughput was suppressed or altered across a meaningful portion of the 2020 log record. The source authors characterize this as suggesting "artificial smoothing or correction" of the log stream — consistent with post-hoc log editing, batch-injection of scan events, or automated regularization of timestamps.
This is the stronger fraud-model signal between the two elections. The per-Ward methodology maximises the pool of qualifying Δt values (because intra-Ward consecutive events have naturally longer gaps that more easily survive the 100-second filter), giving the chi-square test its full statistical power. Under those conditions, the 2020 logs show strong evidence of log-level temporal manipulation.
The 2024 Benford analysis was conducted on a single pooled stream combining all Ward logs together, without prior Ward-level segmentation. As explained in Section 2.1, mixing Ward streams in chronological order introduces large numbers of cross-Ward event pairs with very small Δt values (events from different Wards firing in near-simultaneous wall-clock time). These are removed by the 100-second filter, systematically shrinking the qualifying data pool relative to a per-Ward analysis.
A smaller qualifying pool reduces chi-square test power directly. The same underlying manipulation signal that would produce a 10 % deviation with a full per-Ward pool could produce a much lower measured deviation when the pool is depleted by cross-Ward noise filtering. The 2024 ~4 % figure therefore has two possible interpretations that cannot currently be distinguished:
Until the 2024 logs are re-run using the same per-Ward segmentation applied to 2020, Interpretation A and B cannot be separated. The lower 2024 Benford figure should not be read as an exoneration of the 2024 log record.
Critically, a lower Benford deviation in 2024 does not mean 2024 was clean — it means the type of measurable anomaly present in 2024 is different and, under current methodology, better captured by the checksum analysis in Section 5.
| Comparison | Value |
|---|---|
| Successful Scans − Official Report | +340,638 |
| Total Machine Scans − Official Report | +380,892 |
| Site-Reported Failed Scan Difference | +7,832 |
| Site-Reported Successful Scan Difference | +158,570 |
| Failed Scans as % of Total Machine Scans | 6.01 % |
| Successful Scans as % of Total Machine Scans | 93.99 % |
| Total Machine Scans as % of Official Report | 232.0 % |
The 2020 machine logs record 669,485 total scan events against a certified total of 288,593 — a 2.32:1 ratio. Successful scans alone exceed the certified count by 340,638 (+118.0 %).
| Comparison | Value |
|---|---|
| Successful Scans − Official Report | +404,582 |
| Total Machine Scans − Official Report | +644,325 |
| Site-Reported Failed Scan Difference | +87,633 |
| Site-Reported Successful Scan Difference | +440,491 |
| Failed Scans as % of Total Machine Scans | 21.75 % |
| Successful Scans as % of Total Machine Scans | 78.25 % |
| Total Machine Scans as % of Official Report | 240.7 % |
The 2024 machine logs record 1,102,469 total scan events against a certified total of 458,144 — a 2.41:1 ratio. Successful scans alone exceed the certified count by 404,582 (+88.3 %).
| Metric | 2020 | 2024 | Δ 2020→2024 |
|---|---|---|---|
| Successful Scans | 629,231 | 862,726 | +233,495 (+37.1 %) |
| Failed Scans | 40,254 | 239,743 | +199,489 (+495.6 %) |
| Total Machine Scans | 669,485 | 1,102,469 | +432,984 (+64.7 %) |
| Official Certified Total | 288,593 | 458,144 | +169,551 (+58.7 %) |
| Excess Scans (Total − Official) | 380,892 | 644,325 | +263,433 (+69.2 %) |
| Failed Scan Rate | 6.01 % | 21.75 % | +15.74 pp |
| Benford Log Stream Method | Per-Ward (divided) | All Wards pooled | ⚠️ Not equivalent |
| Benford Deviation (Δt) | ~10 % | ~4 % ¹ | −6 pp (provisional) |
¹ 2024 Benford figure is not directly comparable to 2020. The mixed-Ward pooling methodology reduces qualifying data-point pool size through the 100-second filter, diminishing chi-square test power. By-Ward re-analysis of 2024 logs is pending.
The most important finding of this combined analysis is that the two elections exhibit structurally different anomaly signatures, which carries distinct implications for what may have occurred in each cycle.
| Indicator | 2020 Status |
|---|---|
| Benford log stream method | Per-Ward (divided) — full pool |
| Benford Δt deviation | ⚠️ HIGH (~10 %) |
| Failed scan rate | ✅ Within borderline range (6.0 %) |
| Total scans vs. official | ❌ 2.32× official (+132 %) |
| Nature of anomaly | Temporal log structure |
The 2020 Benford deviation was measured using per-Ward segmented log streams, which is the methodologically sounder approach: each Ward's events are compared against themselves, preserving the natural intra-location voter-arrival signal. This methodology maximises the number of data points surviving the 100-second filter, giving the chi-square test its full power.
The resulting 10 % departure from expected Benford first-digit frequencies is statistically significant and is more consistent with artificial batch insertion, timestamp regularization, or post-hoc log editing than with any hardware failure. The per-Ward division means this signal cannot be explained away as a cross-Ward pooling artefact — the deviation is real within each Ward's own stream.
The failed-scan rate (6.0 %) is elevated above industry norms (~2–3 %) but is not extreme enough on its own to indicate equipment crisis. The overcount relative to the official report is large in both absolute (+380,892) and proportional (+132 %) terms.
Assessment: Under the Benford model, the 2020 logs present the stronger prima facie case for data-level manipulation of the machine log stream. The per-Ward methodology makes this the more analytically robust of the two Benford measurements.
| Indicator | 2024 Status |
|---|---|
| Benford log stream method | All Wards pooled — ⚠️ reduced pool |
| Benford Δt deviation | ⚠️ ~4 % (provisional — see note) |
| Failed scan rate | ❌ CRITICAL (21.75 %) |
| Total scans vs. official | ❌ 2.41× official (+141 %) |
| Nature of anomaly | Hardware/record-level inflation + methodological caveat on Benford |
The 2024 logs present a more complex picture. The Benford deviation appears lower at ~4 %, but this figure was derived from a pooled mixed-Ward stream. When all Wards' events are combined in chronological order, many consecutive event pairs in that stream originate from different Wards firing within seconds of each other in wall-clock time. The Δt for those cross-Ward pairs is frequently under 100 seconds and is removed by the filter, shrinking the qualifying data pool and reducing chi-square test sensitivity.
Because Benford's Law is scale-invariant but not sample-invariant, a depleted pool can suppress measured deviation even when the underlying log-level signal is present. The 2024 Benford figure therefore cannot be reliably compared to the 2020 figure until the 2024 logs are re-run with per-Ward segmentation. By-Ward testing is pending.
What the 2024 data does show clearly — in the checksum domain — is a catastrophically elevated failed-scan rate of 21.75 % (239,743 events), nearly 8–10× the acceptable industry threshold, and a total-scan-to-official ratio of 2.41:1. A genuine equipment failure of this scale across Chicago's precincts would have been visibly catastrophic and widely documented in real-time incident reports. Its apparent absence is a significant anomaly in its own right.
Assessment: The 2024 checksum anomalies are the most severe in absolute terms. The Benford comparison with 2020 must be treated as provisional: the mixed-Ward pooling methodology may have suppressed the 2024 Benford deviation by depleting the qualifying data pool through the 100-second filter. Whether a per-Ward 2024 analysis would reveal a Benford signal comparable to 2020 is an open question that the pending re-analysis will address.
The following are documented technical causes that election auditors investigate when machine-log totals exceed certified counts. They are listed as investigative hypotheses and are not conclusions.
| Factor | 2020 Relevance | 2024 Relevance | Notes |
|---|---|---|---|
| Artificial log smoothing / timestamp regularization | ⚠️ HIGH — Benford evidence | Low — Benford near-normal | Primary driver of Benford deviation in 2020 |
| Batch-injected scan events | ⚠️ Medium | Low | Would suppress natural Δt variability |
| Multi-scan / re-feed events | Medium | ⚠️ HIGH — explains some of 239,743 failed | Rejected ballots reinserted create multiple log entries |
| Incorrect device clock settings | Medium | ⚠️ HIGH — explicitly flagged by source | Records from wrong dates inflate daily totals |
| Test-mode scans not purged | Medium | ⚠️ HIGH | Pre-election L&A testing bleeds into operational logs |
| Provisional / spoiled ballots scanned but not counted | Medium | Medium | Adjudicated out of certified count but remain in log |
| Scanner firmware counting errors | Low | Low | Usually caught during L&A testing |
The 2024 failed-scan total of 239,743 is the single sharpest numerical anomaly in the combined dataset:
This combination — an implausibly high failure count with a provisionally lower Benford deviation — is consistent with multiple scenarios: scanner firmware logging re-scan attempts as discrete "failed" events, test records not purged from device memory, systematic incorrect device-state flags, or a manipulation signal present in 2024 that the current pooled-Ward analysis lacks the statistical power to fully surface.
| Election | Successful Scans Match Official? | Total Scans Match Official? | Failed Rate Normal? | Benford Δt Normal? | Benford Method |
|---|---|---|---|---|---|
| 2020 | ❌ No (+118.0 %) | ❌ No (+132.0 %) | ⚠️ Borderline (6.0 %) | ❌ ~10 % deviation | Per-Ward — full pool |
| 2024 | ❌ No (+88.3 %) | ❌ No (+140.7 %) | ❌ Critical (21.75 %) | ⚠️ ~4 % deviation ¹ | All Wards pooled — reduced pool |
¹ 2024 Benford result is provisional. Mixed-Ward pooling reduces qualifying pool size through the 100-second filter, limiting chi-square power. By-Ward re-analysis pending.
Neither election's machine logs reconcile with the certified report within any reasonable margin. The anomaly type differs: 2020's principal red flag is its Benford temporal signature measured under the more robust per-Ward method; 2024's principal red flag is its failed-scan count and total overcount magnitude. The Benford comparison between the two years is provisional pending methodological alignment.
The 2020 election shows stronger evidence of log-level data manipulation under the Benford model. A ~10 % deviation from expected inter-event timestamp distributions — measured using per-Ward segmented log streams — is statistically significant and consistent with artificial modification or injection of scan event records. The per-Ward methodology is the more analytically sound of the two approaches used and gives this finding its full chi-square power.
The Benford comparison between 2020 and 2024 is not methodologically equivalent and must be treated as provisional. The 2020 analysis used per-Ward segmentation; the 2024 analysis used a pooled mixed-Ward stream. Because Benford's Law is scale-invariant but not sample-invariant, mixing Ward streams in chronological order increases the number of cross-Ward event pairs eliminated by the 100-second filter, shrinking the qualifying data pool and reducing chi-square sensitivity. The 2024 deviation of ~4 % may reflect a smaller qualifying pool rather than genuinely cleaner logs. By-Ward re-analysis of the 2024 logs is pending and is required before the two Benford figures can be directly compared.
The 2024 election shows more severe operational anomalies in the checksum data. A 21.75 % failed-scan rate, 495 % higher than 2020, and a total-scan-to-official-count ratio of 2.41:1 indicate either a catastrophic and unreported equipment failure or systematic over-logging in the scan event record.
The two anomaly profiles are not mutually exclusive. It is possible for 2020 logs to have been manipulated at the log structure level while 2024 suffered from different hardware or software-level failures that inflated scan counts. It is equally possible that 2024 contains a Benford-detectable manipulation signal that the current pooled-Ward analysis lacks the power to measure — a question the pending by-Ward re-analysis will help resolve.
Neither election's machine logs constitute a self-certifying record. In both cycles, total logged scan events exceed the official certified total by more than 2:1, a ratio that cannot be explained by re-feeds and test records alone without further documentation from CBOE.
These findings are preliminary. They are derived from aggregate totals under non-equivalent methodological conditions; precinct-level, device-level, and properly aligned by-Ward Benford analysis is required before any definitive conclusions about the source, geographic distribution, or systemic nature of the anomalies can be drawn.
| Item | Detail |
|---|---|
| Checksum data URL | https://shavidica.cc/page/Projects/Benford-Bench/Elections/basic-election-checksums |
| Benford findings URL | https://shavidica.cc/page/Projects/Benford-Bench/Elections/pre-liminary-findings-2020-vs-2024 |
| Data as of | 2026-05-27 |
| Geographic scope | Chicago, IL (Cook County) — Election Day machine-scan logs only |
| Not included | Early vote logs, vote-by-mail scan logs, precinct-level breakdowns, scanner make/model inventory, L&A test records |
| Methodological non-equivalence | 2020 Benford analysis used per-Ward segmented streams; 2024 used a pooled mixed-Ward stream. These produce different qualifying data-pool sizes under the 100-second Δt filter. Direct comparison of deviation figures is provisional pending by-Ward re-analysis of 2024 logs. |
| FOIA status | Machine logs described as FOIA-released; underlying raw files not independently verified for this report |
| Disclaimer | This is an independent quantitative assessment of publicly cited aggregate figures. It does not constitute a legal, forensic, or official election audit finding. All conclusions are preliminary pending document-level verification directly from the Chicago Board of Elections. Independent review is encouraged; original data FOIA's at https://foia.amfile.org/browse/chicago-board-of-elections |
End of Initial Report