Activity Flagging

Flagging provides a non-destructive way to quarantine questionable data without losing it, which is critical when coordinators need to investigate before making a final decision. NHF specifically requires duplicate detection across their 1,400 local associations, where the same peer mentor activity could be submitted by different coordinators. Without a flagging mechanism, coordinators must either approve potentially duplicate entries or reject them outright, both of which carry risk. Flagging also supports audit trail requirements, as investigators can annotate records with reasons and track resolution history, demonstrating due diligence to Bufdir auditors.

Flag state is stored as an enum column on the activities table alongside a nullable flag_reason text field and flagged_by foreign key. The admin portal renders flagged activities with a distinct visual indicator in the activity list and detail views. A dedicated flagged activities filter view allows coordinators to triage outstanding flags efficiently. The duplicate detection logic performs a query on activities sharing the same contact_id, activity_type, and date within a configurable time window, surfacing potential duplicates as suggested flags. Resolving a flag transitions the activity back to pending review, routing it through the standard approval flow.