KIV: wishlist — data insights, absence log export, teacher self-service

[guangshinhaha]

KIV — Wishlist / Opportunities

Long-term feature ideas from user research. Need prioritization and design work.

Items

1. Data insights / trend analysis — dashboard for school leaders showing aggregate stats: busiest days, coverage rates, workload distribution, term-over-term trends. Draw the line clearly: aggregate operational stats (OK) vs individual teacher absence patterns (surveillance, adoption killer). "Mondays have 30% more absences" = OK. "Teacher X absent 8 times this month" = No
2. Downloadable absence log — CSV/Excel export: teacher name, reason, days, dates, submission timestamp. Schools need this for MOE reporting and accountability. Low effort, high value — consider promoting out of KIV
3. Flag problematic classes — "3A has had 12 different relief teachers this term" is useful operational info. Flagging individual teachers is surveillance. If built, class-level only
4. Teacher daily timetable view with relief slots — relief teacher sees their day: "P1 Normal, P2 Normal, P3 Relief (3A English)". Single point of reference instead of timetable + WhatsApp. Pipeline D12
5. Relief assignment acknowledgement — teacher taps "Acknowledged" so KP knows they have seen it. Partially built (ackToken on ReliefAssignment). Wire up the flow
6. Edit/track submitted absences — absent teacher can view and modify their submission (extend dates, update instructions). Pipeline D27
7. Data sync with school cockpit — auto-import class lists and teacher assignments from MOE School Cockpit. Deferred until a school can provide API docs and test access. Don't design speculatively

Why KIV

Mix of quick wins (#2, #5) and large efforts (#1, #7). Need to prioritize against core workflow improvements.

🤖 Generated with Claude Code