A rewards store and points system: giving recognition a tangible payoff

The first question after a recognition system goes live is always the same: "will these points be worth anything?" If the answer is no, the system tends to fade; if yes and it's built carelessly, it can distort the meaning of recognition itself. The rewards store is where that balance is struck.

Where do points come from?

The sources that produce points should be few and clear. Typically: recognition received, completed training, implemented ideas, and in some companies length of service.

Adding more sources makes the system opaque. If an employee can't answer "why do I have this many points?", the motivating effect disappears.

Points aren't produced in the client

This looks like a technical detail, but the entire credibility of the system rests on it. If a points balance can be written from the browser, the rewards store becomes a game.

In a correct design points are produced only server-side, by database triggers: a recognition record is created and points are written; a reward claim is approved and they're deducted. No balance value sent by the client is trusted. We apply the same principle to quiz scores and request approvals — covered in our recognition article.

Catalogue design: the threshold question

The single critical parameter of a reward catalogue is the first threshold. Too high and nobody reaches it, so the system stays invisible; too low and recognition loses value.

A practical start: a first tier reachable with two or three months of steady contribution. Larger rewards can sit above it, but the first tier should always stay within reach.

Variety matters too. The same reward doesn't motivate everyone: one person wants a day off, another a training budget, another a gift card. Five or six options are enough for most companies.

Cash or experience?

Cash and cash-like rewards (gift cards) are fast and easy to understand but have two weaknesses: they aren't remembered, and they're perceived as an extension of salary.

Experience rewards — an extra day off, attending a conference, a team activity — are remembered longer and sit better with company culture. A mixed catalogue is usually best.

Approval and delivery

A reward claim should have an approval step, both for budget control and to plan delivery. But approval genuinely has to be fast: a gift-card request waiting two weeks consumes the reward's motivating effect.

The status of the claim must also be visible to the employee. That's why it makes sense for the system to use the same infrastructure as requests — covered in our requests article.

Do points expire?

Two common questions: should points have an expiry, and should the points from a deleted recognition be reversed?

On the first, a long validity period is more reasonable than an annual reset; the resentment caused by expiring points outweighs the budget discipline it buys.

On the second our choice is clear: points are not reversed. Even when inappropriate recognition is removed, reward claims made in the meantime shouldn't become invalid. Removal deletes it from the wall; it doesn't rewrite history.

The tax and accounting angle

Benefits provided to employees, in cash or in kind, have a tax dimension that varies by country, reward type and amount. Small symbolic rewards and regular, higher-value ones are treated differently.

This article is general information; we'd suggest talking to your accountant before finalising the catalogue. Settling that side up front is easier than changing the catalogue later.

Team rewards

Placing a team reward alongside individual ones stops the system turning into a competition. A small reward given to a whole department when it reaches a shared goal balances the tension individual point-chasing can create.

A practical structure: individual points come from recognition, team rewards are tied to a periodic achievement. Managing the two from separate budgets stops one eating the other.

Measurement

• Redemption rate — what share of point-holders actually claimed a reward? If it's low, the threshold is too high or the catalogue doesn't appeal.
• Average accumulation time — how long to reach the first reward.
• Catalogue distribution — which rewards are claimed, which are never chosen?
• Effect on recognition volume — after the store opened, did recognition rise, or did point-hunting begin?

The last deserves the most attention: if the quality of recognition messages falls while the count rises, the system has drifted from its purpose.