Records spread across workbooks
Admissions, fees, attendance, and student information had to be checked across separate manual records.
SS49 D1T1TECH connected admissions, fees, biometric attendance, payroll, examinations, and family access through five focused applications. Built for an education and competitive examination preparation business in Nagpur, India.
Admissions, fees, attendance, and student information had to be checked across separate manual records.
Management, students, parents, faculty, and attendance staff work from one controlled source of institutional data.
Enrolment changes preserve financial history, while issuing or returning materials updates stock.
Lakshya Institute's administration depended on spreadsheets, historical financial records, biometric attendance exports, and daily staff inputs. The challenge was to connect that information across admissions, collections, examinations, staff schedules, payroll, and parent communication, rather than digitise each task separately. SS49 D1T1TECH built a common backend with dedicated applications for the people using it.
Admissions, student records, fee ledgers, attendance review, examinations, faculty allocation, timetables, payroll preparation, inventory, notices, user access, reporting, and audit history.
Schedules, assignments, attendance, examinations, results, notices, academic communication, and account controls without sensitive management data.
Linked-student attendance, academics, examinations, schedules, notices, relevant account information, and controlled institute communication.
Assigned batches and subjects, schedules, assignments, examinations, marks entry, notices, and student-specific communication within authorised scope.
Biometric spreadsheet imports and attendance administration, alongside dedicated batch rosters and timestamped attendance marking, separated from faculty permissions.
Student fee accounts hold agreed fees, payment history, outstanding balances, payment methods, and printable statements. Corrections, refunds or reversals, and non-cash settlements such as commission adjustments are handled as distinct financial events.
Client-confirmed payment breakdowns were used to reconcile historical entries. Superseded entries were excluded from active calculations while retained for audit and recovery, so a correction did not erase the source history.
The attendance workflow processes spreadsheet workbooks with separate student and staff worksheets. Staff views show first arrival, final departure, and recorded working time. Application-level designations can differ from a device's generic category without requiring staff to edit every export.
These calculations reflect this institute's agreed workflow. Another organisation's payroll policies and local requirements would need a separate review.
Faculty can enter examination results, including negative scores where the marking scheme requires them. Batch-wise attendance and consolidated examination summaries can be downloaded for selected batches and periods, with incomplete or unavailable information distinguished.
Daily biometric presence is kept separate from subject-level class attendance. Being present at the institute does not establish how many Physics, Chemistry, or Mathematics classes a student attended.
Parent onboarding uses the contact information in the student records, prioritising the father's number and using the mother's where needed. A shared parent number supports linked access for siblings instead of treating each student as a separate household.
Student administration covers batch allocation, programmes, subject selections, and enrolment status. Discontinuation and reactivation coordinate the student record, portal access, and fee-account handling.
Production feedback led to refinements in financial screens, report exports, import handling, role classifications, and historical reconciliation. Investigating discrepancies and preserving data history remained part of delivery, alongside new application features.
Books, bags, T-shirts, and other materials can be issued or returned from a student profile. Every movement updates available stock while retaining a transaction history.
The delivered outcomes are connected records and role-specific workflows. Management can handle changes to student accounts, materials, and access without treating each as a separate system.
The figures below describe the delivery and its intended scale. Student capacity is a design target, not reported enrolment or a load-test result.
Admissions, finance, academics, attendance, communication, inventory, and reporting share a controlled institutional data source.
Management, student, parent, faculty, and attendance users receive separate role-based experiences.
The initial production release moved from discovery and source analysis through implementation and deployment. This describes this project’s initial scope; broader institutional platforms are planned separately, typically over 16 to 18 weeks.
The architecture is designed to support approximately 1,500 students, subject to infrastructure and ongoing usage requirements.
We can review admissions, attendance, finance, academics, inventory, communication, reporting, and access requirements for schools, coaching institutes, colleges, and education businesses.