Activity Flagging

Description

The Activity Flagging feature allows administrators and coordinators to mark individual activity submissions with concern flags without immediately rejecting them, preserving workflow continuity while surfacing items requiring further scrutiny. Flags carry a type such as suspected error, policy question, or missing documentation, plus an optional note. Flagged activities appear in a dedicated filtered view and remain actionable until resolved or escalated. Resolution and dismissal of flags are recorded with actor metadata, maintaining a complete audit trail of administrative attention across all activity records.

Sources & reasoning

Line 195 references corrections as part of the admin oversight mandate, and line 109 establishes NHF's structural complexity as a scaling challenge that binary approval alone cannot address. Blueprint marks this [v1.0] - an enhancement to the MVP approval workflow rather than a launch prerequisite. No explicit Fase 2 mention of flagging, but it naturally extends the oversight capability confirmed by the source and is prerequisite for duplicate detection integration.

docs/source/likeperson.md · line 195

Activity oversight, approval workflows, and corrections
docs/source/likeperson.md · line 109

Bredest organisasjonsstruktur: 12 landsforeninger, 9 regioner, 1 400 lokallag - aktivitetsfordeling mellom ledd må støttes.

Analysis

Business Value

Flagging provides a lightweight intermediate state between full approval and outright rejection, which is essential for high-volume organizations such as NHF with 1,400 local associations where a binary approve/reject model creates bottlenecks during peak reporting periods. Coordinators can surface concerns asynchronously without blocking the peer mentor from continuing to register activities. The flagging system enables systematic quality assurance by allowing patterns of concern - such as consistently missing contact references or unusual durations - to be tracked and addressed programmatically rather than lost in a review queue. It also supports collaborative review where a coordinator flags an activity for supervisor assessment, improving governance without requiring synchronous coordination between admin users.

Implementation Notes

ActivityFlagWidget renders inline on activity cards in the Admin Web Portal, allowing coordinators to flag without navigating to a detail view. Flags are stored in the activity_flags table linked to activities by foreign key, with columns for flag_type enum, note text, created_by user_id, created_at timestamp, and resolved_at nullable timestamp. ActivityFlaggingService enforces that only coordinators with access to the activity's organization can create or resolve flags. Flag creation and resolution both emit audit log entries via AuditLogService. DuplicateDetectionService can programmatically create flags via the same service interface, enabling automated triage alongside manual flagging. A filtered admin view shows all open flags with sortable columns and resolution controls.