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.

ItemValue
ProductMulti-tenant driving school platform (web console + Student app + Trainer app)
Version1.0 – draft for client review
AudienceClient, product owner, solution architect, dev and QA leads
Sign-off needed fromClient sponsor, platform owner, delivery lead

How to read the requirement tables

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

AreaFeatures & Workflow page (HTML)Features by Module (PDF)Client brief
Enquiries, admission, student recordsYesYes (customer codes, RTO PDF auto-fill)Implied
LLR / DL / badge / renewal trackingYes, with pipeline boardYes, plus failed-LLR alertsImplied ("came for licence")
Billing, invoices, expenses, cash bookYesYes (no cash book)Profit reporting
LMS (video, quiz, sequential unlock, certificates)YesYes, with secure video streamingYes
Scheduling, trainers, vehiclesYesNoYes (fleet)
AttendanceEmail code, phone biometric, fingerprint machine, manualNoOTP, trainer-side OTP, supervisor fallback
Live vehicle trackingDuring drive onlyNoYes, in-house, no third party
Start/end kmYesNoYes
Route from-to historyNoNoYes
FeedbackStudent rates trainer onlyNoBoth directions, voice or typed, plus questionnaire
ReportsRevenue, admissions, expense, utilisation, pass rate; ExcelBusiness performance; ExcelMany more metrics, period filters, PDF + Excel
Multi-school owner, one loginBranches + Enterprise overviewNoYes
Mobile appsInstallable web app (PWA) onlyNoNative apps for student and trainer

Gaps and conflicts found, with the BRD decision

#FindingWhy it mattersBRD decision
G1Attendance OTP is a random 6-digit email codeBrief asks for a date-time based code the user cannot work out; many students do not check emailReplace with time-based OTP (TOTP) generated in-app; SMS/WhatsApp only as fallback (section 7)
G2No path for "student has no phone"Brief requires trainer-requested OTP, then supervisor fallbackThree-tier attendance flow (section 7)
G3Manual attendance limited to AdminBrief names Super Admin or SupervisorAdd a Supervisor role (section 4)
G4Only a live map; no stored routeBrief needs "from where to where" historyStore GPS breadcrumb, start/end address, distance and replay (section 8)
G5PWA onlyBackground GPS and reliable OTP need native apps; a PWA cannot track while the screen is offNative Android + iOS Student and Trainer apps (section 5)
G6Feedback is one-way and rating-onlyBrief needs trainer↔student, voice or text, questionnaireFeedback module (section 9)
G7Date of birth not captured as a required fieldNeeded for "customers by age" and minor-consent rulesDOB mandatory at admission
G8Reports export to Excel only; fixed periodsBrief wants weekly/monthly/yearly/custom and PDFCommon report engine (section 10)
G9Hierarchy is Platform → School → BranchBrief: one owner may own several schools and must see all in one loginPlatform → Organisation → School → Branch (section 4)
G10Six languages, all South Indian plus HindiBrief is pan-IndiaLaunch with English, Tamil, Telugu, Malayalam, Kannada and Hindi; language-pack framework so more languages can be added later without code changes (section 6.14)
G11Role names differ (PDF: Super Admin/Admin/Staff; HTML: Owner/Admin/Staff/Trainer)Confuses permissions designOne role model (section 4)
G12PDF allows "delete customers"Financial and licence records must be keptSoft delete / archive only; hard delete via retention policy
G13GST shown as one inclusive figureInter-state schools need IGST, intra-state CGST+SGSTTax split by place of supply
G14No consent capture for location, biometrics or minorsDPDP Act 2023 and DPDP Rules 2025 applyConsent and privacy requirements (section 12)
G15Fingerprint machine and phone biometric untestedRisk to launchKeep 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

  1. Onboard driving schools across India quickly, each in its own private workspace.

  2. Give owners of several schools one login and one dashboard across all of them.

  3. Prove every lesson happened: verified attendance, start/end km and the route driven.

  4. Stop vehicle misuse by comparing recorded km, GPS distance and scheduled lessons.

  5. Give owners decision reports: who comes for training vs licence, age profile, profit by month, busiest periods.

  6. Deliver theory learning (LMS) and assessments inside the same system.

  7. 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

Out of scope for this release (unless the client adds them)

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.

