Fall Enrollment for Microschools: A July–August Playbook¶
It's the first week of July. You sent re-enrollment forms in January, twenty-two families signed and returned them, and you told yourself enrollment was handled. Now you're looking at your inbox and realizing three of those families haven't replied to anything since April — and school starts in seven weeks.
The January commitment isn't the finish line¶
The January re-enrollment ask — collecting signed commitments from returning families — is one part of the enrollment lifecycle. It's not the whole thing. What you asked for in January was intent: "Are you planning to return?" What you need in July is different: execution — confirmed seat, updated records, and a paper trail that holds up if a family drops at the last minute.
The January commitment and the summer close are two distinct operational phases. Most microschool founders have a process for the first one and no documented process for the second. That gap shows up in late July, when you're doing enrollment math in your head and realizing you're not actually sure which of your "committed" families are still coming.
The approximately 95,000 microschools now operating in the United States — most of them past their launch year, according to the National Microschooling Center's May 2025 sector analysis — share this exact problem. They've run the January ask. They don't have the summer close. The median microschool now serves 22 students (up from 16 in 2024, per The 74's coverage), which puts most founders in exactly the 20–30 family range where individual seats matter and a single non-responding family isn't background noise — it's a real enrollment gap.
The summer phase has three tasks. Confirm: get a current, summer-specific response from every returning family, not a January signature from six months ago. Fill: when a seat drops, activate your waitlist within 24 hours, not 5 days. Lock: verify and update every student record before Day 1, not after.
These three tasks are what this post covers. If you haven't run the January re-enrollment ask yet, start with the re-enrollment playbook first — that one handles the initial commitment, tuition-increase communication, and the decision between continuous enrollment and annual re-enrollment. Come back here when you have commitments in hand and a school year approaching.
The 6-week window: a week-by-week confirmation timeline¶
The summer confirmation window runs from July 1 to August 10. It's six weeks, not one email. The mistake most founders make is treating the July confirmation like the January ask — one form, one follow-up, done. It isn't. The January ask was emotionally low-stakes; a family could say yes without changing anything in their life. The July confirmation is logistically high-stakes: school starts in weeks, ESA deadlines are real, and families who've had a summer of second thoughts are making actual decisions right now.
Here's the schedule. Put it on your calendar before you read the next section.
| Week | Dates | Action | Channel |
|---|---|---|---|
| Week 1 | July 1–7 | Send summer confirmation form to all returning families (see Section 3) | NavEd Forms or email |
| Week 2 | July 8–14 | First follow-up to non-responders — personal note, not a broadcast | Email or parent portal message |
| Week 3 | July 15–21 | Second follow-up; flag any family with zero response since April | Same channel, more direct subject line |
| Week 4 | July 22–31 | Final notice: seat will be offered to the waitlist on August 1 if no response | Email with explicit deadline |
| Weeks 5–6 | Aug 1–10 | Seat release decisions finalized; records update window closes; waitlist offers extended | Section 4 decision tree |
Send the first message on July 1, not July 7. Families who haven't responded by August 1 have been given four touchpoints over thirty days. That's not aggressive — that's professional. The alternative, which is waiting until late July to start the process, leaves you with a two-week scramble before Day 1 and no time to fill dropped seats from the waitlist before families find other options.
A note on ESA families: roughly half of microschool students use Education Savings Account or school-choice funds, per the National Microschooling Center. Many ESA programs have authorization renewal deadlines in late summer. A family using ESA funds who hasn't submitted their current-year authorization isn't just an enrollment gap — it's a payment gap. Flag ESA families in your follow-up sequence and move them to the top of the Week 3 list if they haven't responded.
The Week 4 message is the hardest to write. Here's a template that sets a deadline without reading like an ultimatum:
Subject: One more week to confirm [Child's Name]'s spot at [School Name]
Hi [First Name],
We haven't heard from you since reaching out a few weeks ago, and we want to make sure your family's spot is secured before August. We're holding [Child's Name]'s place through July 31. If we don't hear from you by then, we'll need to offer the seat to the next family on our waitlist.
If your plans have changed, just let us know — no explanation needed, no hard feelings. If you're still coming, the confirmation form takes about five minutes: [link].
[Founder Name]
Three sentences. One deadline. One link. No guilt.
The summer confirmation form is not the January re-enrollment form¶
The January re-enrollment form asked a high-level question: are you returning? The summer confirmation form asks operational questions: what do we need to know before your child walks in the door? These are different documents with different purposes. A founder who sends the January form again in July is doing twice the work and getting none of the operational information they actually need.
The summer confirmation form has six to eight fields. Most of them are updates, not new information — you're asking families to review what's on file and flag anything that's changed, not fill out a blank form from scratch.
Here are the fields every summer confirmation form should include:
- Confirm intent — one checkbox: "Yes, [child's name] is returning for [school year]." The checkbox has to be checked. A signature from January is not confirmation for September.
- Emergency contacts — verify or update two contacts, phone numbers confirmed active this year (not the cell number from when they enrolled eighteen months ago).
- Medical and allergy updates — "Have there been any changes since last year?" One yes/no with a text field for details. A new diagnosis, a new allergy, a medication change belongs here.
- ESA or scholarship documentation — upload or confirm current-year authorization letter. Flag this field explicitly for families using scholarship funds; an expired authorization creates payment delays that are painful for everyone.
- Transportation arrangement — confirm pickup and dropoff arrangement. Who collects the child, and when. Not "same as last year" — confirmed, with a name and a phone number.
- Photo and media release — renew annually. Last year's signature may not legally carry over depending on your state and your school's policy.
- Tuition and payment setup — confirm payment method is active for the new year. Not "we'll figure it out after Day 1."
- Communication preferences — parent's preferred channel (email, phone, or app notification), and which parent is the primary contact if that's changed.
NavEd's Forms feature handles this workflow on the Premium plan. When a returning family opens the form link, NavEd identifies them from the school directory — they're not filling in a blank form or creating a new account. From the Forms dashboard, you can see exactly who has responded and who hasn't, without cross-referencing a spreadsheet. The submitted data flows directly into the student record. That means when you open a student's file in August to do the records check in Section 5, the confirmed emergency contacts, the updated medical notes, and the renewed releases are already there. Cross-reference the NavEd Forms announcement for the full feature overview.
If you're using Forms for the summer confirmation, send the link in the Week 1 message. The dashboard becomes your live enrollment status view for the rest of the timeline.
When a family drops a seat: the 24-hour protocol¶
The email you don't want arrives in your inbox on July 18: "We've decided not to return." In a school of 22 students, that's one seat — which is between 4% and 5% of your enrollment, a meaningful gap. What happens in the next 24 hours determines whether you fill it before August or go into the school year short.
Most founders don't have a documented process for this moment. They notify the waitlist eventually. They handle it case-by-case. The problem is that "eventually" is doing a lot of work in late July, when waitlisted families are also making decisions, and "case-by-case" creates inconsistency that comes back to bite you if a family ever asks why they didn't get the call.
Here's the decision tree. Execute it in sequence.
1. Receive the seat release notification (email, call, or form submission)
Reply to the family within the hour with one sentence: "Thank you — we've received your notice. We'll keep [child's name]'s records on file in case your plans change before August." Do not offer to hold the spot unless you have a written policy on holds. Ambiguity here costs you a seat. If they've decided not to return, that seat is now open.
2. Within 2 hours: update your enrollment count
Mark the seat as open in your school management system and note the release date. If the family was using ESA funds, the release date is relevant for any refund processing or documentation requirements in your state. Log the reason for the release if the family provided one — it's useful context if a pattern emerges (multiple families citing the same concern).
3. Within 4 hours: identify the next waitlist family
Waitlist priority should follow a documented method — first-in, first-offered, or lottery. If you haven't documented your waitlist policy, now is the moment that fact becomes painful. Go with first-in, first-offered based on application timestamp and document the decision. If two families applied at similar times and your timestamps don't clearly distinguish them, offer to the one who most recently confirmed active interest (the mid-summer check-in response from your waitlist workflow tells you exactly this).
4. Within 24 hours: send the waitlist offer
Subject: A spot just opened at [School Name] — 72 hours to respond
Hi [First Name],
A seat has become available in [grade/program] for the [school year] school year. You're next on our waitlist, so we're offering it to your family first.
To accept, please reply to this email or complete the enrollment form here: [link]. We need to hear from you by [date — 72 hours from send, written out as a day and date, not just a number].
If this timing doesn't work for your family, just let us know — we'll move to the next family with no hard feelings.
[Founder Name]
The 72-hour response window for a waitlist offer is longer than the 48-hour window used for standard waitlist seat offers (see microschool waitlist management). In late July, families may be traveling or mid-activity. Give them the extra day, but hold the deadline. State the expiration date explicitly — day of the week and date, not "in three days."
5. If the waitlist offer is declined or expires:
Log the outcome with a timestamp, send a one-sentence acknowledgment to the declining family ("Thanks for letting us know — we'll move forward from here"), and repeat steps 3 and 4 with the next family. If the waitlist is exhausted, note the seat as open and begin active outreach — at that point you're in new-family acquisition territory, which is covered in the microschool marketing and enrollment guide.
The 24-hour ceiling is not the goal. Faster is better. A seat that sits open for 5 days without a waitlist offer is a seat that may not fill before August — because waitlisted families who haven't heard from you in five days are making other arrangements.
Lock the record: 9 things to verify before Day 1¶
Before your school year begins — whether that's August 20, September 3, or any date in between — these nine fields in every returning student's record must be verified or updated. Not reviewed, not assumed to be current. Verified.
A wrong emergency contact on Day 1 isn't an administrative oversight. It's a liability. An expired ESA authorization on Day 1 means the first month's payment may not process. A wrong grade assignment in a multi-age program means a student's curriculum plan is wrong from the opening bell.
This checklist takes approximately 15 minutes per student if your records are in a shared system. It takes two hours per student if you're pulling from email threads, a parent sign-in binder, and a spreadsheet. Run through it once per student, in August, before Day 1.
- [ ] Emergency contacts — Two per student, with phone numbers confirmed active this year. Call them if you haven't heard from the family since spring.
- [ ] Medical information — Allergies, medications, and conditions reviewed; any new diagnoses or changes noted in the student record, not just in the confirmation form. Transfer the information from the form.
- [ ] ESA authorization letter — Current-year authorization on file for every student using scholarship funds. An authorization letter from the prior school year is not current. Half of microschool students use ESA or school-choice funds; this field matters for half your enrollment.
- [ ] Grade advancement — Student's grade or level confirmed for the new year. In multi-age programs where grade advancement isn't automatic, confirm explicitly with the family and in the record. Do not assume a fourth grader last year is a fifth grader this year without a documented advancement decision.
- [ ] Enrollment status — Marked as confirmed returning (not "said yes in January" — confirmed via the summer form). Tied directly to the confirmation form workflow in Section 3.
- [ ] Tuition and payment setup — Payment method active for the first billing cycle of the new year. Not "we'll sort it out once school starts." If a family is on a payment plan, confirm the plan is set up and the first payment date is on their calendar.
- [ ] Transportation arrangement — Pickup and dropoff confirmed by name and phone number, not by assumption. "Same as last year" is not confirmation. Who is picking up this child, and what number do you call if they're 30 minutes late?
- [ ] Photo and media release — Current-year signature on file. If your media release expires annually, last year's signature is not valid. Collect new signatures from every family before you post the first photo of the school year.
- [ ] Communication preferences — Parent's preferred contact method verified: email, phone call, or app notification. If your school uses a parent portal, confirm the parent's account is active and their notification preferences are current. An incorrectly configured parent portal means a parent who thinks they're getting alerts isn't getting them.
Nine fields. It takes 15 minutes per student if your records are in a shared system, or two hours per student if you're working from a spreadsheet. The difference is not discipline — it's infrastructure.
What's next¶
NavEd Forms handles the summer confirmation workflow on Premium: it auto-identifies returning families from the school directory, tracks who has responded and who hasn't, and stores submitted data directly in the student record. If you're managing this across 20 to 30 families in a spreadsheet right now, the math on switching is simple.
If you haven't built your January re-enrollment process yet — the initial commitment ask, how to handle tuition-increase conversations, whether to adopt continuous enrollment — start with the re-enrollment playbook.