Thursday, June 19, 2008
The March "Audit"- Part 1
Starting from an end point, between 4/29 and 5/1, Cuyahoga was one of 11 Ohio counties that conducted a "pilot" election "audit," per Secretary of State Directive 2008-39 - to boost "voter confidence" in the trustworthiness of electronic election equipment, and the success and accuracy of the March election. That audit too has been deemed "a success."
Though possibly a baby-step toward thinking about checking their work, and an actual audit – which even the Everest study showed should be mandatory - the CCBOE’s was hardly the “audit” that most people would normally assume.
It was more “a type of” recount, but one that had been actually strategized (though that part of the plan was not shared with witnesses,) to best make sure that the hand counts of each of the 99 precincts selected, would most certainly match the scanner totals – thus avoiding the prospect of having to do a full countywide hand count – and to best assure “success”!
The Directive said if on the second go-round the difference between the handcounts and scan counts was greater than 2 (which after counties got started was announced to have meant 2 per precinct…) a full hand count would have to ensue. (The CCBOE announced after they got started they had changed that to 5 because of their size. I actually thought that change was reasonable among all 7% of Cuyahoga’s 1436 precincts. What was not reasonable was the changing of “audit” “protocols” as workers felt needed, to assure success! - sometimes on the fly, and often not telling anyone.)
So they had the ES&S tech scan one precinct at a time, hardly as in an election environment: and suddenly began calling the M650 scanners, “THE tabulator” when “the tabulator” that was used throughout the election and which prepared the official final results was different software – it was the ES&S Unity software, held on a computer, where after M650 totals had been transferred to ZIP disk, were uploaded and Unity then processed the totals for a report to be printed out.
Though when I could not find the audit supervisor, I appealed to the Deputy Director that regular election software should be checked and used in the audit, and he agreed and told the supervisor to use Unity as the tabulator - after the Deputy Dir. left the warehouse in the morning (it’s not a great place to hang around) and before he returned later in the afternoon, they had begun again using the M650 scanners as the tabulators, printing out the precinct results one at a time from the dot-matrix printers below each scanner. The Deputy Director said nothing about the change. (?)
At the end of this film you’ll hear that interchange, (did not want to stick the camera in people's faces.) At the beginning you’ll see that though audit witnesses were invited to join and take part at 8:30a, the volunteer witnesses sat around wasting time that Tuesday workday morning, as the tech cleaned the scanners (and then they ran the zero reports and a 30-ballot test deck) until well after 10:30a.
You'll also hear both the " we're taking it slow" statement, and "we've got time constraints" statement when it came to uploading results to Unity.
I still wonder why the Unity software was avoided.
(Though it appeared that on the last day they did upload the totals to Unity, you'll be able to see on the final audit film in the next post, and though I've requested that Unity report, as of this date, June 19, I have not received it.)
Though possibly a baby-step toward thinking about checking their work, and an actual audit – which even the Everest study showed should be mandatory - the CCBOE’s was hardly the “audit” that most people would normally assume.
It was more “a type of” recount, but one that had been actually strategized (though that part of the plan was not shared with witnesses,) to best make sure that the hand counts of each of the 99 precincts selected, would most certainly match the scanner totals – thus avoiding the prospect of having to do a full countywide hand count – and to best assure “success”!
The Directive said if on the second go-round the difference between the handcounts and scan counts was greater than 2 (which after counties got started was announced to have meant 2 per precinct…) a full hand count would have to ensue. (The CCBOE announced after they got started they had changed that to 5 because of their size. I actually thought that change was reasonable among all 7% of Cuyahoga’s 1436 precincts. What was not reasonable was the changing of “audit” “protocols” as workers felt needed, to assure success! - sometimes on the fly, and often not telling anyone.)
So they had the ES&S tech scan one precinct at a time, hardly as in an election environment: and suddenly began calling the M650 scanners, “THE tabulator” when “the tabulator” that was used throughout the election and which prepared the official final results was different software – it was the ES&S Unity software, held on a computer, where after M650 totals had been transferred to ZIP disk, were uploaded and Unity then processed the totals for a report to be printed out.
Though when I could not find the audit supervisor, I appealed to the Deputy Director that regular election software should be checked and used in the audit, and he agreed and told the supervisor to use Unity as the tabulator - after the Deputy Dir. left the warehouse in the morning (it’s not a great place to hang around) and before he returned later in the afternoon, they had begun again using the M650 scanners as the tabulators, printing out the precinct results one at a time from the dot-matrix printers below each scanner. The Deputy Director said nothing about the change. (?)
At the end of this film you’ll hear that interchange, (did not want to stick the camera in people's faces.) At the beginning you’ll see that though audit witnesses were invited to join and take part at 8:30a, the volunteer witnesses sat around wasting time that Tuesday workday morning, as the tech cleaned the scanners (and then they ran the zero reports and a 30-ballot test deck) until well after 10:30a.
You'll also hear both the " we're taking it slow" statement, and "we've got time constraints" statement when it came to uploading results to Unity.
I still wonder why the Unity software was avoided.
(Though it appeared that on the last day they did upload the totals to Unity, you'll be able to see on the final audit film in the next post, and though I've requested that Unity report, as of this date, June 19, I have not received it.)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment