Two additions to Recognition topics with levels: an option to keep awarding points as a participant's activity grows within a tier, and a full audit trail — right on the participant's page — of every record and allocation behind their current standing.
On this page
- Where to find it
- Continuous level points
- Seeing how points were calculated
- A worked example
- When to use which mode
Where to find it
Both features live on Recognition topics that use levels — sales incentive ladders, tenure tiers, anything with thresholds a participant progresses through.
Open Admin→Recognition to see every topic in the account. Topics that use levels show the number of levels and what they're calculated from — a data series, a points bucket, e-learning progress, or a metric.
Recognition Topics. The summary line under each topic already tells you its award mode — topic1 here reads "Non-periodic Continuous awards 1 levels, calculated from data series Sales".
Continuous level points
A new Level points mode setting controls whether a level's points are paid out once, or kept in step with the participant's activity for as long as they remain in that tier.
Award on level reached(default)
|
Continuous
|
The setting sits in Topic→Settings→Levels and leaderboards, alongside the existing Regression and Calculation mode controls:
Levels and leaderboards settings for a non-periodic, data-series-based topic. Level points mode is set to Continuous.
The explanatory text under the dropdown adapts depending on whether the topic is periodic:
Non-periodic topics
“By default, a level's points are awarded once, in full, the moment it is reached. Select Continuous to instead reconcile points on every calculation, so a level's points can keep growing (or shrink back) while the participant remains in that tier.”
Periodic topics
“By default, a level's points are calculated once, in full, the moment it is reached, but are only awarded when the period closes. Select Continuous to instead reconcile points on every calculation throughout the period, so a level's points can keep growing (or shrink back) while the participant remains in that tier
Switching a live topic to
Continuous takes effect from its next scan — existing allocations aren't rewritten, but the next calculation reconciles the participant's full history against what they've already received, so past under- or over-payment for the current tier is corrected going forward.
Seeing exactly how points were calculated
The participant recognition status page — reached from a topic's participant list, or a profile's Achievements tab — now shows the full chain from raw records to points, not just the final total.
Points allocations (top right) lists every individual allocation ever created for this participant in this topic — not just the current total. All levels (bottom left) adds a Live points calc column, showing what each level would currently pay out.
Scroll down and, for topics based on a data series or points bucket, a Source records table shows the underlying rows the current value was built from:
Source records. For a sales data series this lists each contributing sale; for a points-bucket topic it lists the individual points credits/debits instead. Capped at 100 rows, matching the window used for the level calculation itself.
WHY IT HELPS
Previously, answering “why does this person have these points” meant checking the database. Now it's three panels on one page — useful for support, and for sanity-checking a topic's configuration before it goes live.
A worked example
Here's an actual participant in a continuous, data-series-based topic, read from the panels above.
-
Sales accumulate against the participant
20 records in the
salesdata series are attributed to them, shown in Source records.Source records total → 3,396.64
-
The level's points rule is applied to the current value
Level
lvl1uses a simple multiplier rule,mult=2, shown in the All levels table's Live points calc column.3,396.64 × 2 → 6,793.28
-
First scan: the gap is allocated
At the first calculation, the participant had already been allocated nothing for this level, so the full amount reached at that point was awarded.
15:15 · lvl1 → +4,111.28
-
A later scan tops up the difference
More sales arrived before the next scan. Because
Level points modeisContinuous, the topic didn't ignore the change — it recalculated the total entitlement and allocated just the difference.15:18 · lvl1 → +2,682.00
| Date | Level | Reason | Amount |
|---|---|---|---|
| 20/7/2026 15:15 | lvl1 | lvl1 | 4,111.28 |
| 20/7/2026 15:18 | lvl1 | lvl1 | 2,682.00 |
| Total allocated = live points calc | 6,793.28 | ||
Under the default award on level reached mode, only the first row would ever exist — the participant's later sales would keep raising their current value and their position on any leaderboard, but their points for lvl1 would stay frozen at 4,111.28 no matter how much more they sold.
When to use which mode
Reach for Continuous when…
- The tier represents ongoing activity you want to keep rewarding — e.g. a commission-style sales tier where staying in "Gold" for longer, or selling more within it, should keep paying out.
- Participants can spend a long time inside a single tier before reaching the next one, and a single lump-sum payment at entry would feel disconnected from their ongoing effort.
Keep the default when…
- A level represents a one-off achievement or milestone — the reward is for reaching the bar, not for however long they stay above it.
- You want award history to stay simple: one allocation per level, per participant, full stop.
Continuous mode relies on the topic being scanned regularly (or run manually via Generate awards) — it reconciles at calculation time, it doesn't award retroactively for gaps between scans.