A suggestion system reward policy example: points, money, recognition
In brief
A reward policy is built without mixing three separate tools: points that show participation, money tied to validated gain, and recognition given in front of everyone. The skeleton of an example policy.
3 November 2026 · 5 min read
Sample company · demo dataReward settings
Most suggestion systems fade not because of the reward but because of its uncertainty. If employees do not know how their idea is judged, they take the first rejection personally and never write again. According to Toyota's own history pages, the company's suggestion system has run since 1951; behind a system that has lived that long is a rule everyone knows in advance about how an idea will be received. This article gives the example skeleton of such a rule; amounts and ratios are the company's decision and are not written here.
Three tools, three purposes
Points: make participation visible. Every suggestion, every Kaizen, every completed audit earns points; points depend on the existence of a contribution, not on the value of the idea.
Money: tied to validated gain. Only work that has been implemented and measured qualifies for a monetary reward; no money is paid on an estimated gain.
Recognition: given in front of everyone. Applause on the board, a name read out at the monthly meeting, a certificate of thanks. Recognition is neither points nor money and does not replace them.
Mixing the three tools is the most common mistake. If points convert to money, low-value records multiply; if money is put in place of recognition, teamwork turns into competition; if there is no recognition at all, money soon becomes a habit and loses its effect.
Example policy skeleton
Scope: which record types qualify for a reward? For example implemented suggestions and completed Kaizens; complaint and report types earn points but not monetary rewards.
Decision: who decides? For small pieces of work a unit owner may give a quick reward; above a certain gain the record goes to the committee. Committee members score without seeing each other's scores.
Calculation: is the monetary reward a share of validated gain, fixed tiers by score range, or both? Whichever is chosen, the rule is written and open to everyone.
Teams: for team work the reward sharing ratio is set in advance and shown on the record.
Being a party: the record's owner, its team or the person who entered it on someone's behalf can neither score nor decide on that record.
Payment: the time from reward decision to payment and who marks the payment are defined. A reward decided but unpaid breeds distrust.
Exclusions: roll-out work, tasks already in the job description and things done because regulation requires them may be kept outside rewards; that too is written down.
What points are for, and what they are not
A points system counts participation: how many people wrote, how many write regularly, which unit is silent. Points may be matched with badges or a small catalogue, but points must be kept apart from the committee reward. The committee reward looks at the value of a piece of work; points look at a person's habit of participating. If the two are poured into the same pool, nobody understands which behaviour is being rewarded.
Why recognition is indispensable
OSHA's worker participation page counts listening to workers' ideas and responding to their contributions as a basic condition of participation in safety programmes. The same principle holds for suggestion systems: everyone seeing that an idea was accepted is a message as strong as money. Recognition is cheap, fast and breeds no envy, provided it is fair. The measure of fairness is that the same kind of contribution is recognised in the same way.
Three rules for writing the policy
Keep it short: one page. A long policy is not read, and an unread policy is perceived as arbitrary.
Keep it open: an employee should be able to read the policy on their phone; a document on the manager's desk is not a policy.
Make it produce reasons: every decision, acceptance or rejection, returns to the record's owner with its reason. A rejection without a reason voids every clause of the policy.
Sample company · demo data
My points
How it is done in Gemy
The committee and reward section is optional; a company may use no rewards at all or only quick rewards. Scoring questions, scales, weights, score ranges and amounts are the company's settings.
Committee members score a record without seeing each other; once the quorum is reached the chair confirms the result, asks for re-scoring, changes the reward with a reason or excludes the work from rewards with a reason. A member or chair who is a party to the record can neither score nor decide on it.
The reward of the range the result score falls into (an amount, a non-monetary reward or both) is assigned; on a team record the reward is shared and the calculation of each share is shown on the record. If a decision step in the flow allows quick rewards, the decider can give one without sending the record to the committee.
Records marked as roll-outs can be excluded from rewards by a setting. At the reward payment step the reward owner marks the payment; a certificate of thanks PDF can be produced for every reward.
Gamification points, badges and the reward shop work separately from the committee reward and are switched on by the company. Board applause is thanks only; it earns no points or reward.
Gemy does not calculate the taxation of rewards; payroll lines are exported, and tax and deductions belong to the company's accountant.
In short
A good reward policy keeps three tools apart: points that count participation, money tied to validated gain and recognition given in front of everyone. The policy is one page, open to all and produces a reason for every decision. No reward is given before scope, decision authority, calculation rule, team sharing, the ban on parties deciding and the payment period are written down. The company sets the amounts; the system's job is to apply the rule to everyone in the same way.
You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/oneri-sistemi-odul-politikasi-ornegi-puan-para-taninma).
Every solved problem is a piece of knowledge; in most companies it leaves with the person who solved it. The four places where knowledge is lost, the view of ISO 30401 and ISO 9001, and five habits that make knowledge independent of people.
A supplier audit is a process, not a visit: which supplier, which question, which finding, which evidence. The audit principles of ISO 19011, the structure of the question list, finding classes and how the reply returns to the same record.
Document control ensures the right version of the right document is with the right person. What ISO 9001 asks for, document types and numbering, the approval chain, distribution and reading, withdrawing the old version and the five most common gaps.
9 November 2026 · 6 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.