Reward points attach to an approved contribution. No points are created without a rule. HR writes the rule name, event, recipient, and point type. The active switch runs the rule. A rule turned off creates no new movement; past lines stay on the ledger. Points do not stand in for the review decision; the step closes first, then the rule posts to the balance. The rule list is reviewed at period start; a wrong active rule inflates the balance without cause.
Submit events and approval 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 or amount line. A second rule does not run for the same person on the same record. Benefit type is the bucket; there is no category field. The wrong event choice writes points on submit and risks a second write on approval. The rule name is read on the period report; renaming is considered with past rows.
Staff see their balance in the portal. Usable balance is the amount after held points are subtracted. When they choose a catalog item, the request receives a date stamp. When the request opens, points are held; the visible usable amount drops. The fulfiller approves or refuses the order. The hold line ties to the order number. Two requests at once cannot exceed usable balance; the second request hits stock or balance control.
On approval, held points finalize and the item is fulfilled. On refusal, points are refunded; the reason stays on the order. The balance does not go negative. When the stock note is exhausted, the item closes; no request opens without an item. A refund does not lower participation; it only corrects the balance. A double request on the same item hits stock control. HR gathers refund reasons by item at period end.
The showcase is not a separate store application. It is a request screen inside the portal. Corporate identity sits on the showcase heading as logo and color. The web-based screen opens in the browser. Item name, point cost, and stock note appear on the list. A free or zero-point item may close under company rules. HR reviews the stock note mid-period; an exhausted item closes.
A separate rule is written by module. Suggestion approval, kaizen close, and success-story approval may be separate events. Near miss is a type on the HSE record; near miss points are a company decision and need a separate rule. Reviewer points require a separate rule; the default recipient is the person who opened the record. Rules for co-authors are defined separately. Quality reads the rule list by event name at period start.
Field guidance affects points indirectly. If the expected-benefit or amount line is empty, a calculated point rule may not run. The reviewer asks for the line in revision; points do not form before the line is filled. Kaizen asks for before and after measures; without a measure close is delayed and the point event does not fire. A success story is the summary of applied work; without a source reference the point rule still looks at record approval.
Reviewer checks come before points. An approval without rationale weakens the point line in an audit. A rejection reason creates no points. A revision note writes the missing field. The due date is written when the task opens; an overdue task does not delay points, it only delays close. Points do not stand in for the duration badge. Quality checks that the step rationale is filled before the point rule runs.
The annual budget is read from the total of fulfilled requests. A held request not yet approved is not a final budget line. 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 figures. A silent unit is read first from a zero-record row, not from a zero-point row.
HR reviews the rule list at period start. Active switch, event, and recipient are written clearly. Catalog items are added or stock notes updated. Fulfillment role is assigned as central or local. A notice describes a new item or a temporary campaign; a notice alone does not write points. Staff read the rule from the portal balance.
Common mistakes are these. The first is expecting the balance to fill when there is no rule. The second is treating held points as spent and opening a second request. The third is complaining before the refund after a refusal. The fourth is reading a demo portal sample balance as a live budget. The fifth is putting points in place of the approval rationale. The sixth is trying to open a request on an item whose stock note is exhausted; if the item is closed no request forms. The seventh is asking to delete a refund line and fix the balance by hand; the refund stays on the order number.
The period meeting may put points second on the agenda. Closed records and rationale come first, then the count of people who received points and fulfilled requests. A campaign item closes when stock ends. A repeating refund reason shows that the item description is weak. Training explains the showcase and the hold rule to units.
An audit ties the point line to the record reference. A refund line stays on the same order number. Excel export depends on permission. Decision rationale does not stand in for point movement; the step closes first. Hold, finalize, and refund are read as three lines. A missing refund line inflates the balance and is corrected.
There is no simulator page. Rules are managed from the list screen. The engine is data-driven; it does not create points from a fixed file. When a rule changes, only new events are affected. Older balances are not deleted; a rule turned off stops new movement. A renamed rule is reported with the name on the past line. HR writes the rule change into the period notice; staff read the balance from the portal.
In a multi-branch structure fulfillment may be central or local. The form relation is company → branch. Balance still sits with the person. A branch report can filter movement; it does not split a person balance across branches. The wrong company choice drops the order into the wrong fulfillment queue. Location is not a separate box. A branch manager sees local requests when permission allows. HR fixes fulfillment role as branch or central at period start.
Module relations stay clear. Suggestion idea approval may create points. Kaizen measure close is a separate rule. A success story may tie to approval of the applied-work summary. Near miss points sit with the HSE decision. For a closed module the rule screen is hidden; a hidden rule creates no new event. Benefit type is suggestion classification; the point rule looks at event and recipient, not a category field. Staff waiting for points on a closed module do not see a rule on the menu.
Period-end balance is read beside the total of fulfilled requests. Held points still sit on open requests; they are not a final budget line. If the refund rate rises, item description and stock note are reviewed. HR closes campaign items at period end. A new period needs a new rule or a new item; an older rule turned off creates no new movement. Quality lists refund reasons by item in the period meeting.
Staff training explains hold and refund in three sentences: when a request opens points are held, they finalize on approval, and they refund on refusal. Usable balance does not show the held amount as available. A second request cannot exceed the held balance. The balance does not go negative. Those three sentences are also repeated in the notice text. The unit manager shows the hold line with a sample order number in training.
Corporate identity sits on the showcase and balance screens as logo and color. A notice drops request approval or refund rationale into the portal inbox. The decision does not stay in an email body. The web-based screen opens in the browser; a separate store application is not installed. A demo portal sample balance is not a live budget. An audit asks for hold and refund lines on the same order number.
In short: points come from a rule, are held on request, finalize on approval, and refund on refusal. The balance does not go negative. Points do not stand in for the review decision. An audit reads by reference and order number. The step closes first, then the rule posts to the balance. Without stock, no request opens. The due date is written when the task opens.