Student Information System for a Small School: What AI Adds

A small school should look for a student information system that holds records, attendance, fees and a parent portal in one place, exports every record in a standard file, and lets you leave cleanly. AI features are worth paying for only where they save staff typing: report drafts, message drafts and record search.

The trap in this market is that AI sits at the top of every feature page while the unglamorous questions decide whether you regret the purchase. Can you get your data out? What happens to fee history on exit? Who sees a pupil's record, and is that logged? Put those first, the AI second, and your shortlist shortens itself. One practical note: many vendors in this space publish no list price. Gradelink's quote page, for example, asks for your school's name, your contact details and the approximate number of students before it emails a quote. So pricing questions below are about how to compare quotes, not about figures I can hand you.

Follow me on Instagram@sagnikteaches

Sort what you need into three piles before opening a demo

Demos are designed to show the features the vendor is proud of. Walk in with your own list instead.

Connect on LinkedInSagnik Bhattacharya

Must-haves: if one is missing, drop the system

• Pupil records with guardians, emergency contacts, medical notes, consents and a change history.
• Daily attendance and lesson attendance, with absence reasons you can report on.
• Role-based access: a classroom teacher sees their class, the office sees contacts, the head sees everything, and every view of a sensitive record is logged.
• Fee billing with statements, part-payments, sibling discounts and a record of what each family paid and when.
• A parent portal or app for attendance, reports, messages and bills.
• A full data export you have tested, not promised.

Should-haves: valuable, but you can work around them

• Report-writing tools with comment banks and a template for each year group.
• Timetable and cover tools. A school with fewer than 10 teachers can often run these on a shared calendar.
• Integrations with your accounting package, payments provider and email.
• Admissions and enquiry tracking.

Nice-to-haves: do not pay extra until you have used the basics for a year

• Predictive analytics or "at risk" flags.
• AI chatbots for parents.
• Behaviour-point systems and wellbeing dashboards.

A school of 150 pupils with nine teachers needs the first pile completely and about half of the second. Almost nobody at that size needs the third pile on day one.

Subscribe on YouTube@sagnikteaches

A worked comparison: scoring three quotes for a 150-pupil school

This is an illustration. Say a school of 150 pupils, with nine teachers and two office staff, gets quotes from three vendors. Names are left out on purpose, because the point is the method. Score each system from 0 to 3 on every row, multiply by the weight, and add up.

System B has the best parent portal and the best AI features, and ranks last. Its export scored 1 because the demo could only produce a pupil list, not fee history or attendance, and its exit terms scored 1 because the contract asked for 90 days' notice with data deleted after 30. A and C tie at 52, so the tie-break is price over three years, including onboarding and any per-module charges. That tie-break is also where a lower sticker price often reverses: ask each vendor for the three-year total with the same pupil count and the same modules.

Records, billing and the parent portal: what to test in the demo

Ask the vendor to do these in front of you, with a sample school rather than their showcase one.

1. Create a pupil with two households. Separated parents each need their own contact details, their own portal login and possibly different permissions. If the system cannot model this, you will end up keeping side notes.
2. Record a late arrival and a part-day absence. Then run an attendance report for the month. Watch whether it counts the part-day correctly.
3. Raise a term's fees for a family with three children, one with a 10 per cent sibling discount. See how the statement reads for a parent who is not good with figures.
4. Take a part-payment, then reverse it. See whether the history shows both entries. A system that silently deletes the original is a system you cannot audit.
5. Log in as a parent on a phone. What does the parent actually see: grades only, or the free-text comment a teacher wrote about their child?

Run the same five steps with each vendor, so you compare like with like. Then ask what the parent portal costs: some vendors charge per family, some include it, and some charge for the mobile app separately.

Integrations: the four connections a small school uses

Integration pages run to dozens of logos. A small school usually needs four, and each one can be tested during a trial rather than taken on trust.

• Accounting. Fee invoices and payments should reach your accounting package without retyping, through a direct link or a scheduled export. Ask to see a week of fees arrive in the accounts with sibling discounts and refunds as separate lines, not netted off.
• Payments. If parents pay through the portal, find out which payment processor sits behind it, what it charges per transaction and whether each payout is matched to a family automatically.
• Staff sign-in. Single sign-on with the Google or Microsoft accounts staff already use means one fewer password, and one place to switch off a leaver on their last day.
• Classroom tools. If teachers set work in a learning platform, ask whether the system supports OneRoster, the 1EdTech standard for exchanging class lists and grades between a student information system and a learning management system, either as CSV files or through a live connection. Without it, someone rebuilds every class by hand at the start of each school year.

Illustration: a 150-pupil school whose office administrator spends, say, two hours a month copying fee payments into the accounts gets those hours back from a working accounting link. That is worth more to her than any AI feature on the page, so score integrations on what the school uses today, not on the length of the logo wall.

AI features versus marketing claims: how to tell them apart

A vendor's feature page will say "AI-powered" next to things that are plain automation or a search box. Use this test on each claim: what comes out, who checks it, and what does it replace?

A sample test: the report comment

