Fee collection runs on a parallel spreadsheet
The receipt book and the accounts sheet disagree, and somebody reconciles them at month end.
Home Industries School management software
EducationSchool management software
Admissions, attendance, fees and examinations on one student record.
KaizenSpark Tech builds custom school and college management systems — admissions, attendance, fee collection, examinations, timetabling and parent communication — built around how a particular institution already runs, rather than configured around a product someone else designed.
What this page is. Described from the problems operators in this sector actually bring us, and from systems we have built for them. Clients are withheld under confidentiality, so what follows covers the problem, the solution and the capability rather than the customer. More of our work is on our solutions.
Who it is for
Does this sound like your operation?
A school, college, or training institution with more than one department, where the admission register, the attendance sheet and the fee ledger are three separate things.
What it looks like
Kaizen Edu, the product behind this.
The same system, shown as it would be configured for this sector. An illustration, not a screenshot.
edu.kaizensparktech.com/dashboard
Kaizen Edu
DashboardStudentsAdmissionsAttendanceFeesExamsReports
One student record,
every department.
every department.
Institution
Admissions, attendance and fees on one record per student
This monthKE
On roll1,284across 4 streams
Present today1,16394% of roster
Fees outstanding₹9.4L142 students
Admissions open38in process
Attendance
Present against roster, last eight weeks
Needs action
Oldest first
| Item | Stage |
|---|---|
| Fee reminder · Term 2 | hold |
| Transfer certificate | wait |
| Exam entry · Sem 3 | wait |
| Attendance · October | ok |
| Scholarship · list | ok |
Interface illustration, drawn with this site’s own design tokens. Sample figures, not a running system.
The problem
What usually brings someone to us.
01
02
Attendance is captured twice
Once on paper in the classroom, once again by a clerk who types it into a system in the evening.
03
Admissions are a folder, not a pipeline
Nobody can say how many enquiries are open, or which stage each applicant has reached.
04
Parents ring the office for everything
Marks, fee dues and attendance all require a staff member to look something up and call back.
05
Examination data is rebuilt each term
Mark entry, grading and report cards start from a blank sheet every cycle.
06
Reports are produced by hand
Management asks a question; somebody spends a day in a spreadsheet answering it.
What we build
What the system would cover.
01
Admissions pipeline
Enquiry to admission as stages, with follow-up owned by a person and a date.
02
One student record
Attendance, fees, marks and documents attached to the same record, not three.
03
Fees and receipts
Structures, instalments, concessions, receipts and an outstanding list that is always current.
04
Examinations
Mark entry, grading schemes, report cards and historical comparison.
05
Parent access
A read-only view of their own child, so routine questions stop reaching the office.
06
Reporting
Management reports read operational records directly, not a monthly export.
Integrations
What it would connect to.
Payment gateways for online fee collection, WhatsApp Business API or SMS for fee and attendance notices, and accounting software for the finance side. Which of these apply depends on what you already run.
How a build runs
The same five stages, whatever the sector.
01
Trace
We follow the work as it runs today and write it down — where the hours go, where data is re-keyed, where errors enter.
02
Scope
Deliverables, integration points, phases and an explicit out-of-scope list, agreed in writing before any code exists.
03
Build
Working software in reviewable increments, with a running environment you can open at any point during the build.
04
Measure
Type checks, automated tests and a manual pass on the paths that matter.
05
Improve
Architecture notes and runbooks ship with the build, then we keep reading the numbers with you.
06
What comes as standard
Written scope, documented handover, and IP transferred to you on final payment. Not extras.
Questions
What people ask before commissioning this.
Can it follow our existing fee structure, including concessions?
That is the usual reason an institution commissions a custom build rather than buying a product: the structure, the instalment calendar and the concession rules are specific, and a configurable product usually gets you most of the way and then stops.
Can parents see only their own child?
Yes. Role-based access is the part worth getting right first, because the failure mode is one parent seeing another family’s record, and that cannot be undone once it renders.
Do we have to move everything over at once?
No. We would normally start with the function that hurts most — often fees or attendance — prove it with one department, then extend.
What about data from our current system?
Migration is scoped separately after we have seen the actual data. Historic records are usually messier than anyone expects, and pricing it before looking would be a guess.
Related
Where to look next.
Start here
Describe the process that costs you most.
We will come back with a scope and a cost range — including if our view is that software is not the right lever.