To run an online voting contest without fraud, make every voter prove who they are with an SMS or email code, a ticket or an account, cap how many votes each person can cast per day, and review flagged bursts of votes before results are final. Just as important, publish the rules before voting opens and void suspicious votes openly, with reasons, so contestants and fans can trust the outcome.
This guide is about fraud prevention. For how audience voting, judges and big-screen results work in general, read how online voting works for pageants and talent shows (नेपालीमा).
What kinds of fraud happen in online voting contests?
Most voting fraud is not sophisticated. It comes from fans who want their favourite to win and find the easiest way to vote more than they should.
Common patterns:
- Many identities, one person: voting with friends' numbers, throwaway emails or several browsers.
- Many devices, one group: a fan club voting from a room full of phones.
- Scripts and bots: automated votes sent faster than any human could.
- Bursts from one network: hundreds of votes from one internet connection in minutes.
- Insider pressure: accusations that the organizer favoured someone, even when nothing was wrong.
The last one matters as much as the others. A contest can be technically clean and still lose trust if the rules were unclear.
Which voter verification should you choose?
Choose the strongest verification your audience can comfortably complete. Every step you add stops more cheating but also stops some genuine voters.
| Method | What it stops | Weakness | Best for |
|---|---|---|---|
| SMS code | Fake identities; one vote set per mobile number | People with several SIM cards; SMS costs | Public pageants and online contests |
| Email code | Casual repeat voting | Free email addresses are easy to create | Awards, smaller contests |
| Account sign-in | Repeat voting from one account | People can create several accounts | Communities with existing members |
| Ticket or pass | Anyone who did not register or attend | Only ticket holders can vote | Talent shows, college fests, live audiences |
| Contact without a code | Very little | Anyone can type any number | Low-stakes fun polls |
| Open (per device) | Accidental double votes | Easy to repeat with other browsers or devices | Quick polls on screen |
For a ticket-based vote, you can also require that the pass was scanned in at the gate, so only people actually in the hall can vote.
How should you set vote limits?
Limits decide how much difference one determined fan can make. Set them before voting opens and do not change them halfway.
- Per day: for example a few free votes per day, resetting at midnight Nepal time. Daily limits keep long contests fair for people who vote regularly but cannot vote in bulk.
- Per contest or per round: a ceiling across the whole contest or each round.
- Per contestant: a cap on how many of one person's votes can go to the same contestant.
- No splitting: optionally, all of a voter's votes in a round must go to one contestant.
- Per submission: a maximum number of votes in one click.
Announce the limits on the contest page in plain language, such as "5 votes per day per mobile number, resets at midnight".
How do rate limits, CAPTCHA and fraud flags work together?
Use three layers: hard limits that block, a CAPTCHA that slows bots, and flags that ask a human to look.
- Hard rate limits block too many votes per minute from one IP address or one device. Set them high enough for a crowded venue where many people share Wi-Fi.
- CAPTCHA before sending a code or casting a vote makes scripted voting much harder.
- Fraud flags mark votes that look unusual — a burst from one IP address, a burst from one network range, or one device used by many different voters — without removing them automatically.
Flags are a prompt to investigate, not a verdict. A college hall or banquet on one Wi-Fi network will naturally produce bursts from one IP address.
How do you void suspicious votes fairly?
Void, do not delete, and always record a reason. A clear trail protects you when a contestant's supporters complain.
- Review flagged votes grouped by network or device, and look at the pattern, not single votes.
- Void the votes you are confident are abusive, with a short reason such as "scripted burst from one device".
- Keep voided votes in the record; they stop counting but remain visible to the organizer.
- Restore votes voided by mistake.
- Note that a voided vote does not give the voter that vote back, so voiding is not a way to "refund" free votes.
- Decide before voting opens who has the authority to void votes, and keep that group small.
How should judges and public votes be combined?
Publish the weighting before the contest starts, for example 60% judges and 40% public in the final. Changing the weighting after seeing the results destroys trust instantly.
Further safeguards for judging:
- Score against named criteria, such as talent, presentation and question-and-answer, each with a maximum.
- With three or more judges, consider dropping the highest and lowest score, or using the median, so one judge cannot swing the result.
- Exclude a judge from scoring a contestant they are related to or have trained.
- Decide tie-breakers in advance: for example judges' score first, then public score, then the earlier vote.
What should the public see during voting?
Decide how much to show based on the kind of contest. Each option has a trade-off.
| Results setting | What the public sees | Trade-off |
|---|---|---|
| Live | Counts and percentages | Exciting, but encourages bandwagon voting |
| Ranks only | Positions without counts | Less pressure on trailing contestants |
| Top few | The leading contestants only | Builds suspense, hides the rest |
| After close | Nothing until voting ends | Calmest, best for finales |
| Hidden | Only the organizer sees results | For contests decided at a ceremony |
Add a short transparency note on the contest page explaining how votes are verified, how flagged votes are reviewed and how the final result is calculated.
What rules should you publish before voting opens?
Publish the rules on the contest page and in your announcements, and keep them unchanged until the contest ends.
- Who can vote and how they are verified.
- How many votes each person has, per day and in total, and when the count resets.
- When voting opens and closes, in Nepal time.
- How judges' scores and public votes are combined, and the tie-breakers.
- How suspicious votes are reviewed and voided.
- When and how results will be announced.
If you sell votes, what changes?
Paid voting is common for pageants in Nepal, and it raises the stakes. If you sell votes, require the same verified identity for buying as for voting, publish the price and any limits, keep a record of every purchase, and decide in advance how refunds and voided paid votes are handled. Be ready to show that paid and free votes were counted exactly as the rules said.
How does Eventlaya help prevent voting fraud?
Eventlaya's contests are built around these principles:
- voter verification by SMS code, email code, account, ticket (optionally checked-in only), contact or open device mode;
- one-time codes that expire after a few minutes, with limits on retries and on how many codes a number can request;
- free vote allowances per contest, per day (Nepal time), per round and per contestant, with optional no-splitting;
- per-minute limits per IP address and device, optional CAPTCHA, and flags for bursts and shared devices;
- voiding and restoring with reasons, and an audit log of voids, round decisions and judge score unlocks;
- judges' scoring on a phone or tablet with weighted criteria, conflict exclusions and tie-breakers;
- results settings from live to hidden, a transparency note, and CSV exports of votes and scores;
- phone numbers, IP addresses and devices stored only as protected hashes, not in plain form.
The college fest guide shows how to use ticket-based voting at a live event. See pricing for plans, or create a free account to try a contest setup.
Voting is one part of an event; for registration, passes and check-in see event management software in Nepal: a complete guide.
Key takeaways
- Verify every voter with an SMS or email code, a ticket or an account; open voting is for fun polls only.
- Set daily and per-contestant limits before voting opens and never change them midway.
- Combine hard rate limits, CAPTCHA and fraud flags, and review flags by hand.
- Void suspicious votes with a reason instead of deleting them, and keep an audit trail.
- Publish the rules, the judge–public weighting and the tie-breakers in advance.
Frequently asked questions
What is the most common fraud in online voting contests?
The most common problems are one person voting from many fake numbers, emails or devices, and bursts of votes sent by scripts or from one network. Verifying each voter and limiting how often they can vote stops most of it.
Is SMS verification enough to stop fake votes?
It stops most casual cheating because each vote needs a real mobile number that receives a code. Determined groups can still collect many SIM cards, so combine SMS codes with daily limits, rate limits and a review of flagged votes.
Should suspicious votes be deleted?
Void them rather than delete them, and record a reason. Voided votes stop counting but stay in the record, so you can explain every decision and restore a vote if it was voided by mistake.
How do you stop a venue's shared Wi-Fi from looking like fraud?
Many honest people at one venue share the same internet connection. Treat bursts from one network as a flag to review, not as automatic proof of fraud, and look at whether the voters were verified separately.
Should the public see live vote counts?
Live counts add excitement but can trigger bandwagon voting and pressure on contestants. Many contests show only ranks, only the top few, or nothing until voting closes, and then reveal results on stage.