Achievements and badges
Badges awarded from portal data
HR defines a condition in the builder, the portal calculates it from activity that has already happened, and awards the badge itself. Fifteen condition types, a preview against real employees before launch, and chains that show how far an employee is from the next tier.
The life of one achievement
- 1
HR assembles the condition
The condition is built on its own tab. Before saving, the builder lists the employees in your company who already match it.
- 2
A preset chain is switched on
The platform ships a catalogue of ready-made achievement chains. A set is enabled in one action, after which the tier thresholds are adjusted for your company.
- 3
The portal recalculates on each event
A recognition sent, an idea submitted, votes collected on it, a colleague congratulated, a profile completed — after every such event the automatic achievements of that employee are recalculated.
- 4
A background service checks tenure hourly
Work anniversaries, months of tenure and birthday month are checked hourly for every company. A five-year badge arrives on the anniversary itself, with no action from HR and without the employee signing in.
- 5
The employee sees the distance to the next tier
The profile shows earned achievements and progress on open ones; the home page carries a widget with the nearest one. Secret achievements stay hidden until they are earned.
What already works
Achievement catalogue in the admin panel
HR creates an achievement, edits it, duplicates a similar one, enables and disables it. Two flags are managed separately: whether the achievement is active, and whether it is visible in the showcase.
A badge can be prepared in advance and stay invisible until launch
Condition builder with a preview
Fifteen condition types, from approved ideas and completed courses to tenure and profile completeness. Before the rule is saved, the builder shows which employees already match it.
HR sees the rule's result on real company data instead of guessing
Collusion limits inside the condition
A recognition-based condition can require a number of different senders, from a number of different departments, with a cap on repeats from one person per period, and excluding the employee themselves.
Ten thank-yous from one colleague do not satisfy the condition
Achievement chains with tiers
Instead of a single badge, a ladder: five recognitions, twenty, fifty. Tier names are chosen from a ready-made set — neutral, career or sport.
An employee sees the current tier and how far the next one is
Manual and bulk award
For what an algorithm cannot catch there is a direct award, to one employee or to a list at once.
Rewarding a project team after a release is a single action
Threshold impact shown before saving
Before a tier threshold is changed, HR sees the reach: how many people receive the achievement immediately, and who drops below the tier.
The reach is shown first and the threshold is saved second
Employee showcase in plain language
A separate page for the employee: what can be earned in this company and for what exactly. Conditions are written in plain text rather than as an expression from the settings.
Secret achievements stay hidden until they are earned
Five rarity levels on the card
Common, uncommon, rare, epic and legendary, shown by label and colour on the card itself. Rarity explains what an achievement is worth without reference to points.
A legendary badge still means something where a points total does not
Catalogue health panel
HR sees which achievements are actually being awarded, which nobody has earned, and how reach has moved over the last thirty days.
A dead badge becomes visible instead of staying decoration
Chain leaderboard
A chain has its own table of who has progressed furthest along that ladder. It is the only leaderboard in the portal's gamification; there is no overall employee ranking by points.
Competition inside one chain, with no company-wide ranking
Achievements in the profile, the app and the assistant
Your own profile carries earned badges and progress on open ones; a colleague's profile carries the public showcase. The mobile app has its own achievements section, and the AI assistant returns them as cards in chat.
Web, mobile and assistant — the assistant reads only, it cannot award
Data isolation per company
Achievements, awards, chains and collections live in a separate database schema for each company. Only the platform's preset catalogue is shared, and it holds no customer data.
Company achievements are isolated at the database schema level
Frequently asked questions
Related TeamEvo capabilities
Turn on a ready-made achievement set
Achievements work in the portal by default. The preset chain catalogue is enabled in one action and the thresholds are adjusted for your company.
