Achievement Badges
Feature Detail
Description
Achievement Badges awards digital badges to peer mentors for reaching meaningful milestones in their volunteering journey — such as completing their first activity, logging 50 hours, mentoring 10 contacts, or earning their digital certificate. Badges are displayed on the peer mentor's profile and in the app's dedicated badges screen, providing persistent visual proof of their contributions. The system supports both automatic award triggers and coordinator-granted badges for special recognition. This feature was explicitly requested by NHF and HLF as a way to surface and celebrate volunteer effort.
User Flow
Analysis
Badge systems tap into well-established behavioral psychology around progress, recognition, and social proof. For peer mentors — who are unpaid volunteers — non-monetary recognition mechanisms are especially powerful motivators. Organizations participating in the Meander platform report difficulty keeping volunteers engaged long-term; a structured achievement system creates ongoing incentive loops tied to real activities rather than artificial game mechanics. Badges also serve a secondary function as trust signals: a coordinator reviewing a peer mentor's profile can quickly assess their experience level and reliability, improving assignment matching and reducing coordinator overhead.
Badge definitions should be stored in a configuration table (achievement_types) with trigger conditions expressed as SQL-evaluable thresholds or event types. A background job evaluates badge eligibility after each activity save, expense submission, or certificate issuance. The Flutter UI renders badge grids using cached SVG assets served from the backend CDN, with locked/unlocked states visually differentiated. Push notifications should be dispatched on badge award via the existing notification pipeline. The admin portal should allow org admins to define custom badges per organization (e.g., 'NHF Ambassador'), stored against the organization_id for proper tenant isolation. All badge assets must meet contrast requirements for WCAG 2.2 AA.
Components (114)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.