To design an event points system, list the behaviours you want, give each a fixed point value and a cap, post every award to one points record, and keep spendable wallet points apart from leaderboard points. Then decide who can adjust the points, who is excluded from rankings, and when the board freezes.
Decide what the points are for
A points system is a statement of what the organisers value. If attendance scans earn the most, people will scan. If photo posts earn the most, the wall fills with photos. Write the target behaviours first, in order of importance, and make sure the top of that list is the real objective of the occasion.
For an employee programme running over months, the objective is usually repeated, verifiable contribution. For a three-day offsite it is usually presence and connection. For a partners meet it is often learning plus participation in the room. The same app can serve all three, but the values will differ.
The five rules every system needs
- A fixed value per action. Avoid vague “bonus for effort”. Participants should be able to predict what an action earns.
- A cap per action and per day. The cap prevents a farming strategy and protects casual participants from feeling hopeless.
- A single points record. If each game has its own board, participants must add scores by hand and organisers cannot report on total engagement.
- A separation of score and balance. Leaderboard points record achievement. Wallet points are the balance a participant can spend.
- A stated freeze. Say when the board closes and what happens to late points.
A worked rule table
The values below are illustrative, not a recommendation of fixed numbers. Scale them to your own programme.
| Action | Relative value | Cap | Why |
|---|---|---|---|
| Check in to a session | Medium | Once per session | Rewards presence |
| Answer a live poll | Low | Once per poll | Keeps the room active |
| Correct quiz answer | Medium | Per question | Rewards attention |
| Complete a feedback form | Medium | Once per form | Lifts response |
| Post a photo to the timeline | Low | Daily limit | Fills the feed without flooding it |
| Finish a hunt marker | Medium | Once per marker | Moves people around |
| Complete a programme submission | High | Per approved submission | Rewards real contribution |
Notice the shape: actions that need little effort carry low values and strict caps, and actions that need real effort carry higher values but need verification.
Separate the leaderboard from the wallet
Participants understand a ranking intuitively: more points, higher position. They also understand spending: I trade my balance for a prize. If both come from one number, redeeming a reward pushes you down the table, and people hoard points instead of enjoying the store. Two balances solve it. The leaderboard shows what you achieved; the wallet shows what you can spend. Tell participants this in the first message about the programme, in one sentence.
Build in fairness controls
- Staff exclusion. Members of the organising or client team should not appear in public rankings. Exclude them before launch.
- Approvals for effortful claims. Where participants submit proof, such as a completed ethics module or a field task, route the submission to a reviewer and award points only on approval.
- Manual adjustment with a log. Mistakes happen: a scan fails, a game glitches. Allow authorised admins to add or subtract points and keep the change in a record.
- A pause control. If the board has to be reviewed, pause it visibly instead of editing numbers while people watch.
Time and scope filters
Decide what views people need. A daily board keeps day two competitive after a lopsided day one. A team board encourages participation from those who will never top an individual list. A quarterly cycle suits a long programme, where the winner of the first quarter should not settle the rest of the year. Plan these views before launch, since they affect how rules are written.
Test with five people
Before the event, ask five colleagues to play for fifteen minutes with the real rules and then explain them back to you. If they cannot, the system is too complex. Fix the explanation or simplify the rule. This test is more useful than any spreadsheet check.
Reporting from the points record
Because everything posts to one points record, you can report which activities drove points, which groups were most active, and how participation changed day by day. Keep the report simple: participation rate, top five activities by volume and the distribution of points, so leaders can see whether a few people dominate.
Common design mistakes
Most points systems that disappoint fail in predictable ways. It is useful to know them before you write your own rules.
Rewarding volume over value. If every photo earns the same points as a completed submission, participants will flood the feed and neglect the work you actually care about. Weight the actions that need effort more heavily, and verify them.
Letting early leaders run away. A system with no daily cap or catch-up mechanism gives day-one leaders an unreachable lead, and the rest disengage by lunchtime on day two. Daily boards, double-points windows and team formats all help.
Rules that change silently. Adjusting a value mid-event without telling anyone feels like moving the goalposts. If you must change a rule, announce it, say why, and apply it from that moment forward.
Points with nothing to spend them on. A leaderboard can motivate on pride alone for a day or two. Beyond that, people want something tangible, even if it is a small token from a reward counter or a mention at the closing session.
Ignoring people who cannot participate in some activities. Not everyone can walk long distances or take part in a late-night game. Offer several routes to points, so a participant who sits out the hunt can still earn through quizzes, feedback or attendance.
Choosing a reward structure
Rewards fall into three broad kinds, and a programme can use more than one.
| Kind | Example | Best for |
|---|---|---|
| Recognition | Name on the leaderboard, a mention on stage | Short events, senior audiences |
| Tangible redemption | Items at a reward counter, bought with wallet points | Booth-based or multi-day occasions |
| Deferred rewards | Points exported for a company recognition scheme | Recurring employee programmes |
If you offer a reward counter, decide stock levels and per-person limits before opening. A popular item that runs out in the first hour leaves everyone else feeling cheated, so reserve some stock for later in the day or limit how many units one person can claim.
Communicating the system
A good points system fits on a single slide and a single card. Use plain words: “You earn points for scanning at sessions, answering polls and giving feedback. Your wallet is for spending; your rank is for pride.” Show the rule table in the app’s information pages, repeat it in the welcome message and give the emcee a line to say before the first poll. Ask the help desk to keep a short script for common questions, such as why a scan did not count.
How Sociana handles this
Sociana’s unified leaderboard takes points from polls, quizzes, games, attendance scans, feedback, steps and hospitality answers into one points record, with time and activity filters, team boards, admin adjustments and staff exclusion. A pause control shows a small red lock when the board is under review. The points wallet and reward store keeps spendable balances apart, so a redemption never lowers a rank.
Integrity Champ, a recurring ethics and compliance ambassador programme that Carlsberg India runs on a multi-occasion Sociana app, is the example to look at: employees submit proof against contests, managers approve from their phones, approved work earns points and quarterly leaderboards rank the cycle. See the Integrity Champ case study. Further reading: employee programmes, leaderboard points and wallet points versus leaderboard points.
Frequently asked questions
How many point-earning actions should an event have?
Start with five to seven. More than that and participants stop reading the rules. You can add a rule mid-event for a specific session, but announce it clearly.
Should points be public or private?
Show ranks publicly for the top group and teams, and let each person see their own score privately. Public ranking of every individual can discourage newcomers, so many organisers show the top ten and team totals only.
What happens if someone disputes their score?
Keep a visible route, such as the help desk, and use the points log to check what posted and when. Authorised admins can adjust points with the change recorded.
Can points be exported for gift cards?
Points can be exported so another system can handle redemption. Sociana runs a venue reward store with QR redemption; it does not operate a gift-card marketplace.