RoleBelongs toSigns in onWhat they do
Platform AdminPlatformPlatform console (separate login)Onboard organisations and schools, plans, pricing, platform invoices, suspend/reactivate. Never sees student data.
Super Admin (Owner)OrganisationWeb consoleSees all schools and branches in one dashboard; adds schools' staff; settings, branding, billing, all reports.
School AdminOne schoolWeb consoleRuns one school across its branches; cannot change organisation-wide settings or billing.
Supervisor (New)One or more branchesWeb console + Trainer app (optional)Approves late/manual attendance, resolves trainer issues, closes the branch cash day, monitors live fleet.
Front desk / StaffOne branch (pinnable)Web consoleEnquiries, admissions, licence work, payments – only modules switched on for them.
Accountant (New, ready-made role)School or organisationWeb consolePayments, invoices, expenses, cash book, financial reports. Read-only elsewhere.
TrainerOne branchTrainer app (+ limited web)Own schedule, students and vehicle; attendance, km, route, skills, feedback.
StudentOne schoolStudent app + web portalOwn lessons, attendance OTP, payments, courses, tests, feedback.
Parent / Guardian (New, S)Linked to a student under 18Student app (guardian view)Gives consent, receives OTP fallback and reminders, sees progress and dues.

Access rules (Must)

Who can do what (summary)

CapabilitySuper AdminSchool AdminSupervisorStaffAccountantTrainerStudent
View all schools in one dashboardYesOwn schoolOwn branchesNoPer assignmentNoNo
Add staff / set permissionsYesOwn schoolNoNoNoNoNo
Admit students, licence workYesYesYesIf enabledNoNoSelf-admission form
Schedule lessonsYesYesYesIf enabledNoView ownRequest slot
Mark attendance (OTP)–––––YesYes
Manual / late attendanceYesYesYes (own branches)NoNoRequest onlyNo
Start/end km, routeViewViewViewNoNoRecordView own
Live fleet mapYesYesOwn branchesNoNoNoNo
Payments and invoicesYesYesYesIf enabledYesNoPay / download own
Close cash day / edit closed dayClose + editCloseCloseNoCloseNoNo
Reports and exportAllOwn schoolOwn branchesIf enabledFinancialOwn statsOwn progress
LMS courses and assessmentsYesYesViewIf enabledNoAssign + gradeTake
FeedbackView allView allView branchNoNoGive + view ownGive + 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.

ChannelUsersFormKey functionsPhase
Platform consolePlatform AdminResponsive webOrganisations, schools, plans, platform billing, healthP1
School web consoleSuper Admin, Admin, Supervisor, Staff, AccountantResponsive web (desktop-first, works on tablet/phone)All back-office modules, reports, live fleet mapP1
Trainer appTrainer (and Supervisor in supervisor mode)Native Android + iOSMy day, start/end drive, km, GPS route, attendance OTP entry, skills checklist, feedback (voice/text), student assessmentsP1 Android, P1/P2 iOS
Student appStudent, GuardianNative Android + iOSAttendance OTP, schedule, licence progress, LMS, tests, payments, invoices, feedback, certificatesP1 Android, P1/P2 iOS
Student web portalStudentResponsive webSame as app except attendance OTP and voice feedbackP1
Public pagesAnyoneWebOnline admission form, certificate verification, school landing page (S)P1

App requirements (Must unless marked)

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)

IDRequirementPriPhaseSrc
PLT-01Platform Admin creates an Organisation with owner name, mobile, email, PAN/GSTIN, state, plan.MP1H, B
PLT-02Platform Admin adds one or more Schools to an Organisation (name, RTO code, licence/accreditation no., address, GSTIN, branches).MP1B
PLT-03System builds an isolated workspace with default roles, expense categories, message templates and a Super Admin login sent by SMS/email.MP1H
PLT-04Plans: Subscription (single school/branch) and Enterprise (multi-school/branch); per-organisation price override; price per branch option.MP1H
PLT-05Lifecycle: Trial (14 days) → Paid → Grace (7 days, banner) → Read-only → Suspended; driven automatically by payment status.MP1H
PLT-06Monthly GST invoice to each organisation (CGST+SGST or IGST by state); online payment via gateway or manual entry; webhook-confirmed, idempotent.MP1H, N
PLT-07Activity trail of every change to an organisation/school (created, plan changed, invoiced, paid, suspended).MP1H
PLT-08Platform dashboard: schools by state, active students, MRR, churn, trials expiring, overdue.SP1N
PLT-09Feature flags per plan (e.g. live tracking, LMS, biometrics) so modules can be sold as add-ons.SP2N
PLT-10Usage metering per school (SMS sent, storage used, video minutes) for fair-use or add-on billing.SP2N

