Reward Governance allows Super Admins to set rules for the recognition program. These rules help prevent misuse, such as repeated nominations or budget overuse, ensuring the program remains fair for all employees.Documentation Index
Fetch the complete documentation index at: https://empuls.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Key Problems Solved
Prevents Gaming the System
Detects circular reward patterns and stops them automatically to prevent employees from trading points with friends.
Prevents Budget Overrun
Set hard limits on the number of nominations a user can give (e.g., max 3 per month).
Prevents Unfairness & Bias
Limits how often one person can be nominated in a short period to avoid popularity contests.
Available Governance Rules
Our rules adapt based on whether the reward is a Spot Award (direct monetary) or Nomination-Based (requires approval).A. Reciprocity Restriction
The Rule: An employee cannot reward someone who has already rewarded them within the same cycle.- Spot Award Logic: In Restricted Mode, the system blocks the transaction to prevent perceived “point swapping.”
- Nomination Logic: If a user nominates someone who previously rewarded them, the Approver is explicitly informed of the reciprocal connection to ensure an unbiased final decision.
B. Duplicate Recognition Control
The Rule: Prevents favoritism where a single individual dominates the reward pool.- User Rule: An employee cannot reward or nominate the same person more than once per cycle (e.g., Isaac cannot nominate Harsha twice in Q1).
- Approver Rule: An approver can only approve one nomination for the same person across all categories in a single cycle.
- Exception: Team Awards are exempt from these limits to ensure group achievements are still celebrated.
C. Reward Distribution Balancing
The Rule: An employee cannot receive more than one reward from the same category in a single cycle. Example: If Harsha receives an “Outstanding Performer” award, he cannot receive a second “Outstanding Performer” award until the next cycle. This ensures recognition is distributed broadly across the workforce.Enforcement Levels
You can choose how strictly to enforce each rule:Observe Mode
The system allows the user to complete the action but logs the violation in the Governance Report. Use this to monitor behavior without blocking users.
Restricted Mode
The system blocks the action immediately and prompts the user to make changes (e.g., “You have reached your nomination limit”). Use this for strict control.
Real-Time Governance UI
When a rule is triggered, the platform provides clear, value-based communication to the user:| Rule | Advisory Message | Restricted Message |
|---|---|---|
| Reciprocity | Reciprocal Reward Detected: We encourage you to consider the intent and whether it’s unbiased. | Action Not Allowed: Reciprocal rewards are blocked to maintain fairness within this cycle. |
| Duplicate Recognition | Duplicate Detected: Consider recognizing someone else who may also deserve appreciation. | Duplicate Blocked: To encourage diverse recognition, you cannot reward this person again this cycle. |
| Category Balancing | Recipient was already recognized in this category. Consider another category or team member. | Duplicate Category Blocked: To prevent reward concentration, only one reward per category is allowed. |
Governance Report
The report provides an overview of all user actions that triggered governance rules across different enforcement modes. Use this to monitor behavior, assess rule impact, and optimize your recognition policies.| Date | Actors (Giver → Receiver) | Rule Triggered | System Mode | Outcome |
|---|---|---|---|---|
| 2025-05-01 | Isaac Lee → Harsha Rao | Reciprocity Restriction | Audit/Observe | Allowed |
| 2025-05-02 | Isaac Lee → Harsha Rao | Duplicate Recognition | Advisory | Warned & Proceeded |
| 2025-05-03 | Isaac Lee → Harsha Rao | Reward Distribution Balancing | Restricted | Blocked |