Never dread an inspection again

I want to ask you something honest: when you hear that an assessment visit is coming—or worse, when an educator pokes their head in and says "there's someone at the door"—what's your first feeling?

For most childcare leaders I've spoken with, it's not confidence. It's a cold rush of did we miss something? And then the scramble begins. Pulling folders, checking sign-in sheets, hunting for that one health action plan you're not sure was updated. It's exhausting, and it's not a reflection of how well you actually run your service. It's a reflection of not having a system that runs quietly in the background, keeping everything in order so you don't have to.

That's exactly what this school is built to give you. I've spent years working through the documentation realities of regulated childcare—the mandatory records, the retention schedules, the incident report formats that actually satisfy a regulator, the enrolment folders that pass inspection versus the ones that raise flags. I've seen what the most common non-compliance findings look like, and I've seen what the settings that don't get those findings have in common. It's not luck. It's system design.

What I teach here is practical, not theoretical. We don't spend time on vague compliance philosophy—we build actual folders, actual checklists, actual SOPs, and an actual rolling audit schedule you can hand off to your team. By the time you work through this school, you'll know what goes in every folder, how long to keep every record, how to write a correctable and defensible incident report, and how to walk an unannounced inspector through your documentation without your heart rate spiking.

You deserve to feel calm when a regulator walks in. Not because you've got nothing to worry about—but because you've built a system that's been quietly doing its job all year. Come and build it with me.