6 Rules for a Point Reward System for Employees That Sticks

Points are easy to hand out and easy to resent. The difference is six decisions you make before anyone earns a single one.

Teams buy a points-based rewards system to solve a real problem. Good work goes unseen. Thank-yous land in a DM nobody else reads. Someone quietly starts looking.

Then the points arrive and a second problem shows up. People stockpile them. Or they dump them at month end so they do not vanish. Or they open the catalog once, see nothing worth having, and never open it again.

That is not a points problem. It is a design problem, and it is fixable. The points-based systems that fail tend to fail for reasons the company chose on purpose.

What a points-based employee recognition program is

A points-based rewards system gives employees points when they do something the company wants more of. They swap those points for real rewards. The points are the unit. The reward is the payoff. The company sets the budget behind both.

Culture Engine is a Slack-native employee recognition and rewards platform. Our points layer is called Coins, and the rules below are the ones we run ourselves.

Every points-based rewards system has four moving parts:

• The trigger. What someone did to earn points — help, effort, a milestone, a company value lived out loud.
• The point values. How many points that action is worth, written down before launch.
• The reward catalog. What points turn into. Gift cards, prepaid cards, and donations are the three that hold up.
• The budget. How much the company funds each month, and who controls it.

Get all four right and the employee reward system runs itself, and the employee reward budget stops being an argument. Get one wrong and people notice quickly.

How employee points are earned and redeemed

Someone earns points

A teammate posts a shoutout, or a manager marks a milestone. Points attach to it. The best employee reward systems make this take seconds and happen in public, in the channel the team already uses.

The points carry a set value

Every points system needs an exchange rate. Ten points to the dollar is the easiest one to hold in your head. Whatever you pick, employees should be able to do the sum without a calculator, or the points feel invented.

The employee redeems them

Rewards points sit in a personal balance until the person wants something. Then they choose. A gift card. A prepaid card. A donation to a cause they care about. Choice is the whole reason points exist instead of a company mug.

An admin funds the pool

Someone sets the monthly budget and tops it up. In a good employee reward point system that is one screen and one number, not a procurement project.

Why employee reward systems stall after the launch

We read through the reviews of rival tools before we built ours. The complaints repeat, almost word for word, and every one of them is a design choice somebody made.

• Expiry. “The points expire after a month. I forget about the app and feel terrible when they disappear.”
• Point dumping. “I had to point-dump at the end of the month so I didn’t lose them.”
• Caps. “Not enough points to give away — too much appreciation to spread.”
• Weak rewards. “Kudos points have no value.” “It takes forever to gain enough points to purchase anything.”
• Rankings. “The same individuals are consistently rewarded… favoritism.”

Every one of those complaints is a rule somebody chose. Which means you can choose differently.

Only 22% of employees say they get the right amount of recognition, and that number has not moved since 2022 (Gallup–Workhuman). An employee recognition program built on points is one of the few things that can shift it. It just has to be built so people trust it.

Rule 1 — Keep the thank-you separate from the rewards program budget

This is the rule that does the most damage when it is missed.

Plenty of tools make one thing do two jobs. The points you send are also the reward currency. That currency costs money, so the tool has to cap it. So the company ends up rationing gratitude. Five a day. Twenty a month. Then it runs out, and people stop saying thank you because the system told them they were done.

Split the two. Recognition should be unlimited. Anyone can thank anyone, any time, as many times as the week deserves. Points are the budgeted layer on top. The company controls the spend without ever putting a ceiling on kindness.

That one split fixes the cap complaint, and it changes how the whole employee recognition program feels. Saying “nice work” stops being a transaction.

Rule 2 — Never expire employee points

Expiry exists for the vendor’s benefit, not yours. Unredeemed employee points sit as a liability on someone’s books, so they get wiped.

The cost lands on your team. People saving for something good lose it. Others learn to spend fast on things they do not want. Both teach employees the points were never really theirs. Once they believe that, the reward system is decoration.

Our Coins never expire. No deadline, no end-of-month scramble, no meaningless flurry of recognition on the 30th. If someone wants to save for six months and buy something that matters, that is their call.

Rule 3 — Publish your earning rules before launch

Vague earning rules are the quiet killer. If nobody can predict what earns them, people assume the points system is random. Or worse, political.

Publish a simple table before day one. Say what earns points, how many, and who can award them. Then leave it alone for a quarter so people can learn it.

Transparent point allocation does something else too. It tells employees what the company actually values, in numbers. That is a far clearer signal than a poster in the kitchen.

Rule 4 — Tie earning to company values, never force it

Linking points to company values is good practice. Positive behaviors get named, repeated, and copied. That is how an employee recognition program turns into a habit instead of an announcement.

Forcing the link is not. The moment a value tag becomes mandatory, you get the complaint we heard again and again: “I have to use the hashtags each time, which is annoying.” Participation drops. The tags you do get are picked at random to clear the form.

