School management software: a checklist for private schools

The situation: one office, five kinds of paperwork

Walk into the office of a private school in March and you will see the whole year in one room. The admissions counsellor has a notebook of enquiries. The class teachers' attendance registers are stacked on a shelf. The accounts counter has a receipt book, a ledger and a spreadsheet of instalments. Report-card templates sit on one computer, and notices go out through printed circulars and a few WhatsApp groups.

Each of these works on its own. The trouble starts between them: the same student is written down in every book, a change in one is not seen in the others, and the owner who asks "how are we doing this term" gets five partial answers.

The tension: every vendor says "all-in-one"

Most school software is sold with a long list of modules. The list is rarely the problem. The problem is that a list does not tell you which parts work today, which are half built and which are a plan, and it does not tell you what happens to your data.

The insight: buy for the work, not the list

A useful way to choose is to start from the work your office does every day and check each part against it. The checklist below follows that order.

Admissions and student records

• Can an enquiry move through application, visit and admission in one place?
• When a child is admitted, does the record start from the enquiry, or is it typed again?
• How does it handle a family that already has a child in the school?

Attendance

• Can a teacher mark a whole class in one pass?
• Does the monthly percentage divide by working days, with holidays left out?
• What happens when a register is not taken?

Fees and receipts

• Fee plans with instalments and concessions.
• Numbered receipts that cannot skip a number.
• An overdue list that comes from the ledger, not from someone's spreadsheet.
• Whether online payment is connected today, and what it costs.

Marks and report cards

• A marks grid with codes for absent or exempt students.
• Grades worked out from your school's scale.
• What happens when a mark is corrected after results are published.

Notices to parents

• Can you see the exact recipient list before sending?
• Are families who opted out left out automatically?
• Is delivery real, or simulated, today?

The decision: ask for states, not promises

For every module on the list, ask the vendor to write down one of three states: built, partly built or planned. Then ask to see the built ones on a walkthrough with demo data. A vendor who cannot separate the three will not be able to tell you later why something does not work.

Ask two more questions before you sign:

1. Where will our data live? A school holds children's records. Find out which country the server is in and what moves before real data is loaded.
2. Who builds it and who answers? You want a company and a person you can call, not only a support form.

The evidence: how Campus One answers the checklist

We publish the same states for Campus One that we ask you to demand from anyone. Today, in the demo with a made-up school:

The demo runs on a server in the USA with made-up data only; before any real school data is loaded, Campus One moves to a server in India. It is built by AskShiva Private Limited, whose leadership team is Divya Prakash Jha (Chief Executive Officer), Vaibhav Jain (Chief Operating Officer) and Zeeshan Khan (Chief Marketing Officer), and the contact page lists the phone numbers and email of a person who answers.

The outcome: a shorter, honest shortlist

Using the checklist usually shortens the shortlist quickly. Software that cannot show its built parts on demo data, or cannot say where the data lives, drops out. What remains is a comparison you can defend to your trustees: the same work, checked the same way, with the gaps written down.

Go deeper: one guide for each step

Each part of the checklist has its own guide, written the same way: the problem in a real office, the rule that fixes it, and what Campus One does today.

• Admissions: the admissions pipeline, from first enquiry to admission
• Attendance: counting working days right in the attendance register
• Fees: instalments, receipts and follow-up at the fee counter
• Marks: from the marks grid to the printed report card
• Question papers: setting a paper from a blueprint that adds up
• Notices: what to plan before sending notices on WhatsApp
• The store: stock, assets, purchases and audits
• Logins: who should see what in a school office
• History: audit trails for marks, receipts and stock
• Data: where a school's data should be stored
• AI: where AI belongs in a school office, and where it does not
• Alternatives: spreadsheets, accounting software or a school system
• Price: what school management software costs in India
• Moving: from registers and spreadsheets to one system
• Trying it: a 30-day pilot plan, week by week

The takeaway

Choose school software by walking through your own office's day and asking, for each step, "is this built today?" Then look at the Campus One product page, where every part carries its state, and ask us for a walkthrough on the demo school.