School management software in Australia for independent and Catholic schools

Who actually buys school software in Australia?

Mostly independent schools and Catholic schools or systems, because government schools generally run on systems their state department provides. That changes the conversation. A government school principal rarely chooses a student information system. An independent school business manager does, and a Catholic diocese or system authority often decides for its schools.

So this page is for three readers: the business manager or principal of an independent school, the ICT lead of a Catholic system, and the vendor building for either. The decisions they share are which platforms to run, how to connect them, and what to build where the platforms stop.

What do Sentral, Compass, TASS, Synergetic and SEQTA each cover?

They split broadly into school management systems that run administration, and learning platforms that run teaching, and most schools run one of each. The boundaries blur as vendors add features, so treat this as a starting map, not a verdict.

Platform	Broad role	Notes
Sentral	School management system	Lists solutions for independent and government schools, plus integration partners
Compass	School management system	Lists independent, Catholic and government school solutions and integration partners
TASS	School management system	Admin, finance, parent and staff portals, analytics and API integrations
Synergetic	School management system	Academic, operational and administrative workflows, finance to HR; now part of Tes
SEQTA	Learning management system	Learning, wellbeing and attendance; now part of Tes
Schoolbox	LMS and school portal	Learning, community portal, pastoral care
Canvas	LMS	Teaching, assessment and course delivery

The gaps between them are where schools feel pain: an enrolment process that lives in forms and spreadsheets until the student is accepted, reporting that needs data from both the SIS and the LMS, and staff tools that no single vendor provides. Each of those is a sensible custom project, built on the vendors’ APIs rather than around them.

How should enrolments, waitlists and fees work?

An enrolment portal should take a family from first enquiry to a confirmed place, and then hand the record to the SIS, without anyone retyping it. Independent schools often run years long waitlists, entry interviews, scholarship tests and sibling priority. Most SIS enrolment modules are built for the student who has already been accepted.

A portal that fits:

1. Enquiry and tour booking, with the source tracked for marketing.
2. Online application with document upload: birth certificate, reports, NAPLAN results, custody orders where relevant.
3. Waitlist by year of entry, with priority rules such as siblings and staff children applied consistently.
4. Interview and assessment scheduling.
5. Offers with deadlines, acceptance and deposit payment.
6. Automatic creation of the student and family records in the SIS, with fee billing set up.

Fee billing usually stays in the SIS finance module, connected to accounting. The custom portal handles everything before the student exists in the SIS, which is the part families see first.

What reporting must your data support?

Census, NCCD and your board, every year, from data that should already be clean. NCCD’s 2026 key dates list 7 August as Non-government Schools Census day, with authorities for non government schools providing information to the Department of Education by 14 August. The NCCD itself is an annual collection of information about Australian school students with disability, and the NCCD Guidelines effective from 2026 onward are now published.

NCCD in particular depends on evidence collected through the year: the adjustments provided, consultation with students and families, and monitoring. When that evidence sits in learning support notes in one system, attendance in another and assessments in a third, the July scramble is predictable.

A data layer, often a small warehouse with scheduled extracts from the SIS and LMS, fixes this once. It also answers board questions that no single vendor report can: enrolment trends by year level, retention between stages, fee debt by family, and learning outcomes joined to attendance. Our data analytics service covers this kind of work.

How should child safety records be handled?

In a controlled system with role based access, an audit trail and clear escalation, because these records may be needed years later. Victoria’s 11 Child Safe Standards are mandatory requirements for organisations including schools, and responsibility for them moved from the Commission for Children and Young People to the Social Services Regulator in February 2026. In NSW, schools must register as child related employers with the Office of the Children’s Guardian, verify staff and volunteer Working with Children Checks online and keep records for each worker.

What schools typically need that a SIS does not do well:

• Concern and incident records restricted to the child safety team, with every view logged.
• Escalation steps and timeframes visible from the moment a concern is recorded.
• WWCC verification records for staff, volunteers and contractors, with expiry alerts.
• Training completion for staff on child safety policies.
• Reports for the leadership team and board that don’t expose individual details.

What does the generative AI framework mean for school tools?

The Australian Framework for Generative AI in Schools gives schools 6 principles and 25 guiding statements, and schools now use it to judge the AI tools they let staff and students use. Education Ministers endorsed the 2024 review of the framework in June 2025. The principles are teaching and learning; human and social wellbeing; transparency; fairness; accountability; and privacy, security and safety.

The sixth principle is the one software design must answer directly. It expects generative AI tools to be used in ways that comply with Australian law, avoid unnecessary collection, limit retention, prevent further distribution and prohibit the sale of student data; school communities to be told what data is collected and how it is used, with consent where needed; and robust cyber security.

For a staff AI assistant, that becomes a short design brief:

Framework expectation	Design choice
Avoid unnecessary collection	Staff assistant answers from policies and curriculum, not student files, unless a use case needs it
Limit retention	Conversation logs kept for a defined period, then deleted
Prevent further distribution, no sale	Australian hosting, no model training on school data, contract terms to match
Privacy disclosure	Plain English notice to staff and families about what the tool does
Accountability	Teachers stay responsible for anything sent to students or parents

Our guide to the Privacy Act and AI covers the legal side, and our RAG knowledge base service covers assistants that answer from your own documents.

What changes when you enrol international students?

Registration on CRICOS, the ESOS framework and the National Code 2018, and enrolment reporting through PRISMS. The Department of Education says the National Code 2018 sets nationally consistent standards for delivering courses to overseas students and commenced on 1 January 2018. For software, that means enrolment, attendance and welfare data for overseas students has to be reliable enough to meet the Code’s obligations and to reconcile with PRISMS. Our education and RTO software page covers the same obligations from the training provider’s side.

How should the systems connect?

Make the SIS the source of truth for students, families, classes and staff, and have everything else read from it. Most integration failures in schools come from two systems both believing they own the class list. A sound pattern looks like this:

• Identity through the school’s directory, such as Microsoft Entra ID or Google Workspace, so staff and students sign in once and leavers lose access on the day they leave.
• Nightly or event driven sync of classes and enrolments from the SIS to the LMS and other tools, never the other way.
• Marks and attendance written back to the SIS through its API, with failures reported to a person.
• A single integration layer, so adding a new tool means one connection rather than five.

Our API development service covers this layer.

What do school software projects cost?

Indicative Australian market ranges, AUD ex GST, for projects around an existing SIS and LMS.

Build	Indicative range
Enrolment and waitlist portal integrated with the SIS	$40k to $110k
Data warehouse and reporting across SIS and LMS	$50k to $150k
Staff AI assistant within the framework	$40k to $120k
Child safety records and WWCC register	$30k to $80k

The basis is Australian agency rates for design, build, testing and launch; hosting and support are extra. Accessibility to WCAG 2.2 AA should be in scope for anything families use; see our app accessibility guide. These are ranges, not quotes.

How AWLabs approaches school software

AWLabs hasn’t yet delivered a project for a school or school system, so we’re upfront that we would be learning your sector’s practices with you; we bring the integration, data and AI engineering. It starts with a Development Consult. A paid Discovery Audit then maps your SIS, LMS, data flows and reporting obligations, with the fee credited in full against the build, and you receive a fixed price Schedule of Work with three options: The Minimum, The Recommended and The Complete. Senior engineers lead every build, updates arrive every Tuesday and Friday, Sydney time, and the code and IP are assigned to you as they are paid for.