How Recognition Budgets Work
Budget types (per-user vs shared), monthly resets, what employees see (balances, limits, errors), and how budgets interact with credits and recognition.
Recognition budgets set how many points people in your workspace can give each month. They reset automatically, keep spending predictable for finance, and make sure appreciation doesn't dry up unevenly across the cycle.
What this is
A recognition budget is a monthly pool of points that controls giving capacity. PraisePal offers two types:
Per-user budgets give each assigned person the same monthly allowance. The total pool scales automatically with headcount — if five people each have 500 points, the pool is 2,500.
Fixed budgets provide a single shared pool that everyone draws from, regardless of group size. Admins can optionally enable a per-person spending cap so one individual can't exhaust the pool alone.
Each person is assigned to exactly one budget at a time. Admins configure amounts in their local currency, which PraisePal converts to points at the current exchange rate (100 points = US$1).
Why it exists
Recognition programs work best when appreciation is frequent and predictable. Without budgets, usage tends to spike early in a cycle and dry up later — or vary wildly across teams.
Budgets give admins control over distribution. Different tiers for individual contributors, managers, and executives keep allocation proportional without micromanaging each recognition. Finance gets visibility into expected monthly spend, and the separation of giving allowance from earned points means budget limits never affect what someone has already received or can redeem.
How it works
When someone sends recognition with points, their budget is drawn down. Per-user budgets track each person's spend individually against their allowance. Fixed budgets debit a single shared pool. If an admin has set a per-recipient limit, it caps the points someone can attach to any single recognition — separate from the overall budget.
Monthly reset happens on the 1st of each month (01:00 SGT, applied globally — not per-user timezone). Per-user budgets recalculate the total pool from current headcount multiplied by the per-user limit. Fixed budgets refill to their configured total. All individual spend counters reset to zero. Unspent points do not roll over.
One nuance with per-user budgets: when someone joins or leaves mid-month, the aggregate pool total isn't recalculated until the next monthly reset or the next time an admin edits the budget. Individual allowance enforcement still works correctly day-to-day — it's the aggregate pool number that may lag behind until reconciliation.
What employees see depends on budget type. Per-user budgets show remaining allowance in points. Fixed budgets show a shared pool percentage. Both display the per-recipient limit when set and the budget name. Tooltips note that allowances refresh on the first of every month.
When a budget runs out, point-bearing recognition is blocked — but people can still send recognition without points. Appreciation doesn't stop; only the point transfer pauses until the next reset or an admin adjustment.
If someone moves between budgets mid-month, their spend travels with them. Allowance spent is tracked on the person, not the budget. Someone who has used 300 points this month and moves to a budget with a 200-point per-user limit will have zero remaining allowance under the new budget until the next reset.
Common misconceptions
Example: per-user vs fixed in practice
A company assigns 5 people to a per-user budget of 500 points each. Total pool: 2,500. One person leaves mid-month; the pool adjusts to 2,000 at the next reset. Each remaining person's allowance stays at 500.
A separate team shares a fixed budget of 10,000 points with a 2,000-point per-person cap. After several recognitions the pool drops to 3,000. No individual can spend more than 2,000, but once the pool hits zero, all point-bearing recognition stops for the group until next month.