6.2 Organisation and multi-school (ORG)

IDRequirementPriPhaseSrc
ORG-01Super Admin signs in once and sees a combined dashboard of all schools and branches, with a filter to drill into one.MP1B
ORG-02School/branch switcher in the header; "All schools" view for Super Admin.MP1H, B
ORG-03Super Admin adds staff to a specific school and branch, assigning role and module permissions.MP1B
ORG-04Side-by-side comparison of schools/branches: admissions, revenue, pass rate, fleet use.MP1H
ORG-05Transfer a student, trainer or vehicle between branches of the same organisation, keeping history.SP2N
ORG-06Organisation-level settings inherited by schools, overridable per school (fees, templates, attendance rules).SP1N

6.3 Enquiries and admissions (ADM)

IDRequirementPriPhaseSrc
ADM-01Record enquiry: name, mobile, interest (training/LLR/DL/renewal/badge), vehicle class, source, follow-up date, assigned staff.MP1H
ADM-02Enquiry follow-up list with due/overdue status and outcome (converted, lost + reason).MP1H, N
ADM-03Convert enquiry to student in one click without retyping.MP1H
ADM-04Public online admission form (mobile-friendly) with document upload and consent checkboxes; staff approve before activation.MP1H
ADM-05Auto-fill student details from an uploaded RTO PDF, Aadhaar/ID or licence image (OCR); staff review before save. Aadhaar number stored masked.SP1H, P
ADM-06Unique student code auto-generated per school (e.g. SCH-2026-00045).MP1P
ADM-07Mandatory fields: name, mobile, date of birth, gender, address with state/district/pincode, purpose (training / licence / both), vehicle class.MP1B, N
ADM-08Duplicate check on mobile number and ID number across the school.MP1N
ADM-09Bulk import from Excel with validation report.SP1H
ADM-10Referral source and referrer recorded; referral reward tracking (C).SP1H, P
ADM-11Students under 18 must have a linked guardian and recorded guardian consent before data processing beyond admission.MP1N

6.4 Student records (STU)

IDRequirementPriPhaseSrc
STU-01One profile showing personal details, services bought, licence status, lessons and attendance, km driven, payments/dues, courses, tests, feedback, documents.MP1H, P
STU-02Optional photo, compressed on device to about 400 px / under 100 KB.MP1H
STU-03Documents (ID, address proof, photos, medical Form 1A where required, LLR copy) with type, expiry and retention rules.MP1H, N
STU-04Enable, disable or reset portal/app access per student.MP1P
STU-05Archive (soft delete) instead of delete; restore by Admin; hard delete only through retention policy.MP1N
STU-06Timeline of all events for the student (enquiry → admission → LLR → lessons → DL).SP1N
STU-07Tags and notes (e.g. "nervous driver", "needs female trainer").CP2N

6.5 Licence and services (LIC)

IDRequirementPriPhaseSrc
LIC-01Service catalogue per school: LLR, DL, renewal, duplicate, address change, badge, training package, refresher course; each with fee, GST rate and steps.MP1H, P
LIC-02LLR: application no., test date, result; failed-LLR alert and retest follow-up.MP1H, P
LIC-03DL: application no., slot date, test result, issue date, DL number, dispatch status.MP1H
LIC-04LLR validity countdown with reminder before expiry (DL test must happen within validity).MP1N
LIC-05Badge, renewal, duplicate and address-change applications with status trail.MP1H, P
LIC-06Pipeline board from enquiry → LLR → training → DL, filterable; stuck cases highlighted after N days.MP1H
LIC-07Vehicle classes as master data (MCWOG, MCWG, LMV, LMV-TR, HMV etc.) per school.MP1N
LIC-08Driving school certificate (Form 5 / Form 5B for accredited centres) generated as PDF once training hours are met.SP1N
LIC-09DL renewal reminders to past students (marketing re-engagement).SP2H

6.6 Scheduling and training (SCH)