Encourage the tag. Never require it. Every compulsory field costs you a share of the people who would otherwise have said something nice.

Rule 5 — Make the rewards worth having

Points are only as good as what they buy. This is where an employee reward system quietly fails, because the catalog was an afterthought.

Three reward types hold up over time:

• Gift cards. Wide choice, instant delivery, and the employee picks the brand.
• Prepaid cards. Spendable anywhere, with none of the “I got a voucher for a shop I never use” problem.
• Charitable donations. For people who would rather the money went somewhere else. Keep the list broad and avoid pushing an agenda.

Let people choose rewards themselves. A reward you picked for someone is a gift; a reward they picked is theirs. Rewards points only feel meaningful when there is a real choice at the end. A thin catalog turns meaningful rewards into a chore.

Our catalog runs to 2,500 options in 200+ countries. That matters more than it sounds if anyone on your team sits outside your head office country. A reward nobody local can redeem is not a reward.

Monetary rewards through a points system are not pay, and should never be sold as pay. Recognition sits on top of fair salary, never instead of it. If people are underpaid, no rewards program will fix that. Pretending otherwise makes the whole thing look cynical.

Rule 6 — Report participation as a team rate

The temptation with any points-based system is to build a scoreboard. Top givers. Top earners. Employee of the month.

Do not. The moment recognition can be ranked, it gets farmed. People send points to whoever sends them back. The loudest teammates win. The quiet ones drop off. The whole thing turns into the popularity contest people complain about.

A points-based rewards system does not need a scoreboard to work. Report one number instead: what share of the team gave or received recognition this week. It shows whether the habit is spreading, without singling out a single person in either direction.

How to set point values in your points system

Start simple. Three tiers cover almost everything, and you can add more later.

Two guardrails. Keep the everyday tier generous enough to use weekly, because frequency is what builds the habit. And keep the top tier rare enough that it still means something when it lands.

Work out the per-person budget first

Divide the monthly budget by headcount and you have your ceiling. A team of 80 with an $800 monthly pool has $10 per person to give away, which at ten points to the dollar is 100 points a week each. Then set your earning tiers so an ordinary week of recognition and rewards fits inside that. It is easy to overshoot here and end up quietly halving the numbers later, so model it on a spreadsheet first.

Let employees accumulate points

A balance that grows motivates in a way a monthly allowance never does. Employees earn points, watch them add up, and choose when to spend. That anticipation is doing real work for you, and it costs nothing.

What to give employee points for

The trigger list is where an employee recognition program either reflects the company or reads like a downloaded template.

• Help nobody asked for. The teammate who quietly fixed the thing before it broke.
• Work that shows a company value in action, named out loud so others copy it.
• Milestones. Anniversaries, a first shipped project, a certification finished at night.
• Effort with no visible result. Sometimes the hardest week produces nothing shippable. Recognize employees for it anyway.
• Cross-team saves. The person in another function who dropped everything to unblock you.

Two things not to reward with points

Do not attach points-based rewards to sales targets or output numbers that already carry a commission. Paying twice for the same thing teaches people to chase the metric, not the work. Incentive programs already cover that ground, and they cover it differently.

And do not reward attendance. It is the fastest way to make a points-based reward system feel like surveillance.

A points-based system vs other employee reward systems

A points layer is not the only option. It earns its place on flexibility — employees choose rewards that mean something to them, which no fixed gift can match.

Plenty of teams run two of these together. A points-based recognition program for the everyday, and something larger once a year. They answer different questions, and a good rewards program does not pretend otherwise.

Where private recognition fits

Not everyone wants a public shoutout. Private recognition with points attached still counts, and for some people it counts more. Give managers both options and let the employee decide. A quiet note with points attached is not a downgrade — for some people it is the only version that lands.

A 30-day plan to launch your employee recognition program

Week 1 — Fix the exchange rate and the pool

Pick your points-to-dollars rate and your monthly per-person figure, and check they survive an ordinary week of recognition. Do this on a spreadsheet, before anyone can see it. Changing the rate after launch is the one edit employees genuinely resent.

Week 2 — Publish the point values, not the philosophy

Post the earning table where everyone can see it, with the redemption catalog next to it. Skip the mission statement. The two things employees want to know are what earns points and what points buy, and both fit in a single message.

Week 3 — Spend the first month’s budget on purpose

Do not let the pool sit unused while people work out whether this is real. Have managers and a few willing teammates give early, publicly, and specifically. The first ten shoutouts are the worked examples everyone else copies.

Week 4 — Audit redemptions, not givers

Check that points are actually being spent, and that nothing in the catalog is unreachable from someone’s country. An employee recognition program can look healthy on giving and still be broken at the till.

How to tell your points program is working

