MEDIUM story-bufdir-report-history-audit-log-organization-admin-005 8 pts
8
Story Points
Medium
Priority
Bufdir Report History & Audit Log
Feature

User Story

As a Organization Administrator
I want to see a side-by-side comparison of the current period's Bufdir data against the most recently submitted report for the same or adjacent period
So that I can spot unusual changes in activity volumes or participant counts before submitting, reducing the risk of submitting erroneous data to Bufdir

Acceptance Criteria

  • Given the coordinator opens the period diff view, when it loads, then the current period's metrics are shown alongside the previous period's submitted metrics in a two-column layout
  • Given a metric has changed by more than 20% compared to the prior period, when the diff view is displayed, then that metric row is highlighted with an amber warning indicator and the percentage change is shown
  • Given the coordinator is viewing the diff, when they tap on a highlighted metric, then a contextual explanation is shown suggesting possible causes (e.g., 'Participant count dropped 35% — check if all activity registrations for the period have been saved')
  • Given there is no previous submission to compare against, when the coordinator opens the diff view, then a clear message explains this is the first report for this organization and no comparison is available
  • Given the diff view is shown, when the coordinator decides to proceed despite warnings, then they can dismiss warnings individually and the dismissal is recorded in the audit log

Business Value

A significant source of Bufdir reporting errors is undetected anomalies — for example, a coordinator submitting a period where half the activities were accidentally not registered. Period comparison catches these issues before submission, protecting organizations from having to submit corrective reports and from potential questions about data reliability from Bufdir.