Solutions · Education
School app and ERP: what to decide, build and test.
Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.
Decisions to make before you brief a school app
Most school software projects go wrong before design starts, because the school has not settled who is allowed to see what. Settle these forks first.
- One campus or a group. A single campus can run on one database with classes and sections. A trust with several campuses needs per-campus admins, shared reporting for the trustees and separate fee heads. Building for one and extending later usually means re-doing the permissions.
- Replace your ERP or sit on top of it. If the office already keeps marks and fee ledgers in older software, a parent app that reads from it is faster to launch but inherits its data quality. Replacing it gives one source of truth but means a migration, which is where most delays come from.
- Fees collected through the school's own account or a gateway settlement. Either way the money should reach the school's bank account through an RBI-authorised payment aggregator, not a personal account. Decide who reconciles, and how concessions, siblings and late fees are recorded.
- Bus tracking by driver phone or by GPS device. A phone running the driver app is cheap but depends on the driver. Fitted devices are steadier but cost hardware, SIMs and fitting per bus.
- Who sends circulars. If any teacher can broadcast to every parent, the feed fills with noise. Decide the approval chain, and whether parents can reply or only read.
Bring answers to these to the first call:
- Number of campuses, classes, sections and students
- Who approves a fee concession and who can see the ledger
- Where student records live today and in what format
- Whether bus tracking is in version 1
- Languages parents actually read
- One named person in the school office who can decide quickly
What the first term should include, and what can wait
| Module | First version | Add later | Why |
|---|---|---|---|
| Student records | Import of class lists, guardians and phone numbers | Transfer certificate and document vault | Everything else hangs off clean records |
| Attendance | Daily class attendance, parent notification | Period-wise and staff attendance | Daily is what parents ask about |
| Fees | Fee heads, instalments, UPI payment, receipts, dues list | Late-fee automation, scholarship workflows | Cash flow is the office's biggest pain |
| Circulars | Class and school-wide notices, read status | Two-way parent chat | Replaces the WhatsApp groups without moderating chat |
| Homework | Post and view by class | Submissions and teacher feedback | Posting is easy; grading is a different product |
| Report cards | Marks entry, one report card template | Several boards or grading schemes, remarks library | Each template needs sign-off by the principal |
| Admissions | Enquiry form, application, document upload, status | Entrance test scheduling, interview slots | Often the first thing the website must do |
| Bus | Route list, stop alerts from driver phone | Fitted GPS devices, route optimisation | Prove parents use it before buying hardware |
| Timetable | Class timetable display | Auto-generation, substitution | Generation is a hard scheduling problem |
How the 8 to 10 weeks run, and what you supply
| Weeks | What we build | What you supply |
|---|---|---|
| 1 | Scope, roles, data model, screens for parent, teacher and office | Fee structure, class list, sample report card, school logo and colours |
| 2–3 | Records import, login by phone number and OTP, attendance | A test export of student data from the current software |
| 3–5 | Fees, receipts, circulars | Payment aggregator account and bank details; a few dummy fee cases |
| 5–7 | Homework, report cards, admissions form and website | Campus photos, text, board-approved marks format |
| 7–8 | Bus alerts if included, parent app polish | Route and stop list; two or three drivers to test |
| 8–10 | Pilot with one class, fixes, staff training, go-live | Teachers and office staff for training; parent communication |
Plan go-live for the start of a term, and pilot a single class two weeks earlier. Keep the old process running in parallel for the first fee cycle.
Our concept build Chalkline shows the school website side of this. The school app guide lists what to build first.
How we work with you each week
The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.
- Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
- Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
- Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
- Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
- One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.
The full version, including how the beta and user testing work across every kind of project, is on our process page.
The beta: one class, before the term starts
The beta is the single-class pilot in weeks 8–10, about two weeks before the planned term start. It begins once a class's records are imported, attendance reaches parents, and a fee can be paid and receipted without the office correcting it by hand.
- What's in it. OTP login for parents, daily attendance alerts, fee dues, UPI payment and receipts, circulars with read status, homework posting, and the office desk that feeds them. Bus alerts only if they are in version 1.
- What stays out. Report cards until marks are due, admissions, timetable display, two-way chat and anything for other classes. One class keeps every problem traceable.
- Who uses it. One section of 30 to 40 students: their parents (including some who share one phone and read Hindi or the local language), the class teacher, one or two subject teachers, the accounts clerk, and the principal or coordinator who approves circulars. The school invites them; a teacher's own family is not a real test.
- How they get it. Parents install the app through TestFlight or Google Play testing, or use the web version on a shared phone. Teachers and the office use the staff login on school computers and their own phones.
- How long. Two to three weeks, including one fee due date, run alongside the old process. Parents give consent for their child's data before the pilot starts, and the school can withdraw any family at any time.
A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the pilot parents towards that, or use an organisation account.
What we test with real people, and the tasks we set
We set each person one real job and watch them do it on their own phone, in the language they read at home. We don't explain the screen or step in. About five people per role tends to show the serious problems, which we fix before testing again. Moderated sessions use a dummy class with made-up children, so no real child's record is on screen while we watch.
| Who | The task | What we watch for |
|---|---|---|
| Parent | "Pay the second term instalment for your younger child and find the receipt." | Do they pick the right child? Is the amount, including any sibling concession, clear before paying? Can they find the receipt later? |
| Parent on a shared phone | "Check whether your daughter was marked present today and read the notice about the sports day." | Can they log in with OTP without help? Is the notice readable in their language and text size? |
| Class teacher | "Mark today's attendance for 7B before the first bell. Two students came late." | Is it faster than the register? Does a late mark send the right message to parents? |
| Subject teacher | "Post tonight's maths homework for 7B with a photo of the worksheet." | Does it reach only that class? Is the photo readable on a low-end phone? |
| Accounts clerk | "A parent paid at the counter in cash and wants the late fee waived. Record both." | Does the dues list update? Is the waiver logged against the clerk's name and approved by the right person? |
| Principal | "Approve the circular about the PTM and check how many parents have read it." | Is the approval step clear? Are read counts honest about parents who haven't installed? |
The numbers that say it's working
In week 1 the school chooses two or three of these. If the office has a current figure, such as fees still due after the last date, we record it as the baseline. Tracking is built in before the pilot class starts. We report at go-live and again 30 days later. We don't commit to the numbers; we make sure the school can see them.
| Goal | What we measure | Where it comes from |
|---|---|---|
| Parents actually use it | Share of families in the class who have logged in at least once | Login records |
| Notices replace the WhatsApp group | Share of circulars read within a day | Circular read status |
| Fees come in on time | Share of instalments paid by the due date, online and at the counter | Fee ledger and payment gateway |
| The office reconciles less | Receipts that need manual correction | Office desk audit log |
| Attendance reaches home | Time from teacher marking to parent alert | Attendance and notification logs |
| Fewer calls to the office | Parent calls about fees, attendance or notices per week | Office tally kept during the pilot |
What a school app costs, and what moves it
A school app has parents, teachers and an office desk, so it sits in the "two user types plus admin" tier of our app development cost guide, a ballpark of ₹10–25 lakh for a small studio. A school website with admissions alone is much smaller. Treat these as ballparks, not a quote.
- Data migration. Clean class lists import in days. Years of inconsistent spreadsheets take weeks.
- Fee rules. One fee per class is simple. Sibling discounts, transport slabs, concessions and part payments each add logic and testing.
- Bus tracking. Phone-based alerts are modest. Fitted devices add hardware and a monitoring screen.
- Campuses and boards. Each extra campus, grading scheme or report card format adds screens and sign-off cycles.
Running costs are separate: hosting, SMS or notification charges, payment gateway fees and a yearly maintenance budget. See app maintenance cost.
India rules and habits for a school app
- Children's data. The DPDP Act 2023 treats anyone under 18 as a child and generally requires verifiable parental consent before processing their data. The Rules notified in November 2025 exempt educational institutions only where tracking or behavioural monitoring is limited to the institution's own educational activities or the safety of enrolled children. Transport providers engaged by a school are exempt only for tracking location during travel to and from school. Do not reuse student data for marketing or analytics beyond that. Most obligations are phased in, reportedly about 18 months after notification, so design for them now. See our DPDP checklist.
- Fee payments. Collect through an RBI-authorised payment aggregator into the school's account. UPI payments to educational institutions can go up to ₹5 lakh per transaction for verified merchants, which comfortably covers annual fees. Read more in UPI payments in your app.
- Tax. A school's own education services and supplementary coaching are treated differently under GST. Ask your CA how your receipts should be raised.
- Languages and phones. Many parents use one shared Android phone and read Hindi or a regional language at home. Offer OTP login, large text and a web version. See regional language apps.
- Habits. Parents expect the app to be where the school's WhatsApp groups were. Retire the groups on a stated date or they will survive.
This is general information, not legal advice. Confirm consent, fee and tax treatment with a lawyer or CA before launch.
Common school app mistakes and what to do instead
- Starting without clean records. A parent seeing the wrong child's attendance ends trust fast. Audit the class lists before building, and verify phone numbers with a test message.
- Launching mid-term. Parents are in routines. Launch at term start, with one pilot class first.
- Treating consent as a checkbox. For under-18s the parent is the person who consents. Record who agreed, to what, and when, and keep marketing separate from school communication.
- Tracking more than the safety purpose needs. Show bus location only for the child's own route and only during travel hours.
- Overbuilding the first release. Timetable generation and a learning platform can wait. Fees, attendance and notices are what get parents installing.
- Ignoring the office. If office staff find the desk slower than the register, they will enter data late. Test it with them, not the principal.
- One shared admin login. Give every staff member their own login and role so changes to marks and fees are traceable.
- No plan for the first fee cycle. Run old and new in parallel, and reconcile every receipt for one full cycle.
Cost and timeline
8–10 weeks for a first version.
Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.
- Number of campuses, classes and students
- Bus tracking hardware or phone-based tracking
- Fee structures, concessions and instalments
- Migration from your current software
- Languages for parents
Questions
About your school app and erp.
How much does a school app cost in India?
It depends on the number of campuses and students, fee rules, bus tracking and whether you are moving data from old software. We give a fixed quote within 48 hours of your brief. Our school app guide explains what to build first.
Can parents pay school fees through the app?
Yes. Parents pay term fees by UPI or card, in instalments if you allow it, and get a receipt instantly. Admin sees who has paid without matching bank statements. Reminders go out before each due date. Concessions are applied automatically.
How long does it take?
A school website, parent app and teacher desk usually take 8 to 10 weeks. Plan the launch for the start of a term so parents adopt it from day one. We also help import student records and train office staff before go-live.
Will it work on parents' low-cost phones?
Yes. The parent app is light, works on older Android phones and can run as a web app for families who don't want to install anything. Circulars and fee receipts stay readable even when the data connection is slow, and text sizes can be enlarged for grandparents.
Who owns the school's data?
The school does. Code, designs and all student and parent data are handed over, and you choose where it is hosted. We also help you plan consent and privacy; see our DPDP checklist. Nothing is locked to our servers, and any team can extend it after hand-over.
Read next
- EducationSchool apps and ERP: what parents and teachers actually use →A plain guide for Indian private schools choosing a school app and ERP: admissions, fees by UPI, attendance, homework, report cards and bus tracking that parents use.
- ComplianceThe DPDP Act for app owners: a practical checklist →What India's Digital Personal Data Protection Act means for your app or website: notice, consent, data rights, children's data, security and breaches, in plain words.
- LanguagesBuilding apps in Hindi, Tamil, Kannada and other languages →How to build an app or website in Indian languages: scripts and fonts, longer text, voice input, transliteration, lakh and crore formats, and translation that sounds right.
Start a project
Tell us how your business runs. We'll build what it runs on.
Four taps, about a minute. Fixed quote within 48 hours.


