Assignment Threshold Tracking

Description

Assignment Threshold Tracking monitors the cumulative number of encrypted assignments completed by each peer mentor within a regional coordinator (RK) scope. Blindeforbundet's honorarium model triggers an office honorarium payment when a peer mentor reaches their third confirmed assignment and a higher payment rate at the fifteenth. The system surfaces current counts and threshold events to administrators, enabling accurate and timely compensation without manual tallying. The counter is tied to the confirmed state of each assignment, not mere dispatch, ensuring payment reflects genuine completed service.

Sources & reasoning

Line 96 explicitly defines the two honorarium thresholds (3rd and 15th assignment) per RK, which requires a tracked counter tied to assignment completion. Line 153 places the parent area in Fase 2 (v1.0). This sub-feature must ship alongside encrypted-assignment-dispatch because the threshold cannot be tracked without confirmed assignments.

docs/source/likeperson.md · line 96

Telling av oppdrag per RK: Kontorhonorar utløses ved 3. oppdrag, høyere sats ved 15.
docs/source/likeperson.md · line 153

Kryptert oppdragshåndtering | - | - | ✓ | - | ✓ | MUST (Blindeforbundet) | 2

Analysis

Business Value

Blindeforbundet's peer mentor compensation model is volume-based: honorarium rates increase at defined assignment milestones. Without automated tracking, coordinators must manually count assignments per peer mentor-a process that is error-prone, time-consuming, and a source of payment disputes. Automating threshold detection removes that overhead entirely, ensures peer mentors are paid correctly and on time, and builds trust in the platform. Reliable honorarium payments are a direct retention lever: peer mentors who experience payment delays or errors are less likely to continue volunteering. Correct threshold data also feeds into grant reporting, where assignment volume evidence may be required for Bufdir reimbursement submissions.

Implementation Notes

A per-(peer mentor, RK) assignment counter is maintained in the database and incremented atomically when an assignment transitions to a confirmed or completed state. The increment operation must be idempotent so that sync retries do not double-count. When the counter crosses the 3rd and 15th thresholds, the backend emits an event that triggers an admin portal alert and optionally a push notification to the coordinator. The admin portal displays the current count and threshold status for each peer mentor in the coordinator's scope. If assignment counts contribute to Bufdir reporting, the tracker must expose an aggregate query compatible with the Bufdir export pipeline. Counter state must survive offline periods and reconcile correctly on next sync.