Enrolment, scheduling, billing, staff, reporting and data protection: the seven systems a small or mid-sized school runs, what breaks when they are separate tools, and what an administrator should expect from a platform that claims to replace them.
This guide is for the person who runs the school day to day: the administrator, the operations manager, the owner who is also the administrator because there is nobody else. It applies to independent schools of any kind at the size where one person can still see the whole thing: language schools, tutoring and exam-preparation centres, private academies, training providers, online schools, after-school programmes. It is not written for a district IT department or a university registrar; those have their own vocabulary and their own vendors.
Administrators buy software differently from heads and owners. A head asks what it will do for teaching; an owner asks what it costs. The administrator asks what happens on the Tuesday morning when a parent emails to say the invoice is wrong, the teacher is off sick and the timetable needs to change, and a new student has to be enrolled by lunchtime. Every claim in this guide is written for that Tuesday.
The guide is organised around the seven systems a school runs and the two it grows into. Four of the clusters are already published and linked below; the others are being written to the same depth. Where SprintUp fits, the guide says so with the plan and the price. Where it does not, it says that too.
The vendors in this market use three terms that overlap and are rarely defined. A student information system (SIS) is the administrative record: who is enrolled in what, who has paid, who attended. A learning management system (LMS) is where the teaching lives: courses, activities, assignments, grades. School management software is what small schools ask for when they want both, plus the website, the payments and the reports, without paying for an integration between them. Large institutions run an SIS and an LMS as separate products from separate vendors and employ someone to keep them in step. Small schools cannot, which is why the question that matters is not which features a platform has but whether the student exists once inside it.
Underneath the acronyms, every school runs these seven:
The enquiry, the application, the offer, the payment and the portal login. Where a prospective student becomes a record.
Which class, which teacher, which room or link, which hour; and who was actually there. The most-edited data in the school.
Courses, activities, homework, assessment and grades. The LMS layer, and the part teachers touch every day.
Programme pages, enrolment forms, the school's own domain. Where local search and first impressions happen.
Invoices, instalments, failed cards, arrears, refunds. The system most schools run in a spreadsheet and a bank statement.
Enrolment, revenue, attendance, progress. What the owner asks for on Friday and the administrator assembles on Thursday night.
What you hold about children and families, where it lives, who can see it, how you delete it. A legal obligation, not a feature.
When these are separate tools, the student exists in each one and the administrator becomes the integration. A change of class made in the LMS does not reach the invoice; a withdrawal recorded in the spreadsheet does not reach the website's enrolment count; a parent's new email address, updated in the payment tool, is still wrong in the one that sends the reports. None of these is a disaster. All of them, weekly, are the administrator's job, and they are the reason the role burns people out.
Schools that set up a platform in the wrong order spend the first term undoing it. The order that works is the order in which each thing depends on the last: the school's structure (programmes, levels, terms), then the classrooms and the teachers who run them, then the public website and its enrolment forms, and only then the students, who arrive through the forms into classrooms that already exist. Setting up students first, because they are the urgent thing, produces a hundred records that all need editing when the structure is finally decided.
The Getting started cluster walks through the campus setup in that order, with the school-structure decisions that are hard to change later and the website setup that makes the enrolment pages work. On SprintUp the whole sequence runs inside one campus and a school can be operational in a day; the guide is honest about which parts take a day and which parts take a term to get right.
Enrolment is the flow that decides whether the school grows, and it is the one most often held together by email. A parent enquires; someone replies with a PDF; the parent fills it in and sends a photo of it; someone keys it into a spreadsheet; an invoice is raised in a different tool; the login is created in a third. Each hand-off is a place where the family compares you with a school whose form took four minutes. The flow that converts is short and needs no human until the student is in a class: programme page, application, offer, payment, portal access.
The Enrolment cluster covers configuring the student portal, designing the flow so that the payment comes before the login, waiting lists, and the first-cohort checklist that catches the things a form cannot. On SprintUp the application, the payment through Stripe and the student portal are one system, so an enrolled student is a student in a class with a login, not three records waiting to be reconciled.
A timetable is built once a term from constraints — teacher availability and load, room or video capacity, the hours students can attend, term dates and holidays — and then edited every week for the rest of the term as people fall ill, families move and classes merge. The schools that cope are not the ones with the cleverest timetabling tool. They are the ones where the timetable is held in the same place as the classes, the teachers and the students, so that a change made once is a change everyone sees, and the ones with a written policy for what happens when a teacher is absent, decided before the first absence rather than during it.
Attendance is the timetable's evidence. For a school with children and teenagers it is a safeguarding obligation as well as an operational one: a register taken every session, absences followed up the same day, and a pattern of absence visible to someone before it becomes a withdrawal. For an adult or online school it is the leading indicator of churn. A student who missed two sessions in a fortnight is a student who is about to stop paying, and the school that sees it in a report on Friday can call on Monday.
The Scheduling and attendance cluster covers building the term timetable, the register and absence follow-up, and the attendance reports parents and inspectors ask for. On SprintUp, classes, teachers, students and live video sessions sit in one campus; the cluster is candid about which parts of attendance the platform records for you and which parts remain the teacher's job.
Most small schools run fees on an invoice sent by email and a bank statement checked by hand, and they call the result "cash flow". It is not cash flow; it is unpaid work, and it compounds. A family that attends for six weeks without paying has learned that the school does not collect, and every subsequent invoice to that family is a negotiation. The alternative is not a finance team. It is a card taken at enrolment, an instalment schedule written down and agreed, automatic retries when a payment fails, and an arrears policy that is applied in week one, politely, every time.
The other half of billing is what the platform takes. Some school and tutoring platforms charge a percentage of every payment a student makes, on top of the subscription. At twenty students it is a rounding error; at three hundred it is the largest number on the invoice, and it grows with the school forever. Ask that question first of any vendor, and ask for the answer in writing.
Nothing. Students and families pay the school directly through Stripe and SprintUp takes 0% of that payment on every plan, including the free plan. Standard Stripe processing fees apply. Courses, terms, packages and programmes are sold as products you define with your own prices, and the Tuition billing cluster covers invoicing, instalments, failed payments and arrears in detail. SprintUp is not an accounting system; a school with corporate invoicing or more than a handful of staff will still run one alongside it.
A new teacher should inherit the school's way of working in their first week: the curriculum they are teaching, the materials, the assessment format, the attendance and safeguarding policies, and the standard for what parents see. A teacher who is handed a class and a login and left to it will build their own version of all of those, and the school will discover the divergence at the first parents' evening. Allocation is the second discipline: which teacher teaches which classes, at what load, with how many different preparations. Twenty contact hours with three preparations is a sustainable job; twenty with seven produces a resignation in the spring term.
Workload is the reason most teachers leave, and most of it is not teaching. It is preparation — planning lessons, building activities, writing quizzes — and it is marking. Those are exactly the tasks that AI generation and auto-marked assessment compress, and it is the part of the platform we are most careful about claiming, because the claims in this market are mostly unevidenced.
In a one-term pilot at Intellect Academy — our sister school — teachers reported that lesson preparation and grading time fell by roughly half.
That is one school, one term, self-reported, and owned by the same company as SprintUp. It is not a controlled study and it is not a promise of what every school will see. It is the reason the platform was built the way it was, and we are now measuring the same thing with schools that are not ours. The full case study, with what the school is, what was measured and what the freed time became, is in the Staff and workload cluster.
For the classroom practices that sit underneath any workload claim — formative assessment, lesson iteration, questioning — the agile teaching and teacher as facilitator guides are the depth; this pillar is the operations view.
Small schools do not lack data; they lack data in one place. Enrolment lives in the spreadsheet, revenue in the bank, attendance in the register, progress in the teacher's head, and the Friday report is the administrator's Thursday evening. The test of a report is not how much it shows but whether it changes a decision: which class to merge, which family to call, which programme to run again, which teacher is carrying too much. Four numbers that someone acts on beat forty that nobody reads.
SprintUp's school analytics bring enrolment, revenue and learning data together on one dashboard for the school administrator, with separate views for teachers and students. The Reporting cluster covers the reports that actually matter for a small school, how to read the enrolment and revenue numbers together, and how to use learning data to help a student rather than to surveil one — a distinction that matters more the younger the students are.
A school holds more sensitive data than most businesses of its size: names, dates of birth and addresses of children, contact details of parents, attendance, assessment results, sometimes medical or safeguarding notes, and payment records. Under GDPR the school is the data controller for all of it. That does not change when you buy software. The vendor is a processor acting on your instructions; the obligations — a lawful basis, a privacy notice families can understand, a retention policy, the ability to answer a subject access request, and a plan for a breach — remain the school's, and no platform can hold them for you.
What a platform can do is make those obligations possible to meet. Where the data is hosted and under which law; whether every student's data can be exported on request and erased on request; who inside the school can see what; whether there is a processing agreement in writing. Those are the questions to ask any vendor, and the answers should come without a pause.
SprintUp holds data under GDPR with EU data residency, and export and erasure requests can be fulfilled for a school's students; Intellect Education Limited is registered in Ireland. The Data protection cluster covers what student data a school typically holds and for how long, the data-residency and vendor questions, and how to handle export and erasure requests when they arrive.
The second campus arrives when the first is full for two terms, and the operational mistake is to open it as a separate school with a separate website, student list and price list to keep in step by hand. Open it as a second site of the same school: one account, one student record, one set of programmes and prices, with separate branding only where the town or the audience needs it. A school with two sites on one system has one Tuesday morning; a school with two systems has two.
The Multi-site and scaling cluster covers multi-campus setup, when to split into a separate account, and the signals that a school has outgrown its plan. On SprintUp, Academy runs up to five websites on the school's own domains from one campus; Pro allows three, and the free plan one on a SprintUp address. Whether to top up fast-lane credits or move up a plan is its own short guide in the same cluster.
Feature lists are written for owners. Administrators should ask the questions that show up in month six. Does the student exist once? When a class changes, do the teacher, the student, the parent and the invoice all find out, or does someone have to tell them? What does the platform take from student payments, and what is that at your numbers in three years? Where is the data hosted and can every record be exported if you leave? And who do you call on Tuesday morning when something is wrong, and how long do they take to answer?
Where SprintUp fits, stated plainly:
One educator, one class, trying it: the free plan. One educator, ten students, one website on a SprintUp address, live classes, the student portal and unlimited AI generation on the relax lane. No card, and it stays free.
A solo educator with more than ten students: Pro, at €29 a month or €261 a year. Up to fifty students, three websites with your own branding, the fast AI lane with 5,000 credits a month and premium models.
A school with staff: Academy. Every teacher and every student, priced by active students — €99 a month covers the first 25, then €4 each to 100 and €3 beyond. Five websites, 250 fast-lane credits per active student pooled across the school, and 30 days free for up to 25 students. Paying yearly is twelve months for the price of ten.
On every plan: students pay the school through Stripe and SprintUp takes 0% of it; the campus, website builder, live video, student portal, analytics, AI curriculum tools and marketplace are included; data is held under GDPR with EU data residency. Domains are sold separately; prices exclude VAT.
Where it does not fit: SprintUp is not a payroll or accounting system, and it is not built for a school that wants to keep an existing SIS and LMS and add a third product between them. It is for schools that want the student to exist once.
The choosing school software guide has the evaluation checklist, the demo script and the vendor comparisons; the pricing page calculator shows what Academy costs at your student numbers.
Software that holds a school's operational records in one place: students and their enrolments, classes and timetables, teachers, fees and payments, and the reports that come from all of it. It overlaps with a student information system (the record of who is enrolled in what) and with a learning management system (where teaching and coursework happen). A platform that does all three with one student record is what small schools usually mean when they ask for "school management software".
An SIS, or student information system, is the administrative record: who is enrolled, in which class, who has paid, who attended. An LMS, or learning management system, is where the teaching lives: courses, activities, assignments, grades. Large institutions run them as separate products with an integration between them. Small schools cannot afford the integration, which is why they need a platform where the same student record serves both.
Pricing models vary more than prices do: per student, per teacher, per site, flat subscription, or a percentage of fees. The first question is which unit you are charged by, because a per-student price that looks small becomes the largest line on the invoice at scale, and a percentage of fees grows with you forever. SprintUp charges by active students on Academy — €99 a month for the first 25, then €4 each to 100 and €3 beyond — with unlimited teachers and no percentage of what students pay you.
Yes. Data is held under GDPR with EU data residency, and data subject requests — export and erasure — can be fulfilled for a school's students. Intellect Education Limited, the company behind SprintUp, is registered in Ireland. The Data protection cluster covers what a school itself is responsible for as a data controller, which no vendor can do on its behalf.
In a one-term pilot at Intellect Academy — our sister school — teachers reported that lesson preparation and grading time fell by roughly half. That is one school, one term, self-reported, and affiliated with us; it is the reason we built the platform the way we did, not a guarantee of what every school will see. We are now measuring it with schools that are not ours.
Yes. On Academy a school can run up to five websites on its own domains from one campus, with one student record underneath; Pro allows three, the free plan one on a SprintUp address. The Multi-site cluster covers when to run a second campus as a site of the same school and when to split it into a separate account.
AI lesson plans, exit quizzes, differentiation, and course outlines — all on the free plan.
Set up your school free →See what schools getSet up a digital campus in a day: school structure, website, classrooms, teachers and your first students, in the order that works.
Enrolment and admissions that convert: the student portal, application flow, waiting lists and the first-cohort checklist.
Class scheduling and attendance for small schools: timetables, registers, absence follow-up and the reports parents ask for.
Tuition billing without a finance team: invoicing, instalments, failed payments, and collecting fees with no platform commission.
Managing teachers and their workload: onboarding, allocation, and what the platform automates — with what our sister school's pilot found.
School analytics that change decisions: enrolment, revenue and learning data in one place, and what to do with it.
GDPR for schools: what student data you hold, where it lives, your obligations, and the questions to ask any software vendor.
Running more than one campus and knowing when to grow: shared accounts, separate branding, and the signals you have outgrown a plan.
Building school curriculum with AI or adopting it from the marketplace: outlines, lesson plans, evaluating listings, and blending both.
The setup sequence that works: school structure first, then website, classrooms, teachers and students.
The three signals that tell you the free plan is no longer enough, and the upgrade path that follows.
Generation is unlimited on the relax lane on every plan. Credits only buy the fast lane and premium models.