Achievement Badges & Status Recognition

Continuous recognition mechanisms have a proven positive effect on volunteer motivation and organizational loyalty. Unlike the annual summary which delivers a single moment of recognition, badge systems provide frequent, incremental rewards that sustain engagement throughout the year. For coordinators, the ability to grant nominations like Coordinator of the Year introduces a social recognition layer that strengthens team cohesion and healthy competition. Organizations such as NHF and HLF explicitly requested gamification mechanics as a response to volunteer attrition concerns. The badge system also creates data artifacts that organizations can use in internal reporting to demonstrate volunteer engagement depth to funders such as Bufdir.

Badge definitions are stored in the PostgreSQL database as configuration records, each specifying the trigger condition, display asset, and eligibility criteria. A server-side evaluation job runs nightly to check conditions and award new badges, storing results in the user_badges join table. Flutter renders badge grids using cached asset URLs; badge assets are SVG or PNG stored in object storage. Coordinator-granted badges (e.g., Coordinator of the Year) require a nomination UI in the admin panel. Half-year summary badges are computed automatically at June 30 and December 31. All badge imagery must meet WCAG contrast requirements and include descriptive alt text for screen reader compatibility.