Bringing a school's admissions, records and communication into one connected system.

Schools run on a surprising amount of coordination — admissions, student records, staff communication, attendance, fees and parent updates. In many independent schools this work is spread across spreadsheets, paper forms, messaging apps and individual memory.

TD School OS began with a simple question: what would it take for one connected system to hold all of this, so the people running the school spend less time chasing information and more time on the work that matters?

Before the project, core information lived in disconnected places. The same details were re-entered across tools, follow-up depended on someone remembering, and it was hard to get a clear, current picture of what was happening across the school.

The risk of that fragmentation is quiet but real: missed follow-ups, inconsistent records, and administrative work that grows heavier every term.

The approach started with mapping how information actually moves through the school today — where it enters, who touches it, and where it stalls — before designing anything.

From that map, the priority became connection over features: fewer places for information to live, clear ownership of each step, and automation only where it removes genuine drag.

TD School OS is designed as a single connected platform: a central record for students and families, structured workflows for admissions and communication, and a reporting layer that gives leadership a current view without manual compilation.

AI and automation are used as enablers — handling repetitive follow-up and surfacing what needs attention — not as the headline of the product.

The system architecture and core data model are complete, and the platform is being built in stages, starting with records and admissions before layering in communication and reporting. An MVP is in progress.

The project is a clear example of the core thesis: the school did not have a growth problem, it had a systems problem. Most of the value comes not from any single feature but from connecting work that used to live apart.

The immediate next step is completing the MVP and running a supervised pilot with a small set of real workflows, then measuring the operational improvement against the design targets.