medium complexity extracted Activity Oversight Confidence: 100%
4
Components
39
Shared
0
User Stories
Yes
Analyzed

Description

This feature provides coordinators and organization administrators with a dedicated interface to review, verify, and approve activity registrations submitted by peer mentors. The workflow surfaces pending activities in a structured queue, allowing reviewers to inspect details, request corrections, or approve submissions before they count toward reporting and statistics. The system supports both individual approvals and batch processing to accommodate coordinators managing large volumes of registrations across multiple peer mentors.

Analysis

Business Value

Activity approval is the quality gate that ensures Bufdir reporting is accurate and defensible. Without a structured review step, organizations risk submitting inflated or erroneous data to the government funding agency, which could jeopardize continued grants. For coordinators, a centralized approval queue replaces ad-hoc follow-up over email or phone, reducing administrative overhead significantly. From a compliance standpoint, the approval audit trail provides evidence that each submission was reviewed by a responsible party, satisfying the documentation requirements several organizations cited during workshops. This feature directly supports the core operational flow described in the product brief and is a prerequisite for one-click Bufdir export.

Implementation Notes

The approval queue is a server-side paginated list filtered by organization and coordinator scope, rendered via server-side rendering in the Next.js admin portal. Status transitions (pending → approved / pending → returned) are managed through a REST endpoint that writes to the activities table and appends an entry to audit_logs. The mobile app must reflect approval state so peer mentors can see when a submission was approved or returned with a correction note. Optimistic UI updates should be avoided on the admin side for approval actions since they affect downstream reporting; all transitions must be confirmed by the server. Role guards enforce that only Coordinators and Org Admins can approve; Global Admins have read-only access to avoid cross-tenant data exposure.

Components (43)

User Interface (2)

Service Layer (2)

Shared Components

These components are reused across multiple features

User Stories

No user stories have been generated for this feature yet.