How to prevent cheating and disengagement in conference competitions

Your conference competition is running, the leaderboard looks busy, and then someone asks how the person at the top completed activities in rooms that were open at the same time. Meanwhile, attendees who joined after lunch have stopped trying. Now you have a result people can reasonably question.

Preventing event gamification cheating starts before anyone earns a point. Define what completion means, limit rewards for repeat actions, and check the claims that can change who wins. To keep people involved, make useful participation achievable without asking them to sacrifice the conference they paid to attend.

You won't eliminate every shortcut. You can make shortcuts less rewarding, correct mistakes without humiliating people, and keep the result credible. That takes clear rules and a manageable review process. It also takes the willingness to remove a task when its points are creating more work than its activity is worth.

Decide what counts before deciding how to catch cheating

Start with the activity you actually want. If you want participants to apply a workshop idea, scanning the slide at the end doesn't establish that they did. If you want relevant introductions, exchanging a room code doesn't show that anyone had a conversation. A digital record only proves what it records.

Write a completion sentence for each scored task. For a conference case challenge, yours might say that a participant submits a proposed response to the supplied scenario, explains the reasoning, and identifies a practical limitation. That tells people what to produce and gives reviewers something concrete to assess.

Then decide whether you need to assess quality or only confirm completion. Those are different jobs. A contribution can meet the participation requirements without being the best answer. If you leave that distinction vague, one staff member may accept every submission while another rejects responses they personally dislike.

Keep tasks within the review capacity you have. A demanding essay with an ambiguous scoring guide is a poor choice when the same team also handles registration and speaker changes. You might get better participation from a short, specific response that a trained reviewer can assess consistently.

For a networking task, avoid scoring another attendee's willingness to share personal details. Someone can make an appropriate introduction and hear a polite refusal. Your rules should explain what happens then. Otherwise, the competition encourages participants to keep pushing until the other person agrees, which makes the networking experience worse.

Remove easy ways to multiply a score

Look at every action through the eyes of someone who wants the reward with the least effort. Can they submit the same response again? Can a colleague collect their code? Does reopening a page generate another completion? You can test these possibilities without assuming your attendees are dishonest.

Put a clear limit on repeatable actions. If the task rewards a completed session reflection, repeated edits to that reflection shouldn't keep adding points. Decide whether corrections replace the original submission or create a separate record. The participant needs to understand the rule, and the scoring system needs to apply it.

A posted code is convenient but easy to share. Use it for low consequence acknowledgement if that suits the activity. For a prize deciding task, consider confirmation tied to the actual contribution, such as the submitted answer or a staff approved completion. The extra check should establish something the code cannot.

Don't demand elaborate proof for trivial rewards. Requiring a photograph, location history and staff signature for a small completion gift creates another event within your event. If the reward doesn't justify verification, reduce the stakes or accept that the measure is approximate. An unverified score shouldn't decide a valuable prize.

There is research behind taking incentive design seriously. In a 2024 Scientific Reports experiment on competition and dishonest reporting, Andras Molnar and Gabriele Paolacci studied 765 participants. Competition increased the amount of dishonest reporting without significantly increasing the proportion of participants who reported dishonestly. That experiment doesn't predict cheating at your conference. It does challenge the assumption that adding competition leaves behaviour unchanged.

Separate an unusual score from evidence of cheating

A sudden score increase deserves a check, not an accusation. The attendee might have completed offline tasks that uploaded together. A staff member might have entered a correction. The platform might have duplicated an award. Start by establishing what happened to the record before deciding what the participant intended.

Choose review triggers you can explain. These might include repeated submissions for the same task, completions recorded for overlapping activities, or a score above the published maximum. A trigger means someone reviews the underlying activity. It shouldn't automatically mean the attendee loses eligibility.

Keep the review proportionate to the consequence. If a duplicate entry adds a minor acknowledgement, removing the duplicate may settle the issue. If the record determines a substantial prize, check the relevant completions and give the entrant a chance to respond before confirming the result. Make that review period part of your timetable.

