Software Development

How to Prevent Late Entries in an Online Competition (Not Just Claim You Do)

A stated deadline in your competition rules is a legal statement, not a technical guarantee against late entries. Here's why server-side enforcement, not a countdown timer, is what actually stops a submission after the cutoff.

By Arnaud Brunel — Founder, Brunel Studios 6 August 2026 Last updated: 6 August 2026
Software Development

A stated deadline in your competition rules is a legal statement, not a technical guarantee. The only way to actually prevent late entries is server-side enforcement: the system checks each entry's timestamp against the deadline at the database level, before accepting it, independent of any countdown timer or the entrant's own device clock.

Does Writing "Entries Close At 18:00" Actually Stop Late Entries?

A countdown timer is a visual cue, not a control. It runs entirely in the entrant's browser, which means it can be bypassed by changing a device clock, disabling JavaScript, using a browser's developer tools to intercept the submission, or simply calling the same endpoint the form uses after the on-screen timer hits zero. None of that requires unusual skill. It requires knowing that most competition entry forms only check the time on the page, not the time on the server.

This matters more in South Africa than the rules pages suggest. Most guidance on online competition rules in South Africa focuses entirely on the legal side: the Consumer Protection Act's Section 36 requires rules to be prepared and published before the competition opens, caps any cost of entry at R1.50 for electronic transmission, and excludes directors, employees and closely related consultants of the promoter from winning. All of that is real and enforceable. None of it says anything about what stops an entry submitted three minutes after the deadline from being accepted anyway.

Server-side deadline enforcement closes that gap. The principle is simple: the moment a fixed timestamp passes, the backend rejects any write attempt tied to that competition, regardless of what the entrant's browser, clock or connection is doing. The deadline lives in the database and in the server logic that guards it, not in a script running on someone else's machine.

The Trade-off Most Rules Pages Never Mention

Treating a deadline as a policy statement instead of an engineering requirement is a real trade-off, and it has a cost. South Africa recorded the highest rate of suspected digital fraud among the African countries analysed in TransUnion's H1 2026 Update: Top Fraud Trends report, with 3.0% of transactions flagged as suspected fraud against a 3.8% global average, and a median reported loss of R11,055 among affected consumers. Timing manipulation on entry systems sits in the same category of exploit as the payment fraud that report tracks: both rely on a gap between what a system displays and what it actually checks.

We saw this firsthand building a sports prediction and lead-generation platform, part of a wider custom software build for a client running prize competitions tied to live matches across rugby, soccer and tennis, where the deadline had real money attached to it. Predictions had to lock the instant a match kicked off, not roughly around kickoff, because a prediction submitted after the whistle with the outcome already visible is not a prediction, it is a guess with inside information. We built the lock server-side: when the kickoff timestamp passed, the system rejected any new prediction attempt at the database level. There was no client-side timing trick that got around it, and no window where a late submission slipped through, because the check never depended on anything running in the entrant's browser. The redemption side of that same build, making sure a prize could never be paid out twice, is a separate story about database-level locking; this is the entry-deadline half of it.

That is the trade-off in one sentence: a client-side deadline is cheaper to build and looks identical to a working one, right up until someone tests it.

What to Ask Before You Launch a Competition With a Hard Cutoff

Anyone running a promotion, auction, tender submission or giveaway with a genuine cutoff should ask their developer one direct question: does the deadline check happen on the server, against a server clock, at the point the entry is written to the database, or does it happen in the browser? If the answer involves JavaScript disabling a submit button, that is a display feature, not enforcement. Low-stakes giveaways with no real prize value can usually live with that risk. Anything involving prize money, limited slots, or a competitive advantage to entering first cannot, because the incentive to test the gap only grows with the stakes.

Rules documents are necessary and the Consumer Protection Act's requirements around cost, eligibility and advance publication are not optional. But a rules document describes what should happen. Only the code that runs when an entry arrives determines what actually does. Businesses running anything with a genuine deadline should treat the technical enforcement as part of the compliance work, not a separate concern handled later, the same shift covered in why compliance by design beats a patch applied after the fact. If the record-keeping requirement (entries and outcomes kept for at least three years) ever gets tested by a disputed late entry, a server-side rejection log is the only version of "we enforced the deadline" that holds up.

Questions About Preventing Late Entries in Online Competitions

Does South African law require accepting late entries in an online competition?

No. The Consumer Protection Act does not mandate a late-entry policy; that is set entirely by the promoter's own rules, prepared and published in advance. A deadline is only as real as its enforcement, since a stated cutoff with no technical backing is easy to dispute after the fact.

What does South Africa's Consumer Protection Act require for promotional competitions?

Section 36 caps any cost of entry at R1.50 for electronic transmission, requires rules to be prepared and available before the competition opens, and bars directors, employees and closely related consultants of the promoter from winning.

How long must competition records be kept in South Africa?

At least three years after the competition ends. This includes entry records, winner selection details and evidence the rules were followed, which matters most when a rejected late entry is disputed afterward.

Can you charge people to enter an online competition in South Africa?

No. Beyond a capped R1.50 electronic transmission cost under Section 36 of the Consumer Protection Act, entrants cannot be charged anything else to take part, regardless of how the entry is submitted.

Who is not allowed to win a company's promotional competition?

Directors, employees, and consultants closely related to the promoter are excluded under the Consumer Protection Act. The restriction exists to prevent insiders from having any advantage, real or perceived, in the outcome.

Is a countdown timer on a website enough to stop late entries?

No. A client-side timer is advisory only, since it runs in the entrant's browser and can be bypassed by changing a device clock, disabling JavaScript, or submitting the underlying request directly. Only server-side enforcement actually blocks a late entry.

What happens if someone submits an entry after a competition closes?

In a correctly built system, the entry is rejected at the database level the instant the deadline timestamp passes. There is no manual review or after-the-fact judgment call, since the rejection happens automatically for every entrant.

Are online prize draws regulated the same as in-store promotions in South Africa?

Yes. Section 36 of the Consumer Protection Act applies equally regardless of channel, so an online prize draw carries the same rules on cost, eligibility and record-keeping as a promotion run in a physical store.

Arnaud Brunel

Founder, Brunel Studios

Arnaud Brunel is the founder of Brunel Studios, a software product studio based in Cape Town. He has spent the last 8 years building digital products for founders and SMEs across South Africa and Africa, working across mobile, web and AI-native platforms.

LinkedIn ↗