Operations

The systems that run your school when you step away.

Every Montessori school has systems — the real question is whether they live in shared documentation or in one person's head. When the front office can read the tuition binder only because someone has always done it that way, the school is running on memory, not systems. It works right up until that person is out sick, or leaves. Operations is the unglamorous engine room of a school: the enrollment steps, the staff onboarding, the opening and closing routines, the vendor list — the "how we actually do this" that keeps the doors open.

Get it into repeatable systems and the whole school gets calmer, more consistent, and far less dependent on any single person. The articles below get practical about how to build that, without needing a quiet week that never comes. Start anywhere, and read the fuller guide near the bottom.

Latest in Operations

When Your School Runs on One Person's Memory

Most leaders can picture it instantly: the one staff member who knows how the waitlist really works, the binder only the office manager can interpret, the login only the founder has. It feels efficient — until that person is out, and a routine task becomes a crisis. Operations is the work of making sure a school's know-how lives in systems the team can run, not in individual memories that walk out the door at 3:00.

The "mental vault" problem

In a growing school, procedures pile up in people's heads faster than anyone writes them down. Each person becomes the sole keeper of their piece — the enrollment sequence, the substitute call list, the year-end licensing packet. It looks like expertise, and it is. But undocumented expertise is fragile: it can't be delegated, it can't be improved by anyone else, and it disappears the moment that person does. The bigger the mental vault, the more the school depends on specific people instead of reliable processes.

A workaround is not a system

Every school has both. A workaround gets you through today: the sticky note, the "just text me and I'll handle it," the spreadsheet only one person understands. A system works tomorrow whether or not any particular person is there. Workarounds live in someone's head and require heroics; systems live in shared documentation and create clarity. Workarounds aren't bad — they're how you survive a busy week. The danger is mistaking a pile of workarounds for an operational system, and only discovering the difference when the person holding it together takes a day off.

Capture as you go

The reason processes never get documented is the same reason everything else doesn't: there's no quiet week coming. So don't wait for one. Capture the work while you're already doing it. The next time you run a task that lives only in your head — the background-check process, the email sequence to prospective families, the opening routine — write the steps down as you go, once. Rough is fine. A plain checklist someone else could follow beats a perfect manual that never gets written. Do that with one process a week, and in a term you've converted a year of mental vault into shared systems.

The prepared environment applies to adults too

Montessori leaders spend enormous care preparing the environment for children — everything ordered, reachable, set up so a child can work independently without an adult hovering. Adults deserve the same. When your team has clear processes, the right access, and a place to find "how we do this," they can act without waiting on you. An operationally prepared environment is what lets staff solve problems themselves instead of routing every question to the leader's desk.

Systems are how a school outgrows its founder

There's a ceiling on any school where operations live in the leader's head: it can only be as big as one person can personally hold. Documented, shared systems raise that ceiling. They make onboarding faster (new staff learn the process, not the person), quality more consistent (everyone follows the same steps), and delegation actually possible (you can hand off a system; you can't hand off your memory). It's how a school moves from "runs because the founder is heroic" to "runs because it's built to."

Where to start

Pick the single process that would cause the most chaos if the person who owns it vanished tomorrow, and document that one first. Then the next. You're not writing an operations manual in a weekend; you're converting your most fragile mental vault into a system, one capture at a time. The articles in this pillar go deeper on documenting without extra time, telling systems from workarounds, and building operations that don't depend on any single person.

Common Questions

How do I document our school's processes when there's never time?

Don't wait for a quiet week — capture each process while you're already doing it. The next time you run a task that lives in your head, write the rough steps once. One process a week becomes a full operational library over a term.

What's the difference between a system and a workaround?

A workaround gets you through today and lives in one person's head; a system works tomorrow whether or not that person is there, because it lives in shared documentation. Trouble starts when a pile of workarounds is mistaken for a system.

How do I make my school less dependent on specific people?

Move the know-how out of individual memories into documented, shared processes with the right access. When the steps live in a system anyone can follow, the school stops depending on who remembers what.

Where should we start with school operations?

Start with the single process that would cause the most disruption if its owner suddenly left. Document that one, then the next most fragile. Prioritize by risk, not by what's easiest to write.