Blog

All articles

Points-Based Reward Catalog Rules That Keep Recognition Fair

A clear rulebook turns recognition points into a reward catalog people trust. Set earning caps, price rewards in points, write redemption terms and review fairness.

Points-Based Reward Catalog Rules That Keep Recognition Fair

Points-Based Reward Catalog Rules That Keep Recognition Fair

Recognition points make a promise: do good work, earn a thank-you, choose something useful. That promise breaks when points are easy to mint or the catalog is confusing. Clear rules protect both sides. They keep the signal finite, the rewards credible and the budget predictable. Wudd's model offers a useful reference point, but the rulebook below works with any recognition program.

Start with the job of points

Write down what points are for before you add a reward. Are they for everyday thank-yous, value-based recognition, milestones, or all three? Keep them separate from salary and bonus. If points become expected pay, the catalog stops feeling like recognition and starts feeling like a second payroll.

In Wudd, each recognition is tagged to a Company Value, weighted, and capped per giver and receiver so the signal stays honest. That is a good principle for any program: points should have a reason attached. If you cannot explain why someone earned them, do not award them.

Rule 1: Cap earning at more than one layer

A points system without caps is a printing press. Set limits at several levels, not just one:

  1. Per-giver weekly cap. Give each sender a finite recognition budget.
  2. Per-receiver monthly cap. Stop one person from accumulating an outsized balance.
  3. Per-Company-Value monthly cap. Keep every value alive in the data, with an override only when you have a reason.
  4. Per-receiver daily cap on manual recognition, plus value-level period caps with per-receiver sub-caps.

Wudd uses a five-layer cap stack, enforced server-side, that rejects a breach. The exact numbers should come from your headcount, recognition frequency and budget, not from another company's rulebook. Test them for a quarter and adjust with notice.

Rule 2: Set the exchange rate before you stock the catalog

Decide what a point is worth before employees start saving. Pick a simple internal anchor and price rewards in consistent multiples. A small thank-you and a major milestone should feel proportionate, not random.

Show points in the recognition flow. If local rules require a cash equivalent, show it clearly at redemption rather than complicating every recognition. Then check the numbers against your budget: points issued, expected redemption rate and unredeemed balances all affect cost.

Rule 3: Curate a small catalog with clear tiers

A catalog does not need hundreds of items. It needs a sensible spread. Build three tiers: everyday rewards people can reach quickly, meaningful rewards worth saving for, and occasional milestone items. Check that the mix works for different tastes, life stages and locations.

Wudd takes a different route from build-your-own catalogs: its store is stocked from a pre-approved supplier network, with no catalog for you to build and no generic vouchers. That reduces administration, but you still need catalog governance. Review what people actually redeem, remove dead items and confirm availability before promoting a reward.

Rule 4: Write redemption rules in plain language

Put the rules where employees can find them. Cover:

  • when points appear after a recognition;
  • minimum redemption amounts;
  • whether points expire, and why;
  • what happens when an item is unavailable;
  • delivery, returns and support;
  • whether rewards are taxable or reportable in your location.

Get finance or legal sign-off on the last point. Tax treatment varies, and a reward catalog is not the place for guesswork. Keep the employee-facing version short. A one-page rulebook beats a policy nobody reads.

Rule 5: Protect fairness across roles and locations

Recognition can drift toward the most visible roles. Catalog rules cannot fix that alone, but they can help. Caps limit concentration. A broad reward mix avoids signaling that only one kind of employee is being recognized. Access matters too: make sure field, remote and part-time employees can earn and redeem on the same terms.

Wudd's Recognition Equity widget surfaces a fairness picture from recognition data. Treat it as a prompt for review, not a verdict. Ask who is earning, who is not, and whether the catalog serves both groups.

Rule 6: Keep recognition first, rewards second

The recognition is the moment. Points are the trace. The catalog is the payoff. If the catalog becomes the main event, people start recognizing to earn points rather than to thank someone.

Wudd treats recognition as a first-class action inside a Connect thread, through a slash command or the wizard, not as a buried text. That placement matters. The reward should follow the thank-you, not replace it.

Rule 7: Review the rulebook every quarter

Use a simple review pack: points issued, redemption rate, unused balances, cap hits, reward popularity, complaints and budget variance. Look for concentration by team, role or manager. Change caps or catalog items only with clear notice. A quiet change to the exchange rate feels like a broken promise.

Results depend on company configuration and adoption. Your own baseline is a better guide than a benchmark from another business.

Put the rules on one page

A practical rulebook has seven sections: purpose, earning caps, point anchor, catalog tiers, redemption terms, fairness checks and review dates. Name an owner for each. Then publish the employee version and keep the operational version behind it.

Wudd brings recognition, KPIs and OKRs together in one system. The Values, Badges and Points stack is included from Wudd Silver onwards, and Strategy KPIs and OKR Key Results read from the same graph from Wudd Gold onwards. Confirm the plan that fits your needs before you design your catalog around it. The rules above are the foundation; the tool should make them easier to run.