Assignment Threshold Tracking
Feature Detail
Description
Tracks the cumulative number of assignments completed per peer mentor within a reporting period and triggers honorarium tier changes at defined volume thresholds. Coordinators can view each peer mentor's current assignment count and active tier. The system automatically applies the correct honorarium rate - a base rate activating at the 3rd assignment and a higher rate from the 15th - supporting accurate reimbursement calculation and financial administration for Blindeforbundet's honorarium model.
Sources & reasoning
Line 96 explicitly describes Blindeforbundet's honorarium threshold model where the 3rd and 15th assignments each trigger a rate change. This is a unique financial compliance requirement within the encrypted assignments area. Phase 2 context from the priority matrix (line 153, column value 2) maps to target_release v1.0.
-
docs/source/likeperson.md · line 96- **Telling av oppdrag per RK:** Kontorhonorar utløses ved 3. oppdrag, høyere sats ved 15.
Analysis
Blindeforbundet's honorarium model is directly tied to assignment volume: a desk-fee (kontorhonorar) triggers at the 3rd assignment and escalates at the 15th. Without automated tracking, coordinators must manually count assignments per peer mentor and apply the correct rate - a time-consuming and error-prone process that risks financial discrepancies. Automated threshold tracking eliminates manual counting, ensures accurate honorarium application, and provides an auditable record of assignment counts per peer mentor. This is a financial compliance requirement for Blindeforbundet and a prerequisite for scaling the peer mentor network without proportional administrative overhead as assignment volumes grow.
The threshold tracker is a server-side aggregate over the assignments table, scoped per peer mentor per reporting period. The backend exposes a read endpoint returning the current count and active honorarium tier for each peer mentor, consumed by the coordinator's overview screen. Threshold transitions should emit domain events (threshold_reached) that trigger coordinator notifications and optionally update honorarium records in connected accounting integrations. The Flutter UI renders a counter widget in the assignment inbox view. Threshold values (3, 15) should be stored as per-organization configuration to support future tenants with different honorarium structures.
Quality Assurance
No QA section has been generated for this feature yet.
Components (20)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.