Shared connections and shared equipment need particular care. Several attendees may use the venue's internet connection or receive help at the same support desk. A common network address doesn't establish that one person created multiple accounts. Nor does a fast submission prove that someone copied an answer they may already understand.

Ask neutral questions when the evidence is unclear. Tell the participant which completion needs checking and what information would resolve it. You might ask which session they attended or request the missing response. Don't ask them to prove their honesty in general. They can answer a specific discrepancy; they cannot sensibly answer a suspicion with no details.

Publish rules that staff can actually apply

Your rules should answer the awkward questions before the prize makes them urgent. Who is eligible? Are event staff, speakers and sponsor employees excluded? Does each person have one account? Can teammates collaborate? Are outside research and AI tools allowed? Describe the conduct you intend to permit or prohibit.

A conference problem solving activity may benefit from discussion between attendees. An individual knowledge competition may require independent answers. Neither choice is automatically better. Trouble starts when the invitation encourages collaboration and the judging team later treats similar responses as misconduct. State the permitted help for each task where necessary.

Be specific about AI assistance if the task involves producing an answer. You might allow research tools while requiring entrants to explain their own recommendation, or prohibit outside assistance in a supervised knowledge round. Choose a rule you can reasonably administer. Don't promise to detect every generated sentence, then disqualify a participant because their writing sounds polished. If original reasoning matters, design the task so entrants demonstrate it through the evidence they select and the explanation they provide. Review the submitted work against the published criteria, and investigate a suspected breach through the same evidence and response process used for other disputed entries.

For UK promotions, the ASA's guidance on promotional abuse warns against disqualifying people who followed the published conditions or introducing restrictions retrospectively. It also discusses the need for evidence when alleging a breach. Use qualified advice for the rules that apply to your event and location, especially where paid admission and prizes interact.

Alongside eligibility, explain completion criteria, scoring limits, deadlines and time zones where relevant. Describe how corrections work, how ties are handled, when results become final and how participants raise a dispute. Make the significant conditions visible before people start, with the full terms easy to find throughout the activity.

Keep an approved version available to the delivery team. Staff can clarify where to submit an answer without changing what qualifies. If a genuine problem requires a decision, the responsible organizer should record it and follow the published process and applicable requirements. Quietly telling different queues different rules is how a small ambiguity becomes a fairness complaint.

Keep the reward within reach of ordinary attendees

A leaderboard can become pointless for someone whose schedule makes catching the leaders impossible. Before changing the prize, check the opportunities available to each person. An attendee arriving on a later ticket, presenting a session or attending a specialist track may have fewer eligible activities through no fault of their own.

If the competition spans the whole conference, design qualifying opportunities around the tickets and schedules people actually have. You can offer equivalent tasks in different sessions or separate activities with their own stated eligibility. Avoid combining unequal opportunities in a ranking and then trying to explain away the difference at the prize announcement.

Think about what remains worthwhile once the top score is unreachable. An achievable completion reward can acknowledge useful participation without requiring everyone to chase the overall winner. If you offer one, state the qualifying work, availability and fulfilment terms. Don't advertise a guaranteed reward unless you can provide it to every eligible person who meets those conditions.

Also check whether rewards repeatedly go to the same people. A participant winning several categories may be consistent with your stated rules, but it can concentrate recognition more than you intended. Decide any limit before opening and explain how an award passes to another eligible entrant. Don't make that adjustment after seeing the names.

Team entries need their own allocation decision. Explain whether a reward belongs to the team, whether every member receives something, and how you confirm membership. Otherwise, a group can complete the work together and discover that only the account holder receives the benefit. Sponsors supplying prizes need to know those fulfilment obligations too.

A random prize among qualifying entries is another possible structure, but changing the selection method changes the promotion. Review its legal requirements before launch, especially at a paid event. Don't quietly convert a skill based competition into a draw because too many people tied. Choose and explain the method beforehand.

