Every school gets the whole system — nothing locked behind a higher tier. Here's everything inside Shiksha CRM.
When a school evaluates management software, the module list is usually where the disappointment begins. The headline product looks complete, but the moment you read the fine print, the features you actually need — transport tracking, the parent app, WhatsApp, online exams — turn out to be paid add-ons, each on its own invoice, each with its own limit. By the time you have assembled the system your school truly needs, the price has doubled and you are managing a patchwork of upgrades. Shiksha CRM takes the opposite approach: every school gets every module, on every plan. The list below is not a menu of options to choose and pay for individually — it is simply what you get.
This matters for more than just price. When every module is included and every module is built on the same connected foundation, the whole system works as one. Your transport module knows which students are on which route because it draws from the same student records as admissions. Your fee module knows a family's transport fee because transport and fees are not separate products bolted together, but parts of one platform. This is the difference between software that was designed as a whole and software that was assembled from separately-sold pieces — and it is why a school running Shiksha CRM spends its time running the school rather than reconciling the gaps between tools.
The modules are organised below into the natural areas of school life — students and front office, fees and finance, academics, daily operations, communication and people, and system and content. Every one of them is live from day one, every one is included in your plan, and every one connects to the rest. Whether your school uses all twenty-five today or grows into them over time, they are there when you need them, with no upgrade to buy and no feature to unlock.
The student and front office modules are the foundation the rest of the platform is built on, because everything else in a school ultimately refers back to a student record. The front office is where a school meets the outside world — admission enquiries, visitors, phone calls, postal dispatch and receipt, and complaints all pass through it — and Shiksha CRM gives it a proper system rather than a diary and a stack of forms. Every enquiry is logged, every visitor recorded, every complaint tracked to resolution, so the busiest desk in the school finally has a memory that does not depend on who happened to be sitting there.
The admissions CRM turns those enquiries into a pipeline. Rather than a list of names on a register, each prospective family is a lead that moves through stages — new enquiry, follow-up, admitted — with reminders so no parent is forgotten and reporting so the school can see how many enquiries are converting and where they are coming from. This is the difference between passively recording admissions and actively managing them, and in a competitive market it is often the most valuable module in the entire platform.
Once a student is enrolled, the student information module holds their whole world: personal details, documents, category and house, guardians and contacts, and their full history across the years they spend at the school. Categories, houses, and the ability to bulk-import and manage large numbers of students at once mean the module scales from a small school to a large one without strain. And because certificates and ID cards draw from this same record, generating a student ID card or a transfer certificate is a matter of a click, not a fresh round of data entry.
The academic modules manage the intellectual life of the school — the classes, subjects, timetables and examinations that are the reason the school exists. Academics covers the structure: classes and their sections, the subjects taught, the timetables that assign teachers to periods and rooms, the promotion of students from one year to the next. Assigning a class teacher, building a timetable, or promoting a whole cohort at year end are handled here, cleanly, so the scaffolding of the school year is set up once and used throughout.
Examinations is where much of a school's administrative pain has traditionally lived, and it is where Shiksha CRM saves a great deal of it. Exam groups and schedules are defined, marks are entered against them, and grades and divisions are calculated automatically according to the scale the school sets. From this, marksheets and admit cards are generated and printed without a single spreadsheet formula — the error-prone, late-night work of compiling results by hand simply disappears. Online examinations and a question bank extend the same module to schools that assess digitally.
Supporting these are the lesson plan and homework modules, which connect the classroom to the home. Lesson plans track syllabus coverage lesson by lesson, so a school can see whether it is on schedule. Homework is assigned and tracked, and because it flows to parents through the mobile app, the gap between what is set in class and what a parent knows about at home finally closes. Together, the academic modules give a school a complete, connected picture of teaching and learning, from the timetable that starts the day to the marksheet that ends the term.
The operational modules handle the physical, logistical life of the school — the buses, the books, the stores, the hostels — the parts of a school that involve moving people and things through the day. Transport is the most visible of these, and with live GPS tracking it becomes one of the platform's standout capabilities: routes and pickup points are defined, vehicles and drivers are recorded, students are assigned to routes, and the whole fleet is tracked live with alerts to parents and administration. Transport fees are linked to the student's route and their overall fee ledger, so a family's bus fee is never an untracked side-note.
The library module gives a school a proper catalogue and circulation system: books are recorded, issued and returned, members enrolled, and fines tracked, so the library runs as an organised resource rather than a room with an honour system. Inventory extends the same discipline to the school's physical assets — items, stores, suppliers, stock levels and issues — so that a school always knows what it has and what it has spent. For schools with boarding, the hostel module manages rooms, room types, allocation and hostel fees, tying residential students into the same connected record as everyone else.
What unites these operational modules is that they take the parts of a school that are easiest to let slide into informality — the register no one updates, the store cupboard no one tracks, the bus fee on a separate sheet — and give them the same structured, connected treatment as the academic and financial core. The result is a school where the logistics are as visible and as well-managed as the teaching, and where the small leaks of unmanaged operations are closed.
The communication and people modules govern how a school connects — to its parents, and to its own staff. Communication is the module through which a school reaches its families, and in Shiksha CRM it is built around the channels that actually work in India. WhatsApp is primary: fee receipts, due reminders, attendance alerts, results and notices go out automatically on the school's own verified business number, reaching parents on the app they check constantly. SMS and email are available too, along with templates so that messaging is consistent and professional, and logs so that every message sent is accounted for. Scheduled messages, login credential dispatch, and notice boards complete a communication suite that turns a chronic school headache into an automatic background process.
The mobile app extends this communication into the pockets of parents and teachers. Parents check and pay fees, see attendance, read homework, view results and track the bus; teachers mark attendance and post homework on the move. Push notifications keep both audiences connected to the school's daily rhythm without anyone having to remember to check. Because the app is branded to the school, it reinforces the school's identity and gives it a direct, owned channel to its community that depends on no outside platform.
Human resource management handles the people who run the school. The staff directory holds every employee's record; payroll is calculated and linked to the attendance and leave that staff themselves record through the system; departments, designations and teacher ratings are managed in one place. Because staff attendance flows directly into payroll, the monthly reconciliation of who worked and who took leave — a recurring source of friction in many schools — is handled by default. The alumni module keeps a school connected to its former students, maintaining records and events so that the relationship with a student does not end at graduation but becomes part of the school's lasting community.
Beneath the modules that staff use every day sits a layer that makes the whole platform trustworthy, configurable and accountable — the system, content and reporting modules. Reporting is where a school turns its daily data into understanding. Finance reports show collection, dues and expense; attendance reports reveal patterns across classes and terms; examination reports summarise performance; transport reports track the fleet. Because every report draws from the same connected records that staff maintain in the course of their work, the numbers are always current and always consistent — there is no separate reporting exercise, because the reports are simply the live data, organised.
The front CMS gives a school a public face: a website with news, events, a gallery and pages, managed from within the same system that runs the school, so that what the public sees is maintained without a separate web project. The download centre lets a school share study material, notices and video tutorials with students and parents. The annual calendar holds holidays, events and the academic year in one view, and the student CV module lets a student build and download a record of their achievements. Together, these content modules mean a school's outward communication and its shared resources live in the same connected platform as everything else.
Underpinning all of it is a system layer that a school configures to its own needs: roles and permissions that control who sees what, custom fields that adapt records to a school's particular requirements, settings for print headers, notifications, payment and more, and audit trails and user logs that record who did what. This is the layer that lets one platform serve a small school and a large trust equally well — flexible enough to fit each school's way of working, controlled enough to keep sensitive data safe, and accountable enough that a school always knows how its system is being used.
If there is one area where school management software proves its worth or fails, it is fees, and Shiksha CRM's finance modules are built to prove it. Fee collection is the beating heart of a school's finances, and it is also, done manually, one of its greatest sources of lost time and lost money. The fees module handles the full complexity of how Indian schools actually charge: multiple fee heads, instalment schedules, discounts, fines, transport and hostel fees, and carry-forward of dues from one session to the next. Fees are assigned to classes and students, collected through cash, UPI, cheque or bank, and each collection generates an instant, numbered receipt while updating the student's dues in the same moment.
Crucially, receipts are immutable. Once issued, a receipt cannot be quietly edited — a correction is made through a reversal entry, leaving a clean and auditable trail. This is the kind of financial discipline that protects a school, ensuring that its records can withstand scrutiny and that money cannot go missing through a silently altered entry. Dues are tracked continuously, so at any moment the school knows exactly who owes what, and reminder cycles send those defaulters automatic WhatsApp messages — turning the dreaded work of chasing fees into an automatic process that measurably improves collection.
Around fee collection sit the income and expense modules, which give a school a complete financial picture. Miscellaneous income is recorded against heads; every expense is categorised and tracked; and the finance reports draw all of it together into daily and monthly collection summaries, class-wise due lists, income-versus-expense views and balances. Because every figure comes from the same live records that staff maintain in their daily work, the school's financial reporting is always current and always consistent — and a principal or trustee can see, at any moment and without a special exercise, exactly where the school's finances stand.
It is worth pausing on why the all-inclusive model is not just cheaper but genuinely better for how a school operates. Schools grow and change. A school that today collects fees on paper may in a year decide it wants WhatsApp reminders; a school without buses may start a transport service; a school managing exams in spreadsheets may finally want a proper examination module. In a feature-gated system, each of these ambitions triggers a negotiation, an upgrade, a new cost and often a new integration headache. In Shiksha CRM, the capability is already there — the school simply starts using it. There is no procurement cycle standing between a school and its own improvement.
The all-inclusive model also removes a subtle but real drag on adoption. When features cost extra, staff hesitate to explore them, administrators ration their use, and the software is never used to its full potential. When everything is included, staff are free to discover what helps them, and the system becomes more valuable the more it is used. A school that knows it has already paid for the whole platform uses the whole platform — and a school that uses the whole platform runs measurably better than one that uses a fraction of a system it is afraid to fully switch on.
Finally, one price for everything makes budgeting honest. A school knows exactly what it will pay for the year, with no surprise invoices when it turns on a feature or crosses a usage threshold on an add-on. For an institution that plans its finances a year at a time and answers to a trust or a board, predictability is itself a feature. Shiksha CRM's pricing reflects only one variable — the number of students — so a school always knows where it stands.
No add-ons, no upsells. Book a demo and see the whole platform.