Oregon EI to ECSE Transition at Age Three: Family Guide

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

Use Oregon's regional EI/ECSE structure

Oregon's EI/ECSE page describes a state education agency partnership with nine local service areas. Families often continue with a regional program while moving from Part C EI into Part B preschool ECSE. Confirm the regional contractor, service coordinator, district relationship, evaluator, and person who can explain the receiving setting. Shared program branding can simplify contacts, yet the age-three eligibility and service decision still needs its own evidence.

Build the calendar from the third birthday

Track the third birthday, IFSP transition steps, notification, conference, ECSE evaluation consent, assessments, eligibility, IFSP changes, placement discussion, transportation, and first ECSE service. Add child care, preschool, Head Start, health-plan therapies, and community programs when relevant. Oregon's single EI/ECSE system can make the handoff look continuous, so clearly record which Part C rights and services end and which Part B rights and services begin. The federal Part C transition rule supplies the national baseline. The state's effective sources and the family's written notices determine the working dates for this child.

Keep each decision with its real owner

The Oregon EI to ECSE transition can touch early intervention, preschool special education, child care, Head Start, health-plan services, private clinicians, and community programs. The early intervention team coordinates its transition duties. A school team decides school eligibility and services. Each community program decides its enrollment. A clinician makes recommendations within scope. A payer decides coverage under the applicable plan. Keep these decisions in separate tracker rows so one approval is never used as evidence for another.

Compare the child's actual day

Within the Oregon handoff, ask what arrival, learning, play, meals, toileting, rest, transportation, therapy, and departure would look like in each proposed setting. Put the weekly schedule beside caregiver work, siblings, medical appointments, travel, and the child's need for recovery time. Visit when possible. Record the supports the program can provide, the evidence still needed, and who can resolve a gap. A program name says little about the child's daily access or the family's workable routine.

Prepare one controlled information packet

For the Oregon family packet, gather the current IFSP, recent evaluations, progress information, family priorities, health and safety information needed for the next setting, and a plain-language description of communication. Include speech, sign, gesture, movement, AAC, backup communication, partner response, and wait time. Add equipment, sensory, mobility, feeding, toileting, medication, allergy, and transportation information when relevant. Index what the family agreed to share, the recipient, the date sent, and confirmation of receipt.

Protect participation during evaluation and transition

During Oregon evaluations and visits, use the communication tools, interpreters, visual access, mobility supports, sensory accommodations, and ordinary health protections the child needs. Ask how the child can accept, decline, pause, request help, and show discomfort. Preserve food, water, bathroom access, mobility, communication, prescribed care, and emergency help throughout the process. Record any access failure as a system issue rather than a child-skill result.

Expect an IFSP rather than an automatic IEP

Oregon's procedural safeguards booklet explains the difference between EI and ECSE and states that both use an IFSP. Families should ask which sections change at age three, how educational need and placement are documented, and which safeguards apply to the current dispute. When the child later reaches school age, Oregon describes a separate move from an ECSE IFSP to an IEP.

A fictional Oregon transition

Jun's family reviews 12 elements in the proposed ECSE IFSP. Nine name the service, setting, frequency, responsible role, start date, and access support, for 9 of 12, or 75% element completeness. Transportation, AAC backup, and the child-care coordination step remain incomplete. The family asks for those fields before signing its readiness tracker, while reviewing the formal proposal under Oregon's procedures.

Questions for the next meeting

Which regional EI/ECSE program owns our transition? What changes from EI to ECSE? Which evaluation establishes ECSE eligibility? How will the IFSP document the receiving services and setting? What placement options were considered? Which transportation and child-care coordination applies? How will AAC, interpreters, mobility, sensory, feeding, and health supports work? Which EI or ECSE safeguard fits a missed timeline, evaluation concern, or disputed proposal?

A final family checklist

For the next Oregon transition event, confirm the third birthday, sending-program contact, receiving-program contact, transition steps, notification, family choices, consent, records, evaluation, eligibility or enrollment, proposed plan, setting, schedule, communication access, health and safety supports, transportation, final current-service date, first receiving-service date, open issues, escalation route, and post-start check-in. Give every unresolved item an owner and a date. Keep counts beside percentages so unfinished work remains visible.

Document the Oregon change inside a continuing IFSP

