Selected work / ClassCover

Timetables that stay explainable.

An offline-first planning desk for school substitutions and invigilation. It turns messy timetable inputs and live availability into recommendations a coordinator can inspect, edit, and safely apply.

Role

Product & engineering

Surface

Offline-first web app

Core constraintRecommend first. Apply second.

01 / The problem

A timetable is not a plan.

School coordinators work from exports, corrections, absence notes, and exam sheets. A useful system has to preserve the raw input, normalize it enough to reason about, and still make the final decision legible to a person.

02 / Product walkthrough

A coordinator's four-move morning.

Here is the product behavior worth showing: start with the timetable, mark the absence, inspect candidates, and apply one explainable change. The controls below are a synthetic walkthrough of the ClassCover desk.

CLASSCOVER. / SUBSTITUTION DESKLOCAL WORKSPACE

Monday · 14 October

Substitution planner / 08:30 start

TERM 1 / WEEK 08
periodclassteacherstate
P18B · MathsA. Sharmaassigned
P27A · EnglishR. Singhassigned
P39C · PhysicsN. Vermaassigned
P410A · HistoryM. Khanassigned
Imported from timetable.xlsx · 24 rows normalized
periodclassteacherstate
P18B · MathsA. Sharmaassigned
P27A · EnglishA. Sharmaabsent
P39C · PhysicsN. Vermaassigned
P410A · HistoryM. Khanassigned
A. Sharma unavailable · 1 affected slot
P. MehtaFree in P2 · no conflict · 2 covers this week
92 / 100best fit
S. IyerFree in P2 · same class level · 4 covers this week
78 / 100available
J. ThomasFree in P2 · subject overlap · release needed
64 / 100trade-off
Ranked by availability, conflict, and fairness history
periodclassteacherstate
P18B · MathsA. Sharmaassigned
P27A · EnglishP. Mehtacovered
P39C · PhysicsN. Vermaassigned
P410A · HistoryM. Khanassigned
P2 cover applied · release chain checked · rollback available
The plan is ready for the coordinator to communicate
Interactive product walkthrough · synthetic data
System model01 / 04

Keep the source intact.

Excel, CSV, manual edits, photos, and PDFs enter a raw layer before the planning model makes them comparable.

INPUT → RAW DATANO SILENT REWRITES
sourceentrystate
workbookMon · P3 · 8Bcaptured
absence noteTeacher unavailablequeued
exam sheetRoom 204 · P2captured

The original value remains available for review when a normalized field needs correction.

Conceptual sequence · synthetic dataReduced motion supported

03 / What I changed

The product boundary is part of the system design.

  1. 01
    Preserved raw timetable entries alongside normalized planning records.
  2. 02
    Made availability, conflict, fairness, and release-chain context visible before a recommendation is applied.
  3. 03
    Scoped assistant actions to validated proposals, with stale-context checks and rollback-aware application.

What the case study should make visible

Not an “AI built a timetable” claim. The interesting engineering is the seam between imperfect data, a constrained planner, and a coordinator who needs to stay in control.

Public version: synthetic rows and simplified topology only. Do not expose school names, teacher rosters, room assignments, private URLs, database files, credentials, or operational screenshots.

04 / The result

Messy input → reviewable plan

The strongest outcome is a calmer operational loop: import what the school already has, understand the affected slots, inspect a recommendation, and apply only what is ready.

Research brief based on the server project, tests, deployment configuration, and the project questionnaire. Diagrams are simplified explanations, not production topology or benchmark telemetry.

Next case studyInsureFlow AI Back to selected workAll projects