Washington ESIT to Preschool Special Education Transition

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Washington ESIT ends at the third birthday

The Washington ESIT transition to preschool special education begins before the third birthday.

Washington DCYF's ESIT page states that early support ends on the child's third birthday and that a transition plan is developed beforehand. Some children may be eligible for early childhood special education through the local school district. Ask the family resources coordinator to identify the district contact, community alternatives, and the exact steps already added to the IFSP.

Turn the plan into a dated worklist

List the third birthday, transition planning meeting, district notification or referral, evaluation consent, records chosen for sharing, assessments, eligibility decision, IEP meeting, family response, setting visits, transportation, final ESIT service, and expected start. Compare the family's record with federal Part C requirements and current Washington or district notices. Give each open task one owner and next date.

Compare the daily experience

For each setting, ask what a typical arrival, meal, play period, group activity, rest, toileting routine, therapy contact, and departure looks like. Add travel time and family work or care schedules. A program may be legally available yet poorly fitted to the child's communication, sensory, mobility, health, or family needs. Use visits and written questions to make the comparison concrete.

Preserve functional communication

Document the child's speech, sign, gesture, movement, AAC, backup communication, partner response, and wait time. Ask how the school evaluation and receiving staff will support those forms from the first interaction. Include allergies, medication, feeding, mobility, elopement or other safety information only as relevant to safe support, with purpose-specific sharing and confirmed receipt.

A fictional Washington tracker

Theo's family has 18 transition controls. Fourteen have current evidence, giving 14 of 18, or 77.8% completeness. The district decision, bus route, AAC backup, and child-care application remain open. Because each item affects a different part of the handoff, the family reviews them individually rather than using 77.8% as a readiness verdict.

Washington family checklist

Confirm the ESIT coordinator, third birthday, transition plan, district contact, consent and referral, records, evaluation, eligibility, IEP proposal, family response, alternative programs, communication and health supports, transportation, equipment, final ESIT date, first-day date, unresolved actions, and follow-up after transition. Ask where to take a concern about the Part C process and where to take a school special education concern.

Work backward from Washington's ESIT end date

Create one calendar that distinguishes a planned action from evidence that the action happened. For the Early Support for Infants and Toddlers transition, use Washington DCYF, Early Support for Infants and Toddlers, the family's IFSP, and current written notices together. Use the third birthday as the ESIT end point, then place the IFSP transition plan, district notification or referral, evaluation consent, assessments, eligibility and IEP meetings, community applications, visits, bus plan, final ESIT service, and receiving starts on a backward calendar. The family resources coordinator should be able to identify the present owner of every transition step, even when another office makes the final decision.

Evidence fields make the calendar useful during a busy handoff. In Washington, identify whether the family resources coordinator, education office, or receiving program owns the row. Give each row an action, responsible person or office, target date, actual date, source, current status, result, and next follow-up. Save the notice, consent, email, meeting note, evaluation, or plan that proves the result. A referral or scheduled meeting shows movement; the related eligibility, enrollment, transportation, or service-start decision stays open until the family receives it. Review the list weekly as the third birthday approaches and bring the unresolved rows to each meeting.

Compare the district and community routes in daily life

Compare the local school district early childhood special education route with community preschool, child care, Head Start, family-selected therapies, and other community programs. Responsibility for district evaluation, eligibility, and IEP decision belongs to the education system. Enrollment offices decide access to community programs, and health plans or Medicaid programs apply their own coverage rules to clinical services. Put every route on its own card with the decision-maker, eligibility or enrollment step, information requested, expected decision, proposed schedule, cost or coverage, transportation, and family contact.

For each Washington option, describe the child's actual week using concrete details instead of a program label. Include location, hours, group size, communication support, health procedures, staff preparation, therapies, travel time, rest, meals, and care before or after the program. Then mark the decision as exploring, referred, consented, evaluated, offered, accepted, declined, wait-listed, or closed. This vocabulary helps a family explain progress accurately and keeps the local school district early childhood special education route visible beside every route that still lacks a decision.

Build an evaluation packet that shows participation

Assemble two layers. The record layer contains plans, evaluations, progress information, health and safety documents, and formal notices. The participation layer explains what the child enjoys, how the child communicates acceptance or distress, which routines are easy or difficult, what supports increase access, and what family priorities should shape the next setting. Prepare the IFSP, recent evaluations, family priorities, participation examples, and a functional profile for speech, sign, gesture, movement, AAC, sensory regulation, mobility, feeding, health, and safety. Track what the family authorizes ESIT to share and confirm receipt with the district or program.

