Voting and entry platforms used in Sri Lanka: what their terms say
Most public votes attached to contests in Sri Lanka run on ordinary online forms rather than dedicated voting software, and the entry terms published by organisers show exactly what those forms do. Dilmah's Flutter Shutter photography competition asks entrants to upload images to a Google Drive folder and share a link through the entry form. The IOBSL e-Photography Competition 2026 states that a submitted entry cannot be edited afterwards, which means the platform records the submission as final. The Ministry of Environment's SOBA SEYA competition requires all photos to be original work taken by the entrants. Reading the terms of each platform before entering tells you what the form logs, what it refuses and what happens if a rule is broken.
Facts rechecked on 8 October 2026.
What the published terms of entry actually cover
Entry terms are the nearest thing Sri Lankan organisers have to a platform manual. Dilmah's Flutter Shutter competition, run through dilmahconservation.org, describes a specific submission path: images go into a Google Drive folder, and each submission is shared as a link through the official form. That single sentence tells an entrant three things about the tooling. The organiser relies on a third-party file service, the judging material arrives as links rather than attachments, and the form itself is the record of who entered what.
The IOBSL e-Photography Competition 2026 takes a different position on the same mechanics. Its published rule, quoted directly, reads: "Once an entry has been submitted it cannot be edited." The platform therefore treats the moment of submission as final. No later swaps, no replacement files, no corrections through a follow-up email. An entrant who spots a mistake after clicking submit has, under that rule, already lost the chance to fix it.
The Ministry of Environment's SOBA SEYA competition addresses the content itself rather than the submission path. All photos must be original work, taken by the entrants. That requirement sits on the entry platform, not on a separate jury document, which means the form's own terms are where the ownership question is settled before anyone reviews a single image.
Put the three side by side and a pattern appears. None of these organisers built custom software. Each one assembled a public vote or a judged entry process out of a form, a file service and a published rule, then let the rules do the work that dedicated contest software would otherwise automate.
For anyone studying voting platforms in Sri Lanka, this is the structural fact. The platform is not one product. It is a stack: a form for identity, a file service for the material, and terms of entry that state what happens on top of both.
The practical consequence follows directly. Every question about duplicate votes, verification or fraud has to be answered from the terms and the mechanics of that stack, because the software itself rarely publishes a policy. The rule page is the platform's policy page.
- A Google Drive link is a submission address, not a vote counter.
- IOBSL's no-edit rule makes the first submission the only submission.
- SOBA SEYA puts originality into the entry terms themselves.
- Form plus file folder plus rule page: that is the whole stack.
- An organiser without custom software leans harder on written terms.
- The entry form doubles as the legal record of who entered.
- Terms written for photography transfer cleanly to public-vote entries.
- Where the software is silent, the published rule speaks.
- Submission-as-final rules shift all care to the moment of clicking.
- Third-party file services carry the material; the form carries identity.
- Nothing here required a bespoke contest product to be built.
Duplicate votes and what the mechanics allow
Duplicate vote rules in Sri Lanka are rarely written as software features. They are written as conditions in the entry terms, enforced by whatever the form and the organiser can actually observe. The IOBSL rule is the clearest example of enforcement by immutability: because a submitted entry cannot be edited, a second submission cannot quietly replace the first. If duplicates arrive, they sit side by side as separate entries, each of them visible to whoever reviews the folder or the form responses.
That is worth pausing on. A no-edit rule does not prevent a second submission from being made. It prevents the second submission from erasing the first. The organiser reviewing entries sees both, and any published rule about one entry per person then applies to the pair. The tool's design makes the duplicate reviewable rather than making it invisible.
Where a public vote is attached to a form-based entry, the counter is usually the organiser's own tally or the platform's response count, and the terms decide what counts as a valid response. No row in our sources describes an automated duplicate filter on any of these tools, which is precisely why the terms carry so much weight. The written rule is the only duplicate rule that exists.
This is also where honesty is required about limits. A form can log an email address, a name, a timestamp and a link, and it can refuse a duplicate if the organiser configures it to. What it cannot do, without dedicated tooling, is verify that the person behind the address is who they claim to be or that they are only one person.
So the answer to what platform terms say about duplicates is short: the terms we have read say either nothing or they say it indirectly. IOBSL says the entry cannot be edited, which freezes the record. The others do not state a duplicate policy at all in the material available, and an entrant who needs certainty should ask the organiser directly rather than infer one.
An entrant who reads the terms before entering knows the exact answer. An entrant who does not is guessing, and guessing about a final-submission rule is the expensive kind of guess.
- No-edit rules make duplicates visible instead of hiding them.
- Immutability is enforcement, just enforcement of a quieter kind.
- A form logs what it is told to log, nothing more.
- No quoted source mentions an automated duplicate filter.
- Ask the organiser when the terms are silent on duplicates.
- Two side-by-side entries tell a reviewer more than one edited entry.
- Email, name, timestamp: the classic trio a form records.
- Identity verification is not something an ordinary form performs.
- Silence in the terms is not the same as permission.
- Read before submitting; the first click is usually the binding one.
- The written rule is the only rule the tool enforces here.
Verification, fraud handling and what organisers can see
Do contest platforms in Sri Lanka verify voters? From the material read for this page, verification is not a feature any of these three organisers describes. Dilmah's mechanism is a form linked to a Drive folder. IOBSL's is a form with a finality rule. SOBA SEYA's is a form with an originality requirement. None of the three publishes a description of identity checks, captchas or voter roll matching on the voting side.
That absence tells you where the verification burden sits. It sits on the organiser, at review time. The folder holds the links; the form holds the responses; a person opens both and applies the published terms. A requirement like SOBA SEYA's originality rule is exactly this kind of check, applied after submission rather than before it.
How do poll tools handle fraud, then? In the ordinary case, they do not handle it at all. They record it. Every submission lands with a timestamp and whatever identifiers the form collected, and an organiser who suspects a problem can compare responses, check the links and act under the terms. The tool's contribution is the record; the handling is human.
This is the honest section, and the limits deserve to be named plainly. The organiser decides what the terms require. The platform decides what the form captures and what the file service permits. And after that, the adjudication is a person reading a response sheet against a rule page. Purchased attention changes nothing in that chain, because the chain's weak point is verification, and every purchased contest vote in a competition still has to pass through the same recorded, reviewable form.
An organiser who wants stronger verification has to add it: a signed declaration, a restriction on who may submit, a request for proof of the work's origin. Nothing in the rows we read shows that step in place, which makes the published terms, thin as they are, the complete statement of each platform's defences.
The takeaway for an entrant is uncomfortable but useful. Follow the terms exactly, submit once, submit original work, and keep your own copy of what you sent, because the platform may not let you correct anything afterwards.
- Verification, where it happens, happens in a human review.
- Originality checks are retrospective in the SOBA SEYA design.
- Forms record; people adjudicate; software mostly just stores.
- The organiser writes the terms and applies the terms.
- Nothing in the sources describes a pre-submission identity check.
- A Drive folder is auditable by exactly whoever holds access.
- Stronger verification means extra steps the organiser must add.
- Keep your own copy; IOBSL's rule forbids later corrections.
- The timestamp is the most reliable thing a form records.
- Every submission, whatever its origin, passes the same reviewable chain.
- Thin terms are still the full defence the platform offers.
What the forms log and whether counts go public
What does an entry platform log? Take the Flutter Shutter mechanism apart. The form records the fields it asks for, which at minimum include the entrant's contact details and the shared link to the Drive folder. The Drive service itself records the file, its upload, its permissions and its activity history. Two systems hold the evidence, and the entry is the thread that ties one to the other.
Are vote counts public? On platforms of this shape, counts are usually whatever the organiser chooses to publish. Nothing in the terms we read commits any of the three organisers to publishing per-entry counts, response totals or a live tally. Where a public vote exists, the count the audience sees is a number the organiser reports, and the response sheet behind it stays with the organiser.
For entrants, the log matters more than the count. IOBSL's rule proves the point: because an entry cannot be edited once submitted, the log is final, and any dispute is settled by reading the record rather than by re-submitting. An entrant who wants a defensible position should screenshot the confirmation and the submitted material at the moment of entry.
The three requirements we have quoted map onto the three questions a cautious entrant brings. Where do I send it: to the Drive folder, via the form, as Dilmah specifies. Can I fix it later: no, under IOBSL's wording. Whose work must it be: mine, under SOBA SEYA's originality condition. Three terms, three answers, no ambiguity left.
There is also a scam question that the terms help answer indirectly. A legitimate organiser publishes its rules, names its requirements and describes its submission path in public. An organiser that asks for entry fees through informal channels, refuses to state how entries are judged, or keeps every mechanism secret is asking entrants to accept terms that were never written down. The published-rule test is not proof of honesty, but secrecy is a reliable warning sign.
Legality is simpler here than readers expect. Entrants submit their own original work to a competition whose terms they have accepted, and nothing about that exchange touches any regulated act. The obligations run in one direction, from the entrant to the rules, and the organiser's obligations run to the entrants through the same published text.
- Two systems hold the evidence: the form and the file service.
- Published counts are a choice the organiser makes, not a default.
- A screenshot at submission time is the cheapest insurance available.
- Response sheets stay with the organiser in these designs.
- Three quoted terms answer the three questions entrants actually ask.
- Secrecy about mechanism is the reliable warning sign, not a fee.
- Published rules let you verify before you commit anything.
- The log is final where the no-edit rule applies.
- Accepting terms is a one-direction obligation for the entrant.
- Informal payment channels signal that no written terms exist.
- Original work, submitted once, through the stated path: the whole duty.
Out of scope
We do not sell votes for any contest and we never run or manage voting on any platform. This page does not list prices, does not rank organisers and does not describe tools whose terms we have not read. We never explain how to mask activity, rotate addresses or create duplicate accounts, because that teaching fails both the reader and the organiser. We also do not vouch for any competition's honesty; a published rule is a rule we can quote, nothing more. Anything a platform decides privately, after a moderation check, stays outside what this page can state.
Your questions
Because a form plus a file service covers nearly everything a small competition needs, at no development cost. Dilmah's Flutter Shutter shows the pattern: images land in a Google Drive folder, links are shared through the entry form, and the organiser reviews the result. Custom voting software earns its cost only when a contest needs live public tallies, automated duplicate rejection or identity verification at scale. Judged photography and art competitions, which are what the sourced rows describe, do not need any of those. The terms of entry then carry the load that software would carry elsewhere, which is why reading the terms is more informative here than inspecting the tool.
Under IOBSL's published wording, nothing can be done: the entry cannot be edited once submitted. That rule makes the first submission final, so the correction you would want to make is unavailable by design. The practical protection is preparation. Check the file, check the form fields and check the link opens correctly before you submit. Keep a copy of the confirmation and of exactly what you sent, because the log is now the authoritative record. If the terms are silent for another competition, email the organiser before submitting rather than after, since a rule that permits corrections is the exception on these platforms, not the rule.
Only to the extent the tooling records something checkable, and the tools described on this page are minimal. A form logs the fields it collects, a file service logs activity on its files, and neither, in the material we read, publishes any identity verification step. So an organiser can compare timestamps, look for repeated patterns in responses and apply the terms, but the record is the whole of what they have. Anything that passes through the form as a normal response looks like a normal response to the record, and anything suspicious surfaces only through human review. Organisers who need stronger signals have to add them to the process themselves.
Published terms protect an entrant in one specific way: they give something concrete to hold the organiser to. Dilmah, IOBSL and the Ministry of Environment all publish their submission paths and their requirements in public, on their own domains, under names that can be checked independently. A competition with no published terms, no named organiser and no verifiable domain offers none of that. The published-rule test is not a guarantee of honesty, and it is not proof that judging will be fair. But it is a real, checkable signal, and an entrant who insists on it screens out the large share of fake contests before any personal information changes hands.
For the entrant, the obligations are contractual rather than legal in any special sense: you accept the published terms when you submit, and the terms govern what happens next. The sourced rows show rules about originality, submission format and immutability, all of which are ordinary conditions of participation. Nothing on this page addresses any electoral or regulatory context, because public contest votes are private arrangements between an organiser and its entrants. If a competition involved a licensed raffle, paid entry or gambling mechanics, different rules would apply, and none of the three competitions described here has that shape. Read the terms, submit original work, and the legal exposure for an entrant is minimal.