Whatever the structure, preserve the attendee's main reason for buying a ticket. A competition that rewards missing a relevant workshop to collect unrelated points can produce activity while weakening the conference. Set sensible task limits and leave enough time for conversations, breaks and sessions that aren't part of the game.

Make access part of fairness

Speed, public speaking and constant movement can become accidental qualification requirements. They may have little to do with the knowledge or contribution you wanted to reward. Check each task for those hidden demands, particularly if a participant must complete every task to remain eligible for the prize.

The W3C's accessible event checklist specifically asks organizers to consider barriers in participant activities, including online polling and quick responses. It also addresses accessible materials and scheduling needs. Use it to question the activity itself, rather than checking only whether someone can enter the room.

For a scenario challenge, you might accept a written response instead of requiring a spontaneous answer through a microphone. For an activity in a crowded area, arrange an equivalent accessible way to complete the same objective. Agree the alternatives before opening, with people responsible for access and the competition review.

Equivalent means preserving a fair opportunity to qualify. It doesn't mean asking a desk volunteer to invent an easier question while everyone watches. Brief the relevant staff privately, explain how approved alternatives are recorded, and provide a contact for requests that need a decision. Participants shouldn't have to disclose medical details to a queue.

Also check ordinary practical barriers. Someone's phone may be flat, their employer may restrict app installation, or the instructions may be difficult to read. A support route helps, but it must feed into the same completion record. Otherwise, attendees using the alternative can do the work and still disappear from the results.

Use a score you can explain on one example

Before launch, calculate a fictional participant's score by hand. Suppose your case challenge has three eligible submissions, each worth ten completion points. The maximum is thirty. Multiple attempts at the same submission replace the earlier version before the deadline; they don't create additional points. These are example rules, not recommended universal weights.

Now test the difficult version. The participant submits two eligible responses, then edits the first. Their completion score stays at twenty. If your system shows thirty, either the configuration or the rule description is wrong. Fix that mismatch before participants start relying on the displayed total.

If you judge response quality as well, keep that score distinct from completion. Tell participants how the quality criteria affect the outcome. For example, reviewers might assess how clearly the response addresses the scenario and whether its recommendation follows from the evidence. Avoid publishing a vague promise to reward the most engaged attendee.

Don't use time submitted as a convenient tie breaker unless speed is relevant, fair and disclosed. People may have different session times, accessibility arrangements or connection delays. A published secondary criterion can work better for a judged challenge. Whatever method you choose needs the same level of clarity as the main scoring rule.

Ask someone outside the planning team to explain the worked example back to you. If they cannot tell why an edit does not earn another completion award, simplify the instructions. You want participants spending time on the conference activity. Reading an elaborate points policy shouldn't become the hardest task in the competition.

Test permissions and corrections before opening

Decide who can award points, who can correct them and who can confirm the final result. A volunteer may need to acknowledge a completed activity without needing permission to alter every participant's score. Keep those responsibilities as narrow as your tools allow, then make the approval route practical during busy periods.

Record corrections with the original value, the changed value, the reason and the person who approved them. You don't need a complicated investigation file for every typo. You do need enough information to explain why a score changed if the entrant or another authorized reviewer asks about it later.

Test what participants see after an adjustment. A silently reduced score can look arbitrary, particularly if the attendee cannot identify which task changed. Provide an appropriate explanation and a route to ask for review. Keep sensitive details out of public notifications. The person needs to understand their own record, not somebody else's disputed entry.

Use your event team briefing to rehearse the actual decisions. Ask a volunteer what they do when someone reports a missing completion, when two names look similar, and when a sponsor requests bonus points for its guests. The exercise is useful only if the answer matches the rules and available permissions.

Include shift changes in the test. A person joining after lunch needs the same approved instructions and outstanding issue record as the morning team. If every exception lives in one organizer's memory, routine handovers will produce inconsistent decisions even when everyone is trying to do the right thing.

