v2 Gap Analysis — Reporting

Reporting — V2 Review Gap Analysis

Source: BACKEND-RAMBLINGS.md line 369 (one sentence; stakeholder deferred)
Spec: docs/admin-spec/09-reporting.md
Implementation: src/pages/reporting/

Stakeholder Position

Stakeholder has deferred all reporting detail. She names three report categories:

• Financial reports
• Student reports
• Student composition reports

Explicitly states: "These statistics are we looking at and tracking are still to be defined."

Current Spec Coverage

The spec defines five reporting screens:

1. Student Report — student performance metrics (submissions, grades, missed weeks, status)
2. Referrals — referral program performance
3. Specific Reports — custom query generator (edge cases, active students not in semester, etc.)
4. Student Composition — NEW; student body breakdown by level, showing new/returning/retention rates
5. Logs — system activity logs (Admin only)

Current Implementation

All five screens are implemented and functional:

• student-report.tsx — full sortable/filterable table with CSV export
• referrals.tsx — referral tracking with status (Pending/Enrolled/Expired)
• composition.tsx — metric cards (Total, New %, Returning %, Graduating) + detail table by level
• specific-reports.tsx — 8 canned report templates with run/schedule capability
• logs.tsx — system activity viewer (Admin only)

Gap / Recommendation

Category mapping:

• Financial reports — NOT in current spec. No invoices, payments, refunds, revenue tracking, or billing analytics.
• Student reports — PARTIALLY mapped. Student Report covers performance; Specific Reports has academic metrics (submissions, grading); full student-level export exists.
• Student composition — FULLY covered. Student Composition screen addresses new/returning/graduating breakdown by level.

Action required: Current spec treats Reporting as academic/operational analytics only. Stakeholder needs financial reporting functionality that does not yet exist in the spec. Recommend scheduling a working session to:

1. Define the three missing financial report categories (revenue per semester? refund status? payment reconciliation?)
2. Clarify whether "student reports" means additional fields/dimensions beyond current Student Report
3. Confirm any other report types needed that aren't in the current five-screen set
4. Until then, current spec should be the working assumption.

Ambiguities to Raise

• Financial detail: What specific metrics? (Revenue per semester; tuition collected vs. outstanding; refund/payment failure rates; revenue by level?)
• Student reports scope: What distinguishes this from the existing Student Report + Specific Reports? (More detail? Different rollup?)
• Student composition axes: The current spec breaks down by level only. Does she need breakdown by geography, enrollment type (new/returning), gender, age, etc.?
• Report export formats: CSV only, or Excel, PDF, scheduled email distribution?
• Frequency: Does she need real-time or daily/weekly snapshots?