What institutions ask before they switch.

We move your student, staff and fee records across for you, from your current system or from the spreadsheets and registers your office keeps. Fee heads and discount rules are mapped, and opening balances are reconciled against your ledger before anything is switched on.

Your office runs a short parallel period, entering real work in both systems, before the old one is switched off.

Core onboarding and go-live take about one week, provided your data reaches us on time. Larger groups go campus by campus, usually starting with the one whose data is cleanest.

Yes, and most institutions do. We set up the running session, bring dues and marks up to date, and move fee collection to Acado from a fixed cut-off date so no receipt is issued twice.

We do, by role. The fee clerk learns the fee desk, class teachers learn attendance and marks, the principal learns approvals and reports. Sessions run on site or remotely, and a recorded session covers staff who join later.

Schools (day-scholar and boarding), nursing and paramedical colleges, degree and engineering colleges, and groups that run several of these. Modules and workflows are configured per institution, so a primary school and a nursing college can run on the same platform with different setups.

No. Most institutions start with admissions, student records, attendance and fees, and switch on transport, hostel, library or gate pass when they need them. Everything works from the same record, so adding a module later never means re-entering data.

Yes. Each campus runs its own day, and the group office sees admissions, collection and attendance across all of them on one dashboard, with shared fee policies where you want them.

Parents pay online through Razorpay or PayU, and payments post straight into the fee ledger. Attendance works with ESSL and ZKTeco biometric and face devices, and with manual marking by the class teacher. If you have a device from another maker, send us the model number before you sign.

One app for parents, students and staff, on Android and iOS (Google Play and the App Store). What each person sees depends on their role: a parent sees their own children, a teacher sees their classes, an administrator sees what their permissions allow.

SMS carries what must arrive: attendance alerts, fee reminders and exam and result notices.

No. The apps and the web system need a connection, and there is no offline mode. When the line is down, attendance and marks are taken on paper as today and entered once it is back.

Acado Assistant, which answers plain-language questions from your live data, is in development and not yet available to clients. When it launches it will be an optional add-on, read-only and limited to what each person's role already allows.

Your institution does. Records are kept separate from every other institution, encrypted in transit and at rest, backed up daily, and visible inside your institution only to the roles you allow.

If you leave, you get a full export of your records. Ask us to write this into your agreement.

Acado is cloud-hosted and managed by us, so there is no server for your office to maintain, update or back up.

An annual licence based on student numbers and the modules you use, plus a one-time setup fee for configuration, data migration and training. You get a written proposal with each line itemised before anything starts.

Hosting, the modules you have licensed, product updates as they ship, and support from a named contact who knows your setup.

A named contact who knows your setup, on call and remote during working hours, with an arrangement for urgent issues outside them. Requests can also be raised from inside Acado. Fee days, results days and the first week of a new session get priority.