Employee of the month schemes rarely fail at launch. They fail around month five. The first two months produce a flood of nominations, the third produces a handful, and by the fifth the same department has won three times, somebody has said out loud that it is a popularity contest, and the person running it is writing nominations themselves the day before the announcement to avoid an empty month.
The form is not the whole cause of that, but it is the part that can be fixed in an afternoon. A nomination form that asks the wrong question produces evidence nobody can judge. One that cannot tell two nominations of the same person apart from two nominations of different people produces a count nobody trusts. And a form that is vague about who reads what destroys the candour that makes the scheme worth running. Anonymous, countable and fair are three separate design problems, and each one has a concrete answer.
What the form has to ask
An employee of the month nomination has four parts, and most forms only get two of them right.
Who is being nominated. Name, team, and if the organisation is large enough for name collisions, location or shift. This should be a list to pick from rather than a box to type in, for reasons covered further down.
Which criterion applies. If the organisation has stated values or behaviours, put them on the form as a required single choice. Nominators find it much easier to write about "went beyond the role to help a customer" than about excellence in the abstract, and the panel gets nominations already sorted into comparable groups.
What actually happened. The core field, and the one that decides whether the scheme has substance. Ask for a specific instance in a specific period: what the person did, when, who was affected, and what would have happened otherwise. A prompt written that way turns one line answers into short stories. A field labelled "reason for nomination" produces "hard worker, always helpful", which cannot be compared against anything.
Who is nominating. Name and email, or in a fully anonymous scheme, at least the department. This is the field with the most consequences, and it is covered in its own section below.
Shorter prompts, more of them
Splitting the evidence into two or three smaller boxes lifts quality more than any wording change. What happened. Who noticed the difference. Why it was beyond the normal expectations of the role. Three boxes of sixty to eighty words each are less intimidating than one large empty box, and they give the panel the same three things for every nominee, which is what makes scoring consistent.
A minimum length on the main box, with the reason stated beside it, is worth setting. A maximum is worth setting too once the panel is reading thirty of these a month.
Eligibility, decided before the first round
Three eligibility questions come up in every scheme and are much easier to answer in advance than in an argument. Whether staff still in a probation period can be nominated, whether contractors and agency staff can be, and whether a team can be nominated instead of an individual. A nominee list drawn from the roster can simply exclude the people who are not eligible, which avoids the situation where somebody is nominated, hears about it informally, and then finds out they were never in the running. Where the list has to be free text, put the rule in one line next to the field rather than in a policy document elsewhere.
Team nominations in particular need deciding early, because a scheme that allows them and a scheme that does not need different prizes and different announcement wording.
Anonymity, and the three versions of it
"Anonymous" means at least three different things, and the form should say which one is in force.
Anonymous to the nominee, named to the panel. The most common and usually the most useful. The panel can weigh who is nominating whom, follow up for detail, and notice when a manager is nominating only their own reports. The nominee never learns who put them forward. This is the default worth choosing unless there is a reason not to.
Anonymous to everyone. No identity collected at all. This protects the most junior nominators and costs two things: nobody can be asked a follow up question, and nothing stops one enthusiastic person submitting six times.
Named to everyone. Appropriate for peer recognition schemes where the point is partly that colleagues see each other's praise, and inappropriate anywhere a nomination might carry a risk for the nominator.
There is a technical wrinkle worth knowing before promising anonymity on a free tool. In Google Forms, the setting that limits each person to one response requires users to sign in to their Google Account, and Google's documentation adds that their usernames will not be recorded unless the setting to collect email addresses is turned on. So a limited, unnamed form is possible there. What is not possible is proving that to a sceptical workforce, because the respondent is being asked to sign in immediately before being told the response is anonymous. Whatever the mechanism, write in plain words on the form who can see the nominator's name, and make sure that sentence is true.
The shift and site problem
Anonymity by sign in has a second cost that matters in retail, manufacturing, hospitality and care. Not everyone has a work account, and not everyone fills in forms at a desk. A scheme that only reaches staff with email quietly excludes the people whose work is least visible already, which is the exact bias the scheme was supposed to correct. A form that opens from a link or a QR code on a break room wall, with no account needed, reaches a different half of the workforce.
Making the result countable
Countable means that at the end of the month, grouping the nominations gives a list of people with a number beside each, without anyone editing anything.
The nominee field decides this. Free text produces "Sam", "Sam T", "Samira from the late shift" and "S. Tahir" as four rows. A dropdown or searchable list from the staff roster produces one row per person and a count that can be sorted in a second. Where a roster list is impractical, split the name into first and last as separate fields, which at least puts near matches next to each other.
One submission per nominator, if volume is meant to matter. Decide first whether it does. If the award goes to whoever gets most nominations, the scheme is a vote and needs vote controls, and it will attract campaigning. If a panel judges the strength of the case, volume is only a tiebreak and the controls matter less. Say which it is on the form, because nominators who organise a campaign and then find out it counted for nothing feel misled.
A window with a start and an end. Nominations for September should be about September. A form that stays open all year accumulates nominations with no month attached, and the month gets inferred from a timestamp, which is wrong for anything submitted on the first of the following month. Ask for the period the nomination relates to, or open and close the form on dates.
Each nomination also needs a status of its own once it arrives: new, checked, shortlisted, not this month, or carried forward. Carried forward is the one most schemes lack, and it is the cheapest fix for a thin month. A strong nomination that lost to a stronger one should not be thrown away; it should be eligible next month with the nominator told so.
Fairness people can actually see
Perceived fairness is the whole scheme. A programme can be run impeccably and still die because nobody outside the panel can see how the decision was made.
Four things do most of the work, and three of them are set once.
Publish the criteria and the process before the first round. What is being rewarded, who decides, how often, and what the prize is. Vagueness here is what invites the popularity contest accusation.
Rotate the panel, and never have it be one person. Two or three readers per cycle, changed each quarter, with a rule that nobody scores a nomination for their own team member. A rotating panel makes the outcome look less like one manager's preference because it is not.
Track where nominations come from, not only who wins. Count nominations by department, shift and role each month. If the back office, the night shift or the field team never appear, that is not because nobody there did anything notable. It is a visibility problem, and it needs a direct ask rather than a general reminder.
Publish the reason with the winner. A short paragraph describing what the person did, taken from the nomination, does more for the scheme than the prize does. It shows the standard, it teaches nominators what a good nomination looks like, and it makes the next month's submissions better.
A cooldown is worth considering as well: a winner cannot win again for six or twelve months. That single rule prevents the most common complaint, which is one popular person winning repeatedly, and it forces nominators to look further afield.
Where the monthly list should live
The scheme runs every month, forever, and usually gets handed to somebody new after a year. That makes the durability of the record more important than it looks at setup.
| Approach | Good at | Where it costs you |
|---|---|---|
| A free form plus a spreadsheet | No cost, running the same day, familiar to everyone | No status per nomination, no carry forward, nominations and the follow up email live in different places, history breaks when the owner leaves |
| A recognition or rewards platform | Points, badges, peer to peer praise, catalogue of rewards, reporting | Priced per employee, so a scheme for a small team costs the same per head as a large programme, and much of what is paid for is unused |
| A form tool with response management | Each nomination keeps an owner and a status, carried forward nominations stay in the list, replies sent from the same screen | Prize fulfilment and points balances are not part of it and need somewhere else to live |
For a team of thirty running one award a month, a per employee recognition platform is usually more machinery than the situation needs, while a spreadsheet loses the history. Check how the shortlist looks in each option before deciding, and check the pricing model rather than the headline number: what a tool counts when it prices matters when a nomination window brings in two hundred submissions in three days and then nothing for a month. The features that decide this are unglamorous, such as a status per response, a nominee list rather than a text box, and a link that works without an account.
What to change first
Rewrite the evidence question to ask for one specific instance in a stated month, since that single change is what separates a scheme with substance from a list of adjectives. Then replace the free text nominee box with a list from the roster so the monthly count needs no cleaning, and write one true sentence on the form about who sees the nominator's name. If nominations, shortlisting and the replies to nominators currently live in three different places, see what all three on one screen looks like before the next cycle opens.
Q1. What questions should an employee of the month nomination form ask?
The nominee picked from a list, which stated value or criterion applies, a specific instance with what happened and what changed as a result, and the nominator's details unless the scheme is fully anonymous. The evidence question does the most work, so ask for a specific event in a specific month rather than a general opinion of the person.
Q2. Can the nomination form be anonymous and still stop repeat submissions?
Partly. In Google Forms the setting that limits responses requires signing in to a Google Account, and Google's documentation notes usernames are not recorded unless email collection is turned on, so a limited and unnamed form is technically possible. The harder problem is convincing staff of that, since they are asked to sign in right before being told it is anonymous, so state clearly on the form who can see what.
Q3. How do you stop the same popular person winning every month?
Two rules do most of it: a cooldown period barring a repeat win for six or twelve months, and counting nominations by department and shift each month so gaps become visible. Publishing the reason alongside each winner also shifts nominators away from general popularity and towards describing specific work.
Q4. Should managers be allowed to nominate their own team members?
Usually yes, since managers see the work most closely, but ask for the nominator's relationship to the nominee so the pattern is visible. The rule that matters more is that nobody scores or votes on a nomination for someone who reports to them.
Q5. What happens to good nominations that do not win?
Give them a carried forward status and let them stand for the following month, with the nominator told that is what happened. This is the cheapest fix for a thin month, and it stops strong cases being thrown away because a stronger one arrived in the same week.
Q6. How do you reach staff who do not have work email or sit at a desk?
Use a form that opens from a link or a QR code without requiring an account, and put that code somewhere physical such as a break room noticeboard. A scheme that only reaches staff with email addresses systematically misses the roles whose work is least visible, which is the bias the award was meant to correct.