During every Washington assessment, confirm the language, communication system, AAC, sensory accommodations, mobility access, visual or processing supports, breaks, and familiar-partner information needed for the child to show current skills. Note when an assessment condition differs from ordinary life and ask how the team will interpret that difference. Afterward, request the report, check factual errors, add missing context in writing, and keep the family's correction with the transition record. Families can also ask which existing evidence the team responsible for district evaluation, eligibility, and IEP decision considered and which new question required additional assessment.

Simulate the Washington handoff before age three

Walk through arrival, bus route, classroom and child-care hours, meals, play, rest, toileting, AAC and its backup, sensory or mobility supports, therapy appointments, departure, and family work schedules. Name the adult responsible at every handoff and the method for reaching that person. Confirm that staff can access the child's communication system, understand essential health and safety information, and carry out the supports expected at arrival. A visit or rehearsal should use the same entrance, approximate time, equipment, and communication method planned for the first day whenever the setting permits it.

A Washington rehearsal becomes more valuable when the family records the result. Write down the travel duration, waiting time, inaccessible step, missing material, communication breakdown, fatigue signal, and question that emerged. Give each correction an owner and retest the parts that affect safe access. Prepare a simple fallback for a late ride, absent trained staff member, unavailable AAC device, schedule change, or delayed program start. The fallback should preserve a usable way for the child to communicate, a safe care arrangement, and a named person who can authorize the next step.

Respond when a transition date or decision slips

When an expected date passes, send a concise written recap: the child and action, the source or notice that supplied the date, what the family completed, what remains pending, the impact on the transition, and the response requested. An ESIT plan concern goes to the family resources coordinator or Part C contact; evaluation and IEP concerns go to the district; transportation, child-care, and payer actions keep their separate owners. Request a dated status from the route responsible for the delay. Ask for the current procedural-safeguard, complaint, mediation, or review information from the system responsible for the concern. The appropriate route depends on whether the issue involves Part C, school special education, enrollment, coverage, privacy, or clinical care.

Route clarity also improves Washington contingency planning. Identify the care and support available while an evaluation, placement, transportation, authorization, or enrollment decision remains unresolved. Ask Early Support for Infants and Toddlers and each proposed provider to state its own end or start date in writing. Treat every system's duration and funding as a separate fact to verify. If accounts conflict, keep both records, ask the responsible offices to reconcile them, and document the family decision using the best confirmed information available at that time.

Review the first ten and thirty days

Theo's family can continue the existing tracker after the formal transition meeting. The district decision, bus route, AAC backup, and child-care application remain named rows until each has a decision and implementation evidence. During the first ten days, the family reviews whether the bus and arrival plan function at the real time of day, whether Theo's AAC backup is available across school and child care, and whether each receiving service started after ESIT ended. Observations should describe the setting, support, response, and impact so the team can distinguish an isolated adjustment from a repeated access problem.

At the Washington thirty-day review, compare the actual week with the accepted plan. Check service start dates, attendance, transportation, communication access, health and safety steps, equipment, provider coordination, family workload, and the child's participation or recovery after the day. Record any gap between the written plan and delivered support, assign it to the office that can act, and set a follow-up date. Keep strengths in the review as well: a successful routine, effective communication partner, or helpful accommodation tells the family resources coordinator and receiving team what to preserve.

Limits of this guide and immediate next steps

This guide organizes a Washington transition; it cannot determine an individual child's eligibility, placement, coverage, rights, or deadline. Those decisions depend on current law, the child's record, written notices, the responsible agency or payer, and family consent. State materials may also change. Verify local contacts and dates with the family resources coordinator, the education office, and any receiving program. Seek qualified legal, clinical, educational, or benefits advice when a disputed or high-impact question requires it.

Next, place the third birthday and final Early Support for Infants and Toddlers date on a calendar, list every receiving route, mark the decision owner for each route, and gather the packet the family is comfortable sharing. Schedule the closest unresolved consent, evaluation, visit, transportation, or meeting action. Before closing the tracker, require a written result, a usable first-day plan, and a named follow-up contact. The transition is ready for review when the family can see both completed evidence and every remaining uncertainty.