What is real, what is scripted
This is an evaluation build: it runs entirely in your browser, with no server and no network. Everything you can click works; some of it stands in for what a server would do. Here is the line between the two.
Works in this build
- One set of records for every role. A register taken on the tablet, a receipt cut at the counter or an exam sat in class shows in the hub and the owner console.
- Offline and sync. The network switch in the bar takes every tablet offline. Entries queue on the tablet and drain, exactly once, when it comes back.
- Owner commands. Lock, unlock and wipe wait for the tablet's next check-in, every six seconds here, and the console shows each step.
- School crests. Drawn from the school code by the same rules every time, here and in the owner's school wizard.
- Role permissions. A teacher in the hub is turned away from fees with the reason; a paused school cannot sign in.
- CSV import. The sample file has three bad rows that you can fix in place before importing.
Scripted
- Sign-in. Any password works. Production uses hashed passwords, OTP for staff, and a per-tablet key.
- Check-in timing. Six seconds here; in production every few minutes and at each sync.
- PDF and Excel exports, printing and SMS. Each control says what it would produce; no file is generated.
- Five years of history. The earlier sessions are summary figures, not full records.
- The tablet. Shown in a frame on a laptop. The real app is an Android APK installed by hand, as the scope describes.
- Data. Five schools, twelve tablets and the VII-B class at Sharada Vidya Mandir are sample records. Every name is invented.
What we need from you
- The name. Daftar is our working name. Alternatives we would test: Pulli (the dot a kolam is drawn around), Shaala, Haajri.
- Receipt printing. A Bluetooth thermal printer at the counter, or an A5 PDF? The receipt layout changes with it.
- Boards and grading. Which boards your first schools follow, so reports carry the right grade scales.
- Lease length. Seven days for every school, or set per plan?
- Pricing. The plans in the rental ledger (₹3,500, ₹6,500 and ₹11,000 a month) are placeholders for yours.
- Two or three pilot schools. With their class lists we can load real structures before the first meeting.
Beyond the scope of work
Ten things the scope did not ask for, which we think the owner and the schools will want. Each is marked as ours in the requirement list.
| Ref | Addition | |
|---|---|---|
| R33 | Rental ledger for the owner: plan, tablet seats, renewal and rent due per school | Open |
| R34 | Day close for each fee counter, reconciled against its receipt series | Open |
| R35 | 75% watch for learners heading below board attendance eligibility | Open |
| R36 | A crest and colour for every school, generated when it is created | Open |
| R37 | Exam integrity timeline and item analysis | Open |
| R38 | Fleet attention queue: lease ending, old app, silent tablets | Open |
| R39 | The teacher's day, with the lesson log asking for itself after each period | Open |
| R40 | APAAR ID status on every student record | Open |
| R41 | RTE 12(1)(c) seats and the reimbursement still owed | Open |
| R42 | DPDP panel for the owner: lock and wipe log, retention, backups | Open |