How does the Indiana First Steps transition work? First Steps develops an IFSP transition plan for every child leaving the program and coordinates with the local education agency when preschool special education may apply. The current policy describes LEA notification at least six months before age three and, with parental consent at 30 months, transmission of First Steps information for the transition conference.
Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.
Identify the SPOE and local education agency
Indiana's current First Steps policy manual assigns transition work to the System Point of Entry, or SPOE, and the service coordinator. The SPOE sends the required LEA notification and coordinates the transition packet. The local education agency controls its evaluation, eligibility, and IEP process. Indiana's program page helps families locate the current First Steps system. Put the SPOE, coordinator, district, and any community program contacts in separate rows.
Build the calendar from the third birthday
Use the third birthday to place the six-month notification point, 30-month information-sharing decision, transition plan, conference, school evaluation consent, assessments, eligibility, IEP, final First Steps services, and expected preschool start. Indiana also has special instructions for children referred at 30 months or later. Ask the SPOE to identify the applicable late-entry sequence and the earliest district contact. 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 Indiana First Steps 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 Indiana 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 Indiana 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 Indiana 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.
Know what happens after a declined referral
The Indiana manual addresses families who initially decline a Part B referral or school evaluation and later request it. The SPOE should advise the family to self-refer to the LEA or assist with that referral. A changed decision deserves a current date, receiving contact, and new timeline. Avoid treating an earlier refusal as permanent or assuming the original transition calendar remains achievable.
A fictional Indiana transition
Priya's family tracks 14 transition decisions. Eleven have written evidence, producing 11 of 14, or 78.6% completeness. The school evaluation consent, preschool visit, and mobility-equipment handoff remain open. The family assigns each to a different owner and keeps the denominator fixed until the review date.
Questions for the next meeting
Which SPOE serves our county? When was the LEA notified? What information can be sent at 30 months with consent? Who will attend the conference? Does the district need new assessments? When will eligibility and an IEP be decided? Which preschool or community routes are available? What follows if we change an earlier referral decision? How will equipment, communication, transportation, and health supports be ready?
A final family checklist
For the next Indiana 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.
Audit the Indiana SPOE-to-LEA packet
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. Indiana First Steps Early Intervention Policy Manual supplies the state framework for this Indiana transition. Connect the six-month LEA notification, the family's 30-month information-sharing decision, IFSP transition plan, conference packet, school evaluation consent, eligibility, IEP, preschool visit, and equipment transfer. For a child entering First Steps at 30 months or later, record the late-entry sequence supplied by the SPOE. 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 Indiana handoff record should name one contact for the System Point of Entry and another for the local education agency. 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 the Indiana receiving route with real equipment
Walk through preschool arrival, mobility-equipment loading and storage, transportation, AAC access, classroom movement, health supports, meals, toileting, community care, and the final First Steps visit. 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 Indiana fallback, prepare a safe equipment and communication plan for a delayed preschool placement, changed family referral decision, or unavailable transportation route. 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 Indiana 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 SPOE and service coordinator own First Steps transition documentation and LEA coordination. The LEA owns evaluation, eligibility, IEP, and school implementation. When a family changes an earlier decision, record the self-referral or assisted-referral date and ask the LEA for a fresh timeline. 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 System Point of Entry, local education agency, 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 Indiana
Priya's 11 of 14 transition decisions have written evidence; the school evaluation consent, preschool visit, and mobility-equipment handoff stay open until the family has both a decision and implementation evidence. During the first ten days, review whether the LEA received the intended records, Priya's equipment works throughout the route and classroom, and each support started under the office that approved it. 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 Indiana 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 local education agency 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 Indiana 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 System Point of Entry and local education agency; 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.
Sources
Finni resources