Assignment Threshold Tracking
Feature Detail
Description
The platform counts completed encrypted assignments per peer mentor per accounting period. Crossing defined thresholds triggers different honorarium rates: a base office fee activates at the third completed assignment and a higher rate applies from the fifteenth onward. The counting logic is configurable per organization and per period so tenants can set their own threshold tiers. Peer mentors see their current count and the next threshold on the assignment inbox screen, making the compensation structure transparent and motivating continued engagement.
Sources & reasoning
Section 3.1 lists this as an explicit Blindeforbundet requirement with concrete threshold values (3 and 15 assignments), directly tied to the honorarium model. It is grouped under the encrypted assignment workflow in the source, placing it in the encrypted-assignments area. The full kryptert oppdragshåndtering set is in the Fase 2 roadmap in §5, confirming v1.0 as target release.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Blindeforbundet compensates peer mentors based on assignment volume, but the current manual tally is error-prone and requires significant coordinator time each period. Automating threshold tracking eliminates calculation errors, reduces payroll processing overhead, and ensures peer mentors receive correct honorarium without manual intervention. Transparent count display gives peer mentors real-time visibility into their earning potential, directly incentivizing continued activity. This reduces coordinator time spent answering honorarium enquiries and provides accurate, auditable counts for grant reporting and compliance - two areas where manual processes frequently introduce discrepancies that affect organizational credibility.
A counter is maintained in the assignment_deliveries table, incremented server-side when a peer mentor marks an assignment as contacted or completed. Threshold configuration (e.g. 3 → base rate, 15 → higher rate) is stored in organization_settings as a JSON config block, allowing per-tenant customization without code changes. The mobile app reads the current count and active thresholds from the session bootstrap response and renders a progress indicator on the assignment inbox. All count reads are server-authoritative; the client display is derived from the API response to prevent client-side manipulation. The admin portal reimbursement overview shows which peer mentors have crossed each threshold for payroll processing.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.