Case study · Deployed for institutional use

A custom education ERP for Lakshya Institute.

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.

Before

Records spread across workbooks

Admissions, fees, attendance, and student information had to be checked across separate manual records.

What we built

Five role-specific applications

Management, students, parents, faculty, and attendance staff work from one controlled source of institutional data.

What changed

Connected daily decisions

Enrolment changes preserve financial history, while issuing or returning materials updates stock.

Project overview

Connect existing records without losing their history.

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.

The challenge
  • Distributed recordsStudent, fee, attendance, and admission information had to be checked across multiple workbooks and manual records.
  • Institute-specific rulesActive, cancelled, and opted-out students required different financial treatment, while attendance followed Tatva and Essential batch structures.
  • Different user boundariesManagement, faculty, students, parents, and attendance staff needed separate permissions and interfaces.
  • Historical traceabilityExisting source records had to remain verifiable after migration without exposing confidential student information publicly.
Five connected applications

Five roles. Five focused workspaces.

Management and operations

Admissions, student records, fee ledgers, attendance review, examinations, faculty allocation, timetables, payroll preparation, inventory, notices, user access, reporting, and audit history.

Student application

Schedules, assignments, attendance, examinations, results, notices, academic communication, and account controls without sensitive management data.

Parent application

Linked-student attendance, academics, examinations, schedules, notices, relevant account information, and controlled institute communication.

Faculty application

Assigned batches and subjects, schedules, assignments, examinations, marks entry, notices, and student-specific communication within authorised scope.

Attendance desk

Biometric spreadsheet imports and attendance administration, alongside dedicated batch rosters and timestamped attendance marking, separated from faculty permissions.

Data migration and reconciliation
  • Legacy references preservedOriginal source context remains available for audit and later verification.
  • Admissions standardisedRecords were separated by status and connected to generated admission numbers, batches, subjects, and attendance.
  • Payments normalisedCondensed descriptions were interpreted as transactions, payment modes were standardised, and unknown dates remained explicitly unknown.
  • Exceptions stayed reviewableMissing information was never silently invented; records requiring clarification remain available for manual completion.
Financial control

Fee agreements, payments, and adjustments in one ledger.

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.

01
Preserve money receivedExisting receipts and the original fee agreement remain intact when a student opts out.
02
Close only unpaid liabilityAn auditable adjustment removes unpaid future liability from active totals without deleting history.
03
Cancel future schedulesPlanned payments are closed when access and enrolment status change.
04
Disable linked accessStudent and parent accounts are invalidated when the student is no longer active.
05
Retain the ledgerManagement can still review the complete transaction and adjustment history.
06
Reverse without rewritingIf the student rejoins, a corresponding reversal restores the account while preserving previous transactions.
Historical financial corrections

Correct the active balance without deleting the original record.

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.

Attendance and payroll

Use the biometric exports the institute already has.

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.

Translate the agreed payroll rules into calculations.

  • Payable daysDays in the month minus absent days.
  • Daily rateMonthly salary divided by days in the month.
  • Payable amountDaily rate multiplied by payable days.
  • Net payablePayable amount minus the advance given.

These calculations reflect this institute's agreed workflow. Another organisation's payroll policies and local requirements would need a separate review.

Examinations and reporting

Report what the records actually establish.

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 and student access

Model the family, not just one login per student.

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.

After deployment

Refining the ERP through daily use.

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.

Inventory integration

Student material distribution now updates stock automatically.

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.

Key outcomes

One platform for daily institute operations.

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.

  • Change enrolment without erasing fee historyOpt-out adjustments close unpaid future liability while preserving receipts and the original agreement. A reversal supports rejoining without rewriting past transactions.
  • Keep material issues and stock connectedIssuing or returning materials from a student profile updates available stock and retains a movement history.
  • Give each role a focused workspaceManagement, students, parents, faculty, and attendance staff have separate experiences aligned with their responsibilities and authorised access.
  • Prepare payroll from reviewable attendanceBiometric imports, working-time records, and the institute's payroll rules support preparation without treating missing punches as confirmed absence.
  • Export academic and operational summariesBatch attendance and consolidated examination reporting preserve distinctions between recorded, incomplete, and unavailable information.

The figures below describe the delivery and its intended scale. Student capacity is a design target, not reported enrolment or a load-test result.

1 source

Admissions, finance, academics, attendance, communication, inventory, and reporting share a controlled institutional data source.

5 apps

Management, student, parent, faculty, and attendance users receive separate role-based experiences.

3 weeks

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.

~1,500

The architecture is designed to support approximately 1,500 students, subject to infrastructure and ongoing usage requirements.

Need a similar system?

Build around the way your institution works.

We can review admissions, attendance, finance, academics, inventory, communication, reporting, and access requirements for schools, coaching institutes, colleges, and education businesses.

Book institutional review