Plan the outage before the scoring freezes

A connection failure can make honest participation look suspicious. Several completions may arrive together when service returns, or an attendee may submit twice because the first attempt appeared to fail. Explain how participants report missing records and how your team checks them without automatically rewarding every unsupported claim.

Prepare a fallback that confirms the same qualifying activity. That might be a controlled staff record of the entrant, task and completion time, later reconciled against the digital record. Keep it secure and limited to the information needed. Reconciliation should check whether the completion already exists before adding anything.

The deadline needs a specific fallback decision too. Distinguish when the participant completed the task from when the system received the record, if your published rules allow that distinction. Don't make the support desk improvise eligibility decisions while people are waiting for the final announcement. Assign someone who can apply the approved process.

If the failure prevents a reliable result, delay confirmation through the procedure your terms allow. Tell attendees what happened, which results remain provisional and when to expect the next communication. An entertaining closing ceremony isn't a good reason to announce a winner you already know you cannot verify.

Rehearse a failure near the deadline, rather than only a convenient outage early in the day. Check how staff reach the decision maker, where they record completions and how they contact participants. The useful test is whether the team can preserve fair treatment while the rest of the conference continues operating.

Give people a fair way to challenge a decision

Publish a private contact or submission route for missing points and eligibility questions. Ask for the activity, approximate time and a short explanation. Don't require entrants to collect information about other participants or post their complaint publicly. Your team should investigate its own records rather than recruit attendees to monitor one another.

Set a realistic response process. A support volunteer can acknowledge a report and fix a clear entry error within their authority. A disputed disqualification should go to the designated reviewer. Tell the entrant when they can expect a decision, especially if the issue could affect a prize being confirmed that afternoon.

Keep a distinction between correcting a record and alleging deliberate misconduct. If two identical completions appeared after an upload, remove the duplicate and explain the correction. Disqualification carries a much bigger consequence. It needs a stated rule, evidence of the breach and a response that fits the circumstances and applicable requirements.

Where possible, have another authorized person review a disputed decision that could change the result. The original decision maker may have useful context, but fresh review can catch a mistaken assumption. Record the conclusion and communicate it directly. Avoid public commentary about an attendee's motives, even after you resolve the scoring issue.

Your wider guide to handling difficult attendees can support staff conversations when someone becomes frustrated. Start with the facts and listen to the specific concern. An attendee challenging a score is using the process you offered. Treating the challenge itself as troublesome discourages people from reporting genuine errors.

Walk through a disputed result before it happens

Imagine the fictional case challenge has closed. One entrant appears to have the maximum thirty completion points, but another reports that their own third submission is missing. Your closing session starts soon. The temptation is to trust the displayed total and announce the person already at the top.

Instead, use the process you planned. A staff member acknowledges the missing submission report and checks the relevant activity record. The reviewer discovers that the response was submitted before the deadline but its completion award failed. They confirm that the content meets the same requirements applied to the other entries and approve the correction.

The correction creates a tie. That doesn't mean the correction was unfair, and it doesn't justify inventing a new challenge on stage. Apply the published tie process. If judging remains necessary, keep the result provisional until that work is complete. Tell the affected entrants what happens next through the agreed contact method.

Now change one fact. Suppose the missing response arrived after the deadline and there is no recorded outage or permitted exception. A participant's understandable disappointment doesn't give the reviewer permission to ignore the condition. Explain the decision and available review route. Consistency includes applying a fair rule when someone strongly prefers another outcome.

Finally, consider the entrant whose score originally appeared highest. They haven't cheated because another person's missing award changed the ranking. Don't describe a routine correction as catching a dishonest winner. Your announcement can explain that scores were checked and finalized without exposing private complaints or attributing motives to anyone involved.

This rehearsal shows whether your plan has enough time, authority and information to work. If the entire process depends on a volunteer finding the event director during the keynote, change that arrangement. Assign an available reviewer and protect a realistic period for checking results before you promote the announcement time.