IDRequirementPriPhaseSrc
SCH-01Calendar (day/week) by trainer, vehicle and student; book lessons, theory classes and test days.MP1H
SCH-02Block double booking of trainer, vehicle or student; respect trainer leave and vehicle service days.MP1H, N
SCH-03Training package defines number of sessions/hours, split into theory and practical (default LMV 8 h + 21 h); progress shown against it.MP1N
SCH-04Recurring bookings (e.g. Mon–Sat 7:00–7:45 for 4 weeks).MP1N
SCH-05Student requests or reschedules a slot from the app within rules (cut-off hours, max reschedules); staff approve.SP1N
SCH-06No-show and late-cancel marking with optional penalty fee.SP2N
SCH-07Driving skills checklist per vehicle class (clutch control, reversing, parking, hill start, highway, night…) ticked by trainer with level 1–3.MP1H
SCH-08Lesson notes per session visible to next trainer.SP1N
SCH-09Pickup point per lesson (home/branch) shown in Trainer app with navigation.CP2N

6.7 Trainers and vehicles – master data (TRN)

IDRequirementPriPhaseSrc
TRN-01Trainer profile: ID, login, mobile, licence no. and expiry, years of experience, vehicle classes allowed, languages spoken, branch, default vehicle.MP1H, N
TRN-02Assign students to a trainer (primary/backup); trainer sees only assigned students.MP1H
TRN-03Vehicle profile: registration no., type/class, make/model, fuel, dual-control yes/no, default trainer, current odometer.MP1H
TRN-04Vehicle documents with expiry alerts: RC, insurance, PUC, fitness, permit, driving school vehicle authorisation.MP1N
TRN-05Service schedule by km or date; vehicle blocked from booking while in service.SP1N
TRN-06Fuel log (litres, amount, odometer) and km-per-litre report.SP2N
TRN-07Trainer leave and availability.SP1N
TRN-08Trainer licence/experience expiry alerts (regulators require minimum experience for instructors).SP1N

6.8 Billing and finance (FIN)

IDRequirementPriPhaseSrc
FIN-01Fee per service with GST rate; discounts with reason and approval above a limit.MP1H, P
FIN-02Record payment (cash, UPI, card, bank transfer, cheque) with instalments and auto-numbered receipt PDF.MP1H, P
FIN-03Online payment from Student app/portal via payment gateway (UPI first); webhook confirmation, no double posting.MP1H
FIN-04GST invoice PDF (school GSTIN, HSN/SAC, place of supply, CGST/SGST/IGST), email/WhatsApp/download.MP1H, P
FIN-05Outstanding dues per student and ageing (0–30, 31–60, 60+ days); due reminders.MP1P
FIN-06Refunds and credit notes with approval.MP1N
FIN-07Expenses by category (fuel, salary, rent, maintenance, RTO fees, marketing…), branch, vehicle; bill upload.MP1H, P
FIN-08Government fees collected on behalf of student (pass-through) kept separate from school income in profit reports.MP1N
FIN-09Cash book per branch: opening balance, day totals, cash count, close day; closed day locked except Super Admin, with audit.MP1H
FIN-10Trainer payout report (sessions/hours × rate) for payroll.SP2N
FIN-11Export to Tally/accounting format (C).CP2N

6.9 LMS – online learning (LMS)

IDRequirementPriPhaseSrc
LMS-01Course builder: modules, video lessons, PDFs, quizzes; drag-and-drop ordering.MP1H, P
LMS-02Video upload, converted for secure adaptive streaming; no direct file URL; optional watermark with student name/phone.MP1P
LMS-03Sequential unlock: next lesson opens only after the video is watched (≥ 90%) and the checkpoint quiz is passed.MP1H, P
LMS-04Enrol single, bulk, or automatically by service bought.MP1H, P
LMS-05Quiz builder (MCQ, image questions, true/false), auto-grading, pass mark, retry limit.MP1H, P
LMS-06Progress and analytics per student/course; theory hours counted toward the training package.MP1H, P, N
LMS-07Certificate PDF on completion with QR code; public verification page.MP1H, P
LMS-08Courses in multiple languages; student sees their language version.SP1N
LMS-09Ready-made road-signs and LLR mock-test question bank shared by the platform to all schools (Platform content library).SP1N
LMS-10Download for offline viewing inside the app (encrypted).CP2N

6.10 Assessments and questionnaires (ASM)

