Built for single and multi-branch schools. Admissions through report cards, attendance period by period, and a parent app that gets opened rather than uninstalled.
The same record is read from very different places. Each desk gets the screen its job actually needs.
Opens one dashboard: today’s absentees, fee position by class, staff on leave, and which sections are behind on assessment entry.
Marks attendance in four taps, enters marks against the school’s own grading scheme, and messages a parent without leaving the register.
Sees attendance, homework, fee dues and the bus location in one place — and pays without a phone call to the office.
Every module writes to the same record. Turning one on is a permission change and a form — never a migration, never a second login.
The full module matrixEnquiry to allotted seat, with waiting lists, sibling rules and document checklists.
Daily or per period, with automatic parent notification on an unexplained absence.
Concessions, siblings, transport slabs and late fees — computed, not maintained by hand.
Your grading scheme, your report card format, generated for a whole section at once.
Conflict-checked timetables, and a same-morning substitution that notifies everyone affected.
Stops, fees and live vehicle position, with boarding confirmation to the parent.
Leave, workload and salary structure, with teaching load visible against the timetable.
One child or four, one login. Attendance, homework, dues, circulars and payment.
A record is created once, with documents attached, and never re-keyed again.
Allotment drives the register, the fee schedule and the parent’s app view at once.
Marks entered by subject teachers roll into the report card without a spreadsheet in between.
A whole cohort moves up in one action, carrying history, dues and documents forward.
Boards and schools differ, and a template you cannot change is a template you will abandon. Formats are configured, not hard-coded.
A teacher calls in sick at 7:40. Cover is assigned, the timetable updates, and every affected class and parent knows before first bell.
Sibling concessions, mid-term joiners, transport changes and partial payments are ordinary cases here, not exceptions requiring a workaround.
One campus, a few hundred students, an office of three. Everything on by default and nothing to configure for a month.
Shared fee policy and report card formats, separate ledgers and staff per branch, one board-level view.
Different grading logic per stage on one roll, so a child moves up without changing systems.
Every system encodes a view of how the work is done. Here is ours, written down before you buy it rather than discovered in month three.
| We assume | What it buys you | Where it strains |
|---|---|---|
| One child, one record, for fourteen years | Attendance, marks, fees and documents stay on a single ID from nursery to Class 12, so history survives every promotion. | Schools that re-admit under a fresh number each year need a one-time merge before go-live. |
| The class teacher is the point of entry | Attendance and marks come from the person who saw the child, not from an office re-keying a paper register at 4 pm. | Where teachers have no device access, the office fallback screens work but cost the office an hour a day. |
| Fees are computed, never typed | Heads, concessions, sibling rules, transport slabs and late fees are rules — so a receipt is reproducible two years later. | A cash discount agreed verbally has to be entered as a named concession, or the ledger will not reconcile. |
| Parents are users, not recipients | One family login covers every child on roll: ledger, receipts, attendance, homework, circulars and bus position. | Below roughly 40% parent smartphone coverage, SMS fallback carries the load and the app’s value drops sharply. |
If two or more of the right-hand column describe you, say so on the call — it changes the implementation plan, not the price.
Two hundred enquiries in three weeks, each with documents, sibling checks and a waiting list that reorders itself as seats free up.
Forty teachers entering marks against one scheme, and a whole section’s cards generated the same afternoon.
An ageing view by class, reminders that go out on a schedule, and a receipt the parent gets instantly.
Cover assigned, timetable updated, and every affected class and parent notified before first bell.
Two hundred enquiries in three weeks, each with documents and a sibling check.
Enquiry forms, ~8× normal writes
Sections allotted, timetables published, fee schedules generated for the whole roll.
Bulk generation, one heavy night
Attendance and homework every day; the only season where nothing is exceptional.
6 concurrent registers per section
Forty teachers entering marks against one scheme, then a section’s cards in an afternoon.
Marks entry, ~40 concurrent users
A cohort moves up in one action; last year stays queryable and unmodified.
Cohort write, run out of hours
A gap named in the sales conversation is a decision. The same gap found after go-live is a grievance.
We store what was taught and assessed. We do not build your worksheets, videos or question banks — and we do not pretend an LMS is bundled.
Rooms, mess and wardens are handled as fee heads and custom fields. A residential school with 600 boarders should tell us so in the demo.
Salary structure, leave and workload are here. PF, ESI and TDS returns stay with your accountant, and we export what they ask for.
Transport shows live position from devices you already run. We do not sell, fit or warrant the tracker in the bus.
You send whatever exists — spreadsheets, an old ERP dump, printed registers. We map it and return a gap list, not a quote revision.
Your data in a sandbox with real fee heads and last year’s marks. The office signs off on ten receipts and ten report cards.
Both systems live for one fee cycle. If reconciliation fails, we roll back and the clock stops.
Old system read-only, not deleted. You keep the export for as long as you want it.
Service figures are placeholders pending sign-off — confirm the contracted terms before publishing.
CBSE, ICSE and ISC, and state boards including Maharashtra, Gujarat, Uttar Pradesh, Madhya Pradesh, Rajasthan and Tamil Nadu. Board choice affects assessment structure, report card format and statutory reporting, all configured during implementation.
Yes, and it is a standard part of implementation rather than a customisation charge. Templates are versioned, so a card issued in a previous year reprints exactly as it was issued.
Yes. The teacher app holds the register locally and syncs when signal returns, timestamped when the marks were taken rather than when they synced.
Yes, though it takes longer than a year-start migration. Importing students is quick; reconciling opening fee balances and part-paid instalments is the slow part.
Four separate products, one platform underneath. A school, a college, a centre and a student never share a record.
What a student counts as, when the count is taken, and what is never billed extra — written down, next to the number.
See SchoolDeck pricingWe will configure it live on the call, using your classes, fee heads and grading scheme.