Confirm prizes with enough time to check the result

Display scores as provisional where verification remains outstanding. Explain what that means before the end of the competition. People can enjoy following progress while understanding that eligibility and relevant completions still need checking. The final announcement should follow those checks, rather than force your team to rush through them.

For a judged UK prize competition, the ASA's guidance on independent judges and observers describes the independence required when selecting a winning entry involves subjective interpretation. Its guidance distinguishes judged competitions from random draws. Confirm the requirements for your actual promotion and jurisdiction before appointing reviewers or promising a selection method.

A prize sponsor shouldn't be able to direct a discretionary award toward its customer because it supplied the prize. Agree the sponsor's recognition and delivery responsibilities separately from selection. If your competition includes a sponsor judged category, review and disclose the arrangement properly. Don't describe somebody as independent when their relationship undermines that claim.

Check fulfilment before announcing the winner. Confirm the actual item or benefit, any restrictions, the notification method and the acceptance process. A professional attendee may be unable to accept a valuable gift under their employer's policy. Your published terms should explain the relevant conditions and what happens if an award cannot be accepted.

Keep evidence of the result and required checks for the period you have justified. Tell participants how and when you will communicate the outcome. If review takes longer than expected, send the promised update. Silence after a highly promoted prize can damage trust even when your team is doing careful work behind the scenes.

Diagnose disengagement before adding more rewards

When people stop participating, ask where they stopped. Did they never complete the first task? Did they finish one activity and then leave the competition alone? Did they remain involved until their score fell behind? Those patterns suggest different problems, and increasing the prize doesn't tell you which one you have.

For early drop off, watch someone attempt the task. The instructions may be unclear, the submission may fail, or the activity may demand more time than the invitation suggested. If access to the app itself is the problem, the event app adoption guide covers useful first tasks and support. Don't treat every login problem as a motivation problem.

For later drop off, ask whether participants still have an achievable and worthwhile reason to continue. You can remind them of an existing completion reward or explain the remaining eligible opportunities. Avoid inventing bonus points that favour the people currently nearby. A mid event surprise can create another fairness problem for everyone following the original schedule.

Talk to people who left as well as the enthusiasts still playing. Ask what they expected, what became difficult and what they chose to do instead. Someone may have stopped because a valuable conversation ran long. That can be a good conference outcome even though your competition dashboard records an unfinished task.

After the event, compare participation with the work the activity was intended to encourage. Count useful submissions separately from clicks, check how many corrections staff made, and review complaints and access requests. Record the staff time too. A competition that requires constant intervention may need simpler tasks and lower stakes before you repeat it.

Collect enough information to run the competition

Fairness checks need a reliable connection between an eligible participant and their qualifying activity. They rarely justify collecting everything a device can report. Decide what information answers an actual administration question before you enable collection. If you cannot explain how location history would resolve a relevant dispute, don't collect it speculatively.

The UK's ICO explains data protection principles including purpose limitation, data minimisation and storage limitation. Where UK GDPR applies, those principles shape your handling of competition records. Check your own applicable requirements and explain the purpose, sharing and retention through the event's privacy information.

Set a deletion or review date for the competition record when you design the process. Keep unresolved disputes and any required evidence under your justified retention arrangements, then remove information you no longer need. A future conference doesn't automatically need every individual submission from this one, especially when a short, anonymous account of the problem would support the improvement.

Limit who sees identifiable progress. The competition reviewer may need individual records; a sponsor usually wants an account of the activity's results. Those are different information needs. Avoid sending a complete participant activity log because it is convenient to export. Use the minimum appropriate information for the agreed reporting purpose.

Before the next conference, remove tasks you couldn't verify fairly, fix instructions that produced repeated disputes and keep the review process small enough to deliver. Then run a complete test with someone who didn't write the rules. Ask them to participate, make a correction and challenge a missing completion. Open the competition only when your team can explain and deliver the result.