IDRequirementPriPhaseSrc
ASM-01MCQ assessments scheduled daily, weekly, every N days or on custom dates, with a per-day attempt limit.MP1H
ASM-02Question bank with categories, difficulty, language; random draw per attempt.MP1N
ASM-03Timed tests; result with explanation; score trend per student.MP1N
ASM-04Practical assessment by trainer (rubric per skill) at milestones and before the RTO test ("test readiness" score).SP1N
ASM-05Questionnaire builder shared with Feedback (section 9).MP1B

6.11 Communication (COM)

IDRequirementPriPhaseSrc
COM-01Automatic reminders: lesson, LLR test, DL test, fee due, LLR expiry, document expiry, renewal.MP1H
COM-02Channels: push (free, default), SMS (DLT-registered templates), WhatsApp Business, email. Per-school choice and fallback order.MP1H, N
COM-03Editable templates per language with placeholders; message log with delivery status.MP1H, P
COM-04In-app notification bell (mark one/all read).MP1H, P
COM-05Welcome message with app download link and login.MP1P
COM-06Broadcast to a filtered group (e.g. all students with LLR expiring this month).SP2N

6.12 Settings and administration (SET)

IDRequirementPriPhaseSrc
SET-01Branding: name, logo, colour, light/dark.MP1H
SET-02Language: school default plus per-user choice.MP1H, B
SET-03Feature switches per school with dependencies.MP1H
SET-04File retention per upload type (N days or forever), daily cleanup with log.MP1H
SET-05Attendance rules per school/branch (section 7).MP1H, B
SET-06Tracking rules: GPS interval, overuse thresholds (section 8).MP1N
SET-07Working hours, holidays, slot length per branch.MP1N
SET-08Password policy, session timeout, lock after 5 failed attempts for 15 min.MP1H

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.

ColourSuggested hex (light theme)MeaningUsed for (examples)
Green#16A34AGo, complete, healthyPrimary buttons (Start drive, Save, Pay), Present, Paid, Passed, LLR/DL issued, vehicle documents valid, trial/paid plan active
Yellow (amber)#F59E0BCaution, pending, due soonPending 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#DC2626Stop, failed, overdueAbsent, 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 backgroundContentBody text, tables, cards, so the three signal colours stay meaningful
IDRequirementPriPhaseSrc
UI-01Apply the red / yellow / green colour code to all statuses, badges, buttons, alerts, charts and the pipeline board across web and apps.MP1B
UI-02Thresholds that turn an item yellow or red (e.g. days before fee due, days before document expiry, km overuse %) are configurable per school.MP1B, N
UI-03Colour 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.MP1N
UI-04Yellow backgrounds use dark text; all colour pairs meet WCAG 2.1 AA contrast (4.5:1 for text).MP1N
UI-05Dark-theme versions of the three colours are defined in the design system with the same meanings.SP1N
UI-06Dashboards open with a red/yellow/green summary strip (e.g. "3 red: overdue fees, 1 expired insurance") linking to the items.SP1N
UI-07School branding (logo, accent colour) may change headers and logos, but never overrides the signal colours.MP1N

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.

LanguageScriptWeb consoleStudent appTrainer appLMS / testsSpeech-to-text
EnglishLatinYesYesYesYesYes
TamilTamilYesYesYesYesYes
TeluguTeluguYesYesYesYesYes
MalayalamMalayalamYesYesYesYesYes
KannadaKannadaYesYesYesYesYes
HindiDevanagariYesYesYesYesYes
IDRequirementPriPhaseSrc
LNG-01All screens, menus, buttons, messages, errors and push notifications available in the six launch languages.MP1B
LNG-02Super 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.MP1H, B
LNG-03Student app asks for language on first launch, before sign-in.MP1N
LNG-04Reminder and notification templates maintained per language; each student receives messages in their own language.MP1B
LNG-05Invoices, receipts and certificates printed in English plus the student's language where the school chooses (bilingual PDF), using fonts that render all six scripts.SP1N
LNG-06LMS courses, quizzes, assessments and questionnaires can hold a version per language; the student sees their language, falling back to English.MP1B
LNG-07Speech-to-text feedback works in all six languages; typed input supports each language's keyboard.MP1B
LNG-08Names and addresses can be stored in English and in the local script.SP2N
LNG-09Search works across scripts for student names entered in English (e.g. search "Murugan" finds the record).SP1N
LNG-10Dates, numbers and currency use Indian formats (DD-MM-YYYY, lakh/crore grouping, Rs) in every language.MP1N
LNG-11All 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.MP1N
LNG-12Translation management screen for the Platform Admin to review and edit wording; missing translations listed.SP1N
LNG-13Every translation reviewed by a native speaker before go-live; layouts tested with the longest language strings so nothing is cut off.MP1H

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.

