Reward points attach to an approved suggestion, kaizen, or success story. No points are created without a rule. HR writes the rule name, event, recipient, and point type. The active switch runs the rule.
A submit event creates points when the record opens. An approval event creates points at close. The two events are not mixed in the same rule. A fixed point is the same on every record. A calculated point can attach to the expected-benefit line.
Staff see their balance in the portal and choose a catalog item. The request receives a date stamp. The fulfiller closes or refuses the order. On refusal, points are refunded; the reason stays on the order. The balance does not go negative.
When the showcase stock note is exhausted, the item closes. No request opens without an item. The web-based showcase is not a separate store application; it is a request screen inside the portal.
A separate rule is written by module. Awarding points for near miss is an organization decision; HSE participation is rewarded only if that rule exists. The default recipient is the person who opened the record. Reviewer points require a separate rule.
A second rule does not run for the same person on the same record. A rule turned off does not create new movement; past lines stay on the ledger. An audit ties the point line to the record reference.
The annual budget is read from the total of fulfilled requests. A unit manager sees the balance if permission allows. Participation is tracked by the number of people who received points and the count of fulfilled requests. The dashboard shows those two figures.
Corporate identity sits on the showcase heading as logo and color. Points do not stand in for the review decision. The step closes first; points are written if a rule exists.