Driving School Platform – Business Requirements Document
Version 1.0 (Draft for client review) ·
1. About this document
This BRD defines what the pan-India Driving School Platform must do so the client can sign it off and development can start. It merges three inputs: the client brief received on 22 Nov 2026, the existing "CRM Features and Workflow" page, and the "RDS CRM – Features by Module" PDF. Where the inputs disagree, this BRD states the decision and flags it for client confirmation.
| Item | Value |
|---|---|
| Product | Multi-tenant driving school platform (web console + Student app + Trainer app) |
| Version | 1.0 – draft for client review |
| Audience | Client, product owner, solution architect, dev and QA leads |
| Sign-off needed from | Client sponsor, platform owner, delivery lead |
How to read the requirement tables
ID – unique reference used in design, test cases and change requests (e.g. ATT-03).
Priority – M = Must have for launch, S = Should have, C = Could have (nice to have).
Phase – P1 = first release (MVP), P2 = second release, P3 = later.
New – marks requirements that were in neither existing document (from the client brief or suggested in this BRD).
Items the client must answer before design freeze are collected in section 13.
2. Review of the existing documents
The two documents describe a solid back-office CRM, but they do not yet cover the client brief. The biggest gaps are native mobile apps, the OTP design, route capture, trainer-to-student feedback, speech-to-text, multi-school ownership and the reporting depth the client asked for.
What each document covers
| Area | Features & Workflow page (HTML) | Features by Module (PDF) | Client brief |
|---|---|---|---|
| Enquiries, admission, student records | Yes | Yes (customer codes, RTO PDF auto-fill) | Implied |
| LLR / DL / badge / renewal tracking | Yes, with pipeline board | Yes, plus failed-LLR alerts | Implied ("came for licence") |
| Billing, invoices, expenses, cash book | Yes | Yes (no cash book) | Profit reporting |
| LMS (video, quiz, sequential unlock, certificates) | Yes | Yes, with secure video streaming | Yes |
| Scheduling, trainers, vehicles | Yes | No | Yes (fleet) |
| Attendance | Email code, phone biometric, fingerprint machine, manual | No | OTP, trainer-side OTP, supervisor fallback |
| Live vehicle tracking | During drive only | No | Yes, in-house, no third party |
| Start/end km | Yes | No | Yes |
| Route from-to history | No | No | Yes |
| Feedback | Student rates trainer only | No | Both directions, voice or typed, plus questionnaire |
| Reports | Revenue, admissions, expense, utilisation, pass rate; Excel | Business performance; Excel | Many more metrics, period filters, PDF + Excel |
| Multi-school owner, one login | Branches + Enterprise overview | No | Yes |
| Mobile apps | Installable web app (PWA) only | No | Native apps for student and trainer |
Gaps and conflicts found, with the BRD decision
| # | Finding | Why it matters | BRD decision |
|---|---|---|---|
| G1 | Attendance OTP is a random 6-digit email code | Brief asks for a date-time based code the user cannot work out; many students do not check email | Replace with time-based OTP (TOTP) generated in-app; SMS/WhatsApp only as fallback (section 7) |
| G2 | No path for "student has no phone" | Brief requires trainer-requested OTP, then supervisor fallback | Three-tier attendance flow (section 7) |
| G3 | Manual attendance limited to Admin | Brief names Super Admin or Supervisor | Add a Supervisor role (section 4) |
| G4 | Only a live map; no stored route | Brief needs "from where to where" history | Store GPS breadcrumb, start/end address, distance and replay (section 8) |
| G5 | PWA only | Background GPS and reliable OTP need native apps; a PWA cannot track while the screen is off | Native Android + iOS Student and Trainer apps (section 5) |
| G6 | Feedback is one-way and rating-only | Brief needs trainer↔student, voice or text, questionnaire | Feedback module (section 9) |
| G7 | Date of birth not captured as a required field | Needed for "customers by age" and minor-consent rules | DOB mandatory at admission |
| G8 | Reports export to Excel only; fixed periods | Brief wants weekly/monthly/yearly/custom and PDF | Common report engine (section 10) |
| G9 | Hierarchy is Platform → School → Branch | Brief: one owner may own several schools and must see all in one login | Platform → Organisation → School → Branch (section 4) |
| G10 | Six languages, all South Indian plus Hindi | Brief is pan-India | Launch with English, Tamil, Telugu, Malayalam, Kannada and Hindi; language-pack framework so more languages can be added later without code changes (section 6.14) |
| G11 | Role names differ (PDF: Super Admin/Admin/Staff; HTML: Owner/Admin/Staff/Trainer) | Confuses permissions design | One role model (section 4) |
| G12 | PDF allows "delete customers" | Financial and licence records must be kept | Soft delete / archive only; hard delete via retention policy |
| G13 | GST shown as one inclusive figure | Inter-state schools need IGST, intra-state CGST+SGST | Tax split by place of supply |
| G14 | No consent capture for location, biometrics or minors | DPDP Act 2023 and DPDP Rules 2025 apply | Consent and privacy requirements (section 12) |
| G15 | Fingerprint machine and phone biometric untested | Risk to launch | Keep as P2 options, not P1 dependencies |
Everything else in both documents is carried into section 6 unchanged unless noted.
3. Business overview and scope
The platform lets a software owner sell a subscription to driving schools anywhere in India, and lets each school run admissions, licence paperwork, training, fleet, attendance, money and learning in one system. School owners and staff use a web console; students and trainers use mobile apps.
Business objectives
Onboard driving schools across India quickly, each in its own private workspace.
Give owners of several schools one login and one dashboard across all of them.
Prove every lesson happened: verified attendance, start/end km and the route driven.
Stop vehicle misuse by comparing recorded km, GPS distance and scheduled lessons.
Give owners decision reports: who comes for training vs licence, age profile, profit by month, busiest periods.
Deliver theory learning (LMS) and assessments inside the same system.
Support the 29-hour LMV course structure (8 h theory, 21 h practical, within 4 weeks) used by accredited driver training centres, so schools that are or want to be accredited can show compliance.
In scope
Platform console (software owner), web console (organisation, school, branch staff), Student app, Trainer app.
All modules in section 6, the attendance design in section 7, fleet and tracking in section 8, feedback in section 9, reports in section 10.
Subscription billing of schools by the platform owner.
Out of scope for this release (unless the client adds them)
Direct submission to Sarathi/Parivahan government portals (staff still apply on the portal; the platform tracks status).
Hardware GPS devices in vehicles (designed for, see FLT-12, but not delivered in P1).
Driving simulators and in-car cameras.
Payroll for trainers (only trainer hours and payout reports are in scope).
4. User roles and hierarchy
The data hierarchy is Platform → Organisation → School → Branch. An Organisation is one business owner; it can hold one or many schools (each with its own name, GSTIN and RTO registration), and each school can have one or many branches. The owner is the Super Admin of the organisation and signs in once to see every school.
| Role | Belongs to | Signs in on | What they do |
|---|---|---|---|
| Platform Admin | Platform | Platform console (separate login) | Onboard organisations and schools, plans, pricing, platform invoices, suspend/reactivate. Never sees student data. |
| Super Admin (Owner) | Organisation | Web console | Sees all schools and branches in one dashboard; adds schools' staff; settings, branding, billing, all reports. |
| School Admin | One school | Web console | Runs one school across its branches; cannot change organisation-wide settings or billing. |
| Supervisor (New) | One or more branches | Web console + Trainer app (optional) | Approves late/manual attendance, resolves trainer issues, closes the branch cash day, monitors live fleet. |
| Front desk / Staff | One branch (pinnable) | Web console | Enquiries, admissions, licence work, payments – only modules switched on for them. |
| Accountant (New, ready-made role) | School or organisation | Web console | Payments, invoices, expenses, cash book, financial reports. Read-only elsewhere. |
| Trainer | One branch | Trainer app (+ limited web) | Own schedule, students and vehicle; attendance, km, route, skills, feedback. |
| Student | One school | Student app + web portal | Own lessons, attendance OTP, payments, courses, tests, feedback. |
| Parent / Guardian (New, S) | Linked to a student under 18 | Student app (guardian view) | Gives consent, receives OTP fallback and reminders, sees progress and dues. |
Access rules (Must)
ROL-01 One person can hold roles in several schools of the same organisation and switch school/branch from the header without signing in again.
ROL-02 The Super Admin creates staff for a chosen school and branch, picks a ready-made role, then switches individual modules on or off.
ROL-03 Permissions are checked on the server on every request, not only hidden in the screen.
ROL-04 A user pinned to a branch never sees other branches' students, money or vehicles.
ROL-05 Every create/edit/delete/export is written to the audit log with user, time, IP/device and before/after values.
ROL-06 Organisations never see each other's data; each has its own logically isolated workspace.
ROL-07 Staff accounts start with a one-time password that must be changed at first sign-in; optional two-step sign-in (OTP) for Super Admin and Admin.
Who can do what (summary)
| Capability | Super Admin | School Admin | Supervisor | Staff | Accountant | Trainer | Student |
|---|---|---|---|---|---|---|---|
| View all schools in one dashboard | Yes | Own school | Own branches | No | Per assignment | No | No |
| Add staff / set permissions | Yes | Own school | No | No | No | No | No |
| Admit students, licence work | Yes | Yes | Yes | If enabled | No | No | Self-admission form |
| Schedule lessons | Yes | Yes | Yes | If enabled | No | View own | Request slot |
| Mark attendance (OTP) | – | – | – | – | – | Yes | Yes |
| Manual / late attendance | Yes | Yes | Yes (own branches) | No | No | Request only | No |
| Start/end km, route | View | View | View | No | No | Record | View own |
| Live fleet map | Yes | Yes | Own branches | No | No | No | No |
| Payments and invoices | Yes | Yes | Yes | If enabled | Yes | No | Pay / download own |
| Close cash day / edit closed day | Close + edit | Close | Close | No | Close | No | No |
| Reports and export | All | Own school | Own branches | If enabled | Financial | Own stats | Own progress |
| LMS courses and assessments | Yes | Yes | View | If enabled | No | Assign + grade | Take |
| Feedback | View all | View all | View branch | No | No | Give + view own | Give + view own |
5. Channels: web console and mobile apps
There are four front ends on one shared backend: the Platform console, the School web console, the Student app and the Trainer app. Student and Trainer apps must be native (Android first, iOS next) because background GPS, OS-level speech-to-text, biometrics and offline OTP do not work reliably in a browser.
| Channel | Users | Form | Key functions | Phase |
|---|---|---|---|---|
| Platform console | Platform Admin | Responsive web | Organisations, schools, plans, platform billing, health | P1 |
| School web console | Super Admin, Admin, Supervisor, Staff, Accountant | Responsive web (desktop-first, works on tablet/phone) | All back-office modules, reports, live fleet map | P1 |
| Trainer app | Trainer (and Supervisor in supervisor mode) | Native Android + iOS | My day, start/end drive, km, GPS route, attendance OTP entry, skills checklist, feedback (voice/text), student assessments | P1 Android, P1/P2 iOS |
| Student app | Student, Guardian | Native Android + iOS | Attendance OTP, schedule, licence progress, LMS, tests, payments, invoices, feedback, certificates | P1 Android, P1/P2 iOS |
| Student web portal | Student | Responsive web | Same as app except attendance OTP and voice feedback | P1 |
| Public pages | Anyone | Web | Online admission form, certificate verification, school landing page (S) | P1 |
App requirements (Must unless marked)
APP-01 Sign in with mobile number + OTP or password; stay signed in on a trusted device; bind the account to the device for attendance (re-binding needs Supervisor approval).
APP-02 Work offline for the drive: OTP generation/validation, km, GPS points and feedback are stored on the phone and synced when the network returns.
APP-03 Push notifications for lessons, reminders, dues, test dates and results.
APP-04 Language chosen per user; all app text from the same language packs as the web.
APP-05 Background location only while a drive is active, with a visible "Drive in progress" notification; no tracking outside a drive.
APP-06 Minimum supported: Android 9+ and iOS 15+; app size under 40 MB; works on 2 GB RAM phones (S).
APP-07 Forced update when a security fix is released; soft prompt otherwise.
APP-08 Play Store / App Store listings under the platform brand, with each school's logo and colours shown after sign-in (white-label per school = C).
6. Functional requirements by module
Each module lists its requirements with priority, phase and source. Source: H = Features & Workflow page, P = Features by Module PDF, B = client brief, N = new in this BRD. Attendance, fleet, feedback and reports have their own sections (7–10).
6.1 Platform and school onboarding (PLT)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| PLT-01 | Platform Admin creates an Organisation with owner name, mobile, email, PAN/GSTIN, state, plan. | M | P1 | H, B |
| PLT-02 | Platform Admin adds one or more Schools to an Organisation (name, RTO code, licence/accreditation no., address, GSTIN, branches). | M | P1 | B |
| PLT-03 | System builds an isolated workspace with default roles, expense categories, message templates and a Super Admin login sent by SMS/email. | M | P1 | H |
| PLT-04 | Plans: Subscription (single school/branch) and Enterprise (multi-school/branch); per-organisation price override; price per branch option. | M | P1 | H |
| PLT-05 | Lifecycle: Trial (14 days) → Paid → Grace (7 days, banner) → Read-only → Suspended; driven automatically by payment status. | M | P1 | H |
| PLT-06 | Monthly GST invoice to each organisation (CGST+SGST or IGST by state); online payment via gateway or manual entry; webhook-confirmed, idempotent. | M | P1 | H, N |
| PLT-07 | Activity trail of every change to an organisation/school (created, plan changed, invoiced, paid, suspended). | M | P1 | H |
| PLT-08 | Platform dashboard: schools by state, active students, MRR, churn, trials expiring, overdue. | S | P1 | N |
| PLT-09 | Feature flags per plan (e.g. live tracking, LMS, biometrics) so modules can be sold as add-ons. | S | P2 | N |
| PLT-10 | Usage metering per school (SMS sent, storage used, video minutes) for fair-use or add-on billing. | S | P2 | N |
6.2 Organisation and multi-school (ORG)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| ORG-01 | Super Admin signs in once and sees a combined dashboard of all schools and branches, with a filter to drill into one. | M | P1 | B |
| ORG-02 | School/branch switcher in the header; "All schools" view for Super Admin. | M | P1 | H, B |
| ORG-03 | Super Admin adds staff to a specific school and branch, assigning role and module permissions. | M | P1 | B |
| ORG-04 | Side-by-side comparison of schools/branches: admissions, revenue, pass rate, fleet use. | M | P1 | H |
| ORG-05 | Transfer a student, trainer or vehicle between branches of the same organisation, keeping history. | S | P2 | N |
| ORG-06 | Organisation-level settings inherited by schools, overridable per school (fees, templates, attendance rules). | S | P1 | N |
6.3 Enquiries and admissions (ADM)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| ADM-01 | Record enquiry: name, mobile, interest (training/LLR/DL/renewal/badge), vehicle class, source, follow-up date, assigned staff. | M | P1 | H |
| ADM-02 | Enquiry follow-up list with due/overdue status and outcome (converted, lost + reason). | M | P1 | H, N |
| ADM-03 | Convert enquiry to student in one click without retyping. | M | P1 | H |
| ADM-04 | Public online admission form (mobile-friendly) with document upload and consent checkboxes; staff approve before activation. | M | P1 | H |
| ADM-05 | Auto-fill student details from an uploaded RTO PDF, Aadhaar/ID or licence image (OCR); staff review before save. Aadhaar number stored masked. | S | P1 | H, P |
| ADM-06 | Unique student code auto-generated per school (e.g. SCH-2026-00045). | M | P1 | P |
| ADM-07 | Mandatory fields: name, mobile, date of birth, gender, address with state/district/pincode, purpose (training / licence / both), vehicle class. | M | P1 | B, N |
| ADM-08 | Duplicate check on mobile number and ID number across the school. | M | P1 | N |
| ADM-09 | Bulk import from Excel with validation report. | S | P1 | H |
| ADM-10 | Referral source and referrer recorded; referral reward tracking (C). | S | P1 | H, P |
| ADM-11 | Students under 18 must have a linked guardian and recorded guardian consent before data processing beyond admission. | M | P1 | N |
6.4 Student records (STU)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| STU-01 | One profile showing personal details, services bought, licence status, lessons and attendance, km driven, payments/dues, courses, tests, feedback, documents. | M | P1 | H, P |
| STU-02 | Optional photo, compressed on device to about 400 px / under 100 KB. | M | P1 | H |
| STU-03 | Documents (ID, address proof, photos, medical Form 1A where required, LLR copy) with type, expiry and retention rules. | M | P1 | H, N |
| STU-04 | Enable, disable or reset portal/app access per student. | M | P1 | P |
| STU-05 | Archive (soft delete) instead of delete; restore by Admin; hard delete only through retention policy. | M | P1 | N |
| STU-06 | Timeline of all events for the student (enquiry → admission → LLR → lessons → DL). | S | P1 | N |
| STU-07 | Tags and notes (e.g. "nervous driver", "needs female trainer"). | C | P2 | N |
6.5 Licence and services (LIC)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| LIC-01 | Service catalogue per school: LLR, DL, renewal, duplicate, address change, badge, training package, refresher course; each with fee, GST rate and steps. | M | P1 | H, P |
| LIC-02 | LLR: application no., test date, result; failed-LLR alert and retest follow-up. | M | P1 | H, P |
| LIC-03 | DL: application no., slot date, test result, issue date, DL number, dispatch status. | M | P1 | H |
| LIC-04 | LLR validity countdown with reminder before expiry (DL test must happen within validity). | M | P1 | N |
| LIC-05 | Badge, renewal, duplicate and address-change applications with status trail. | M | P1 | H, P |
| LIC-06 | Pipeline board from enquiry → LLR → training → DL, filterable; stuck cases highlighted after N days. | M | P1 | H |
| LIC-07 | Vehicle classes as master data (MCWOG, MCWG, LMV, LMV-TR, HMV etc.) per school. | M | P1 | N |
| LIC-08 | Driving school certificate (Form 5 / Form 5B for accredited centres) generated as PDF once training hours are met. | S | P1 | N |
| LIC-09 | DL renewal reminders to past students (marketing re-engagement). | S | P2 | H |
6.6 Scheduling and training (SCH)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| SCH-01 | Calendar (day/week) by trainer, vehicle and student; book lessons, theory classes and test days. | M | P1 | H |
| SCH-02 | Block double booking of trainer, vehicle or student; respect trainer leave and vehicle service days. | M | P1 | H, N |
| SCH-03 | Training package defines number of sessions/hours, split into theory and practical (default LMV 8 h + 21 h); progress shown against it. | M | P1 | N |
| SCH-04 | Recurring bookings (e.g. Mon–Sat 7:00–7:45 for 4 weeks). | M | P1 | N |
| SCH-05 | Student requests or reschedules a slot from the app within rules (cut-off hours, max reschedules); staff approve. | S | P1 | N |
| SCH-06 | No-show and late-cancel marking with optional penalty fee. | S | P2 | N |
| SCH-07 | Driving skills checklist per vehicle class (clutch control, reversing, parking, hill start, highway, night…) ticked by trainer with level 1–3. | M | P1 | H |
| SCH-08 | Lesson notes per session visible to next trainer. | S | P1 | N |
| SCH-09 | Pickup point per lesson (home/branch) shown in Trainer app with navigation. | C | P2 | N |
6.7 Trainers and vehicles – master data (TRN)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| TRN-01 | Trainer profile: ID, login, mobile, licence no. and expiry, years of experience, vehicle classes allowed, languages spoken, branch, default vehicle. | M | P1 | H, N |
| TRN-02 | Assign students to a trainer (primary/backup); trainer sees only assigned students. | M | P1 | H |
| TRN-03 | Vehicle profile: registration no., type/class, make/model, fuel, dual-control yes/no, default trainer, current odometer. | M | P1 | H |
| TRN-04 | Vehicle documents with expiry alerts: RC, insurance, PUC, fitness, permit, driving school vehicle authorisation. | M | P1 | N |
| TRN-05 | Service schedule by km or date; vehicle blocked from booking while in service. | S | P1 | N |
| TRN-06 | Fuel log (litres, amount, odometer) and km-per-litre report. | S | P2 | N |
| TRN-07 | Trainer leave and availability. | S | P1 | N |
| TRN-08 | Trainer licence/experience expiry alerts (regulators require minimum experience for instructors). | S | P1 | N |
6.8 Billing and finance (FIN)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| FIN-01 | Fee per service with GST rate; discounts with reason and approval above a limit. | M | P1 | H, P |
| FIN-02 | Record payment (cash, UPI, card, bank transfer, cheque) with instalments and auto-numbered receipt PDF. | M | P1 | H, P |
| FIN-03 | Online payment from Student app/portal via payment gateway (UPI first); webhook confirmation, no double posting. | M | P1 | H |
| FIN-04 | GST invoice PDF (school GSTIN, HSN/SAC, place of supply, CGST/SGST/IGST), email/WhatsApp/download. | M | P1 | H, P |
| FIN-05 | Outstanding dues per student and ageing (0–30, 31–60, 60+ days); due reminders. | M | P1 | P |
| FIN-06 | Refunds and credit notes with approval. | M | P1 | N |
| FIN-07 | Expenses by category (fuel, salary, rent, maintenance, RTO fees, marketing…), branch, vehicle; bill upload. | M | P1 | H, P |
| FIN-08 | Government fees collected on behalf of student (pass-through) kept separate from school income in profit reports. | M | P1 | N |
| FIN-09 | Cash book per branch: opening balance, day totals, cash count, close day; closed day locked except Super Admin, with audit. | M | P1 | H |
| FIN-10 | Trainer payout report (sessions/hours × rate) for payroll. | S | P2 | N |
| FIN-11 | Export to Tally/accounting format (C). | C | P2 | N |
6.9 LMS – online learning (LMS)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| LMS-01 | Course builder: modules, video lessons, PDFs, quizzes; drag-and-drop ordering. | M | P1 | H, P |
| LMS-02 | Video upload, converted for secure adaptive streaming; no direct file URL; optional watermark with student name/phone. | M | P1 | P |
| LMS-03 | Sequential unlock: next lesson opens only after the video is watched (≥ 90%) and the checkpoint quiz is passed. | M | P1 | H, P |
| LMS-04 | Enrol single, bulk, or automatically by service bought. | M | P1 | H, P |
| LMS-05 | Quiz builder (MCQ, image questions, true/false), auto-grading, pass mark, retry limit. | M | P1 | H, P |
| LMS-06 | Progress and analytics per student/course; theory hours counted toward the training package. | M | P1 | H, P, N |
| LMS-07 | Certificate PDF on completion with QR code; public verification page. | M | P1 | H, P |
| LMS-08 | Courses in multiple languages; student sees their language version. | S | P1 | N |
| LMS-09 | Ready-made road-signs and LLR mock-test question bank shared by the platform to all schools (Platform content library). | S | P1 | N |
| LMS-10 | Download for offline viewing inside the app (encrypted). | C | P2 | N |
6.10 Assessments and questionnaires (ASM)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| ASM-01 | MCQ assessments scheduled daily, weekly, every N days or on custom dates, with a per-day attempt limit. | M | P1 | H |
| ASM-02 | Question bank with categories, difficulty, language; random draw per attempt. | M | P1 | N |
| ASM-03 | Timed tests; result with explanation; score trend per student. | M | P1 | N |
| ASM-04 | Practical assessment by trainer (rubric per skill) at milestones and before the RTO test ("test readiness" score). | S | P1 | N |
| ASM-05 | Questionnaire builder shared with Feedback (section 9). | M | P1 | B |
6.11 Communication (COM)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| COM-01 | Automatic reminders: lesson, LLR test, DL test, fee due, LLR expiry, document expiry, renewal. | M | P1 | H |
| COM-02 | Channels: push (free, default), SMS (DLT-registered templates), WhatsApp Business, email. Per-school choice and fallback order. | M | P1 | H, N |
| COM-03 | Editable templates per language with placeholders; message log with delivery status. | M | P1 | H, P |
| COM-04 | In-app notification bell (mark one/all read). | M | P1 | H, P |
| COM-05 | Welcome message with app download link and login. | M | P1 | P |
| COM-06 | Broadcast to a filtered group (e.g. all students with LLR expiring this month). | S | P2 | N |
6.12 Settings and administration (SET)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| SET-01 | Branding: name, logo, colour, light/dark. | M | P1 | H |
| SET-02 | Language: school default plus per-user choice. | M | P1 | H, B |
| SET-03 | Feature switches per school with dependencies. | M | P1 | H |
| SET-04 | File retention per upload type (N days or forever), daily cleanup with log. | M | P1 | H |
| SET-05 | Attendance rules per school/branch (section 7). | M | P1 | H, B |
| SET-06 | Tracking rules: GPS interval, overuse thresholds (section 8). | M | P1 | N |
| SET-07 | Working hours, holidays, slot length per branch. | M | P1 | N |
| SET-08 | Password policy, session timeout, lock after 5 failed attempts for 15 min. | M | P1 | H |
6.13 Look and feel – traffic-signal colour code (UI)
The whole product (web console, Student app, Trainer app, PDFs and reports) uses a traffic-signal colour code: green means go / done / good, yellow means wait / attention / due soon, red means stop / problem / overdue. The same meaning applies on every screen, so a user learns it once.
| Colour | Suggested hex (light theme) | Meaning | Used for (examples) |
|---|---|---|---|
| Green | #16A34A | Go, complete, healthy | Primary buttons (Start drive, Save, Pay), Present, Paid, Passed, LLR/DL issued, vehicle documents valid, trial/paid plan active |
| Yellow (amber) | #F59E0B | Caution, pending, due soon | Pending approval, manual attendance under review, fee due in ≤ 7 days, document expiring in ≤ 30 days, grace period, enquiry follow-up today, drive in progress |
| Red | #DC2626 | Stop, failed, overdue | Absent, Failed test, overdue fees, expired documents, overuse/GPS mismatch alerts, read-only/suspended account, delete and cancel actions |
| Neutral (grey/white/dark) | #1F2937 text, #F9FAFB background | Content | Body text, tables, cards, so the three signal colours stay meaningful |
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| UI-01 | Apply the red / yellow / green colour code to all statuses, badges, buttons, alerts, charts and the pipeline board across web and apps. | M | P1 | B |
| UI-02 | Thresholds that turn an item yellow or red (e.g. days before fee due, days before document expiry, km overuse %) are configurable per school. | M | P1 | B, N |
| UI-03 | Colour is never the only signal: every coloured status also carries a text label and an icon (tick, clock, cross), for colour-blind users and printing. | M | P1 | N |
| UI-04 | Yellow backgrounds use dark text; all colour pairs meet WCAG 2.1 AA contrast (4.5:1 for text). | M | P1 | N |
| UI-05 | Dark-theme versions of the three colours are defined in the design system with the same meanings. | S | P1 | N |
| UI-06 | Dashboards open with a red/yellow/green summary strip (e.g. "3 red: overdue fees, 1 expired insurance") linking to the items. | S | P1 | N |
| UI-07 | School branding (logo, accent colour) may change headers and logos, but never overrides the signal colours. | M | P1 | N |
The exact shades are a proposal for the design team to finalise in the design system.
6.14 Multilingual platform (LNG)
The whole platform is multilingual from day one. Launch languages are English, Tamil, Telugu, Malayalam, Kannada and Hindi; English is the base language and the fallback when a translation is missing.
| Language | Script | Web console | Student app | Trainer app | LMS / tests | Speech-to-text |
|---|---|---|---|---|---|---|
| English | Latin | Yes | Yes | Yes | Yes | Yes |
| Tamil | Tamil | Yes | Yes | Yes | Yes | Yes |
| Telugu | Telugu | Yes | Yes | Yes | Yes | Yes |
| Malayalam | Malayalam | Yes | Yes | Yes | Yes | Yes |
| Kannada | Kannada | Yes | Yes | Yes | Yes | Yes |
| Hindi | Devanagari | Yes | Yes | Yes | Yes | Yes |
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| LNG-01 | All screens, menus, buttons, messages, errors and push notifications available in the six launch languages. | M | P1 | B |
| LNG-02 | Super Admin sets the default language per school; every user (staff, trainer, student) can change their own language at any time from the profile or the sign-in screen. | M | P1 | H, B |
| LNG-03 | Student app asks for language on first launch, before sign-in. | M | P1 | N |
| LNG-04 | Reminder and notification templates maintained per language; each student receives messages in their own language. | M | P1 | B |
| LNG-05 | Invoices, receipts and certificates printed in English plus the student's language where the school chooses (bilingual PDF), using fonts that render all six scripts. | S | P1 | N |
| LNG-06 | LMS courses, quizzes, assessments and questionnaires can hold a version per language; the student sees their language, falling back to English. | M | P1 | B |
| LNG-07 | Speech-to-text feedback works in all six languages; typed input supports each language's keyboard. | M | P1 | B |
| LNG-08 | Names and addresses can be stored in English and in the local script. | S | P2 | N |
| LNG-09 | Search works across scripts for student names entered in English (e.g. search "Murugan" finds the record). | S | P1 | N |
| LNG-10 | Dates, numbers and currency use Indian formats (DD-MM-YYYY, lakh/crore grouping, Rs) in every language. | M | P1 | N |
| LNG-11 | All text kept in language files (no text hard-coded), so adding a language later (e.g. Marathi, Bengali, Gujarati) needs only a new language pack. | M | P1 | N |
| LNG-12 | Translation management screen for the Platform Admin to review and edit wording; missing translations listed. | S | P1 | N |
| LNG-13 | Every translation reviewed by a native speaker before go-live; layouts tested with the longest language strings so nothing is cut off. | M | P1 | H |
7. Attendance and OTP design
Attendance uses a three-tier flow: the student's app OTP first, a trainer-requested OTP when the student has no phone, and a Supervisor/Super Admin entry when both fail. Every record shows which tier was used, so owners can see how often fallbacks happen.
Most lessons should end green through Tier 1; Tiers 2 and 3 exist so a forgotten phone or dead network never loses a real lesson, but they stay visible in reports.
How the OTP works (Tier 1 – standard)
The OTP is a time-based one-time password built from the current date and time, not a random number sent by SMS. It is delivered inside the app, the student enters it, and the system validates both the OTP and the student and approves attendance automatically – no staff action is needed:
When the trainer opens the booked lesson, the OTP is shown in the app. It is calculated from the current date-time, the booking reference and a hidden secret key using a one-way cryptographic function (HMAC-SHA256, TOTP method, RFC 6238), and only the last 6 digits are shown.
Because the code depends on the hidden secret, nobody can work it out from the date and time. It changes every 60 seconds, works without internet and is valid only for that lesson within a ±1 minute window.
The student enters the OTP in the Student app.
The system validates the OTP (correct, unused, within the time window) and the student (signed in on their registered device, booked on this lesson with this trainer, inside the check-in window, and – if switched on – within the set distance of the trainer's phone).
If every check passes, attendance is approved automatically and marked Present (green). If any check fails, the student sees the reason and can retry; repeated failures alert the Supervisor.
Tier 2 – student has not brought the phone
Trainer taps "Student has no phone" and requests an OTP; the OTP is delivered in the app (no SMS needed).
The Trainer app opens a locked student check-in screen; the student enters the OTP there together with their personal attendance PIN (or date of birth, school setting) so the system can validate the student.
The system validates the OTP and the student in the same way as Tier 1 and approves automatically.
The record is marked Present – trainer-assisted (yellow): counted, but flagged in reports.
Tier 3 – trainer and student both have issues
No network, dead phones or app failure: the trainer can raise a "missed attendance" request when back online, or the Supervisor/Super Admin creates the record directly.
Allowed only within a configurable window after the lesson (default 48 hours), with a mandatory reason and optional evidence (photo, km readings).
The record is Manual – pending approval (yellow) until a second person (Supervisor or Super Admin) approves; then it is counted, still flagged as manual. A rejected request leaves the lesson Absent (red).
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| ATT-01 | 6-digit time-based OTP delivered in the app (refreshes every 60 s, derived from date-time + hidden secret + booking ID); the student enters it in the Student app; the system validates the OTP and the student and approves attendance automatically. | M | P1 | B |
| ATT-02 | OTP works offline on both phones; validation happens on sync using the device timestamp and server time offset. | M | P1 | B, N |
| ATT-03 | OTP is single-use per lesson; 5 wrong entries lock check-in for that lesson for 15 minutes and alert the Supervisor. | M | P1 | H |
| ATT-04 | Check-in only allowed within a window around the booked slot (default 15 min before to 30 min after). | M | P1 | N |
| ATT-05 | Trainer-requested OTP when the student has no phone, delivered in the app; student enters it with their attendance PIN on the trainer's phone; validated and approved automatically; record flagged "trainer-assisted". | M | P1 | B |
| ATT-06 | Supervisor or Super Admin can add attendance later, with reason, within a configurable window; second-person approval; flagged "manual". | M | P1 | B |
| ATT-07 | Both phones' GPS positions are saved at check-in; if they are more than a set distance apart (default 200 m) the record is flagged. | S | P1 | N |
| ATT-08 | Student account bound to one device; changing phone requires Supervisor approval (stops students sharing codes). | M | P1 | N |
| ATT-09 | Clock-tamper and rooted/jailbroken device detection; flagged, not blocked. | S | P1 | N |
| ATT-10 | Optional extra checks per school: phone fingerprint/face unlock, branch biometric machine, selfie match. | C | P2 | H |
| ATT-11 | Theory class attendance by rotating QR code on the classroom screen scanned by the Student app. | S | P2 | N |
| ATT-12 | Attendance statuses with colour code: Present (green), Trainer-assisted / Manual pending (yellow), Absent / No-show / Rejected (red). | M | P1 | B |
| ATT-13 | Attendance report by student, trainer, branch and tier, with % of lessons using fallbacks per trainer. | M | P1 | N |
| ATT-14 | Staff attendance (trainers clock in/out with app + geofence of branch). | S | P2 | N |
Note: because OTPs are delivered and entered inside the apps, the attendance flow needs no SMS provider and has no per-message cost.
8. Fleet, live tracking and route capture
Every practical lesson is a "drive" that records start and end km, the GPS route from where to where, and the time, all captured by the Trainer app and stored on the platform's own servers. No third-party tracking service or GPS hardware is needed in P1.
Drive lifecycle in the Trainer app
Trainer opens the booked lesson; student checks in with OTP (section 7).
Trainer taps Start drive, enters the odometer reading and (optionally) photographs the odometer. The reading must be ≥ the vehicle's last end reading.
GPS points are recorded in the background while the drive is active and streamed to the server; if the network drops they are stored on the phone and uploaded later.
Trainer taps End drive and enters the end reading. The system calculates odometer km, GPS km, duration and start/end addresses.
Trip summary (km, minutes, route map) appears in both the student's and trainer's apps; the daily log updates automatically.
In-house mapping, no third party
Location comes from the phone's own GPS through the native app; points are stored in the platform database.
Maps are drawn from OpenStreetMap data served by the platform's own tile server, and start/end addresses come from a self-hosted geocoder. This avoids per-call fees and external tracking providers. (Open question Q5: confirm the client accepts OpenStreetMap map style instead of Google Maps.)
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| FLT-01 | Start/end odometer readings per drive; km = end − start; reading validated against the vehicle's last reading. | M | P1 | H, B |
| FLT-02 | Odometer photo at start/end (S); automatic reading of the digits from the photo (C). | S | P1 | N |
| FLT-03 | Record GPS point every 10 s or 20 m while moving (configurable), with speed and accuracy; batched upload; offline buffer. | M | P1 | B |
| FLT-04 | Save start and end location (lat/long + address) and full route polyline per drive. | M | P1 | B |
| FLT-05 | Route replay on a map with play/pause, speed, stops (> 2 min) and timestamps. | M | P1 | B, N |
| FLT-06 | Live fleet map for Super Admin/Admin/Supervisor: vehicles in an active drive, trainer, student, speed, last update. | M | P1 | H, B |
| FLT-07 | Vehicle map markers use the colour code: green = in lesson and moving, yellow = idle > 5 min or signal lost, red = alert (overuse, overspeed, outside area). | M | P1 | B |
| FLT-08 | Tracking only during an active drive; drive auto-ends (with reminder) after configurable idle time; trainer can see when tracking is on. | M | P1 | H, N |
| FLT-09 | Overuse alerts: unrecorded km between drives (next start − previous end), GPS vs odometer difference > X%, km/day above limit, drive without booking, drive outside working hours. | M | P1 | H |
| FLT-10 | Overspeed alert above a configurable limit (default 50 km/h for learner lessons). | S | P1 | N |
| FLT-11 | Training-area geofence per branch; alert when a drive leaves it. | S | P2 | N |
| FLT-12 | Design the tracking API so hardware GPS devices (AIS-140) can feed the same data later. | S | P3 | H |
| FLT-13 | Daily log per day and branch: vehicles used, trainers, students, drives, km (odometer and GPS). | M | P1 | H |
| FLT-14 | Vehicle utilisation: hours booked vs available, km per day, idle vehicles. | M | P1 | H |
| FLT-15 | Battery-aware tracking: lower frequency when stationary; warn trainer at low battery. | S | P1 | N |
| FLT-16 | Route data retention configurable (default 12 months), then summarised and deleted. | M | P1 | N |
| FLT-17 | SOS button in Trainer and Student apps during a drive, sending live location to Supervisor and emergency contact. | S | P2 | N |
9. Feedback: voice, text and questionnaires
Feedback runs both ways after every drive: the trainer gives feedback on the student, and the student gives feedback on the trainer and the lesson. Each side can speak (converted to text), type, and answer a short questionnaire set up by the school.
Speech-to-text approach
P1 uses the phone's built-in speech recognition (Android speech services, iOS Speech framework). It supports English and the major Indian languages, costs nothing per use and needs no third-party contract.
The converted text is shown for editing before submission; the original voice clip is optionally kept (school setting, default off, to save storage and protect privacy).
P2 option: a self-hosted speech model on the platform's servers for languages or phones where on-device recognition is weak.
| ID | Requirement | Pri | Phase | Src |
|---|---|---|---|---|
| FBK-01 | After each drive, Trainer app prompts the trainer for student feedback: skills rating per checklist item, comments by voice or typing. | M | P1 | B |
| FBK-02 | Student app prompts the student to rate the trainer and lesson (1–5 stars) with comments by voice or typing. | M | P1 | H, B |
| FBK-03 | Speech-to-text in the user's chosen language; editable before submit; works with short clips up to 2 minutes. | M | P1 | B |
| FBK-04 | Questionnaire builder: rating, single/multi choice, yes/no, text and voice-answer questions; versioned; per language. | M | P1 | B |
| FBK-05 | Questionnaire triggers: after every lesson, after N lessons, at course end, after RTO test result, on demand. | M | P1 | B, N |
| FBK-06 | Anonymous option for student-to-trainer feedback (school setting). | S | P1 | N |
| FBK-07 | Low ratings (≤ 2 stars) or flagged words create a red alert for the Supervisor with follow-up tracking. | S | P1 | N |
| FBK-08 | Student sees trainer feedback history and skill progress chart in the app. | M | P1 | N |
| FBK-09 | Trainer scorecard: average rating, trend, response rate, comments; comparison across trainers. | M | P1 | H |
| FBK-10 | Net Promoter Score question at course completion; Google review link prompt for promoters (C). | S | P2 | N |
| FBK-11 | Feedback can be given within 24 h of the drive (configurable); reminder if skipped. | S | P1 | N |
10. Reports and analytics
All reports run on one report engine with the same filters, period options and exports, so new reports can be added without new screens. Each report shows the selected period against the previous period and the same period last year.
Common rules for every report (Must)
RPT-01 Period filter: Today, This week, This month, This quarter, This year (calendar), Financial year (Apr–Mar), Weekly / Monthly / Yearly grouping, and Custom date range.
RPT-02 Scope filter: All schools (Super Admin), school, branch; plus trainer, vehicle, service, vehicle class, age band, gender, source.
RPT-03 Export every report to PDF (with school logo, filters used, generated by/at) and Excel (raw rows + summary sheet).
RPT-04 Charts and tables on screen, with the red/yellow/green colour code for targets and thresholds.
RPT-05 Scheduled reports emailed weekly/monthly to chosen users (S).
RPT-06 Every export is logged (who, what, filters, when).
RPT-07 Reports respect permissions: a branch user only sees their branch.
RPT-08 Reports over large ranges run in the background and notify when ready.
Report catalogue
| ID | Report | Answers | Key measures | Pri |
|---|---|---|---|---|
| RPT-10 | Owner dashboard | How is the business today? | Admissions, revenue, collections, dues, active students, lessons today, vehicles on road, red alerts | M |
| RPT-11 | Purpose mix | Who came for training vs licence? | Count and % of training-only, licence-only, both; by service and vehicle class | M |
| RPT-12 | Customers by age | Which age groups do we serve? | Count by band (<18, 18–25, 26–35, 36–45, 46–60, 60+), by gender, by purpose | M |
| RPT-13 | Profit by period | Which month is most profitable? | Revenue (excluding pass-through govt fees), expenses, profit, margin %, best/worst month highlighted | M |
| RPT-14 | Volume and peak periods | Which periods are busiest? | Admissions and lessons by month, weekday and hour slot (heatmap) | M |
| RPT-15 | Revenue and collections | What did we bill and collect? | Billed, collected, by payment mode, by service, by staff | M |
| RPT-16 | Outstanding dues | Who owes us? | Dues by student with ageing buckets | M |
| RPT-17 | Expenses | Where does money go? | By category, branch, vehicle | M |
| RPT-18 | GST summary | What tax do we file? | Taxable value, CGST/SGST/IGST by month, invoice register | M |
| RPT-19 | Enquiry funnel | Are we converting leads? | Enquiries → admissions, conversion %, lost reasons, by source and staff | M |
| RPT-20 | Source and referrals | Where do students come from? | Students and revenue by source/referrer | S |
| RPT-21 | Licence pass rates | How do our students do at RTO? | LLR and DL first-attempt pass %, retests, by trainer and branch | M |
| RPT-22 | Time to licence | How long does it take? | Days admission → LLR → DL; stuck cases | S |
| RPT-23 | Attendance | Are lessons happening? | Attendance %, no-shows, Tier 1/2/3 share per trainer | M |
| RPT-24 | Training completion | Are packages completed? | Hours done vs package, theory vs practical, drop-outs | M |
| RPT-25 | Trainer performance | Who are our best trainers? | Lessons, hours, km, ratings, student pass rate, fallback usage | M |
| RPT-26 | Vehicle usage and km | How are cars used? | Odometer km, GPS km, difference, utilisation %, overuse alerts, fuel efficiency | M |
| RPT-27 | Route history | Where did the car go? | Drives with start/end address, km, route replay link | M |
| RPT-28 | Customers by location | Where do students live? | By district/pincode, map view | S |
| RPT-29 | LMS and assessments | Is theory learning working? | Course completion, quiz/assessment scores, weak topics | M |
| RPT-30 | Feedback | How satisfied are students? | Ratings, NPS, comments by trainer, questionnaire results | M |
| RPT-31 | School comparison | Which school/branch performs best? | Side-by-side of the key measures above | M |
| RPT-32 | Cash book | Does cash tally? | Opening, receipts, payments, closing, differences per day | M |
| RPT-33 | Platform (Platform Admin) | How is the SaaS business? | Schools by state, MRR, trials, churn, overdue, usage | S |
A custom report builder (pick columns, filters, grouping and save) is suggested for P2 (RPT-40, Could).
11. Suggested additional features
These are not in the brief or the existing documents; they are proposed because they raise revenue, cut admin work or reduce risk for schools. The client can accept, defer or drop each one.
| ID | Feature | Benefit to the school | Suggested phase |
|---|---|---|---|
| SUG-01 | Guardian access for students under 18: consent, OTP fallback, progress and dues | Meets parental-consent rules; parents are often the payer | P1 |
| SUG-02 | Test readiness score combining skills checklist, practical assessment and mock-test results before booking the RTO slot | Higher first-attempt pass rate, fewer retest costs | P1 |
| SUG-03 | LLR mock tests and road-sign library shared by the platform to all schools, in every language | Ready content on day one; strong selling point | P1 |
| SUG-04 | Accredited-centre compliance pack: 29-hour LMV / 38-hour HMV hour tracking (theory vs practical), Form 5/5B certificate, trainer qualification records | Supports schools that are or want to become accredited | P1–P2 |
| SUG-05 | Self-booking of lessons by students within open slots | Less phone work for front desk | P2 |
| SUG-06 | Package builder and offers: combos (training + LLR + DL), seasonal discounts, coupon codes | Higher ticket size | P2 |
| SUG-07 | WhatsApp chatbot for enquiries, fee reminders and slot confirmations | Faster lead response | P2 |
| SUG-08 | Lead capture from website and social media forms straight into enquiries | No missed leads | P2 |
| SUG-09 | SOS and safety: emergency button, live location share, incident report with photos | Student and trainer safety; insurance claims | P2 |
| SUG-10 | Vehicle maintenance and fuel management with service reminders and cost per km | Lower running cost; fewer breakdowns | P1–P2 |
| SUG-11 | Trainer payout calculation from verified sessions | Fair pay, no disputes | P2 |
| SUG-12 | Refresher and specialised courses (highway, night driving, women-only batches, senior citizens) | New revenue lines | P2 |
| SUG-13 | Corporate/fleet driver training module with company billing | B2B revenue | P3 |
| SUG-14 | Gamification: badges and streaks for LMS and practice | Better course completion | P3 |
| SUG-15 | Public school profile page with ratings and an enquiry button | Marketing; feeds SUG-08 | P2 |
| SUG-16 | AI driving tips: auto-summarise trainer voice notes into "3 things to practise" for the student | Clearer feedback for students | P3 |
| SUG-17 | Harsh braking / sharp turn detection from phone sensors during drives | Objective driving-quality data per student | P3 |
| SUG-18 | Document expiry tracking for vehicles and trainers with red/yellow alerts | Avoid fines and lapsed insurance | P1 |
| SUG-19 | Data backup export for the school owner (all their data as Excel/ZIP) | Trust; easier sales | P1 |
| SUG-20 | Help centre and in-app support tickets to the platform team | Lower support cost | P2 |
12. Non-functional requirements
The platform must be secure, India-hosted, privacy-compliant and usable on low-end phones and weak networks. Targets below are proposals for the client to confirm.
| ID | Area | Requirement | Pri |
|---|---|---|---|
| NFR-01 | Scale | Support 1,000 schools, 100,000 active students and 5,000 vehicles tracked at the same time without redesign. | M |
| NFR-02 | Performance | Web pages load in < 3 s on 4G; API responses < 500 ms at the 95th percentile; live map updates within 15 s. | M |
| NFR-03 | Availability | 99.5% monthly uptime; planned maintenance outside 6 am–10 pm IST. | M |
| NFR-04 | Offline | Trainer and Student apps keep working for a full drive without network and sync safely afterwards. | M |
| NFR-05 | Data residency | All personal data, location and media stored in Indian data centres. | M |
| NFR-06 | Privacy (DPDP) | Purpose-specific consent at sign-up (incl. location and photo), privacy notice in the user's language, consent withdrawal, data access/correction/erasure requests, grievance contact, breach notification process. | M |
| NFR-07 | Minors | Verifiable guardian consent before processing data of students under 18 (DPDP Rules 2025, Rule 10). | M |
| NFR-08 | Security | HTTPS everywhere; encryption at rest; passwords hashed; Aadhaar masked; secrets in a vault; OWASP Top 10 and mobile (MASVS) checks; annual third-party penetration test. | M |
| NFR-09 | Tenant isolation | Separate logical database/schema per organisation; automated tests that one tenant cannot read another's data. | M |
| NFR-10 | Audit | Immutable audit log retained 3 years (configurable). | M |
| NFR-11 | Backup | Daily backups, 30-day retention; restore tested quarterly; RPO 24 h, RTO 4 h. | M |
| NFR-12 | Languages | Six languages at launch: English, Tamil, Telugu, Malayalam, Kannada and Hindi (details in section 6.14); further languages added later as language packs; translations reviewed by native speakers. | M |
| NFR-13 | Accessibility | WCAG 2.1 AA for web; large tap targets; colour never the only signal (UI-03). | S |
| NFR-14 | Devices | Android 9+, iOS 15+, latest two versions of Chrome, Edge, Safari, Firefox. | M |
| NFR-15 | Battery | A 1-hour drive should use no more than about 10% battery on a mid-range phone. | S |
| NFR-16 | Observability | Central logs, error tracking for web and apps, uptime alerts, per-tenant usage dashboards. | M |
| NFR-17 | Compliance | GST-compliant invoices; e-invoicing readiness when a school crosses the turnover threshold; SMS via DLT-registered templates. | M |
The DPDP Rules, 2025 were notified on 14 November 2025 with an 18-month phased rollout, so full obligations apply by about May 2027 – within this product's first year. Legal review by the client's counsel is recommended.
13. Assumptions, open questions, phasing and sign-off
Twelve questions below need the client's answer before design freeze; the rest of the BRD can move to design now.
Assumptions
Schools apply for LLR/DL on the government portal themselves; the platform tracks status only.
Trainers use their own or school-provided Android/iOS smartphones with GPS and mobile data.
One organisation's schools may have different GSTINs and states; tax is calculated per school.
Payment gateway, SMS (DLT) and WhatsApp Business providers are contracted by the platform owner; schools do not need their own accounts.
Existing features in both documents remain in scope unless the client removes them.
Open questions for the client
Q1. Answered: the OTP is delivered in the app, the student enters it, and the system validates the OTP and the student and approves automatically (section 7).
Q2. Confirm the Tier 2 approach: student enters the OTP plus a personal attendance PIN on the trainer's phone.
Q3. Is a check-out OTP also needed at the end of each lesson, or is check-in + end drive enough?
Q4. Manual attendance window: how many hours after the lesson can a Supervisor still add it (proposed 48 h)?
Q5. Maps: is OpenStreetMap acceptable, or must Google Maps be used (third-party, per-use cost)?
Q6. Is a Supervisor a separate role from School Admin, and can one person supervise several branches?
Q7. Do owners with several schools need separate GSTINs/branding per school, or are they really branches of one school?
Q8. Enterprise pricing: per school, per branch, or per active student? (Subscription is Rs 1,500/month incl. GST in the existing page.)
Q9. Answered: launch languages are English, Tamil, Telugu, Malayalam, Kannada and Hindi. Still open: who reviews each translation?
Q10. iOS at launch, or Android first and iOS in P2?
Q11. Should voice clips be stored with the transcribed text, and for how long?
Q12. Which of the suggested features in section 11 should enter P1?
Proposed phasing
| Phase | Scope | Exit criteria |
|---|---|---|
| P1 – MVP | Platform onboarding, multi-school dashboard, roles, admissions, licence tracking, scheduling, finance, LMS, assessments, Tier 1–3 attendance, drives with km + GPS route + live map, two-way feedback with speech-to-text, core reports with PDF/Excel, Android apps (iOS if Q10 = yes), traffic-signal UI | 2 pilot schools run for 4 weeks with all lessons recorded in the apps |
| P2 – Growth | iOS apps (if not P1), biometrics options, geofence, SOS, self-booking, packages and offers, WhatsApp bot, payouts, broadcast, more languages, custom report builder | 20 schools live; < 5% of lessons on Tier 3 attendance |
| P3 – Scale | Hardware GPS, corporate training, driving-quality sensors, AI tips, gamification | Agreed after P2 review |
Sign-off
| Name | Role | Decision | Date |
|---|---|---|---|
| Client sponsor | |||
| Platform owner | |||
| Delivery lead |