Arizona AzEIP to Preschool: Family Transition Guide

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

Use the current AzEIP policy and named public education agency

Arizona's AzEIP program page identifies the statewide Part C program. The AzEIP policy directory provides the controlling chapters and implementation aids. Ask the service coordinator to cite the current transition chapter, identify the public education agency, and record the date each required notice or meeting was completed. Use the policy version that is effective for the child's timeline rather than an older downloaded checklist.

Build the calendar from the third birthday

AzEIP Chapter 4 calls for an ongoing process and a formal Transition Planning Meeting by the end of the month in which the child turns two years six months, with an earlier window beginning at two years three months. Track that meeting, notification and any opt-out choice, conference, evaluation consent, assessments, eligibility, IEP, program applications, final AzEIP date, and first new service. Confirm every child-specific date in the family's notices. The federal Part C transition rule supplies the national baseline for notification, late referrals, conferences, IFSP steps, and state options. Arizona's effective sources and the family's current written notices control the working plan for this child.

Keep every decision with its actual owner

The Arizona AzEIP transition may involve Arizona Early Intervention Program, preschool special education, Head Start, child care, a health plan, private clinicians, and community programs. The Part C team owns its coordination duties. The education agency decides school eligibility and services. Each community program controls enrollment. A clinician recommends within scope, and a payer decides coverage under the plan. Use separate tracker rows so one organization's approval never stands in for another's.

Compare the child's complete weekly routine

For the Arizona handoff, place each proposed schedule beside caregiver work, siblings, medical visits, travel time, and the child's recovery needs. Ask what arrival, learning, play, meals, toileting, rest, transportation, therapy, and departure would look like. Visit the actual site when possible. Record which supports are confirmed, which evidence is missing, and who can resolve each gap. A program category does not show whether the child's day or the family's week will work.

Prepare a controlled transition packet

The Arizona packet can include the current IFSP, recent evaluations, progress information, family priorities, and the health or safety information needed by the next setting. Describe speech, sign, gesture, movement, AAC, backup communication, partner response, and wait time in plain language. Add equipment, sensory, mobility, feeding, toileting, medication, allergy, and transportation details when relevant. Index what the family agreed to share, the recipient, the date sent, and confirmation of receipt.

Protect access during evaluation and visits

During Arizona evaluations, meetings, and program visits, use the child's ordinary communication tools, interpreters, visual access, mobility supports, sensory accommodations, and health protections. Ask how the child can accept, decline, pause, request help, and show discomfort. Preserve food, water, bathroom access, movement, communication, prescribed care, and emergency help. Document an access failure as a system condition so it is not mistaken for evidence about the child's ability.

Separate notification, conference, and evaluation consent

Arizona's transition path contains several actions that can sound interchangeable. Notification tells the public education agency about a potentially eligible child under the applicable rules. The conference brings invited participants together. Evaluation consent authorizes the school evaluation. Initial-service consent addresses a later proposal. Ask what each AzEIP or school form does, keep a signed copy, and record the recipient and delivery date.

A fictional Arizona transition

Sofia's family follows 18 dated actions. Fifteen are complete, giving 15 of 18, or 83.3% completion. The preschool eligibility report, AAC partner-training date, and summer transportation route are unresolved. The family does not label the handoff ready merely because notification and the conference were timely.

Questions for the next meeting

Which AzEIP policy version applies? When was the Transition Planning Meeting held? Which public education agency was notified? Did we receive the applicable opt-out information? When is the conference? What evaluation consent and records are needed? When will eligibility and the IEP be decided? Which summer or community options need separate applications? How will communication and transportation access be tested?

A final family checklist

Before the next Arizona transition event, confirm the third birthday, sending-program contact, receiving-program contacts, IFSP steps, notification, family choices, consent, records, conference, evaluation, eligibility or enrollment, proposed plan, setting, schedule, communication access, health and safety supports, transportation, last Part C date, first receiving-service date, open issues, escalation route, and post-start check-in. Give every unresolved item one named owner and one next date. Keep counts beside percentages so unfinished work stays visible.

Give each Arizona transition event its own proof