Every lesson ends in one of four attendance statesGreen counts fully; yellow counts but is flagged in reports; red is not countedLesson startsbooked slotHas phone?Tier 1: app OTPStudent enters app OTPPresentverifiedTier 2: OTP requestOTP + PIN on trainer appCode entered?Presenttrainer-assistedTier 3: added laterSupervisor, within 48 hManualapproved, flaggedAbsentrejectedyesnoyesnoapprovedrejected
attendance flow · 3 tiers, 4 outcomes

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:

Tier 2 – student has not brought the phone

Tier 3 – trainer and student both have issues

IDRequirementPriPhaseSrc
ATT-016-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.MP1B
ATT-02OTP works offline on both phones; validation happens on sync using the device timestamp and server time offset.MP1B, N
ATT-03OTP is single-use per lesson; 5 wrong entries lock check-in for that lesson for 15 minutes and alert the Supervisor.MP1H
ATT-04Check-in only allowed within a window around the booked slot (default 15 min before to 30 min after).MP1N
ATT-05Trainer-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".MP1B
ATT-06Supervisor or Super Admin can add attendance later, with reason, within a configurable window; second-person approval; flagged "manual".MP1B
ATT-07Both phones' GPS positions are saved at check-in; if they are more than a set distance apart (default 200 m) the record is flagged.SP1N
ATT-08Student account bound to one device; changing phone requires Supervisor approval (stops students sharing codes).MP1N
ATT-09Clock-tamper and rooted/jailbroken device detection; flagged, not blocked.SP1N
ATT-10Optional extra checks per school: phone fingerprint/face unlock, branch biometric machine, selfie match.CP2H
ATT-11Theory class attendance by rotating QR code on the classroom screen scanned by the Student app.SP2N
ATT-12Attendance statuses with colour code: Present (green), Trainer-assisted / Manual pending (yellow), Absent / No-show / Rejected (red).MP1B
ATT-13Attendance report by student, trainer, branch and tier, with % of lessons using fallbacks per trainer.MP1N
ATT-14Staff attendance (trainers clock in/out with app + geofence of branch).SP2N

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

  1. Trainer opens the booked lesson; student checks in with OTP (section 7).

  2. Trainer taps Start drive, enters the odometer reading and (optionally) photographs the odometer. The reading must be ≥ the vehicle's last end reading.

  3. 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.

  4. Trainer taps End drive and enters the end reading. The system calculates odometer km, GPS km, duration and start/end addresses.

  5. 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

IDRequirementPriPhaseSrc
FLT-01Start/end odometer readings per drive; km = end − start; reading validated against the vehicle's last reading.MP1H, B
FLT-02Odometer photo at start/end (S); automatic reading of the digits from the photo (C).SP1N
FLT-03Record GPS point every 10 s or 20 m while moving (configurable), with speed and accuracy; batched upload; offline buffer.MP1B
FLT-04Save start and end location (lat/long + address) and full route polyline per drive.MP1B
FLT-05Route replay on a map with play/pause, speed, stops (> 2 min) and timestamps.MP1B, N
FLT-06Live fleet map for Super Admin/Admin/Supervisor: vehicles in an active drive, trainer, student, speed, last update.MP1H, B
FLT-07Vehicle map markers use the colour code: green = in lesson and moving, yellow = idle > 5 min or signal lost, red = alert (overuse, overspeed, outside area).MP1B
FLT-08Tracking only during an active drive; drive auto-ends (with reminder) after configurable idle time; trainer can see when tracking is on.MP1H, N
FLT-09Overuse 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.MP1H
FLT-10Overspeed alert above a configurable limit (default 50 km/h for learner lessons).SP1N
FLT-11Training-area geofence per branch; alert when a drive leaves it.SP2N
FLT-12Design the tracking API so hardware GPS devices (AIS-140) can feed the same data later.SP3H
FLT-13Daily log per day and branch: vehicles used, trainers, students, drives, km (odometer and GPS).MP1H
FLT-14Vehicle utilisation: hours booked vs available, km per day, idle vehicles.MP1H
FLT-15Battery-aware tracking: lower frequency when stationary; warn trainer at low battery.SP1N
FLT-16Route data retention configurable (default 12 months), then summarised and deleted.MP1N
FLT-17SOS button in Trainer and Student apps during a drive, sending live location to Supervisor and emergency contact.SP2N

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

