SchoolMIS by designbykalakar replaces your attendance registers, fee ledgers, exam mark sheets and salary books with a single, privately hosted system — purpose-built for your school, maintained by one person who built it.
Nine modules covering the full school lifecycle — from a child's admission application to their final report card, and from a teacher's monthly salary to the school's annual balance sheet.
Permanent student records, guardian information, admission pipeline from application through enrollment, sibling linking, RTE quota tracking, and Transfer Certificate management.
Daily attendance marking by section, default-present with exception model, 7-day backdate support, holiday calendar, and attendance percentage calculations that feed directly into report cards.
Per-class fee structures, monthly invoice generation, partial payment support, receipt numbers for every transaction, dues reports by class, and automatic journal entries into the accounting module.
Subject-wise mark entry per exam term, bulk entry for a full section in one save, grade scale, term-on-term comparison, and computed report cards with attendance pulled from Module 02.
A single staff-facing student summary page for parent-teacher meetings — attendance, marks, fee status, and leaving/transfer flags in one view. Append-only meeting notes with follow-up date tracking.
Excel-based import wizard for migrating existing paper and spreadsheet records. Plain-language error preview with green/red/yellow rows. Batch revert capability. Covers students, guardians, fee history, and last year's attendance and marks.
Parent notifications for absence, overdue fees, and school circulars — triggered by staff from within the system. Meets parents where they already are, without requiring a separate parent app or portal login.
Per-staff customisable salary structures, monthly payroll runs with printable payslips, full chart of accounts, journal ledger, trial balance, and Income & Expenditure Statement and Balance Sheet — PDF-exportable for your CA.
The principal sees today's attendance, low-attendance students, overdue fees, pending payroll, PTM follow-ups, and a 6-month I&E trend — on one screen, on login. The accountant sees the finance and payroll view only.
Each feature below includes a plain-language description for school management, and an optional technical detail for IT teams evaluating the implementation. Every screen shares one consistent design language — a teacher who learns attendance marking already knows where to look on the fees or exams screen.
When a fee payment is recorded, the accounting ledger updates in the same action — no double-entry, no end-of-month reconciliation, no two systems that disagree with each other. The accountant has one correct number at all times.
Promotions, class changes, and transfers don't overwrite history. Every year's enrollment, attendance, marks, and fee records are preserved — the system can answer "what was Aarav's attendance in 4th standard" five years from now.
The bulk import wizard generates a pre-filled Excel template from your current class list. Staff fill it in offline, upload it, and see a clear preview — green rows ready to import, red rows with plain-language explanations of what needs fixing — before anything is committed.
The Income & Expenditure Statement and Balance Sheet are PDF-exportable, formatted to Indian accounting conventions (lakhs, I&E not P&L), and carry a clear disclaimer that they require CA certification before any official submission.
Every technology in SchoolMIS has been chosen because it will still work correctly, be maintained, and be understood by any competent developer five years from now.
Access is enforced server-side. A teacher cannot see fee amounts even by inspecting browser source. A front-office staff member cannot approve payroll. Role boundaries are hard constraints, not UI-level hiding.
Permissions checked in Django views, not in JavaScript. Sensitive data (fee amounts, payroll figures) is never sent to the browser for roles without access.
Every edit to a student record, admission application, or enrollment is logged with who made it and when. Disputed changes have a verifiable answer.
Every record is scoped to your school at the database query level — a structural boundary, not a permissions checkbox that could be misconfigured. No third-party data handlers, ever.
Role permissions at a glance:
| Action | Principal | Accountant | Front Office | Teacher |
|---|---|---|---|---|
| Student records & admissions | ✓ | ✗ | ✓ | Own class only |
| Mark attendance | ✓ | ✗ | ✓ | Own section only |
| View fee details & amounts | ✓ | ✓ | Flag only, no amounts | ✗ |
| Record fee payments | ✓ | ✓ | ✗ | ✗ |
| Manage payroll | ✓ | ✓ | ✗ | ✗ |
| View own payslip | ✓ | ✓ | ✓ | ✓ |
| Financial statements | ✓ | ✓ | ✗ | ✗ |
| Enter exam marks | ✓ | ✗ | ✗ | Own section only |
| Bulk import data | ✓ | Financial data only | ✓ | ✗ |
| Send WhatsApp alerts | ✓ | ✗ | ✓ | Own section only |
SchoolMIS is architected as a multi-tenant system from the ground up. A single campus runs on the exact same backbone that would serve a network of schools under one management — no re-platforming, no data migration, no "we'll rebuild it properly later."
Every query is automatically scoped to a school at the database layer. There is no code path — a form, a report, an admin screen — that can accidentally surface one school's students, fees or payroll to another.
If the system can't confirm which school a request belongs to, it stops and raises an error rather than guessing. A missing safeguard shows up immediately as a bug report, never as leaked data.
Each school can enable or disable optional modules — payroll, accounting, timetable — on its own timeline, without affecting any other school sharing the platform.
A management trust running multiple schools gets one place to onboard a new campus, without any risk of one school's staff seeing another's records — even by accident, even under a shared login for a support visit.
A short conversation is enough to understand whether SchoolMIS fits your school's size, structure, and existing process. No obligation, no sales pitch.