Build proof around the state-specific handoff, not merely a list of meetings. Arizona Early Intervention Program, Chapter 4 Transition Policy supplies the current primary framework for this Arizona guide. Use the effective AzEIP policy version to identify the formal Transition Planning Meeting and every later action. Keep notification and any opt-out choice, the transition conference, evaluation consent, assessments, eligibility, IEP, initial services, summer transportation, and community applications on separate tracker rows. A dated notice, signed consent, receipt, evaluation report, eligibility record, plan, or enrollment decision should close the corresponding tracker row. A scheduled event stays in progress until its result reaches the family.

Give every cross-system record an index entry with title, author, date, purpose, family permission, sender, recipient, sent date, receipt confirmation, correction, and next action. Keep earlier versions when they explain a decision, then mark the version the receiving team currently uses. Name one contact for the AzEIP service coordinator and another for the public education agency. Ask the receiving contact to identify unreadable pages, missing attachments, stale health information, or new evaluation questions before the next decision meeting.

Stress-test the Arizona summer transition schedule

Walk through the public education program, summer calendar, transportation route, AAC partner training, heat and hydration needs, child care, clinical services, meals, rest, and family travel. Use the actual location and approximate travel time planned for the first day whenever a visit is available. Confirm who meets the child, who can use the communication system, where equipment and health information go, and how the family reaches the responsible person during the day. A placement, program, or service route becomes workable when those connections have names and evidence.

Prepare a communication-trained contact, safe transportation alternative, and care schedule for any gap between the final AzEIP date and the selected receiving program. Record the travel duration, waiting time, inaccessible step, missing material, communication breakdown, fatigue signal, and question found during rehearsal. Assign every correction to an office or person able to act, then retest the highest-impact part. The backup should preserve safe care, a reliable communication method, necessary equipment, and one person who can coordinate the next decision.

Recover a late or conflicting Arizona action

When a target date passes, send a short written recap naming the action, source for the expected date, family steps already completed, current impact, requested response, and next follow-up. AzEIP answers questions about its planning meeting, notification, conference coordination, and Part C exit. The public education agency answers evaluation, eligibility, IEP, transportation, and first-service questions. Attach the applicable policy version to a disputed date so the issue stays tied to the correct rule set. Ask the responsible system for its current procedural-safeguard, complaint, mediation, or review information when the concern remains unresolved. Keep conflicting answers in the record until the responsible offices reconcile them.

Contingency planning should identify real care and support without predicting a legal outcome. Ask the AzEIP service coordinator, public education agency, community program, clinician, and payer to state their own end or start dates and interim responsibilities. Mark the first affected date for any gap in care, communication, transportation, equipment, or family coverage. This gives the next meeting a concrete problem while preserving the separate authority of each system.

Review the first ten and thirty days in Arizona

Sofia's family begins the post-start review with 15 of 18 dated actions are complete; the preschool eligibility report, AAC partner-training date, and summer transportation route remain active until each has a decision and implementation proof. During the first ten days, check whether the written eligibility and IEP decisions match the implemented setting, Sofia's AAC partners are prepared, and the summer route operates at the actual travel time. Describe each observation with the routine, support, child's response, and practical impact. That record helps the receiving team preserve effective supports and investigate a repeated access problem.

At the Arizona day-thirty review, compare the actual week with the accepted IFSP, IEP, enrollment plan, authorization, or family schedule. Check attendance, delivered services, location, transportation, communication access, equipment, health and safety procedures, provider coordination, family workload, and the child's participation or recovery after the day. Send any gap between the written plan and delivered support to the office that can correct it and assign a response date. Record strengths beside gaps because a successful partner or routine tells the team what to preserve.

Limits and immediate next steps for Arizona families

This draft organizes transition work. It cannot determine an individual child's eligibility, placement, service, coverage, right, or deadline. Current law, the child's record, written notices, family consent, and the responsible agency, program, or payer control those decisions. State options, manuals, portals, local contacts, and program capacity can change. Verify the operative source and assigned owner with the AzEIP service coordinator and public education agency; seek qualified educational, legal, clinical, or benefits advice when a disputed or high-impact question requires it.

Next, place the third birthday and last current-service date on the family calendar. List every school, community, developmental-disability, and clinical route under consideration, then name its decision owner. Choose the closest unresolved consent, record, evaluation, meeting, site visit, transportation, or start action and request its date in writing. Keep the tracker open until the family has a confirmed receiving plan, a usable first-day test, and a post-start review date.