Support Accept Reject Abstain voting: Difference between revisions

From electowiki
Content added Content deleted
imported>Homunq
No edit summary
imported>Homunq
(Redirected page to Majority score voting)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
#REDIRECT [[Majority score voting]]
Support Accept Reject Abstain (SARA) works as follows:

# '''Voters can support, accept, reject, or abstain on each candidate. Default is abstain. Candidates get 2 points for each percent of "support" and 1 point for each percent of "accept", for a total of 0-200 points. '''
#*''"Support" the best candidates (perhaps a quarter of them), "reject" the worst (perhaps half of them). "Accept" and "abstain" are for the ones in the high middle range. For those, "accept" if you want to help them beat somebody worse, and "abstain" if you could live with them but are hoping for somebody better.''
# '''Eliminate any candidates rejected by over 50%, unless that leaves no candidates with over 50 points.'''
#* ''If possible, the winner shouldn't be somebody opposed by a majority. But this shouldn't end up defaulting to a candidate who couldn't at least get accepted by over 1/2 or supported by over 1/4 (as in, a majority subfaction of a divided majority, such as Nashville voters in the example below).''
# '''Highest points wins. In case of a tie, fewest rejections wins.'''
#* ''This finds the candidate with the widest and deepest support.''

== As the first round of a two-round system ("SARA with runoff") ==

If this system is used as the first round of a two-round runoff, then you want to use it to elect at two finalists in the first round. Thus, run the system twice. The first time, replace "50%" in step 2 with "2/3".

Then, to find the second winner, if the first-time winner got 1/3 or more support, first downweight those ballots as if you'd eliminated enough of them to make up 1/3 of the electorate. Otherwise, discard all of the ballots which supported first-time winner. After downweighting or discarding, run SARA normally.

If all the candidates in the first round got a majority of 0's, then you can still find two finalists as explained above. But the voters have sent a message that none of the candidates are good, so one way to deal with the situation would be to have a rule to allow candidates to transfer their 2-votes to new candidates who were not running in the first round, and if those transfers would have made the new candidates finalists, then add them to the second round along with the two finalists who did best in the first round. In that case, since there would be more than two candidates in the second round, it would be important to use SARA for the second round too.

== Relationship to NOTA ==

As discussed in the above section, if all the candidates in the first round got a majority "reject", then the voters have sent a message that none of the candidates are good, akin to a result of "[[none of the above]]" (NOTA). SARA still gives a winner, but it might be good to have a rule to limit the chance that such a winner would remain in office for multiple terms. This could either be a hard term limit, so that such a winner could only legally serve one term; or perhaps a softer rule that if they run for the same office again, the information of what percent of voters had rejected them should be next to their name on the ballot

== An example ==

{{Tenn_voting_example}}

Assume voters in each city give their own city 2; any city within 100 miles, 1; any city between 100 and 200 miles, a blank; and any city that is over 200 miles away or is the farthest city, 0. (These assumptions can be varied substantially without changing the result, but they seem reasonable to start with.)

<div class="floatright">
{| border=1
!City
!Support
!Accept
!Abstain
!Reject
!score
|-
!bgcolor="#fff"|Cutoff<br>(must be)
|bgcolor="#fff"|
|bgcolor="#fff"|
|bgcolor="#fff"|
|bgcolor="#fff"|<50
|bgcolor="#fff"|>50
|-
!bgcolor="#fff"|Memphis
|bgcolor="#fff"|42
|bgcolor="#fff"|0
|bgcolor="#fff"|0
|bgcolor="#fcc"|58
|bgcolor="#fff"|(84)
|-
!bgcolor="#fff"|Nashville
|bgcolor="#fff"|26
|bgcolor="#fff"|0
|bgcolor="#fff"|74
|bgcolor="#fff"|0
|bgcolor="#bfb"|52
|-
!bgcolor="#fff"|Chattanooga
|bgcolor="#fff"|15
|bgcolor="#fff"|17
|bgcolor="#fff"|26
|bgcolor="#fff"|42
|bgcolor="#fcc"|47
|-
!bgcolor="#fff"|Knoxville
|bgcolor="#fff"|17
|bgcolor="#fff"|15
|bgcolor="#fff"|26
|bgcolor="#fff"|42
|bgcolor="#fcc"|49
|}
</div>

Chattanooga and Knoxville both get under half a point per voter, and are eliminated. Memphis is explicitly rejected by a majority, and is eliminated. Nashville remains and wins.

If Memphis voters tried to strategize by rejecting Nashville at 0 in the above scenario, it would have no effect.

If Chattanooga and Knoxville tried to strategize by supporting each other, this has a chance of working, but Memphis could safely defend Nashville by accepting it. Since Memphis is essentially guaranteed to be solidly rejected, the Memphis voters have nothing to lose by defensively accepting Nashville like this. A mere 13% of "accept" from Memphis's 42% — that is, under a quarter of the Memphis population — would give Nashville 65 points, more than double the combined size of Chattanooga and Knoxville, safely defending it.

[[Category:Graded Bucklin systems]]

Latest revision as of 17:52, 27 October 2016