The participation rate is climbing

One number, tracked weekly. Rising means the habit is taking. If it stays flat, something in the setup is in the way, and it is usually a rule rather than the people.

Points are being redeemed

A big pile of unspent rewards points is a warning, not a saving. It usually means the catalog is thin or redemption is fiddly.

Recognition is spreading sideways

If points are still flowing only from managers once the program has bedded in, the reward system has become a management tool. In the teams where it works, peer recognition runs across functions without anyone asking permission.

Only 17% of employees receive recognition weekly (Achievers Workforce Institute). Clear that bar and your team is getting recognition that most employees never do.

What changes when employees recognize each other

Plenty of points programs make the manager the only source. That puts one person in charge of noticing everything, which nobody can actually do.

Open it up and the shape changes. Peer recognition catches the things a manager never sees. The late reply that saved a client call. The teammate who rewrote someone else’s messy handover. Open peer recognition fixes that, because there are forty pairs of eyes instead of one.

The manager’s week changes too. Instead of hunting for something to say on a Friday, they read what the team already wrote and add to it. Their job shifts from having to recognize employees single-handedly to helping the whole team reward employees well. That is a much easier job, and it produces better writing.

It moves motivation, not just mood

Employee motivation is mostly about whether effort gets noticed. A points layer that lets anyone reward employees makes noticing cheap and frequent. Frequency turns a nice moment into a habit. That is the honest answer to “will this actually motivate employees” — not the points, the noticing.

Public recognition does most of that work, because it teaches by example. Every shoutout in a shared channel shows the team what good looks like here. That repeats the positive behaviors you wanted more of.

Employee engagement follows participation

Employee engagement is a lagging measure. Participation is a leading one. If more of the team takes part this month than last, employee engagement and employee satisfaction follow later. If participation is falling, no survey is going to save you.

Meaningful recognition beats bigger rewards

When a program feels flat, the first instinct is usually more money per point. It rarely works.

What makes recognition land is specificity and speed. “Thanks for the deck” does very little. “You rewrote the pricing slide at 9pm so the client call made sense — that is why we won it” does a lot, and it costs the same. Meaningful recognition is a writing problem before it is a budget problem.

Points make that writing worth doing, because they turn a good sentence into something the person can hold. But the sentence is the part that moves employee motivation. Double the point value on a vague message and you get a vague message with a bigger price tag.

Give it in public, close to the moment

A shoutout three weeks late reads like an audit. Continuous recognition is small, quick, and in the open. It beats a quarterly ceremony on every measure that matters, including how many employees join in.

Does a points system help employee retention?

Yes, when the recognition behind it is frequent and real. Employees who get high-quality recognition are 45% less likely to leave within two years (Gallup–Workhuman). That is the number worth building a rewards program around.

The money side is blunter. Replacing an employee costs 50–200% of their annual salary (Gallup). Lose two or three good people a year and the bill is real money, spent on a problem a thank-you might have prevented. Our turnover cost calculator puts your own number on it in about ten seconds.

Employee satisfaction moves for a simpler reason. People who feel seen do not go looking. Employee engagement surveys pick that up before resignations do. That is why the participation rate is worth watching weekly, not annually.

Mistakes that kill an employee recognition program

Launching without a budget

“We will work out the spend later” means the first redemption request becomes an argument. Fund it before you announce it.

Making the rules complicated

Multipliers, tiers, seasonal bonus points. Points-based programs die of small print. Every extra rule loses you people. Simple beats clever here every time.

Letting managers be the only source

If only managers can award points, employees learn that recognition is a performance review in small pieces. Let everyone give.

Treating points as a substitute for pay

They are not, and employees will say so out loud. Monetary rewards on top of a fair salary read as generosity. The same rewards instead of a raise read as an insult.

Bolting it onto a separate portal

Another login is another reason not to bother. A recognition platform nobody visits is a recognition and rewards budget you are throwing away. “Having to log in every time” is a complaint we heard over and over about rival recognition platforms, and it is entirely self-inflicted. Keep it where the team already talks.

Where a points system fits in a wider recognition system

A points layer is one part of a bigger picture. If you are still deciding what the whole thing should look like, start with the guide to employee rewards programs and come back here for the mechanics. If you want triggers to steal, the employee reward ideas list is the shortcut.

What makes any of it work is repetition. Employees who receive weekly recognition are 11.5× more likely to trust their manager (Achievers Workforce Institute). Weekly is the word doing the work there. A generous points-based recognition program used once a quarter beats nothing, but it does not build a habit.

From the start, the thanks at Culture Engine came with something real attached. Coins you redeem for gift cards, prepaid cards, or donations, because a thank-you that buys nothing stops feeling like much. That is the whole reason a points layer exists, and the whole reason the six rules above matter more than the size of the budget.

Frequently asked questions