Starting a microschool means you're suddenly the front office, the registrar, and the compliance officer, on top of being the teacher. A district has a dozen people handling enrollment forms, attendance policy, and state filing. In a microschool, that's you, usually on evenings and weekends, usually built from scratch because nobody hands you the district's templates.
The paperwork that actually can't wait
- An enrollment packet that captures what you legally need, not just a friendly welcome form. Emergency contacts, health information, whatever your state requires for the specific legal structure you're operating under (homeschool umbrella, private microschool, hybrid).
- A written attendance policy, even for a school of twelve kids. What counts as present, what triggers a family conversation, how it's tracked. Without this written down, you're inventing the answer under pressure the first time a family pushes back on it.
- A basic operations one-pager: hours, what happens in an emergency, who to call, what the daily schedule actually is. New families need this on day one, not assembled from memory during a hallway conversation.
- Whatever your state's specific filing or notification requirement is. This is the one place microschool founders most often get burned, because it varies enormously by state and by which legal umbrella you're under, and "I didn't know I needed to file that" isn't a defense anyone accepts later.
Building it in the right order
1. Confirm your legal structure and what it actually requires (this determines everything else, do it first, not last).
2. Draft the enrollment packet against that requirement, not a generic template.
3. Write the attendance policy before you have your first attendance dispute, not after.
4. Put the operations one-pager together so new families get the same clear picture, not a different verbal explanation each time.
A quick before/after
Before: enrollment handled family-by-family over text messages, attendance tracked in a personal notebook, and a scramble every time a new family asks "wait, what's your policy on X."
After: one enrollment packet every family fills out the same way, a written attendance policy you can point to instead of deciding fresh each time, and a one-page operations sheet that answers the questions before they're asked.
Where this gets easier to build
Our [microschool planning tool](/microschool-plan) is built to generate this backbone, enrollment structure, attendance policy, and operations basics, in one pass instead of you drafting each piece separately under deadline pressure the week before you open.
The question founders skip until it costs them
"What happens if I need to close for a day, or a family needs to withdraw mid-year" feels like a problem for later, right up until the week it actually happens, usually with no policy written down and a frustrated family in front of you. Deciding your closure and withdrawal policy before you open, even in three sentences, means you're reading from a document instead of inventing fairness on the spot under pressure.
The test of a microschool that's actually ready to open
Ask whether a new family's first three questions, "what does a day look like," "what's your attendance policy," "what do I do in an emergency," could be answered by handing them something you already have written. If every one of those still requires a live explanation from memory, the school isn't quite ready to run without you in the room every single day.
