Activity Flagging
Feature Detail
Description
The Activity Flagging feature enables administrators and coordinators in the Admin Web Portal to mark specific activity registrations as requiring attention, adding structured reason codes and free-text comments to flag concerns such as suspected errors, policy violations, missing attachments, or duplicate candidates. Flagged activities enter a dedicated review queue, allowing teams to triage and resolve data quality issues systematically without immediately rejecting or approving the activity pending further investigation.
Sources & reasoning
NHF raised duplicate detection and Bufdir auditability as explicit needs. Flagging is the coordination mechanism bridging detection and resolution - it provides the holding state when an activity cannot be immediately approved or rejected. Blueprint targets v1.0 (Phase 2), consistent with the priority matrix placing quality-control tooling in Fase 2.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Not every suspicious activity warrants immediate rejection - coordinators often need time to consult the peer mentor before deciding. Activity Flagging provides the intermediate state needed to hold activities for investigation without blocking the overall review queue. For organizations like NHF with complex multi-level structures spanning 1 400 local chapters, flagging enables distributed review where regional coordinators flag issues for national admins to resolve. This workflow also supports Bufdir audit readiness by documenting that data quality concerns were identified, tracked, and resolved before any export was generated.
Implemented as an extension to the activity detail page in the Admin Web Portal. The backend adds a flags table (activity_id, flagged_by, reason_code, comment, resolved_at, resolved_by) with a foreign key to activities. REST API exposes POST /api/v1/activities/:id/flags and PATCH /api/v1/activities/:id/flags/:flagId for creation and resolution. The activity list gains a Flagged filter tab alongside Pending/Approved/Rejected. Reason codes are a controlled enum (data_error, duplicate_suspected, missing_attachment, policy_concern, other) enabling structured reporting on flag patterns. Org admins and coordinators are notified when an activity they manage is flagged.
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.