IDRequirementPriPhaseSrc
FBK-01After each drive, Trainer app prompts the trainer for student feedback: skills rating per checklist item, comments by voice or typing.MP1B
FBK-02Student app prompts the student to rate the trainer and lesson (1–5 stars) with comments by voice or typing.MP1H, B
FBK-03Speech-to-text in the user's chosen language; editable before submit; works with short clips up to 2 minutes.MP1B
FBK-04Questionnaire builder: rating, single/multi choice, yes/no, text and voice-answer questions; versioned; per language.MP1B
FBK-05Questionnaire triggers: after every lesson, after N lessons, at course end, after RTO test result, on demand.MP1B, N
FBK-06Anonymous option for student-to-trainer feedback (school setting).SP1N
FBK-07Low ratings (≤ 2 stars) or flagged words create a red alert for the Supervisor with follow-up tracking.SP1N
FBK-08Student sees trainer feedback history and skill progress chart in the app.MP1N
FBK-09Trainer scorecard: average rating, trend, response rate, comments; comparison across trainers.MP1H
FBK-10Net Promoter Score question at course completion; Google review link prompt for promoters (C).SP2N
FBK-11Feedback can be given within 24 h of the drive (configurable); reminder if skipped.SP1N

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)

Report catalogue

IDReportAnswersKey measuresPri
RPT-10Owner dashboardHow is the business today?Admissions, revenue, collections, dues, active students, lessons today, vehicles on road, red alertsM
RPT-11Purpose mixWho came for training vs licence?Count and % of training-only, licence-only, both; by service and vehicle classM
RPT-12Customers by ageWhich age groups do we serve?Count by band (<18, 18–25, 26–35, 36–45, 46–60, 60+), by gender, by purposeM
RPT-13Profit by periodWhich month is most profitable?Revenue (excluding pass-through govt fees), expenses, profit, margin %, best/worst month highlightedM
RPT-14Volume and peak periodsWhich periods are busiest?Admissions and lessons by month, weekday and hour slot (heatmap)M
RPT-15Revenue and collectionsWhat did we bill and collect?Billed, collected, by payment mode, by service, by staffM
RPT-16Outstanding duesWho owes us?Dues by student with ageing bucketsM
RPT-17ExpensesWhere does money go?By category, branch, vehicleM
RPT-18GST summaryWhat tax do we file?Taxable value, CGST/SGST/IGST by month, invoice registerM
RPT-19Enquiry funnelAre we converting leads?Enquiries → admissions, conversion %, lost reasons, by source and staffM
RPT-20Source and referralsWhere do students come from?Students and revenue by source/referrerS
RPT-21Licence pass ratesHow do our students do at RTO?LLR and DL first-attempt pass %, retests, by trainer and branchM
RPT-22Time to licenceHow long does it take?Days admission → LLR → DL; stuck casesS
RPT-23AttendanceAre lessons happening?Attendance %, no-shows, Tier 1/2/3 share per trainerM
RPT-24Training completionAre packages completed?Hours done vs package, theory vs practical, drop-outsM
RPT-25Trainer performanceWho are our best trainers?Lessons, hours, km, ratings, student pass rate, fallback usageM
RPT-26Vehicle usage and kmHow are cars used?Odometer km, GPS km, difference, utilisation %, overuse alerts, fuel efficiencyM
RPT-27Route historyWhere did the car go?Drives with start/end address, km, route replay linkM
RPT-28Customers by locationWhere do students live?By district/pincode, map viewS
RPT-29LMS and assessmentsIs theory learning working?Course completion, quiz/assessment scores, weak topicsM
RPT-30FeedbackHow satisfied are students?Ratings, NPS, comments by trainer, questionnaire resultsM
RPT-31School comparisonWhich school/branch performs best?Side-by-side of the key measures aboveM
RPT-32Cash bookDoes cash tally?Opening, receipts, payments, closing, differences per dayM
RPT-33Platform (Platform Admin)How is the SaaS business?Schools by state, MRR, trials, churn, overdue, usageS

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.

