Direct link to this page: http://www.copswiki.org/Common/SnapshotProtocol
- July 2016 -- Conducting Snapshot Protocol in San Diego and detected violation of election code. Filed lawsuit Details: M1658
- August 2016 -- Press conference detailing the court ruling in our favor. M1670
- June 2016 -- Sent letters to all 58 counties with some refinements from the prior election. Our team will be processing these responses soon.
- Compliance is higher but not 100%. Really small (one precinct) counties need not participate.
- Sent letters to all 58 counties in California requesting that they implement the Snapshot Protocol in the November 2014 elections.
The Snapshot Protocol
is designed to detect election fraud, in jurisdictions that use durable paper ballots (that can be recounted) and a post-election audit, a manual recount a fraction of the precincts and all races. This includes all counties in the state of California and a few other states.
California implements post-election manual tally procedures. These are intended to make sure the electronic devices are working correctly, and nothing more. Specifically, this process is not intended to detect election fraud due to compromised election officials or hackers. However, if we collect an election "snapshot," (a data file describing the election to the precinct level) at the right time, we can use these procedures as a check for central-tabulator election fraud which can flip elections. The protocol is easy to implement and is not unduly time consuming. We hope this protocol can be deployed to other election districts throughout California and other states where post-election audits are required.
Conducting this oversight protocol is important in itself to stop election fraud. If any potentially compromised employee or hacker knows an oversight group is conducting this protocol, they will be less likely to attempt such activities when there is a threat of being caught.
The steps in the oversight protocol are:
- Send a letter to the Registrar of Voters informing them of our requirements
- In San Diego, For June, 2014 election we sent this on May 15, 2014, and we received confirmation that they will be cooperative with our oversight requirements on May 28, 2014.
- In November of 2014, we sent letters to all 58 counties in California to enlist their support of the protocol, and many cooperated.
- Meet at the Registrar of Voters office the day after the election OR have the election office upload the snapshot file to our FTP Server (or access it on their website).
- On June 4, 2014 we:
- Picked up a CD with a full snapshot of the election as of the counting on election night.
- Assisted with and ensure the random selection of precincts for the 1% manual tally.
- We also fully video recorded the actions we take at this step.
- We also downloaded the (XML) report of the current results of the election
- (The snapshot file (173MB) was reduced to a spreadsheet (2MB).
- For Nov, 2014 we:
- Repeated the steps above for San Diego plus interacted with many Counties to get their cooperation remotely.
- On June 9th, and Nov 10th, they started the 1% manual tally.
- We visited the Registrar's office again and witnessed and video recorded the start of this process and some of the actual tallying.
- Registrar Michael Vu resisted video recording but he finally did allow it in June. In November, he agreed to videorecording without any resistance.
- Access the 1% Manual tally report, and create our oversight report.
- Completed for June 2014.
- Pending for Nov 2014
- If we detect manipulation of the election, will pursue it at this point, probably in the courts.
- We did not detect any election fraud in this election.
This protocol can be implemented in any jurisdiction that includes a post-election audit similar to the 1% manual tally required in California. The following map shows the current state. Please note that the light gray color in the legend relates to the lighter gray colors in the map! Primarily, we can focus on: Alaska, Connecticut, Montana, Minnesota, Missouri, New Mexico, and West Virginia. Also, the states of Nevada, New York, Oregon, and Wisconsin are also probably compatible. We will need to review the actual procedures used in each state to confirm that they are indeed compatible.
- States with Post-election audit procedures:
A complete list of the status of post-election audit procedures is here:
Most recent results first.
California counties are now required to use durable paper ballots and perform a one-percent manual tally. The manual tally was required by the Secretary of State to check that the computers are all working correctly; the manual tally was not designed to detect fraud. This Snapshot Protocol
will provide a means to detect election fraud if it is occurring to a significant level. We know that this method does not eliminate all chances for fraud, but it is important that the Registrar Of Voters
is aware that we intend to review it in this manner will put a check on some possible abuses. Hopefully, they will realize that fraud may be detected and they will not even try it.
The one-percent manual tally is based on a preliminary snapshot of the election, created within days of election night but before the election is certified. In the past, the Registrar Of Voters
would not include in this snapshot ballots that included any write-ins, Vote-by-mail (VBM) ballots or provisional ballots, and the sample size is known to be insufficient to be used as a check on the election, but it still usually will mirror the election quite well.
Traditional practice has been to select a set of precincts for manual tally by using a "random" selection process. Then, the operators of the central tabulator would produce reports of these precincts and provides those to the staff that will be performing the manual tally. There are usually about 17 precincts chosen where all the races are tallied, plus more are selected to make sure that all races have at least one precinct tallied.
Although we are not accusing anyone of any impropriety, we must assume certain possible manipulations of the vote to design a means to detect it. One manipulation can occur by compromised RoV
staff in the central tabulator by shifting votes from one candidate to the other. Without a full recount, this is very difficult to detect. A full recount is not automatic unless the vote count is close. Therefore, if this manipulation is used, it will be a significant modification such that the election will not undergo any form of full recount.
But the election is still subjected to the 1% manual tally, which could potentially detect a significant modification. If the election was fraudulently manipulated by RoV
staff using the central tabulator as mentioned, then it would be possible to cover that up in the 1% manual tally by producing "good" reports (undoing the manipulation) for the precincts in the manual tally while allowing many other precincts to remain compromised.
The Snapshot Protocol
requests that the RoV
supply our team a CD with a preliminary report of all the precincts PRIOR TO SELECTION for the manual tally. Thus, any precinct may be chosen for the manual tally and the election staff cannot "fix up" the data for the precinct (removing any election fraud) prior to the manual tally. The data on the CD should match the manual tally. If the manipulation occurred prior to the manual tally, then the snapshot review will discover errors in the 1% manual tally. If the manipulation occurred after the 1% manual tally, then the tally will not show an error, but the results in the snapshot data will be different from the final election results.
Assuming a worker at the Registrar Of Voters
is compromised, for example, with this snapshot comparison in place, it will be much more difficult to perform such electronic election fraud. If widespread fraud is occurring, it will likely also occur in the precincts chosen for the manual tally, and thereby detected. Therefore, compromised actors will not be able to perform their fraud.
With the snapshot protocol in place, the only other opportunity for fraud would occur in ballots added to the total after the manual tally occurred. It will be instructive to compare the preliminary snapshot with the ultimate results of the election. If any races flip due to those final ballots included, fraud may exist.
The following protocol uses the terms "Registrar of Voters" (or "ROV") and "1% Manual Tally" or "Manual Tally." These are specific to San Diego County and the state of California. Other states may use other terms, such as "Post-Election Audit," "Manual Count," etc.
- Send a letter to the Registrar Of Voters informing them of the oversight protocol we will be using and make specific requests, (see sample) as follows:
- Request a snapshot of election data on a CD. This must be made available for pickup prior to the random selection of manual tally precincts. This snap shot must be of the stage of the election that is also used for the manual tally. In other words, no additional ballots can be added to the election results until after the manual tally is complete. This CD MUST be received prior to doing the random selection. If it is not received prior to the random selection, then the protocol is broken.
- Request to observe (and possibly participate in) the random selection of the precincts to be used in the manual tally (probably about 15 precincts in San Diego).
- Request to observe the manual tally process. (You don't need to observe the whole thing, but you should understand what is going on).
- Request the report of the 1% manual tally including any discrepancies with computer counts. We are particularly interested if any reruns of computer counts are performed with differing results. If the final results differ from the snap shot, that information should be included and why it occurred. Also request checklists, logs, and work-papers created in the manual tally process.
- Download the official report of the election after election night from the Registrar's website. (In San Diego, we "view source", copy all, and save to a text file.)
- A group of team members should pick up the CD just prior to the random selection of manual tally precincts. A video camera should be used to document this.
- NOTE: In a prior attempt to perform this oversight procedure, they did not provide the CD until just after the random selection of manual tally precincts as they were "still working on it." After reviewing that procedure, we realized it was absolutely necessary that we receive the snapshot CD prior to the random selection of the manual tally precincts, or the protocol is broken and cannot be used to detect fraud.
- Team members should observe (and participate in) the selection of the manual tally precincts. It is okay if you are the outsider who rolls the dice, pulls ping pong balls, or whatever they use. Also video record this process.
- Team members should observe part of the manual tally process to understand the process. Video record your visits for documentation.
- The final report should be accessed of the manual tally results, and other checklists, logs and work-papers accessed from the ROV.
- Note: In the past, the report was vastly incomplete because it did not provide the actual election results for that precinct. But since we have the snapshot prior to the start of the manual tally process, that snapshot is also the partial result of the election that corresponds to the manual tally.
- Data analysis. After the election is complete the following steps should be completed.
- Vote counts for the precincts used in the manual tally should be extracted from the rest of the election data on the CD.
- Citizens Oversight has developed some computer programs to parse the election data and create concise spreadsheets, and to pull out the precincts utilized in the manual tally process.
- Review the Manual Tally report, taking special note if any reruns had to be performed.
- If reruns were required (i.e. re-scanning the ballots) to gain agreement with the manual tally, then election fraud may have been attempted.
- In this case, you should request that you inspect the tapes from the actual scans of those precincts. Take snap shots of the tapes to document them.
- If the tapes differ from the snap shot, then election fraud (central tabulator results manipulation) has likely occurred prior to the manual tally.
- Total up the results of the election using only the manual tally precincts from CD data. Compare with the actual results of the election.
- If the manual tally matches the snapshot and no problems were found in the review of the manual tally (no reruns) BUT if the sample of the election represented by the 1% manual tally DOES NOT match the results of the election (such as if the results were flipped significantly), then this implies election fraud may have occurred.
- If there are no discrepancies reported in the manual tally, and if the snapshot results are roughly the same as the election, then they probably did not attempt this type of election fraud, or simply lucked out and selected precincts that were not included in the sample.
Manual Tally Procedure as used by the San Diego Registrar of Voters
Manual tally procedure in a nutshell (COPS has several issues with this procedure and the RoV
has been notified).
- Select dates for the random draw of precincts and the actual tally, notify the public by placing a notice at the front counter (and perhaps the website).
- Random Selection of Precincts
- Calculate one percent and round up.
- Have scheduled observers attend the draw
- The procedure uses three sets of balls from 0-9 and one set of balls numbered 0 and 1, representing the four digits, (ones, tens, hundreds, and thousands, respectively).
- Shake the containers and draw balls manually.
- Draw ones, tens, hundreds digits.
- If the three numbers in step six is 650 or less, the thousands container is then shaken, otherwise if the number is 651 or greater, the selection is complete.
- Probability of selecting any number 650 or less or from 1000 to 1650 = (0.1)*(0.1)*(0.1)*(.65)*(0.5) = 0.0325%
- Probability of selecting any number 651 to 999 = (0.1)*(0.1)*(0.1)*(0.35) = 0.0350%
- The only time this would be correct is when "Cut Off" (i.e. 650 in this case) is 666 so that 666/2 = 1000-666.
- Probability of selecting any number 666 or less or from 1000 to 1666 = (0.1)*(0.1)*(0.1)*(.666)*(0.5) = 0.0333%
- Probability of selecting any number 667 to 999 = (0.1)*(0.1)*(0.1)*(0.333) = 0.0333%
- Therefore, this procedure does not produce exact results and is not generally applicable, however, results are approximately correct because 650 is almost the same as 666.
- Selecting precincts randomly will not necessarily result in even sampling of the precincts. In the November 2008 election, no precincts were selected in the range from 1 to 453 inclusive while nine precincts were chosen in the highest numbered 450 precincts. The likelihood of that happening is about 1 chance out of 10,000 tries, which is rare indeed.
- Record contests as selected by the random draw.
- Select additional precincts for the manual tally to cover all remaining contests on the ballot.
- Prepare for the manual tally, including:
- Order summary reports for election night and the related ballots. (COPs note: the staff creating these reports will know which ones are being requested, and therefore, could conceivably prepare known good reports for those precincts while the balance of the election may be substantially modified.)
- Conduct the manual tally
- Each precinct as one three-person team, one calls out the vote and two tally on separate sheets.
- Supervisor compares with summary report.
- If there is a variance, they re-tally until they agree, but no more than three times.
- Supervisor records results, variances, and causes (if knoswn) on consolidation log.
- When the tally is complete, return ballots for secure archival
- Compile a memo of the results for the RoV.
- We have received the response from the Registrar Of Voters and we are in the process of analysis. If you have computer skills and want to help, please let us know!
(Just attach your images to this topic and they will automatically be added to the gallery above!)
Summary of articles submitted (Add | All):
- (M1746) Snapshot Protocol Tutorial for Los Angeles 2017-04 election -- Ray Lutz, Citizens Oversight, 2017-03-27 CA_LosAngeles
- (M1735) Early VBM Discrepancies in San Diego 2016 Primary -- Ray Lutz, Citizens Oversight, 2017-03-19 CA_SanDiego, Questions to Election Official
- (M1728) Election Team Conference Call of 2017-01-05 -- Ray Lutz, Citizens Oversight, 2017-01-05
- (CitizensOversightStatusUpdate2016) Citizens Oversight Status Update 2016 -- Ray Lutz, Citizens Oversight, 2016-12-30
- (LegislativeAgendaForElectionIntegrity) Legislative Agenda for Election Integrity -- Ray Lutz, Citizens Oversight, 2016-12-20
- (M1721) CA_SantaClara Manual Tally Nov 2016 -- Lise Rehbock, Citizens Oversight, 2016-11-23
- (M1720) Tour of Socal Manual Tally Operations -- Ray Lutz, Citizens Oversight, 2016-11-22
- (M1718) CA_SanBernardino Manual Tally November 2016 -- Anna Mc Naughton, Citizens Oversight, 2016-11-21
- (M1717) CA_Alameda County Random Draw, Nov 2016 -- Lise Rehbock, Citizens Oversight, 2016-11-18 CA_Alameda
- (M1719) FL_PalmBeach Manual Audit -- Ray Lutz, Citizens Oversight, 2016-11-18
- (M1715) CA_San Diego Nov 2016 Manual Tally -- Ray Lutz, Citizens Oversight, 2016-11-15
- (M1716) CA_Sacramento Nov 2016 Manual Tally -- , Citizens Oversight, 2016-11-15
- (SnapshotProtocolFlorida2016Nov) Snapshot Protocol Trip to Florida 2016 Nov -- Ray Lutz, Citizens Oversight, 2016-11-14
- (M1713) Election Team Conference Call of 2016-11-13 from Sarasota FL -- Ray Lutz, Citizens Oversight, 2016-11-13
- (M1712) CA_Riverside Nov 2016 Manual Tally -- Anna Mc Naughton, Citizens Oversight, 2016-11-10 CA_Riverside
- (ManualTallyOversight) Manual Tally Oversight Procedure -- Ray Lutz, Citizens Oversight, 2016-11-07
- (RandomDrawOversight) Random Draw Oversight Procedure -- Ray Lutz, Citizens Oversight, 2016-11-07
- (ElectionOversightFlorida2016November) Election Oversight - Florida 2016 November -- Ray Lutz, Citizens Oversight, 2016-11-06
- (M1709) Visit to OC ROV during early VBM processing -- Ray Lutz, Citizens Oversight, 2016-11-02
- (M1707) 20161030 - Election team Orientation -- Ray Lutz, Citizens Oversight, 2016-10-30 Conference call also provides power-point presentation on election oversight -- 90 mins
- (M1706) 20161022 - COPs Party 2016 Presentation -- Ray Lutz, Citizens Oversight, 2016-10-22 Presentation at the 2016 COPs Party.
- (M1710) Experts: State should audit election results -- Michael Gerstein, Detroit News, 2016-10-17
- (M1703) 2016 10 03 Pre-trial Election Lawsuit Press Conference -- Ray Lutz, Citizens Oversight, 2016-10-03
- (M1704) SB-1235 (2006 - Bowen) Legislative History from SOS Archive -- , Secretary of State Archives, 2016-09-29 Requested by Raymond Lutz for Election Audit Lawsuit. Raymond collected key documents into a single package and underlined relevant passages. Otherwise unmodified.
- (M1696) Citrus County Random Selection and Audit Process -- Margaret Carlock, Citizens Oversight, 2016-09-09 FL_Citrus
- (M1694) Broward County Audit for 2016-08-30 Primary -- Diane Padro, Citizens Oversight, 2016-09-06 FL_Broward
- (M1690) Election Team Email of 2016-09-04 -- Ray Lutz, Citizens Oversight, 2016-09-04
- (M1691) Florida Manual Audit Election Code 101.591 -- Ray Lutz, Citizens Oversight, 2016-09-04
- (WelcomeElectionOversightNewbies) Welcome Election Oversight Newbies -- Ray Lutz, Citizens Oversight, 2016-08-31
- (M1684) Citizens' Oversight: Election Scrutiny Extended to Florida and Arizona Primary Elections -- Ray Lutz, Citizens Oversight, 2016-08-30
- (OversightSuggestionsInArizonaAndFlorida) Oversight Suggestions In Arizona and Florida for 2016-08 Primary -- Ray Lutz, Citizens Oversight, 2016-08-29
- (M1685) 2016 08 28 -- Emergency Conference Call on FL and AZ Primaries -- Ray Lutz, Citizens Oversight, 2016-08-28
- (M1677) 2016 08 25 Election Team Conference Call -- Ray Lutz, Citizens Oversight, 2016-08-25
- (M1676) Election Audit Lawsuit Update Press Release, Aug 23, 2016 -- Ray Lutz, Citizens Oversight, 2016-08-23
- (M1679) Election lawsuit on track for October trial -- Plaintiffs want registrar to count provisional ballots in quality control audit -- Joshua Stewart, Union Tribune, 2016-08-23
- (M1675) Election Lawsuit Overview and Status on Aug 21, 2016 -- Ray Lutz, Citizens Oversight, 2016-08-21
- (M1682) Tutorial -- Add an audit to Election audit database -- Ray Lutz, Citizens Oversight, 2016-08-21
- (M1673) Roster Review Procedure Tutorial -- Ray Lutz, Citizens Oversight, 2016-08-18
- (M1674) Election Oversight Team Conference Call of 2016-08-18 -- Ray Lutz, Citizens Oversight, 2016-08-18 (Invite and Agenda: Election Team Email 2016-08-16)
- (ElectionOversightProcedures) Election Oversight Procedures -- Ray Lutz, Citizens Oversight, 2016-08-10
- (M1672) Citizens' Oversight -- Election Team Conference Call 2016-08-10 -- Ray Lutz, Citizens Oversight, 2016-08-10 (Invite and Agenda: Election Team Email 2016-08-07)
- (ElectionAuditBestPractices) Election Audit Best Practices -- Ray Lutz, Citizens Oversight, 2016-08-08
- (RequestingInformationProcedure) Requesting Information Procedure -- Ray Lutz, Citizens Oversight, 2016-08-08
- (StateElectionDistrictTargetingProcedure) State Election District Targeting Procedure -- Ray Lutz, Citizens Oversight, 2016-08-08
- (M1700) 20160721 Snapshot Protocol Tutorial -- Ray Lutz, Citizens Oversight, 2016-08-02
- (M1699) Snapshot Protocol Tutorial -- Ray Lutz, Citizens Oversight, 2016-07-21
- (M1697) Contesting the Election Press Conference 2016-07-11 -- Ray Lutz, Bill Simpich, Citizens Oversight, 2016-07-11
- (M1668) July 6 Election Lawsuit Press Conference -- Ray Lutz, Citizens Oversight, 2016-07-06
- (M1663) Press Release: June 28, 2016 Press Conf: COUNT EVERY VOTE -- Ray Lutz, Citizens Oversight, 2016-06-27
- (M1661) Registrar of Voters Lawsuit Tutorial -- Ray Lutz, Citizens Oversight, 2016-06-26 -- Includes explanatory graphic image.
- (M1662) San Diego County Manual Tally selection meeting, June 8, 2016 -- Ray Lutz, Citizens Oversight, 2016-06-08
- (SnapshotResultsCaSanDiego2016Jun) Snapshot Results Ca San Diego 2016 Jun -- Ray Lutz, Citizens Oversight, 2016-06-07
- (M1711) Michigan Election Audit Documents -- , Michigan State Bureau of Elections, 2016
- (M1506) Snapshot Protocol for Election Oversight, tutorial seminar -- Ray Lutz, Citizens Oversight, 2014-10-12
- (M1504) Press Release on Oct 12, 2014 Snapshot Protocol Training Seminar -- Ray Lutz, Citizens Oversight, 2014-10-07
- (M1491) Election Snapshot Oversight Tutorial -- Ray Lutz, Citizens Oversight, 2014-09-15
- (M1451) Election Snapshot Data for June, 2014 -- San Diego County -- Ray Lutz, Citizens Oversight, 2014-06-04 Includes raw data and spreadsheet format.
- (M1443) Request Letter to ROV regarding Election Snapshot Review for June, 2014 -- Ray Lutz, Citizens Oversight, 2014-05-15 Includes the email response from Michael Vu, San Diego County Registrar
- (M1317) Request for Pre-tally selection Snapshot for 2012 -- Ray Lutz, Citizens Oversight, 2012-10-31 Registrar Of Voters
- (M1678) Risk-Limiting Post-Election Audits: Why and How -- Risk-Limiting Audits Working Group, Risk-Limiting Audits Working Group, 2012-10
- (M1686) Maricopy Precinct Selection Meeting for Aug 2010 Election -- John Brakey, Audit AZ, 2010-08-30 Precinct Selection Meeting: AZ_Maricopa county does not provide computer results that can be compared with the hand tally, which makes the audit a sham.
- (M1729) Principles and Best Practices for Post-Election Audits -- , electionaudits.org, 2008-09
- (M1503) Improving the Security, Transparency and Efficiency of California's 1% Manual Tally Procedures -- Joseph Lorenzo Hall, UC Berkeley School of Information, 2008-07-01 Manual Tally Procedures
- (M1683) Procedures for California's 1% Manual Tally -- Joseph Hall, UCBerkeley, 2008
See List Serve
for all email discussion lists and to add more.