Preview: Wonderschool’s Early Intervention Prototype for Part C Teams

We’re happy to introduce a preview of Wonderschool’s Early Intervention module: a prototype for discussing referral intake, routing, case visibility, and service-coordination needs with IDEA Part C teams. This is a prototype demonstration, not a production-product launch.

State Part C administrators, regional programs, and service-coordination leaders need a clear view of what happened, who owns the next step, and how families receive information. When the workflow spans separate inboxes and records, even understanding the current status can take additional work.

What does the Early Intervention prototype explore?

The prototype brings referral intake, routing, case visibility, and service-coordination concepts into a connected demonstration. It gives agencies a concrete starting point for discussing how their own operating process could be supported.

• Referral intake: What information begins the process, and who receives it?
• Routing: How should a referral reach the appropriate team?
• Case visibility: What does a coordinator need to understand the current stage and next action?
• Service coordination: How should responsibilities and family-facing next steps remain understandable?

These are prototype concepts to evaluate, not a claim that a production deployment or every proposed workflow is available.

Who is this preview for?

The intended audience is teams evaluating administration of early intervention under IDEA Part C. Their work may span referral, evaluation and eligibility, an individualized family service plan, service coordination, and communication with families.

Part C is distinct from CCDF and from pre-K enrollment. This preview is not a child care subsidy eligibility system or a claims-processing announcement. Agency policies, privacy requirements, and program responsibilities need their own implementation review.

What should agencies bring to a prototype demo?

Bring one representative, de-identified workflow and the questions your team most needs to answer. A useful discussion might follow a referral from receipt through assignment and the next family communication.

1. Map responsibility: Who receives the referral, determines the next action, and follows up?
2. Identify the information needed: What must each role see, and what should remain restricted?
3. Describe timing: Which deadlines or handoffs does the team need to understand?
4. Explain family communication: How do families learn what happens next and whom to contact?
5. Separate current scope from future needs: Which requirements are demonstrated, which would need configuration or development, and which are outside scope?

What is outside this announcement?

The announcement does not include production availability, Medicaid billing or claims capabilities, or live external integrations. A demo is an opportunity to discuss requirements and implementation needs, not a substitute for confirming product scope, security, accessibility, procurement, or program obligations.

Frequently asked questions

Is this a production-ready Early Intervention system?

This announcement presents a prototype. Production availability and implementation scope need separate confirmation with Wonderschool.

Is this the same as EarlyDay?

No. EarlyDay is Wonderschool’s teacher-recruitment offering. This preview concerns Wonderschool Early Intervention and IDEA Part C workflows.

How can my team learn more?

Request an Early Intervention prototype demo and tell us about your agency’s workflow and questions.

Have questions about the module? Contact Wonderschool to schedule a prototype demo, or explore our Early Intervention overview.