Running fair award nominations, judging and public votes

Award schemes rarely fail because nobody entered. They fail because the nomination form asked the wrong things, the judges got a spreadsheet instead of a scorecard, or the public vote got stuffed by one team refreshing the page two hundred times. Each of those is a form problem, not a people problem, and each has a straightforward fix.

Design the whole pipeline before the first form

An awards process has three stages, and it's worth mapping all three before building anything: how nominations come in, how they get scored, and how a result gets announced. A nomination form built without knowing how judging will work tends to collect prose where judges need numbers, and a voting form built without an anti-fraud plan tends to need re-running once someone notices the numbers don't add up.

• Nominations need enough detail that a judge who's never heard of the nominee can understand the case. - Judging needs structure — the same criteria, the same scale, every time — or scores can't be compared. - Public voting needs a way to stop one person voting fifty times, agreed before the vote opens, not after someone complains.

The five forms that run an awards scheme

1. Award nomination form

Ask who is being nominated, who is nominating them, which category, and — this is the field people skip — specific evidence. "Describe a time this person went above and beyond" gets you a paragraph judges can actually score. "Why should they win?" gets you an adjective. Cap the word count; a hard limit of 200–300 words produces sharper answers than an open text box.

Allow self-nominations if the category makes sense for it, but say so explicitly — assuming it's obvious is a common source of no-shows in categories like "rising star".

2. Employee of the month nomination

Keep this lightweight — it needs to happen every month without becoming a chore. Name, nominee, one example of what they did, and a category tag if you run more than one type of recognition. Route submissions straight to whoever runs the announcement, not into a folder that needs chasing.

3. Community hero / public nomination

These attract vaguer entries than internal awards because nominators often don't know the nominee well. Ask for one concrete story rather than general praise, and consider a photo upload — a picture of the person in action does more to bring a nomination to life than another paragraph.

4. Judging scorecard

This is the form most schemes get wrong by not building one at all and asking judges to email opinions instead. Build a scorecard with the same numeric criteria for every entry — say, four criteria scored 1–5, plus one comments field — so scores are comparable across judges and entries. Show the judge which entry they're scoring clearly at the top, and never let a judge see other judges' scores before submitting their own.

Common mistake: too many criteria. Five well-chosen criteria judged carefully beat twelve judged in a hurry.

5. Public award voting form

Public votes need friction against repeat voting, agreed in advance: one vote per verified email, or one per device per day, stated clearly on the form itself. Show the categories and entries clearly, allow one vote per category rather than a single combined vote, and never show a running leaderboard during an open public vote — it turns voting into a bandwagon rather than a genuine choice.

Keeping it fair and defensible

• Publish the criteria before judging starts. A scorecard built after entries are in looks, and often is, built to favour a particular result. - Separate nomination from judging. Whoever collects entries should not also be the sole judge — even the appearance of a conflict undermines an otherwise well-run scheme. - Keep an audit trail. Store submission timestamps and, for public votes, enough detail (without over-collecting personal data) to investigate a dispute if one comes up. - Decide ties in advance. A published tie-break rule, even a simple one, avoids an argument after the fact.

Announcing results without a mess

Once judging closes, a short "shortlist announced" step before the final winner reveal builds anticipation and gives you a natural point to double-check the scoring before it's public. Keep the scorecard data somewhere you can export it — auditors, sponsors or simply next year's organiser will thank you for a clean record rather than a folder of emails.

A quick checklist before you publish

• Does the nomination form ask for evidence, not just praise? - Are judging criteria fixed and published before scoring opens? - Can judges see the entry but not each other's scores? - Is there an anti-fraud rule for public voting, stated on the form? - Is there a published, simple tie-break rule? - Have you tested the voting form on a phone, as a member of the public would?

Get those right and an awards scheme stops depending on trust in the organiser and starts depending on a process that's visibly fair.