Assignment Threshold Tracking
Feature Detail
Description
This feature tracks the cumulative number of completed assignments per peer mentor within a reporting period and automatically calculates honorarium tiers based on configurable thresholds. For example, a peer mentor may qualify for a base office honorarium upon completing their third assignment, and a higher-rate honorarium upon reaching their fifteenth. The system surfaces threshold progress to both the peer mentor (motivational dashboard widget) and the coordinator (team overview), and triggers notifications when a threshold is crossed.
User Flow
Analysis
Accurate threshold tracking is a financial and compliance requirement for organizations that use assignment counts to trigger honorarium payments — a model explicitly used by Blindeforbundet. Without automated tracking, coordinators manually count assignments in spreadsheets, introducing errors that lead to either underpayment (demotivating peer mentors) or overpayment (a financial control risk). Surfacing progress toward the next threshold also serves as a lightweight gamification signal that motivates continued engagement, directly supporting volunteer retention — a top concern across all participating organizations. The feature also provides auditable records for accounting and Bufdir reporting.
Threshold configurations are stored per organization in the assignment_threshold_configs table, allowing each organization to define their own tier boundaries and honorarium rates without code changes. The tracking service listens for assignment status-change events (assignment marked as completed) and increments a counter in the assignments table, then evaluates all configured thresholds. Threshold crossing events are persisted and trigger push notifications via the existing Push Notification Service. The dashboard widget reads pre-aggregated counts from the Stats Store to avoid expensive live queries on every screen load. Honor thresholds should be versioned so historical reporting reflects the rules in force at the time of each assignment.
Components (115)
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.