01 / ENREnrolment & admissions
Enquiry through to offer and acceptance, with document collection, interview scheduling, waitlists and a conversion view of the whole funnel.
Schools adopt Microsoft 365 quickly and end up with content sprawl: hundreds of sites, duplicated policies, and departments running shadow systems because the official one was too hard. We build the structure, automation and governance underneath it, so staff collaborate in one governed place. We have delivered this for an independent college.

Why they call us
Every department creates its own site, policies get duplicated and drift, and nobody can say which version of the excursion form is current.
Permission slips, leave requests, incident reports and purchase approvals move as attachments, which means they are slow, unauditable and easy to lose.
Attendance, child safety, staff clearances and funding reporting assembled by hand each period from systems that were never designed to talk.
What’s in the platform
Every organisation starts from the same core and diverges within weeks. The modules below are the starting point, not the ceiling.
Select a zone to see what it does
01 / ENREnquiry through to offer and acceptance, with document collection, interview scheduling, waitlists and a conversion view of the whole funnel.
02 / STUOne record per student across academic history, wellbeing notes, medical and consent documents, and family relationships, with access scoped by role.
03 / ATTRoll marking across classes and excursions, unexplained absence follow-up, and the reporting your education authority requires without a manual export.
04 / TTTimetable publication, room and resource booking, cover and relief allocation, and a single view of who is where.
05 / COMAnnouncements, permission forms, parent-teacher bookings and secure messaging, delivered through the channels families actually read.
06 / STFStaff records, working-with-children and background clearance expiry tracking, professional development and onboarding workflows.
07 / FEEFee schedules, discounts and sibling rules, payment plans, extras and excursions, reconciled into your finance system.
08 / RPTCompliance reporting, board packs, policy currency and site governance, so the annual audit is a report rather than a project.
Customization
Most vendors stay vague about this until you are mid-contract. Here it is up front, so you can price the gap before you commit.
The AI layer
Off-the-shelf systems bolt a chatbot onto a decade-old database. We build the intelligence into the workflow, using the same engineering we ship for enterprise clients on Azure AI.
Answers prospective-family questions from your own published information, captures the enquiry into the funnel, and books tours, with anything sensitive routed to a person.
A grounded assistant over your policy and handbook library, permission-trimmed, citing the source document. New staff stop asking the same six questions, and the answers are current.
Surfaces attendance patterns that predict disengagement early enough for a wellbeing team to act, rather than at the end of term.
Drafts report comments from assessment data and teacher notes as a starting point. The teacher edits and signs, and the draft is never published unreviewed.
Classifies and tags incoming documents into the right library with the right retention, which is what actually keeps a governance model alive after year one.
A grounded assistant over enrolment and attendance data. "Which year levels lost the most enrolments after the fee change?" answered from your records.




Integrations
We integrate rather than replace, so what already works keeps working.
Compliance & data
Designed against FERPA and state student-privacy law in the United States, and the Privacy Act and Australian Privacy Principles in Australia, with access scoped so staff see only what their role requires.
Clearance and working-with-children expiry tracking, incident recording with restricted access, and reporting aligned to Child Safe Standards in Australia and state mandatory-reporting requirements in the US.
Retention schedules on student and staff records, versioned policy libraries showing what was current when, and exportable audit trails on access to sensitive records.
How the build runs
We map departments, content, permissions and the processes that currently run on email. The governance model is agreed before anything is built, because that is what makes it last.
Site architecture, document libraries, metadata and the first automated processes stood up in your own Microsoft 365 tenancy.
Existing content migrated and tagged, finance and communication systems connected, and duplicate or dead content retired rather than carried over.
One department goes live with us on hand, staff trained, then a two-week hypercare window before the rest of the school follows.
A named engineer, an agreed response SLA, and a termly cycle where you decide what gets built next. It runs in your tenancy, so you own it outright.
Questions
The structure and the discipline. Microsoft 365 gives you the tools, not the information architecture, the automation or the governance model. That gap is why most schools end up with sprawl, and it is the part we build.
Yes. We delivered Microsoft 365 collaboration, SharePoint document management and Power Platform automation for an independent college, with a governance model designed to stay maintainable after handover.
Usually not, and we will say so. Most schools keep their SIS and we build the collaboration, document and process layer around it, integrating where it matters. Replacing an SIS is a much larger decision.
Lifecycle rules, owner accountability on every site, retention that runs automatically, and a review cycle. Governance that depends on people being disciplined forever does not work, so we automate the parts that can be automated.
The assistants are grounded in your own content and permission-trimmed, so they cannot surface anything the asker could not already open. You choose whether any content is processed outside your tenancy, and AI features are optional throughout.
Some of it, yes, because it looks like the Microsoft tools they already use. That familiarity is a real argument for building on Microsoft 365 rather than introducing another separate system with its own login.
That is what we recommend. One department proves the architecture and the migration pattern, and gives you internal advocates before the wider rollout.
Thirty minutes, a working demo build, and an honest answer about whether a custom platform is right for you. If off-the-shelf is the better call, we will say so.
You’ll speak with engineers, not account managers.
PanaceaLogics
Typically replies within an hour
Hi there! 👋 How can we help with your project?
Start chat on WhatsApp