Ask the vendor to produce a report comment from this input, live, with the same data entered each time:

Pupil: Year 5, [first name], reading age 1 year ahead, maths steady, struggles to start
written work, works well in pairs, improved attendance this term (96 per cent from 88).
Tone: warm, specific, two sentences, no comparison with other pupils.

Illustrative output: "[First name] is reading well above expectations and shows real confidence in paired work. Starting written tasks remains the next step, and the improvement in attendance this term has clearly helped." What to fix: the draft often adds an invented example ("especially in the class novel") that the teacher never mentioned. Any AI report tool that does this regularly should be switched off or tightly edited. Count how many of five drafts include something you did not supply. Zero or one out of five is workable; three or more means the tool creates more checking than it saves.

Also ask where the text goes. Does the vendor send pupil data to a third-party model provider? Is that provider barred from keeping or training on it? Get the answer in the data processing agreement, not in a sales call; what to check in an AI vendor's data processing agreement lists the clauses.

Data export and exit terms: the part to put in writing

Schools do switch systems, often after a vendor is bought or raises its prices, and the contract you sign now decides how painful that day is. AI vendor lock-in and data portability covers the general case; for a school, these are the clauses.

• Export format. A standard, openly readable format (CSV for tables, PDF for reports) for every record type: pupils, guardians, attendance, grades, comments, fee ledger, documents, message history.
• Test export during the trial. Ask for a full export of a sample school and open it. A common failure: the export contains the pupil list but attendance is only a summary percentage.
• Export during the contract, on demand, not only at the end and not for an extra fee.
• Notice period and renewal. Look for auto-renewal with a long notice window. Put a calendar reminder 120 days before the renewal date.
• Deletion. A written commitment to delete your data after exit, with the date and a confirmation.
• Price changes. A cap on annual increases, or the right to leave if the increase exceeds it.
• What happens if the vendor closes. Checks before you commit covers escrow and export rights.

Realistic mistake: the fee ledger that did not come out

Illustration. A small school moves systems at the start of a new year and exports pupils, guardians and grades. The old system is cancelled. In January a family disputes a deposit paid two years earlier. The ledger is gone because the export covered only the current balance. The fix is cheap and has to happen before cancellation: export the full fee ledger by family, including payments, refunds and adjustments, and keep a second copy with your accountant.

Cost: what to ask so quotes can be compared

Vendors package differently, so quotes arrive in incompatible shapes. Ask every vendor to quote on the same sheet.

• The pupil count you will have at the start and in three years (say 150 and 190).
• Included modules, itemised. Attendance, billing, parent portal, reports, AI add-ons and mobile app.
• One-off fees: set-up, data import, training, a custom domain.
• Payment fees. If the system takes fee payments, what does the processor charge, and who pays it, you or the parent?
• Support hours and response time, and whether phone support costs extra.
• Price at renewal for years two and three.

Then compute a three-year total for each. A system that is cheaper in year one but doubles at renewal tells you more than a headline figure. A small-business scorecard for vendors gives you a ready layout if you want one.

Three types of small school and what each should prioritise

A 60-pupil independent primary

The office is one person. Billing and the parent portal matter most, because every fee query lands on her. AI helps most with message drafting and a search box she can ask in plain English. Skip timetabling and analytics.

A 200-pupil school with a secondary section

Timetabling, cover and subject-level attendance become real jobs. Insist on lesson-level attendance, a grades history by subject, and role-based access, since more staff now touch records. AI report comments save teachers the most time here because each teacher writes dozens.

A specialist school: music, languages or sport

You may not need a general SIS. Part-time pupils, group lessons and term-time bookings suit a scheduling product more than a full school system. If you run music lessons, how a music school uses AI for lesson notes and parent emails shows what that job looks like. Be honest about whether you are a school or a lesson business; the software categories differ.

An email to send every vendor before the demo

Sending the same questions in writing gives you answers you can compare and keep. Here is a filled-in version for a school of 150 pupils; edit the figures to match yours.

Subject: Questions before we arrange a demo

We are a school of about 150 pupils (190 in three years), with nine teachers and two office staff.
Please answer in writing:

1. Please quote for attendance, fee billing, parent portal and report writing, itemised, for
   150 and 190 pupils, with year-two and year-three prices.
2. Which AI features are included and which cost extra? For each, which third-party model
   provider receives pupil data, and is it barred from keeping or training on it?
3. Can we export every record type (pupils, guardians, attendance by lesson, grades, comments,
   fee ledger, documents, messages) in CSV or PDF at any time, free of charge?
4. Can you give us a sample export from a demo school before we sign?
5. What is the notice period, the renewal term and the cap on annual price increases?
6. When we leave, how long until our data is deleted, and will you confirm in writing?
7. Where is our data stored, and who at your company can see it?

Two things to watch in the replies. First, vague answers to question 2: "we use industry-leading AI partners" is not an answer. Second, a refusal on question 4. A vendor who will not show a sample export is telling you something about the day you want to leave.

Realistic scenarios to test AI claims against

Besides the report comment, run two more short tests, because they reveal different weaknesses.

A natural-language search test

