To stop cheating in a step challenge, make the fair route the easy one. Cap the steps counted per day, exclude manually typed steps so only phone sensor data counts, review days that the app flags as unusual and publish every correction. Sociana provides these controls; the rules you announce make them work.
Who this guide is for
You run a corporate step challenge and the leaderboard has started to look wrong. Someone is at 90,000 steps on a Tuesday, a team has a spike every Friday and a participant has told you, quietly, that “a few people shake their phones”. You need rules that protect the honest majority without turning the programme into a policing exercise.
How a step board gets distorted
Four patterns account for most disputes. Manual entries inflate a total. A phone placed on a vibrating surface, a pet or a bicycle racks up movement. An outlier day from a genuine long hike pushes someone far ahead of the field. And a sync failure leaves honest people behind, which feels like cheating by others even when it is not.
Gallup finds engagement among Indian managers fell from 39% in 2024 to 30% in 2025 (Gallup, 2026); in a workforce that is already sceptical, a leaderboard that is seen to be unfair loses the participants you most need. Fairness is part of the engagement design, not an afterthought.
The controls and what each one does
| Control | What it does | Stops | Cost to honest users |
|---|---|---|---|
| Daily cap | Limits steps counted per day | Outlier days, shaking | A genuine long walk is capped |
| Manual-entry exclusion | Ignores steps typed in by hand | Typed totals | None, if sensor data is available |
| Unusual-day flag | Marks abnormal days for admin review | Sudden spikes | Occasional review request |
| Boost days | Multiplies steps on set days | Not a control, but a lever | None, applied to everyone |
| Admin adjustment | Adds steps by hand with a record | Sync failures | None, and the record is visible |
| Team target | Shifts weight from individual to team | Personal gaming | None |
| Close and freeze | Fixes the result at a stated time | Late changes | None |
Step by step
Step 1: Write the fair-play rules before launch
Three paragraphs, plain English: what counts, what does not, what happens if a day looks wrong. Pin it in the app and repeat it in the launch message. Rules announced on day one are accepted; rules introduced on day twenty feel like accusations.
Step 2: Set a daily cap that fits your audience
The cap should be above a normal active day and below an extreme one. Decide it from your pilot or from previous programmes, not from guesswork. The step challenge target planner and leaderboard fairness simulator help you test it.
Do it in Sociana: step challenges and health sync with the daily cap rule.
Step 3: Exclude manual entries
Switch on manual-entry exclusion so that only data from the phone’s health store counts. At the HSBC Wellness Expedition, manual entries were visibly shown as not counted, so participants could see the rule at work. Explain the reason: the board is about sensor data.
Step 4: Review flagged days with care
The unusual-day flag marks days with abnormal counts. Review each with a two-line message to the participant: “Your count on Saturday was unusually high. Was this a trek or a sync issue?” Most flags have an innocent cause. Record the decision.
Step 5: Correct honest errors with a visible record
When a sync fails, admins can add steps by hand, and the addition is recorded. Make the log available to a programme owner. A visible correction is a trust-builder; an invisible one is a rumour.
Step 6: Pause sync when you must
If a platform issue affects a day’s data, the organiser can pause syncing. At the Expedition, the app showed a paused-by-organiser state. Tell participants the same day what you paused and why.
Step 7: Use team targets to dilute gaming
A team target shifts attention to collective progress; one inflated individual matters less. Pair it with individual streaks, which reward showing up and are hard to fake by shaking a phone for a day.
Step 8: Freeze the result at a stated time
The YEC 2024 programme closed its step challenge and showed “Steps Challenge is closed”, which froze the result. Announce the time, freeze at that time and publish the final rank with the rules beside it.
What to say when someone is flagged
The conversation is more important than the flag. Open with the data, not an accusation: “Your count on Saturday was well above the daily cap, so it was held for review.” Ask one question: “Was this a long walk, or could it be a sync problem?” If the answer is a trek, accept it and tell the person how the cap treated the day. If it is a sync fault, correct it with a recorded addition and thank them for telling you. If it looks like shaking the phone, remind them of the rules and note the conversation.
Keep these notes in a simple log with the date, the person, the day in question and the decision. If a team captain later disputes a ruling, the log answers the question. Never name people in the feed or the team chat; handle everything in private messages.
Pitfalls
- Naming people publicly. Handle flags in private messages.
- Rules that change midway. Lock them in advance.
- Treating every spike as fraud. Many are treks, runs and festival days.
- A cap with no explanation. Explain it in one sentence.
- Forgetting Android sync. Failed sync looks like low effort; support it.
India and SAARC notes
Indian office programmes have specific patterns: weekend treks, festival walks and pilgrimages produce legitimate outliers; Diwali and family travel weeks lower counts for everyone. Treat these in the rules, not in disputes. In multi-country programmes, devices vary: confirm that every participant’s phone writes to Health Connect or Apple Health, since Sociana does not sync directly with Fitbit, Garmin or Strava. Step data is health-adjacent personal data, so keep reports to participation figures and agree data handling with your counsel; see health data handling.
How Sociana handles this
The controls are part of the step module: a daily cap that limits steps counted per day, an unusual-day flag for admin review, manual-entry exclusion and admin-added steps with a record. Consistency, improvement and variance reports, first used for the Road to Phuket programme’s daily exports, help you see patterns that a single total hides. The HSBC Wellness Expedition is the example to look at: counting only automatically recorded steps and letting organisers pause syncing kept its walking board fair. Open the step challenge dashboard demo to see the flags.
FAQ
Can people still cheat with a watch or a shaker?
Sensor data can be gamed physically. Caps, flags and team targets reduce the payoff, and consistency reports show patterns. No system removes it entirely, so keep the stakes proportionate.
Should we ban people who cheat?
Start with a conversation. Remove steps from a day if needed and record why. Reserve disqualification for repeat cases written into the rules.
Do manual entries ever count?
They are shown as not counted when exclusion is on. Admins can add steps by hand with a record where a sync failure justifies it.
How do we tell participants about a correction?
Message the person and, if the change affects the board, post a short note in the feed. A visible record is better than a quiet fix.
Related reading
Glossary: unusual-day flag, step cap, boost, team target. Occasion hubs: wellness and step challenges, employee programmes. Related: how to run a step challenge at work.