Admissions, academics, attendance, fees, staff and operations — for schools, colleges, universities and coaching institutions. Plus ExamEdge, a preparation product students buy for themselves.
A school is not a university, and a coaching centre is neither. Each product carries its own data model — and all four share one platform underneath.
Single or multi-branch schools, pre-primary through senior secondary. Admissions to report cards, with a parent app that actually gets used — and a class-teacher flow that survives the 7:50am attendance rush.
Colleges and universities. Departments, credits, semester registration, internal and external marks, and the accreditation tables that come due once a cycle and take a fortnight by hand.
Batches with their own start dates, test series that rank, and enquiry-to-enrolment follow-up. Built for centres that live and die by conversion, retention and a results sheet parents will read closely.
The one product a student buys themselves. Practice, spaced revision and performance analytics that say which chapter is costing marks — no institution, no admin, no approval required.
The four differ in their data model, not their polish. Find the row that describes your institution — and if two rows fit, you are probably a group, and groups usually run two.
| Product | It assumes | Billing unit | Wrong fit if |
|---|---|---|---|
| SchoolDeck | A class-and-section structure, one promotion a year, and marks that roll into a report card format a board recognises | Per student, per year | You register students into credit-bearing courses each semester |
| CampusHub | Departments and programmes, semester registration, internal plus external marks, and an exam cell that owns results end to end | Per student, per year | You are one centre that needs batches and tests, nothing more |
| TutorDesk | Batches that start and end on their own dates, enquiry follow-up as the main daily job, and a test series that ranks | Per active student | You file statutory board returns and keep a 12-month register |
| ExamEdge | A student, a target exam and a date. No institution, no administrator, no approval in the middle | Per seat, per term | You need fees, staff or compliance — it holds none of them |
A Class X student on SchoolDeck who joins your junior college keeps the same record, history and fee ledger under CampusHub.
No second contract negotiation, no second implementation, no second login for staff who work across both.
You are not billed twice for a shared student. Bands and annual figures sit on the pricing page. See pricing
Fees, attendance and results resolve to the same student record. Nothing is exported to be re-imported somewhere else.
A school that opens a junior college, or a coaching centre that adds branches, changes configuration — not vendors.
Roles and permissions are defined once and hold across every module, branch and academic year.
Students who already practise on ExamEdge can link it to their institution, so teaching responds to real performance data.
Twenty-four modules, enabled when you need them. Every one writes to the same record, so turning a module on is a permission change and a form — never a migration, never a second database to keep in step.
Software gets abandoned in specific weeks: admission rush, instalment day, results day. These are the stretches we design for, and what runs in each.
Enquiries, forms, document checks, seat allocation, first instalment, section allotment. The one month where a slow front office costs you admissions outright.
Timetable published, teaching loads balanced, transport routes assigned, books issued, parent and student accounts activated in one batch.
Daily attendance, instalment reminders, unit tests, parent meetings, leave and substitutions. Roughly seven in ten of the year’s writes land in these five months.
Seating plans, dummy numbering, evaluation tracking, moderation, report cards, transcripts and the returns the board or university wants in its own column order.
Promotions, arrears carried or written off with a reason, transfer certificates, staff appraisals, and the year locked to read-only so last year’s numbers stop moving.
Attendance between 7:40 and 9:10. The payment gateway on the first five days of a month. Both are planned for capacity separately — a fee rush should never slow a teacher marking a register.
Results day and admission opening. We freeze releases through both, and a named engineer stays on standby for your exam and admission weeks at no extra cost.
Everything. A student’s attendance, marks and ledger stay queryable across academic years and across products, without opening an archive or restoring a backup.
One app with a role switcher sounds efficient and tests badly. A parent should never land on a screen that is not about their own child.
Absences, the next amount due and a way to pay it, report cards when released, and messages actually addressed to them. Two children in the same school appear as two cards, not two logins.
Attendance for a whole section in one pass, marks against the rubric that will print on the report card, one note to thirty parents, and substitution alerts that arrive before the period starts.
What is next, what is due, what came back. Library returns, hostel and transport notices, and their own ExamEdge practice if they use it — in the same place, without a second password.
A student downloads it, picks a target exam and a date, and starts. If their institution runs TurtleDock they can link the two — and then teaching sees which topics are actually costing marks.
Every field is permissioned. A class teacher never sees another branch’s fee ledger.
Marks, fees and attendance edits are immutable and attributed, with a reason on every override.
Choose where records are stored, with encryption in transit and at rest as standard.
Complete structured export on demand. No lock-in through inaccessible records.
The order matters more than the speed. We configure the year first, load people second, and only switch on money once the ledger reconciles against your existing books.
Branches, academic years, classes and sections, fee heads, grading scheme, exam pattern. Done once, on a screen share, with the person who knows the exceptions.
Students, staff, opening fee balances and last year’s marks arrive as four sheets. We validate before import and send back the rows that need a decision.
Front office, accounts and class teachers get separate sessions of under an hour each. Everyone else learns the one screen they need on the day they need it.
Attendance and communication start on day one. Fee collection switches over at a month boundary so your books close cleanly on the old system.
Nobody starts from nothing, and nobody starts from clean data. The honest version of each starting point, including the part that needs a decision from you rather than an import script.
Students, staff, fee structure and last year’s marks map straight across. What takes the time is duplicates, siblings recorded twice and the three columns whose meaning only one person remembers.
Typically 2–3 weeks
We take a database dump or CSV exports and reconcile balances to the rupee before go-live. Custom fields that no longer serve a purpose get dropped deliberately, in writing, rather than carried forever.
Typically 4–6 weeks
The tool usually holds the cleanest data you have, so it goes first. Run both in parallel for one collection cycle, reconcile the two receipt series, then switch at a month boundary.
Typically 2 weeks plus one cycle
We do not ask you to digitise ten years of registers. Current students, current balances and one year of marks go in; the rest stays on the shelf where an auditor can still find it.
Typically 3–5 weeks
Nobody buys software for its payment gateway. Everybody abandons software whose gateway does not reconcile.
UPI, cards, netbanking and cash at the counter land in the same ledger. Settlement files reconcile automatically; a failed payment never leaves a receipt behind.
Bring your own sender ID and template approvals, or use ours. Credits are passed through at cost — there is no per-message margin in our pricing.
Existing attendance terminals push to us over the standard protocols. Bus tracking reads from the units already on your vehicles.
Daily or monthly journals export in the layout your accountant already uses, mapped to your own ledger heads rather than ours.
Google Workspace or Microsoft accounts, with SAML on Group. Leavers lose access the moment your directory says so.
Affiliation returns, scholarship lists and accreditation tables generate from live records, in the column order the receiving body expects.
| Who | Opens it to | Where |
|---|---|---|
| Principal | Yesterday’s attendance by section, collection against target, and the four things flagged as needing attention | Web |
| Registrar | Today’s enquiries, incomplete admission files, transfer certificates waiting on a signature | Web |
| Class teacher | Marking attendance in one pass, entering marks against a rubric, sending one note to thirty parents | Mobile |
| Accounts | Receipts issued today, instalments due this week, the day’s cash and bank position, journal export | Web |
| Exam controller | Seating plans, dummy numbering, evaluation progress by examiner, results held for moderation | Web |
| Transport | Route rosters, who boarded, which bus is running late and which parents were told | Mobile |
| Parent | Absences, the next fee due and a way to pay it, report cards, and messages that are actually for them | Mobile |
| Student | Timetable, assignments due, results when released, and their own ExamEdge practice if they use it | Mobile |
No. Almost everyone starts with one. The account is shared, so adding a second product later is a settings change, not a second migration.
Yes. You export from whatever you run today; we give you validated templates for students, staff, fees and marks, and check the files before anything goes live.
You do. Every record is exportable as structured files on demand. We do not sell it, share it, or train anything on it.
A single-branch institution is usually live in two to three weeks. Multi-branch groups take four to six, and most of that is waiting on clean data.
Attendance and fee collection keep working offline in the mobile apps and sync the moment the network returns.
A named person who knows your configuration, reachable on the same number all year — not a ticket queue that resets every time you write in.
A 40-minute walkthrough using your structure — your branches, classes, fee heads and exam pattern. No slides.