The ISV calendar, without the spreadsheet
The association sends the calendar once a year and the school retypes it. EthosOne holds it as a profile instead: load it, prune it to the obligations your school actually carries.
EthosOne holds the ISV compliance calendar in its profile library.
A Victorian independent school loads the profile instead of retyping the PDF, prunes it to the obligations that apply, and every occurrence it generates carries a named owner, a due date and the evidence that closes it.
What we keep hearing
It is the first week of term and the calendar has arrived as a PDF. Somebody copies it into the spreadsheet the school has used for four years, adjusting the dates, dropping the rows that do not apply and adding the ones the spreadsheet grew on its own. It takes two afternoons. By October nobody is certain the spreadsheet and the PDF still say the same thing, and the only way to find out is to read both.
Four views, one reconciled picture. Each one drills to the record it came from.
- 01
The profile, loaded rather than retyped
The library holds the ISV calendar as a profile. Load it, and the obligations arrive structured, not as a page of text to transcribe.
- 02
Pruned to your school
Not every obligation applies to every school. Prune the profile to yours, and what is left is the calendar your school actually runs, rather than the sector's calendar with your exceptions remembered by one person.
- 03
An owner and a date on every occurrence
Each obligation generates its occurrences with a named owner and a due date. Overdue means overdue: it is a state the record carries, not a colour somebody applied to a cell.
- 04
Evidence that traces back
Closing an occurrence attaches the evidence, and the evidence keeps its link to the obligation and the regulation the obligation came from. When the question is why a thing was done and not only whether, the answer is on the record.
The ISV calendar is one profile in the library, and it runs on the same spine as the rest. Policies and assurance logs hold the evidence an occurrence closes with, the risk register carries the controls some obligations rely on, and PolicyAI supplies the obligation's source. Beside it, Regulatory Readiness loads the VRQA Guidelines for Registration that the VRQA reviews against, so the recurring work and the registration review read from one set of records. The Victoria framework, and what the VRQA asks to see, is on its own page.
What it does not do
- It is not an ISV product, and EthosOne is not affiliated with or endorsed by Independent Schools Victoria. The calendar is the association's published material; EthosOne holds it as a profile schools can load.
- It does not replace the association's own advice, membership or services.
- It does not invent obligations. A profile holds what the published calendar holds, and a school prunes it rather than the system guessing.
- It does not treat a loaded profile as proof of compliance. An occurrence is closed by evidence, not by the calendar being present.
- Stored in AustraliaAWS Sydney and Melbourne, one database per school
- AI stays in the country tooAmazon Bedrock; never trained on your content
- Published, not describedTrust Centre · ISMS policy · How we handle your data
The six we are asked every time.
Still weighing something up? Thirty minutes with us, on your own registers, answers the rest.
Book your school a demo01Is this the ISV calendar, or EthosOne's version of it?
It is the association's published calendar, held as a profile you load. You prune it to your school; EthosOne does not add obligations to it.
02We already get the calendar from ISV. What does this add?
The calendar tells you what is due. It does not tell you who owns it, whether it happened, or where the evidence went. Loading it as a profile turns each line into occurrences with an owner, a date and an evidence trail.
03Does this replace our ISV membership?
No. The association's advice, resources and membership are its own. This is the software a member school runs the calendar in.
04What if our school does not do everything on the calendar?
Prune the profile. What is left is your school's calendar, and it stays that way next year rather than being rebuilt from the PDF.
05Can we run more than one calendar?
Yes. A school can run the association profile beside an audit or accreditation stream, and they stay separate rather than merging into one list.
06Is the VIC registration framework in here too?
It is, in Regulatory Readiness rather than the calendar: the VRQA Guidelines for Registration as the VRQA structures them, with evidence linked to each criterion. The two read from the same records.
What are the AI paragraphs you are currently missing from your policies? Watch how we do it.
Free, under ten minutes, and yours to keep whether or not you talk to us.
“It meets all of the real frustrations of business directors in one place.”
“School governance and risk is a complex area without a clear solution.”
Thirty minutes on your own calendar,not a generic walkthrough.
The ISV compliance calendar, held in the EthosOne library: load the profile, prune it to your school, and every occurrence carries an owner, a due date and the evidence that proves it.