Childcare Enrollment Bottlenecks: Find and Fix the Stalled Step
- Define a cohort and stage events before calculating conversion.
- Distinguish family actions, staff reviews and genuine form failures.
- Use record-level evidence to choose a change, then compare equivalent cohorts.
To fix a childcare enrollment bottleneck, first identify the step where a family is waiting and what must happen next. A form problem, an unanswered question and an application awaiting staff review need different responses. Counting every incomplete application as a lost family hides those differences.
Download the editable CSV worksheet.
Start with a defined group of inquiries and a snapshot date. Keep the same group throughout the review so the totals describe one journey, rather than mixing this week's inquiries with last month's confirmations.
Define the stages you can verify
Use events with clear evidence: inquiry received, form started, form submitted, staff review completed, offer made and place confirmed. Write down what each event means in your program. “Interested” and “almost done” are not reliable substitutes for recorded stages.
For the current workload, also record the next action, its owner and the date it became due. Separate a family action from a staff action. A family that submitted everything should not receive another missing-form reminder while staff are still reviewing the record.
Read a worked enrollment funnel
The following is a fictional, simplified cohort in which everyone moves through the same stages in order. It is not an industry benchmark.
| Stage reached by the snapshot | Families | Share of the original cohort |
|---|---|---|
| Inquiry received | 40 | 100% |
| Form started | 30 | 75% |
| Form submitted | 24 | 60% |
| Staff review completed | 18 | 45% |
| Offer made | 12 | 30% |
| Place confirmed | 9 | 22.5% |
Form completion among families who started is 24 ÷ 30 = 80%. Confirmation among families offered a place is 9 ÷ 12 = 75%. Neither is the same as the share of all inquiries that confirmed, 9 ÷ 40 = 22.5%.
Six submitted applications have not yet reached completed review. That difference identifies records to inspect; it does not prove that staff are late. Some may have arrived just before the snapshot. Likewise, the three unconfirmed offers may still be within their response period.
If families can skip stages in your actual process, document those paths before applying this simple funnel. Count a person once per stage and explain any reopened or duplicate record.
Inspect the reason before changing the workflow
Review a small set of stalled records using the approved system, without copying sensitive information into a broadly shared spreadsheet.
| Observed state | What to check | Possible next action |
|---|---|---|
| Form started, not submitted | Error reports, unclear questions, duplicate attempts | Test the reported step on the same kind of device |
| Submitted, awaiting review | Arrival date, queue owner, missing decision | Assign the review and record the next check |
| Offer made, no response | Offer delivery, deadline, unanswered question | Follow the actual offer policy and contact process |
| Declined or withdrawn | Recorded reason, if voluntarily provided | Close the record accurately; do not invent a cause |
Use the phone and keyboard form checklist when the evidence points to the form. Test with fictional records and include an error-and-recovery attempt. More reminder messages will not fix a control that cannot be used.
Separate returning families from new inquiries
Returning families may need a different decision sequence: indicate interest, request days, receive an offer and confirm. Use the preschool re-enrollment checklist to keep those events distinct. Do not treat silence as a withdrawal unless your actual policy and communication process support that decision.
For a family deciding after a visit, review the preschool tour follow-up guide. Keep the next step specific to the family's recorded status.
Make one change and review the result
Choose a change that addresses the observed issue: clarify a field, correct an error, assign a queue owner or explain what confirmation means. Record the change date and the evidence that led to it.
Review a later cohort at an equivalent point in its journey. Show counts as well as rates and note differences in available places, schedules or inquiry sources. A higher rate alone does not prove the change caused the improvement.
Bloomily's enrollment overview describes forms, offers and waitlists. During a demo, trace one fictional application from inquiry through confirmation, including a missing-item case. Check whether staff can see the status and owner you need before assuming software will remove the bottleneck.