Mock Data Audit

Mock Data Audit — March 2026

This document records the findings and fixes from a comprehensive audit of the QuranFlow Admin mockup's mock data. The audit was motivated by staff walkthrough confusion — contradictory student states made the mockup unreliable for demonstrating workflows.

Audit Scope

Every file in src/data/ was read and cross-referenced. The audit checked:

• Student status vs. subscription vs. enrollment consistency
• Submission counts in students.ts vs. actual records in submissions.ts
• Student group memberCount vs. students actually assigned to each group
• Scholarship discount % vs. payment amounts in billing.ts
• Dashboard alert tile counts vs. the data they claim to summarize
• Deferment status vs. student active/inactive status
• Family group allActive flags vs. member subscription statuses
• Appointment and calendar event cross-references

Student Story Matrix

Each of the 20 mock students must tell a coherent story across all data files. Here is the canonical narrative for each:

Detailed Student Narratives

Exemplary Students (5): Sarah Ahmed (L0) is the model student on a family plan with 5 on-time submissions. Fatima Hassan (L1) shows the installment billing workflow with 6 submissions. Amina Osman (L2) is the top performer on an annual plan. Noor Abdullah (L4) has near-perfect grades across 6 submissions. Sumaya Jaber (Y2) has the highest average grade (4.9) on a full scholarship that's expiring.

Scholarship Students (3): Zainab Patel (L0, 100% scholarship) and Ibrahim Sharif (L2, 100% scholarship) show $0 payments with "Scholarship Full" plan name. Hassan Ali (L1, 50% scholarship) shows a $100 payment with "Semester Standard (50% Scholarship)" plan name. These demonstrate how scholarship discounts appear in the billing screens.

Payment Problems (3 — escalating severity): Ali Rahman (L0, Incomplete) is the mildest case — his payment setup never completed, his partial scholarship coupon couldn't be applied, and he's At Risk with only 2 submissions. Mariam Khan (L1, Past Due) has three failed installment retries in March, is behind on submissions (3/6), cancelled an appointment, and filed a high-priority payment issue. Bilal Hussain (L3, Unpaid) is the worst active case — subscription exhausted all Stripe retries, content is locked, he skipped week 4 entirely, no-showed his appointment, and filed an issue about content access. Together they show the full payment failure cascade an admin would encounter.

Inactive Students (2): Khadijah Noor (L2) returned from a travel deferment but couldn't keep up — 1 submission, grade 2.1, no-show appointment, cancelled and refunded. Now requesting reactivation via the Issue Queue. Layla Mahmoud (L2) has zero submissions and withdrew entirely after originally requesting a deferment.

Deferment (1): Hafsa Rizvi (L4) was active with 5 submissions through week 5, then went on medical leave (March 6). Subscription correctly paused, reporting correctly shows "On Track" (excused), and no action needed until her return date of April 6.

Steady with Minor Issues (4): Omar Syed (L1) plans to cancel at period end — a retention signal. Yusuf Bakr (L2) found a content typo. Aisha Yilmaz (L3) is requesting a TA change. Hamza Qureshi (L4) had a timezone bug that's been resolved.

Year 2 (2): Sumaya (covered above) tracks elective Tajweed Advanced at Practice Tier 2. Tariq Mansoor flagged that his Tafsir Basics elective only has 3 of 6 weeks of content uploaded — a high-priority content gap the admin would escalate.

Issues Found and Fixed

Category 1: Student Status Contradictions

Category 2: Submission Data Gaps

Before: 40 submission records. 14 of 20 students had fewer submissions than their submissionCount field claimed.

After: 94 submission records. Every student's submissionCount now matches the actual records in submissions.ts.

Added 54 records with:

• Correct assessment IDs and titles matching assessments.ts
• Dates following the weekly submission cadence (week 1 = ~Feb 8, week 6 = ~Mar 10)
• Grades calibrated to approximate each student's avgGrade in reporting.ts
• Reviewer matching the student's assigned TA
• Latest submissions marked "Under Review" for on-track students

Category 3: Group Member Counts

Category 4: Scholarship-Billing Mismatch

Three students with 100% scholarships were showing $199 payments:

Category 5: Dashboard Accuracy

• Students Behind tile: Changed from 3 to 2 (Mariam Khan + Bilal Hussain). Ali Rahman is "At Risk" (separate category). Hafsa Rizvi is on deferment (excused). Khadijah Noor is Inactive (not counted).
• Y2 Appointments tile: Changed from "2/10 booked" to "1/2 booked" (only Tariq has an upcoming appointment in the current week).
• Dashboard comments: Rewritten to accurately explain the derivation of each count.

Not Changed (Validated as Correct)

• Bilal Hussain (#14): Active / Enrolled / Unpaid is intentionally a realistic edge case. His issue "Cannot access level 3 content" makes sense — content is locked because subscription is unpaid. Useful for admin workflow demos.
• Family group allActive flags: Khan Family (false) and Noor Family (false) are correct — each has at least one non-Active member.
• Expired coupons: Coupons with past expiry dates are shown as-is. Archiving is a UI concern.
• Ali Rahman (#3) scholarship: stripeCouponApplied: false is correct — his subscription never completed, so the coupon couldn't be applied.

Cross-Reference Rules (for future data changes)

When modifying mock data, these rules must hold:

1. Student status coherence: If subscriptionStatus is Cancelled, student status must be Inactive and enrollmentStatus must be Fail.
2. Submission counts: student.submissionCount must equal submissions.filter(s => s.studentId === student.id).length.
3. Group member counts: group.memberCount must equal students.filter(s => s.groupId === group.id).length.
4. Scholarship payments: Students with 100% scholarships should have $0 payment records with "Scholarship Full" plan name.
5. Deferment consistency: If a student has an Active deferment, their subscription should be Paused. If they've withdrawn (Inactive/Cancelled), deferment should be Completed.
6. Dashboard derivation: Alert tile counts must be derivable from actual data. Document the derivation in comments.
7. TA reviewer match: submission.reviewedBy should match the student's assigned TA name.
8. Family allActive: familyGroup.allActive is false if any member has a non-Active subscription status.
9. Reporting exclusions: Students on approved deferment should not be marked "Behind" in reporting.

Files Modified