Achievement Badges

Statusbadges were explicitly named in workshop summaries from NHF, HLF, and Barnekreftforeningen as a desired mechanism to make volunteer effort visible and motivate consistent reporting. Unlike the annual summary which fires once a year, badges provide continuous feedback that reinforces reporting behaviour after each logged activity. For organizations, badge progress serves as a lightweight proxy for volunteer engagement levels, enabling coordinators to identify at-risk volunteers before disengagement occurs. The feature also supports onboarding: introductory badges for early milestones give new peer mentors immediate wins that lower the psychological barrier to consistent platform use.

Badge eligibility is evaluated server-side after each activity save using a rule engine that checks aggregate thresholds, ensuring clients cannot award badges by manipulating local state. The Flutter client fetches the badge collection via a dedicated endpoint and renders it with a grid of BadgeWidget components displaying locked versus unlocked states. New badge unlocks should trigger an in-app toast within the same session so the event feels immediate. Badge definitions - labels, thresholds, and descriptions - must be configurable per organization via the terminology/labels system without code deployment. WCAG 2.2 AA compliance requires all badge images to have descriptive alt text and that locked/unlocked state is communicated via text label in addition to visual treatment, not colour alone.