IDFeatureBenefit to the schoolSuggested phase
SUG-01Guardian access for students under 18: consent, OTP fallback, progress and duesMeets parental-consent rules; parents are often the payerP1
SUG-02Test readiness score combining skills checklist, practical assessment and mock-test results before booking the RTO slotHigher first-attempt pass rate, fewer retest costsP1
SUG-03LLR mock tests and road-sign library shared by the platform to all schools, in every languageReady content on day one; strong selling pointP1
SUG-04Accredited-centre compliance pack: 29-hour LMV / 38-hour HMV hour tracking (theory vs practical), Form 5/5B certificate, trainer qualification recordsSupports schools that are or want to become accreditedP1–P2
SUG-05Self-booking of lessons by students within open slotsLess phone work for front deskP2
SUG-06Package builder and offers: combos (training + LLR + DL), seasonal discounts, coupon codesHigher ticket sizeP2
SUG-07WhatsApp chatbot for enquiries, fee reminders and slot confirmationsFaster lead responseP2
SUG-08Lead capture from website and social media forms straight into enquiriesNo missed leadsP2
SUG-09SOS and safety: emergency button, live location share, incident report with photosStudent and trainer safety; insurance claimsP2
SUG-10Vehicle maintenance and fuel management with service reminders and cost per kmLower running cost; fewer breakdownsP1–P2
SUG-11Trainer payout calculation from verified sessionsFair pay, no disputesP2
SUG-12Refresher and specialised courses (highway, night driving, women-only batches, senior citizens)New revenue linesP2
SUG-13Corporate/fleet driver training module with company billingB2B revenueP3
SUG-14Gamification: badges and streaks for LMS and practiceBetter course completionP3
SUG-15Public school profile page with ratings and an enquiry buttonMarketing; feeds SUG-08P2
SUG-16AI driving tips: auto-summarise trainer voice notes into "3 things to practise" for the studentClearer feedback for studentsP3
SUG-17Harsh braking / sharp turn detection from phone sensors during drivesObjective driving-quality data per studentP3
SUG-18Document expiry tracking for vehicles and trainers with red/yellow alertsAvoid fines and lapsed insuranceP1
SUG-19Data backup export for the school owner (all their data as Excel/ZIP)Trust; easier salesP1
SUG-20Help centre and in-app support tickets to the platform teamLower support costP2

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.

IDAreaRequirementPri
NFR-01ScaleSupport 1,000 schools, 100,000 active students and 5,000 vehicles tracked at the same time without redesign.M
NFR-02PerformanceWeb pages load in < 3 s on 4G; API responses < 500 ms at the 95th percentile; live map updates within 15 s.M
NFR-03Availability99.5% monthly uptime; planned maintenance outside 6 am–10 pm IST.M
NFR-04OfflineTrainer and Student apps keep working for a full drive without network and sync safely afterwards.M
NFR-05Data residencyAll personal data, location and media stored in Indian data centres.M
NFR-06Privacy (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-07MinorsVerifiable guardian consent before processing data of students under 18 (DPDP Rules 2025, Rule 10).M
NFR-08SecurityHTTPS 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-09Tenant isolationSeparate logical database/schema per organisation; automated tests that one tenant cannot read another's data.M
NFR-10AuditImmutable audit log retained 3 years (configurable).M
NFR-11BackupDaily backups, 30-day retention; restore tested quarterly; RPO 24 h, RTO 4 h.M
NFR-12LanguagesSix 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-13AccessibilityWCAG 2.1 AA for web; large tap targets; colour never the only signal (UI-03).S
NFR-14DevicesAndroid 9+, iOS 15+, latest two versions of Chrome, Edge, Safari, Firefox.M
NFR-15BatteryA 1-hour drive should use no more than about 10% battery on a mid-range phone.S
NFR-16ObservabilityCentral logs, error tracking for web and apps, uptime alerts, per-tenant usage dashboards.M
NFR-17ComplianceGST-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

Open questions for the client

Proposed phasing

PhaseScopeExit criteria
P1 – MVPPlatform 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 UI2 pilot schools run for 4 weeks with all lessons recorded in the apps
P2 – GrowthiOS apps (if not P1), biometrics options, geofence, SOS, self-booking, packages and offers, WhatsApp bot, payouts, broadcast, more languages, custom report builder20 schools live; < 5% of lessons on Tier 3 attendance
P3 – ScaleHardware GPS, corporate training, driving-quality sensors, AI tips, gamificationAgreed after P2 review

Sign-off

NameRoleDecisionDate
Client sponsor
Platform owner
Delivery lead