Treat a record as handed off only when the family can identify what moved, why it moved, who sent it, who received it, and what action follows. Oregon Department of Education, Early Intervention and Early Childhood Special Education supplies the state framework for this Oregon transition. Shared EI/ECSE branding can hide a meaningful Part C-to-Part B change. Mark the ECSE evaluation and eligibility basis, revised IFSP services, setting, frequency, responsible role, start date, placement discussion, transportation, and the safeguards that apply after age three. A receipt, dated email, signed form, evaluation report, or written plan gives the tracker stronger evidence than a general statement that the teams are coordinating.

Version control matters when several offices use the same packet. Put the child's name, document title, author, date, family permission, recipient, sent date, receipt date, and missing follow-up in the index. Keep older versions when they explain a decision, then mark the version currently in use. The Oregon handoff record should name one contact for the regional EI program and another for the regional ECSE program. Ask the receiving contact to identify unreadable pages, missing attachments, stale health information, or additional evaluation questions while there is still time to respond.

Test what changes when Oregon ECSE begins

Walk through the regional ECSE setting, transportation, AAC backup, child-care coordination, interpreters, mobility, sensory and feeding supports, service frequency, family routines, and the first date each revised IFSP element is delivered. Use the location and approximate time planned for the real first day whenever a visit is available. Confirm who meets the child, who can use the child's communication system, where equipment goes, how health or safety information reaches the responsible staff, and how the family receives a same-day update. A program offer becomes usable only after these connections have owners.

For the Oregon fallback, prepare a regional-program contact for every incomplete IFSP field and a child-care or transportation bridge while the receiving arrangement is corrected. Record the travel duration, waiting time, inaccessible step, missing supply, communication breakdown, fatigue signal, and unresolved question from any rehearsal. Assign every correction to the office able to act and test the high-impact part again. The backup should preserve safe care, a reliable communication method, necessary equipment, and one person authorized to coordinate the next move.

Respond to a late or conflicting Oregon decision

When a target date passes, write a short factual recap with the pending action, source for the expected date, family actions already completed, current impact, requested response, and next follow-up. The regional program may remain the family's visible contact, yet the record should still identify whether the question concerns EI transition, ECSE eligibility, placement, the revised IFSP, or an outside child-care route. Request the safeguard notice that matches that stage. Request the current procedural-safeguard, complaint, mediation, or review information from the system responsible for the exact concern. Preserve call notes and conflicting answers until the responsible offices reconcile them in writing.

Keep contingency planning separate from a legal conclusion about continued services. Ask the regional EI program, regional ECSE program, community program, clinician, and payer to state their own end date, start date, and interim responsibility. Map the care, communication, transportation, and family schedule that can operate while a decision remains open. If a gap remains, show its first affected date and owner. That makes the problem concrete for the next meeting without implying that one system automatically extends or funds another.

Review the first ten and thirty days in Oregon

Jun's 9 of 12 proposed ECSE IFSP elements have complete implementation fields; the transportation, AAC backup, and child-care coordination step stay open until the family has both a decision and implementation evidence. During the first ten days, review whether all twelve proposed ECSE IFSP elements have usable implementation fields, Jun's AAC backup is present, and regional continuity results in actual services rather than an assumed handoff. Write observations with the routine, support, child's response, and practical impact. This format helps the receiving team preserve successful supports and investigate repeated access problems.

At the Oregon day-thirty review, compare the actual week with the accepted IFSP, IEP, enrollment plan, authorization, or family schedule. Check attendance, delivered services, setting, transportation, communication access, equipment, health and safety procedures, provider coordination, family workload, and the child's participation or recovery after the day. Record any difference between the written plan and what happened, give it to the regional ECSE program or other office that can correct it, and set a response date. A strength, such as an effective partner or routine, belongs in the review beside every gap.

Limits and next steps for this Oregon guide

This draft is an organizer. It cannot decide an individual child's eligibility, placement, services, coverage, rights, or deadline. Current law, the child's record, responsible agency or payer, written notices, and family consent control those decisions. State options and local contacts can change, especially a year-specific extension, an age-based route, or a program affected by funding. Verify the current rule and contact with the regional EI program and regional ECSE program; seek qualified educational, legal, clinical, or benefits advice for disputed or high-impact questions.

Next, place the third birthday and final current-service date on the family calendar. Identify every school, community, and clinical route under consideration, then name its decision owner. Choose the closest unresolved consent, evaluation, meeting, visit, transportation, record, or start action and request its date in writing. Before closing the transition tracker, require a confirmed receiving plan, a workable first-day test, and a post-start review date. Keep each remaining uncertainty visible until its own evidence arrives.