Ask the system five office questions in plain words and compare the answers with a count you do by hand. Illustrative set: "Which pupils have been absent three or more days this month?", "Which families have an unpaid balance over $200 for more than 30 days?", "Which Year 4 pupils have a peanut allergy?", "Who has not returned the trip consent form?" and "How many late arrivals did Year 6 have last week?" A good system gets four of the five right and tells you when it cannot answer. A poor one answers all five confidently, and two are wrong. Wrong answers with confidence are the danger, especially for the allergy question.

A parent message test

Give the drafting tool this brief: "Letter to Year 3 parents: trip to the museum moved from Tuesday to Thursday, same cost, new consent forms not needed, deadline for dinner choice Wednesday." Illustrative good output is four sentences with the new date up front and the deadline in bold. What to fix is usually the opening, since the tool tends to apologise at length for a change that needs one line. Time the whole job: if drafting plus editing takes less than five minutes against your usual ten, the feature is earning its place.

A children's data check

Whatever the feature, ask: is any pupil name, grade or medical note sent outside the vendor's own system to produce this text? If yes, who is that provider, and is it covered by the same agreement? Children's records are the most sensitive data your school holds, so a vague answer here should count against the vendor more than any missing feature.

Access and permissions: a test that takes ten minutes

In a small school, one person often wears several hats: the head teaches, the office manager is also the safeguarding lead, and a parent volunteer helps with the library. Role-based access is where this goes wrong. Create four test users in the trial (a classroom teacher, a teaching assistant, an office administrator and a volunteer) and try to open the same pupil's medical note as each. Then ask the vendor to show the access log for that record. If the log cannot say who opened it and when, you cannot answer a parent who asks who has seen their child's file. Also check what happens when a member of staff leaves: can you switch off their access in one place, on the same day, without deleting the notes they wrote?

Illustration: a school of 150 pupils has an after-school club run by an outside provider. The provider needs a register and emergency contacts for that club only. A system that can only grant access to a whole year group, not to one club, forces a choice between over-sharing and printing lists. Ask about this case specifically.

Roll-out: moving staff and parents without losing a term

1. Weeks 1 to 2: clean the data in the old system first. Merge duplicate guardians, fix misspelt names, and agree one format for dates. Garbage imports stay garbage.
2. Weeks 3 to 4: import a copy and have the office and two teachers test it with real tasks.
3. Weeks 5 to 6: run both systems side by side for attendance only. A mismatch between the two is a bug to find now.
4. Switch at a term boundary. Keep the old system read-only for six months, and keep your exported ledger.
5. Tell parents a week early with a one-page guide and a screenshot of the first login.

How to check it worked after one term

Measure four things: hours the office spends on attendance and fee chasing each week (compare with the old figure), parent portal log-ins as a share of families, the number of corrections to AI-drafted text (aim for editing, not rewriting), and complaints about missing data. If the office hours have not dropped, the system is not set up well, not necessarily the wrong system.

For more on the wider job list, five education workflows to automate first sets the SIS in context.

Questions small-school buyers ask about SIS software

Is a free student information system good enough for a small school?

It can be for a school under about 50 pupils with simple billing. Check three things first: who owns the data, whether you can export everything in one file, and how the free tier is paid for. If the answer to the last is advertising or selling data, walk away.

Do I need an SIS if I already use spreadsheets?

Usually yes once you pass about 60 pupils or add a second adult who edits records. Spreadsheets fail on permissions, history and parent access, not on size. The trigger is the first time two people overwrite each other's changes.

Can the AI features in an SIS replace a teacher's judgement?

No. Treat any grade, risk flag or attendance prediction as a prompt to look, not a decision. The useful AI features save typing: report drafts, message drafts and search across records.

How long does moving to a new system take?

For a school of 100 to 300 pupils, plan a term for a careful move: data export and clean-up, a test run alongside the old system, then a switch at a natural break such as a new term. Quick switches mid-term tend to lose attendance and fee history.

Further reads

• Parents' Evening Booking System: Slots, Reminders and Clashes With AI — Slots, reminders and clashes for parents' evenings.
• Questions to Ask an AI Vendor Before You Sign Anything — General questions to put to any AI vendor.
• How to Check an AI Software Vendor's Customer References — How to call a vendor's existing customers.
• SOC 2 and ISO 27001 Explained: Checking an AI Vendor's Security — Reading a vendor's security certificates.
• What Uptime and Support Should an AI Vendor Promise You? — What uptime and support to ask for in writing.
• Tutoring Centre Admin With AI: Enquiries, Timetables, Invoices — Admin for tutoring centres, a close cousin of small schools.
• Independent Educational Consultant Software: An AI-Built Tracker — Build a student and deadline tracker in Google Sheets with AI help: tabs, working formulas, a weekly digest, parent update emails and consent.
• How to Start a Language School: Accreditation, Agents and AI — What a new language school costs in year one, how accreditation and agents fit together, and where AI saves admin time from the first term.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Gradelink quote page, vendor product and pricing pages read November 2026. Several school-software vendors publish no prices, so none are quoted for them.