EthosOne vs. iSAMS

iSAMS was designed for the operational and administrative complexity of independent and international schools globally. It solves real problems: fragmented student records, inconsistent reporting, disconnected finance systems.

EthosOne was built for a different problem entirely.

It was built for the governance obligations that Australian independent schools carry: State association and regulatory compliance frameworks. ISO 31000-aligned risk governance. Board reporting across multiple assurance domains. Duty of care for camps, excursions, and high-risk activities. Policy management with version control and assurance tracking. Meeting governance with action accountability.

None of that is in iSAMS. Not because it is a poor product. Because it was never designed for it.

School A runs iSAMS. Student records are centralised. Academic reporting is clean. Finance is integrated. But before every board meeting, the Principal and Business Manager are assembling governance manually. The risk register is in a spreadsheet. Compliance obligations are tracked in a shared calendar. Policy reviews are managed by email. iSAMS tells the school everything about its students. It tells the board nothing about its governance posture.

School B runs EthosOne alongside its MIS. Student operations continue in their existing system. But governance, risk, compliance, duty of care, and board reporting live in one connected environment. The board does not receive a reconstructed summary. It sees a live governance picture.

iSAMS answers the question: "How do we manage the academic and administrative operations of our school?"

EthosOne answers a different one: "How do we demonstrate that our school is governed well, to our board, our regulator, and our community?"

Those are not the same question.

A Familiar Moment: "iSAMS gives us everything we need to run the school. But when the registrar asks about our governance framework, I'm pulling it together from three different places."

That is the moment schools begin looking for governance infrastructure.

iSAMS includes some compliance and safeguarding functionality. Student wellbeing monitoring. GDPR data compliance modules. HR documentation.

These are operational compliance features built for the schools iSAMS primarily serves: international schools in the UK, Europe, and Asia.

They are not aligned to Australian state compliance frameworks. They do not include AISSA calendar obligations. They do not produce board-level governance reporting. They do not connect risk, compliance, and duty of care into a single assurance picture.

EthosOne does.

iSAMS includes compliance features mapped to international school contexts.

EthosOne works directly with the compliance calendars published by Independent Schools Associations in each Australian state, turning them into: Assignable obligations with named owners. Visible progress for leadership teams. Board-reportable completion records. Auditable evidence for regulators.

Compliance is not approximated. It is built for Australian independent schools.

iSAMS does not publish a structured risk governance framework among its modules. That is a statement about what iSAMS publishes, not about what it can do. Ask them directly.

EthosOne runs risk as a governed register rather than a report: board, ICT, AI and operational risks under one approved matrix and appetite, each with a cause, a consequence, an owner and inherent and residual ratings, and each control carrying a named owner and a review date. A Bowtie report generates from any activity assessment as a PDF, which is the form most reviewers already read.

iSAMS publishes a Compliance module, so this is not a comparison about whether compliance exists. It is about whether the obligations arrive knowing your state.

Risk is not reconstructed quarterly. It is governed continuously.

iSAMS remains a strong platform for schools where: International or multi-campus operational complexity is the primary challenge. Academic management, admissions, and finance integration are the priority. Governance reporting is managed through other systems or manually.

For those schools, it delivers real value.

Australian independent schools begin exploring EthosOne when: Governance and compliance obligations are growing and becoming harder to manage manually. Boards want structured reporting, not assembled summaries. Risk needs to be visible and governed, not stored in a spreadsheet. Duty of care for camps and excursions needs connected workflows. The gap between the MIS and the boardroom is costing leadership time and confidence.

EthosOne does not replace an MIS. It fills the governance layer the MIS was never designed to cover.

iSAMS helps schools manage academic and administrative complexity. EthosOne helps Australian independent schools govern with clarity.

For schools where governance still lives outside the system, the difference is not about features. It is about whether your board can see your governance posture clearly, between meetings, not just when someone assembles it beforehand.